Hello, I’ve moved your topic into #third-party-addon-discussion:aircraft for better placement as this seems to reference 3rd Party Aircraft. The #bugs-and-issues categories are more for reporting on stock sim with some exceptions.
I think this is a issue with all openable window airplanes once airborne.
This is from the SWS Kodiak manual:
We recommend the following settings:
Crashes due to aircraft stress DISABLED: when Flight Simulator detects an exit opening in mid-air, it will consider the aircraft overstressed. This will preclude you from using the storm window and skydive door.
I think this can be considered a sim bug. Just because stock aircraft do not have the feature that allows this bug to be seen, it doesn’t change the fact that it’s still a core MSFS issue that’s causing it.
Whilst that is certainly understandable, we’ve been putting 3rd Party related topics in the relevant subcategory, even if MSFS may be at fault. In this case, 3rd Party vendors are responsible for notifying MS/Asobo of any issues. That’s the guidance that has been given to us. You can also bring any issues to the attention of the vendor directly.
You can disable aircraft stress damage in game options for the time being if you want to use that feature. Engine stress damage can remain enabled. I think this should be tweaked at least. In any case you may expect a cabin pressurization drop (when applicable) but definitely not an instant fatal damage.
I suppose it’s not a bug so much as a constraint. You can open the vents on the ground without causing a stress event, so there is code to detect the vent opening in flight. I wonder if you can take off with the vent open and close it after you are in flight, much like you would with some canopies. If this is the case, then opening a window or vent causes the stress event because the SDK incorrectly treats windows and vents as exits. I get that this way you simplify things; doors open on the ground very differently from how they open in flight. I guess the correct answer is, correct as is.
So the onus is on the 3rd party developer to add a placard saying do not open in flight, or custom code to handle opening windows in flight. If that is the case, then the bug is on Carenado.
There are some developers who I think have written custom code to handle window/door opening in flight not using the window/door opening feature built into the sim, but that comes with its own limitations I think.
I don’t think it’s fair to blame Carenado for using a feature of the sim which is bugged and has been bugged since the sim launched which only MS/Asobo can fix but which the latter never bothers to address. Placards in the cockpit would be unsightly, and unrealistic in their own way. Presumably Carenado (and the other developers who use this functionality) don’t want to curtail the features of their products because they trust that the problem will be fixed eventually… except MS/Asobo seems to very cleverly evade responsibility by omitting this feature on their bare-bones default aircraft and then implying third parties are at fault every times it comes up… note the instructions the moderators say they’ve received above.
This is the fourth or fifth time at least I’ve seen this same discussion happen on these forums, going back months and months. “Hey, the window opening is messed up.” “Moved to third party discussion.” “But it happens on every plane with opening windows, it’s obviously a sim issue.” “Does it happen on any Asobo planes?” “None of Asobo’s planes have opening windows implemented.” “Ah, well.”
The bug isn’t on the third party developers. It’s the Sim that tells it to register a crash if a window is opened, and we agree a window cracked open at 2000ft shouldn’t destroy a plane..
B-24 crews used to fly with the bomb bay doors slightly open because the plane leaked fuel constantly and they needed a way to exhaust the fumes.
I can’t wait until someone makes a B-24 for MSFS, a user tries to do this and finds their flight ends instantly because this bug still isn’t corrected, and then we can have this whole discussion over again.
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:
