Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
no
Brief description of the issue:
opening storm window crash overstress damage in all 3rd party airplanes
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
start in flight with kodiak turbo arrow c414 milvix c310r etc…all the airplanes that have storm window…open the storm window …afters seconds o r minutes the game crash by overstress…not ctd…crash by overstress
PC specs and/or peripheral set up if relevant:
i9 9900k 3080ti 32gb ram hotas whartog
Build Version # when you first started experiencing this issue:
from day one launch
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
yes
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
True, and that’s what I’ve done since day 1. Not a fan of the black screen.
Does anyone know the technical reason for why this happens, as in how is it measured, and is there a variable exposed in SimConnect that contains this “value”?
They have dropped this post inthe 3rd party section but i originally put this in the bug section…is not a 3rd party bug…is a sim code bug…all the 3rd party aircaraft manuals report that is a sim code and say thet we should select the options in the menu to disactivate the damage for overstress…but this is a bug
Sorry, it does not work that way: You are talking about a computer and a computer program (MSFS). It is programmed this way. People calling it an “bug” because in real life something like that would not happen. But still, it is programmed that way and changing that asks for reprogramming. Maybe Asobo does not want to do that. Ofcourse, you can send Asobo a ticket and ask them to reprogram it, but it will take time and they still might not do it. So, it is more easy to disable the aircraft stress damage setting.
Maybe Asobo does not want to do that. Of course, you can send Asobo a ticket and ask them to reprogram it, but it will take time and they still might not do it. So, it is more easy to switch to X_plane.
More Easy – MAYBE, the solution to the problem – NO …
There are a couple of issues here that have resulted in this situation. Many 3rd party aircraft are using the legacy FSX “exit/canopy” code to drive door and window state animations (like the OP’s storm window), and currently in the sim any “exit” being open at speed is set to create an immediate overstress crash. This code was never really developed as none of the default aircraft included door and canopy animations, but it is still accessible. I don’t recall this issue being initially present in the sim (it wasn’t in FSX) but I think its handling might have changed during one of the sim updates.
There are some very good reasons to use that legacy exit code: It already has inputs set up, drives the animations for you, and has significant time saving advantages for audio volume and spatialization control as it automatically triggers and manages blending between exterior and interior audio.
The only ways for developers to entirely circumvent the issue currently are to either roll their own custom door and window code, including audio, which is doable but requires quite a bit of extra work, or to simply keep the doors and windows permanently closed.
Personally I would love to see some extra flags added to the aircraft config files to handle various door types and their airframe stress relationships at some point. There are many kinds of windows, doors and canopies that are designed to be opened in flight, some that can be forced opened but will immediately close again due to ram air pressure, and some that cannot be opened at all (pressurized etc).
As others have said, if the plane in question uses the exit code then only workaround right now is disabling stress damage.
Interestingly, I was able to open and close the canopy on the DHC-1 Chipmunk in flight with no problems the other day… I wonder if I was accidentally in dev mode or something.
Still works when definitely not in dev mode and overstress is enabled. So this will depend on the plane.
I’m using SU10 and not in dev mode and there are plenty of 3rd party aircraft where I can open the storm window without triggering a failure (there doesn’t seem to be any difference with that from SU9 but obviously I can’t check that).
I’ve tried the JF Turbo Arrow III, Kodiak, Milviz C310R, FSW C414 and of those only the Kodiak triggered a failure opening the storm window for me. Certainly it’s a problem I’ve seen with all the Carenado aircraft but it doesn’t seem to be universal.
Quite sure I can fly around in the Spitfire ( IX ) with the hood back. I have turned overstress off because the turbulence sometimes spikes enough to overstress even a combat aircraft, and I’m not putting up with that.
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
