A definition of insanity

jmig

SOH-CM-2025
The picture says a thousand words. Why do I continue to torture myself with this absolute, total, unmitigated POS.

This was a reload after spending 30 minutes setting up switches and starting the engines, only to have the jet go careening through a B-37 and off the apron onto the grass; even though the throttles were back to the stops.
 

Attachments

  • Screenshot 2025-04-03 082058.png
    Screenshot 2025-04-03 082058.png
    6.6 MB · Views: 54
Maybe the control binding for throttles need reversing?

I seem to remember having to do that once, can't remember what aircraft it was though! doesn't help the whole control binding set up within MSFS2024 is a wee bit of a pain when I either forget to save certain control bindings to all aircraft, or when I did remember to save, some glitch stops it saving! :banghead:

Keith.
 
You guys ever think of using an external app to control your equipment like Spad.Next or FSUIPC? I've started migrating over to Spad.next myself and already like the fact that after I set up an aircraft in a profile, the profile automictically changes to the correct profile when you switch aircraft. FSUIPC does the same and I've used that in the past but Spad.next just seems to offer more at the moment for me. Plus, the profiles can be carried over from MSFS to 2024 so no need to reprogram everything. Just a thought.

However, that won't help you to remember to check and make sure that your throttle isn't set to wide open when you load up (how do I know this? lol)

LouP
 
I do agree with Lou, I switched over to Spad.neXt for control mapping and have been pretty pleased with the results.

For the MSFS and a definition of insanity......I have a skewed take. I view DCS as the cold start sim, and have checklists for every aircraft (here). MSFS is the 'kick the tires' simulator for a huge variety of aircraft and world navigation / exploration. It means that 'cold start' is a status for an aircraft to achieve in MSFS, where module-specific control mapping is earned after several flights. I have my own set of requirements for what should be achieved after those proving flights....but it's not particularly relevant. Everyone has their own list of what makes a great add-on.
 
So, after I posted that, I took a flight in 2020 in a L39 from the Reno package, and it was just broken. Analog ASI was kaput, it read 60 knots while a glass gauge read 330 knots and the gns 430 in the cockpit was completely unclickable. I thought it may have been a VR thing so I went into 2D and nope, broken. Got me thinking if things are still broken in 2020, what chance is there of getting 2024 fixed? I found myself looking at alternatives the other day because of another incident, including re-installing P3D v4.5 as I still have a ton of ORBX stuff just begging to be re-installed into P3D.

I figure that right about when 2024 is just about repaired, they will be shoving 2026 down our throats anyway. Should have fixed 2020 before moving on but I'm just grumpy right now!

LouP
 
Today I tried three times to do a quick flight. All three attempts ended with the sim freezing, requiring me to shut it down via Task Manager. Finally had enough for one day. Microsoft truly bombed bad this time. NC
 
You guys ever think of using an external app to control your equipment like Spad.Next or FSUIPC? I've started migrating over to Spad.next myself and already like the fact that after I set up an aircraft in a profile, the profile automictically changes to the correct profile when you switch aircraft. FSUIPC does the same and I've used that in the past but Spad.next just seems to offer more at the moment for me. Plus, the profiles can be carried over from MSFS to 2024 so no need to reprogram everything. Just a thought.

However, that won't help you to remember to check and make sure that your throttle isn't set to wide open when you load up (how do I know this? lol)

LouP
I use Axis&Ohs, along with FSUIPC. I own Spad.Next but find it to hard to use. Yes, I had the throttles set correctly. Tomorrow I am going back to flying DCS.
 
I'm guessing you already checked, but it could be a key binding on another controller (or keyboard) is set to full throttle. I don't like the MSFS2024 keyboard/controller setup at all, but you get used to using it after some practice. Every now and then, I discover a conflicting binding.
 
Back
Top