Since the latest Spitfire update, I’ve been noticing inexplicable behavior from the plane.
See video. I am NOT making adjustments on the throttle, stick, or anything else. The only way to temporarily solve this is to restart engines, but it happens again. This is happening at full throttle. What am I doing wrong?
It looks like you have overheated the engine which is causing strange behaviour. Don’t use a high amount of boost & RPM for extended amounts of time, and keep an eye on the temperatures. You can have a look through the user Manual for Max Operating Limits (page 22 or 23 I think).
I think the custom coding some Devs have added for engine overheating damage isn’t tied into the default sim engine stress realism options. Not sure why but could be an SDK limitation
I’m curious Alex, was this behavior recently introduced? I only ask because I’ve been flying the plane for weeks now pretty much at full throttle for decent distances. Just curious! Thanks!
Engine failures revised, overheat failures improved. The engine must now be flown inside real-world operating limits or it will very likely fail
So it’s been in for about a month now. If you got it on the Marketplace it probably took a few weeks longer to get updated which may explain why you’re only recently seeing it.
This is something we want to fix in a later update. We are currently investigating to see if it is possible to access the sim’s failure settings or not. If not, we may look into implementing a custom toggle
I’ve tried to abide by this limit, but find in order to get the rpm even down to 2700 I have to cut the throttle to almost idle, and I’m doing around 150 knots. That doesn’t seem right. Can’t keep pace with a DC-6 at that speed.
There’s a third control: Mixture, Throttle AND Prop RPM reduce RPM not engine power.
In straight and level flight keep the engine power at 0% boost and prop RPM around 2500 and you’ll trundle along at 250MPH without overheating the Merlin
I am not familiar with the „aircraft building“ aspect of the SDK myself (I am coming from the „SimConnect“ side ;)), but one would think that accessing the „game options“ like crash/stress/engine failure would be basic functionality.
I hope you are reporting those deficiencies of the SDK to Asobo, to improve their SDK for you aircraft developers.
Oh, and I haven‘t checked for a while, but if you could support the „CANOPY OPEN“ simulation variable, that would be great
In case that answer was directed at my question: well, that wasn’t my question I know that the cockpit opens within the flight simulator (by the method you just said)
I was asking for SimConnect support, namely the existing “CANOPY OPEN” simulation variable (which - last time I checked - did neither report the actual canopy state, nor did it affect it when trying to set it).
By the way, is it possible that you click on “Reply to Topic” instead of “Reply to Post”? Because I didn’t get a “notification” twice now when you replied.
So: if you want to reply to a specific post of someone else, click on “Reply to Post” instead. Like this the author gets a) notified and b) can be sure that the reply was really in reference to his/her post.
Only if you want to reply to the “entire topic” (in a “general way”, without referring to some specific other post) click on “Reply to Topic”.
That helps figuring out who is replying to whom
UPDATE: Whoops! Never mind! I actually got a notification (now) of your second reply (but not for the first, or so it seems). Sorry about that…