Why is my Spitfire doing this?

Hello all,

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?

edit – Wrong section, sorry! Fixing.

1 Like

Hi @mblpenguin ,

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 usually fly with ~6 boost and ~2-2500 RPM.

Hope this helps.

Cheers,
Alex

2 Likes

ha, had that too, its an overheat issue. too long too much throttle and you get that.

2 Likes

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

Interesting! This never happened to be before. I’ll mind my throttle from now on.

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! :smiley: Thanks!

May 24th notes for patch 1.0.2 under ‘systems’:

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.

Ah-ha! I grabbed it on the marketplace. That explains it. Thank you very much. Alas, my days of ignoring the throttle are at an end. :smiley:

1 Like

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 :slight_smile:

2 Likes

8 boost, 2650 rpm, should be fine

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.

1 Like

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

4 Likes

Thanks so much Glenith. Appreciate it.

2 Likes

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 :wink:

Also refer to:

1 Like

Canopy opens with field click above. No button mapping though.

Hi Donny,

I’ve written a small program that causes random failures. I can confirm there are twelve available failure settings which all seem to work just fine.

Hope that helps.
Pete.
Please see here for details: FS Forum Post

In case that answer was directed at my question: well, that wasn’t my question :wink: I know that the cockpit opens within the flight simulator (by the method you just said) :wink:

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).

Apologies for stating the obvious, rather than properly addressing your question - for which I clearly didn’t have the answer :upside_down_face:

1 Like

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 :wink:

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…

No problem :smiley: