worldsfair Posted April 14, 2023 Share Posted April 14, 2023 I seem to remember some years back that there was a way to remove the "overspeed" notification in FSX. Can anyone tell me how this was done so I can make the change? Link to comment Share on other sites More sharing options...
mrzippy Posted April 14, 2023 Share Posted April 14, 2023 Try this: close fsx open file fsx.cfg find line: hide infotext=0 change to: hide infotext=1 close and save the file. Keep in mind that if this eliminates the "Overspeed" warning, you will still get the clicking sound and you are going too fast! Slow down or maybe increase the aircraft's Max_speed in the aircraft.cfg. 1 Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
snave Posted April 14, 2023 Share Posted April 14, 2023 You are overspeeding. Try going slower and change the FSX to Display IAS (indicted air speed)-https://steamcommunity.com/sharedfiles/filedetails/?id=358912186 Link to comment Share on other sites More sharing options...
PhrogPhlyer Posted April 14, 2023 Share Posted April 14, 2023 The whole reason behind the overspeed warning is to help you be responsible and aware of aircraft limitations. If you want to go faster, get a different aircraft. "This is you Captain speaking, If you feel a bit of shaking or hear any strange noises don't be alarmed, I'm just ignoring the aircraft's structural speed limitations to get you to your destination sooner." 1 Always Aviate, then Navigate, then Communicate. And never be low on Fuel, Altitude, Airspeed, or Ideas. Laptop, Intel Core i7 CPU 1.80GHz 2.30 GHz, 8GB RAM, 64-bit, NVIDIA GeoForce MX 130, Extra large coffee-black. Link to comment Share on other sites More sharing options...
Rupert Posted April 14, 2023 Share Posted April 14, 2023 2 hours ago, PhrogPhlyer said: "This is you Captain speaking, If you feel a bit of shaking or hear any strange noises don't be alarmed, I'm just ignoring the aircraft's structural speed limitations to get you to your destination sooner." LMAO!!! You could have added the disclaimer,"If I get you to your destination." Having said that. I always have tried to sim. in the same manner as I RW flew. Flying in a sim when I couldn't physically fly RW is part of how I, and from what I've heard, many others beat that part of my/their past that added to our PTSD issues. One poster asked why I used things like a checklist when I was only simming? IMO if you're not doing things correct to procedure in the sim, you're just playing a video game. (Nothing wrong with playing a video game of course, if that's what you choose to do.) Michael 1 Being an old chopper guy I usually fly low and slow. Link to comment Share on other sites More sharing options...
mrzippy Posted April 14, 2023 Share Posted April 14, 2023 The only notification that bothered me was "Don't sink"! "Sink rate" was OK but whenever I was landing, even at the recommended rate using the Glide Slope, "Don't sink" blared over the loud speaker. IMHO ya gotta sink to land! Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
PhrogPhlyer Posted April 14, 2023 Share Posted April 14, 2023 1 hour ago, mrzippy said: IMHO ya gotta sink to land! Unless you're a seaplane. 1 Always Aviate, then Navigate, then Communicate. And never be low on Fuel, Altitude, Airspeed, or Ideas. Laptop, Intel Core i7 CPU 1.80GHz 2.30 GHz, 8GB RAM, 64-bit, NVIDIA GeoForce MX 130, Extra large coffee-black. Link to comment Share on other sites More sharing options...
PhrogPhlyer Posted April 14, 2023 Share Posted April 14, 2023 1 hour ago, Rupert said: I always have tried to sim. in the same manner as I RW flew. As do many of us. Always Aviate, then Navigate, then Communicate. And never be low on Fuel, Altitude, Airspeed, or Ideas. Laptop, Intel Core i7 CPU 1.80GHz 2.30 GHz, 8GB RAM, 64-bit, NVIDIA GeoForce MX 130, Extra large coffee-black. Link to comment Share on other sites More sharing options...
lnuss Posted April 14, 2023 Share Posted April 14, 2023 1 hour ago, PhrogPhlyer said: Unless you're a seaplane. Then you have to sink to water... 1 Larry N. As Skylab would say: Remember: Aviation is NOT an exact Science! Link to comment Share on other sites More sharing options...
mrzippy Posted April 14, 2023 Share Posted April 14, 2023 Hey! Maybe I can cruise around in the "Flying Sub" from the TV series "Voyage to the Bottom of the Picture Tube"! Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
PhrogPhlyer Posted April 14, 2023 Share Posted April 14, 2023 The 2004 fans are in luck with the flying sub. https://www.allflightmods.com/flight-simulator-2004/fs20042002-flyingsub_02-v-2-t-v-series-voyage-bottom-sea-2/ Always Aviate, then Navigate, then Communicate. And never be low on Fuel, Altitude, Airspeed, or Ideas. Laptop, Intel Core i7 CPU 1.80GHz 2.30 GHz, 8GB RAM, 64-bit, NVIDIA GeoForce MX 130, Extra large coffee-black. Link to comment Share on other sites More sharing options...
lnuss Posted April 14, 2023 Share Posted April 14, 2023 Phrog, my browsers won't let me connect to that link, apparently an expired certificate. Larry N. As Skylab would say: Remember: Aviation is NOT an exact Science! Link to comment Share on other sites More sharing options...
PhrogPhlyer Posted April 15, 2023 Share Posted April 15, 2023 2 hours ago, lnuss said: apparently an expired certificate. Seems to be. I took the chance since Norton 360 said it was a low risk. I should have said so in the initial comment. And another thread that went astray. Always Aviate, then Navigate, then Communicate. And never be low on Fuel, Altitude, Airspeed, or Ideas. Laptop, Intel Core i7 CPU 1.80GHz 2.30 GHz, 8GB RAM, 64-bit, NVIDIA GeoForce MX 130, Extra large coffee-black. Link to comment Share on other sites More sharing options...
worldsfair Posted April 15, 2023 Author Share Posted April 15, 2023 21 hours ago, mrzippy said: Try this: close fsx open file fsx.cfg find line: hide infotext=0 change to: hide infotext=1 close and save the file. Keep in mind that if this eliminates the "Overspeed" warning, you will still get the clicking sound and you are going too fast! Slow down or maybe increase the aircraft's Max_speed in the aircraft.cfg. There is no hide infotext=0 in the cfg. file. Link to comment Share on other sites More sharing options...
lnuss Posted April 15, 2023 Share Posted April 15, 2023 2 hours ago, worldsfair said: There is no hide infotext=0 in the cfg. file. So insert hide infotext=1 in the DISPLAY section of the .cfg 1 Larry N. As Skylab would say: Remember: Aviation is NOT an exact Science! Link to comment Share on other sites More sharing options...
f16jockey_2 Posted April 15, 2023 Share Posted April 15, 2023 3 hours ago, worldsfair said: There is no hide infotext=0 in the cfg. file. Just for the record: the correct syntax is HideInfoText=1 or HideInfoText=0 (default). BTW Some RW airplane crashes are confirmed to be caused by disabling warning systems (more spefically by popping circuit breakers). Wim 1 Link to comment Share on other sites More sharing options...
PhrogPhlyer Posted April 15, 2023 Share Posted April 15, 2023 14 minutes ago, f16jockey_2 said: BTW Some RW airplane crashes are confirmed to be caused by disabling warning systems (more spefically by popping circuit breakers). Here is the link to the NTSB Safety Alert page. Much can be learned here to make you a more professional and safe pilot, RW or sim. https://www.ntsb.gov/Advocacy/safety-alerts/Pages/default.aspx Always Aviate, then Navigate, then Communicate. And never be low on Fuel, Altitude, Airspeed, or Ideas. Laptop, Intel Core i7 CPU 1.80GHz 2.30 GHz, 8GB RAM, 64-bit, NVIDIA GeoForce MX 130, Extra large coffee-black. Link to comment Share on other sites More sharing options...
lnuss Posted April 15, 2023 Share Posted April 15, 2023 28 minutes ago, f16jockey_2 said: the correct syntax is HideInfoText=1 or HideInfoText=0 (default). You're right- thanks for the correction. Larry N. As Skylab would say: Remember: Aviation is NOT an exact Science! Link to comment Share on other sites More sharing options...
worldsfair Posted April 15, 2023 Author Share Posted April 15, 2023 5 hours ago, f16jockey_2 said: Just for the record: the correct syntax is HideInfoText=1 or HideInfoText=0 (default). BTW Some RW airplane crashes are confirmed to be caused by disabling warning systems (more spefically by popping circuit breakers). Wim Once again in the FSX cfg file there is no HideInfoText=1 or HideInfoText=0 (default). Link to comment Share on other sites More sharing options...
lnuss Posted April 15, 2023 Share Posted April 15, 2023 Once again: So insert HideinfoText=1 in the DISPLAY section of the .cfg Larry N. As Skylab would say: Remember: Aviation is NOT an exact Science! Link to comment Share on other sites More sharing options...
mrzippy Posted April 15, 2023 Share Posted April 15, 2023 1 hour ago, lnuss said: Once again: So insert HideinfoText=1 in the DISPLAY section of the .cfg COPY HideinfoText=1 and then PASTE it into your FSX,.cfg under [Display]. Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now