Flying the Black Square King Air 350. I have a dual monitor setup, but the second monitor is just for web browser, and stuff like LIttle NavMap when I'm flying, etc. The problem I've run into is the left window latch in the KA350 is (not so) perfectly positioned that when I mouse over to the second monitor, any time I click on the toolbar to pop open a program/window it also pop's open the KA's window!! Which as you can imagine when flying is no good! 

Is there someway through a config file on the plane that I can disable the ability to open the window? It's driving me mad when flying this plane to not be able to use the toolbar to open programs. 

I guess I can change the default view, but I'd really like to keep it as it is if possible. 

Edited September 13, 20241 yr by bahnzo

I can't help specifically I'm afraid as I don't have this particular aircraft but I had similar issue with the PMDG 777 where clicking on a second monitor above my main monitor caused the sun visor to deploy. I was able to fix this by editing the relevant xml file to disable the sun visor. The file you need to look for will likely be called something like "[aircraft_name]_interior.xml" or similar and will typically be in the aircraft's model folder (with some 3rd party aircraft it may be in a folder called "behaviours" or something similar).

Once you have located the file you can open it with a text editor and look for the section that relates to opening the window, this will typically contain code that writes either 1 or 0 to a variable, changing it so that it only ever writes 0 will more than likely disable it.

Usual caveats apply of any modifications being at your own risk and making a back up of the original file before editing it!

Thanks, I'll give that look. I'm not adverse to editing and modding files so I'm not too worried about that. I think it's just a matter of trying to find the correct file to edit. 

 

Fixed! 

@PJD the point to model folder was what I needed. Thanks again. 

 

For anyone that might run across this later. The trick was to find the xml which controls this "switch" and simply comment it out. A HUGE tip I've learned, is there's an easy way to find the name of switches in your cockpit. Enable developer mode, and then use the "behavior" tool. If you mouse over/highlight the switch you want, and press ctrl-g, it'll show you the name of the switch which will help when searching for it in the xml code. Otherwise you gotta read thru thousands of lines of code to find it, and that ain't fun!

You're welcome, glad you fixed it!