This has happened to me three times today flying the third party Kodiak 100. I cannot reproduce it at will but each time I recall it happened when I clicked outside of the cockpit window on a Chrome shortcut on the Microsoft taskbar to open a new browser.
After clicking on the shortcut I first hear a wind noise as if one of the doors or windows in the plane was opened. Then the report pictured above is produced.
Something about clicking outside of the msfs window seems to be causing a door or window to open which overstresses the plane. Otherwise, all of the engine parameters of the plane are within normal tolerances. The following is a pic of a simulated FIP showing engine values.
I know it\s possible that this is due to a bug in the third-party plane, and I’ll report it to the developers of the plane, but since it seems to occur when clicking outside of the window, I thought it might be a bug in msfs.
This happened a third time for me today after giving this report and creating a ticket with Simworks Studio. After a little more testing, I can now reproduce the behavior on demand. Here are the steps:
Set up two monitors side by side, each with the same resolution. The taskbar should be on the left-hand monitor, and msfs should show in full-screen mode on the right-hand screen.
With msfs running, start a flight with Kodiak 100.
Within the cockpit, find a view that shows a sliver of the storm window on the captain’s door. On my 1200x900 screen, it looks like this:
Make sure that msfs is the selected application if necessary by clicking on the right-hand screen where msfs is running.
Move the mouse to the left-hand screen and click an icon on the taskbar along the bottom of the screen.
The storm window opens as if it received the click. Apparently, msfs “thinks” the cursor is still on the left edge of the right-hand window, so the storm window opens when it is clicked. In flight, this can overstress the aircraft apparently and cause a crash.
I doubt this behavior is the fault of the third-party plane, and I suspect something similar could happen with any aircraft if buttons or controls just happened to be on the edge of a screen that was next to another screen.
Thanks for your reply. I agree with everything you say. This seems to be an issue with how msfs handles the mouse inputs. Here is how my two display screens are set up now:
The left screen is 1200x900. I thought the right was too, but I just saw that it’s 1920 x 1080.
When the little window is right in the lower corner of the right-hand screen, clicking on any icon in the taskbar causes the window to open.
Since this was happening several times in one day, I figured there had to be a reason for it. It just took a little testing to find it.
Surprisingly, the click has to be on an icon in order to open the window. Clicking within the system tray or on a blank spot on the taskbar does not cause the behavior.
Thanks for responding. Once I realized what was happening, I knew this would be a good work-around. It makes for a bit less realism, but it’s not very realistic to have windows opened when you click on a second screen, either. So I’ll make this change, at least for now.
Is it worth checking for this behaviour with stock (Asobo) aircraft?
If this seems to be an actual sim (active window focus/mouse input) issue it would seem the only way to have this recognised by Asobo and not buried and forgotten as a “third party” issue will be to verify the fault with one of their own aircraft.
Your specific 2nd screen click problematic put aside - for me it adds to realism to be able to open the side windows or skydiver door etc. in the Kodiak or the MilViz Porter without crashing, knowing that I also decrease realism by disabling stress damage .
And not everything is black and white, even if you read the manual. Playing in onAir’s Thunder World for example forces you to have damage on. So this still stays annoying.
onAir is a third party program, that simulates an economy, akin to FSEconomy to give you something to do. It is quite comprehensive and adds stuff like fuel, fees, maintenance and parking costs. Basically a game around the game. And that is tiered in different difficulties, Thunder being the “hardest”. And this tracks whether or not your damage is enabled.
The whole multi monitor situation is in a sorry state. So I think threads like these are very important. This also expands to using touch screens. When you dock out a GTN750 or a G3000 Screen onto a hardware touchscreen and actually do touch it, your controls get locked up in the main sim (i.e.: if you are in a left turn with yoke you cannot return to center) until you manually give focus back to the sim. And this can also open your storm window then and crash you.
All I am saying is that stuff like RTFM always sounds kind of cool, but maybe there are use cases that are not on your radar that make people appreciate threads like these.
Thanks for the explanation what onAir is, did not know this before.
Btw, losing focus of the main window when interacting with another window is default Windows behaviour. Not ideal, in your use case, I know.
Better would be to send the rendered image to some kind of Avionics Server which then sends it to the tablet. And also reads the Touch input and sends this to the simulator.
But, currently it is as it is.
Yeah and the way older P3D manages that flawlessly, as does XP11. It is just an oversight by Asobo. And the sad part is, you do not even have to click. Just undocking say the vfr map and hovering the mouse above it is enough to lock the controls. But that is a different topic…
