Problem with windowed mode after cockpit extraction
-
Hi all.
Having two monitors, I tried to use the interesting cockpit extraction feature. Following some tutorials, I was able to extract several elements (MFDs, DED and so on), but the real problem is that, when I launch the program after the extraction, I obtain it in windowed mode, with the bottom part, containing the various commands (Commit, Takeoff and so no) invisible.
My main monitor use a resolution of 19201080, the second one have a resolution of 16801050. The system is Windows 7 64 bit.
Is there a way to solve the problem?
Thanks. -
In your BMS.cfg file is the UI set to be centered? It should be set to 1, ie.( set g_bCenterUI 1 ) it is found under Misc settings.
The config file is found here - C:\Falcon BMS 4.32\User\Config\falcon bms.cfg
-
Hi Sarge55.
Thanks for the indication, I did not know about that option in the cfg file. I tried to modify it following your suggestion. Now the situation in the menu screens is a bit better, with the bottom part partially visible. The problem is that when I pass to the action, the screen is huge, largely beyond the limits of my monitor.
I tried to read the various tutorial available on the Net about cockpit extraction, but probably I am still missing something important, considering the results. In my sistem I have a single Nvidia ASUS GTX 560 DirectCU II OC, which drives the two monitors. Usually I don’t have problems with the programs that allow putting sections on two screens, but with Falcon Bms I still obtain strange results.
Any help is appreciated, thanks. -
You need to set the window coordinates for each extracted window. You may have done that already? Also, double check your resolution setting the the BMS SETUP –> GRAPHICS screen. Make sure it’s set to the correct native resolution of your main monitor (1920x1280).
I’ve got a similar set up - main monitor 1920x1280, 2nd monitor 1280x1024. BMS opens in the 2D UI as a window on the main monitor. When committing to the 3D ‘flying’ screen, it goes full screen at 1920x1280. Other bits (HUD, RWR, MFD’s, etc.) extract to the second monitor.
I’ve attached a couple screen shots so you can see how it’s set up and the end results. You need to think of this as one big monitor (extended desktop), in my case of 3200 x 1280/1024 with the main window running from (x,y) 0,0 to 1920,1280 and the secondary windows in the space 1920,0 to 3200, 1024.
(ignore the blank spaces; I extract some additional gauges with MFDE.)
-
Hi AgaveBlue,
thanks for your suggestions and the examples.
I tried to follow exactly your indications, also considering that your setup seems quite similar to mine, but I still have the problem of the “giant” 3D flying screen. I checked that in BMS Setup the resolution is 1920*1080, as for my main monitor, but when the program goes in 3D flying mode, it seems using a much bigger resolution, and so the image goes beyond the main monitor. On the second monitor, besides a part of the main window, I also see the extracted MFDs, so it partially works, but for some reason it seems screwing the coordinates of the main screen.
Do you have any idea of the possible reasons?
By the way, do you use a single video card to drive the two monitor, as in my case?
Thanks. -
Yes, single graphics card driving both monitors.
Not sure why your game screen is ‘losing’ it’s native resolution. Does your Windows resolution (right click destop –> screen resolution) match your expected resolution … is it set at 1920x1080? Correct main display selected? Seems to me it’s something in the resolution settings … Windows, your graphics card or BMS. My guess, anyhow.
Also, I’ve been saying I’m 1920x1280, which is incorrect, it’s actually 1920x1080.
-
That is a puzzle.
I run two monitors with a single GPU as well. Only extract the MFD’s with the ingame extractor and use MFDE for the other gauges. When I get home I’ll go through my setup and see if I can come up with any other suggestions.
Are you using a laptop? If so check to make sure the game is running using the video card and not the built in graphics. Oop’s I said game… I meant sim.
-
Hi,
problem (almost) solved
Thanks to your help and suggestions, I finally rememberd that I had similar problem of “strange” resolution with X-Plane. And actually the reason was the same. Being my eyesight not perfect, in Windows I set a customised DPI size of 150%, to have a bigger system text dimension. This seems influencing some games/sims, and requires that in the Properties panel of the program I must, in the Compatiblity tab, disable the screen resizing for high DPI.
I just tried this with the BMS executable, and actually it had effect. The strange thing is that now the 2d windows (menus and various pages) are quite small (about half of my monitor resolution), but still readable, but when the program goes in 3d (for flying) now it is in effective full screen at full resolution, and in the second monitor I actually see the extracted elements (MFDs, DED) with the expected sizes and positions.
So thanks a lot for the help, I can stand with the smaller 2d windows, the important thing is the full 3d screen and the secondary cockpit elements.
One last question, considering that I am completely new to the whole issue of cockpit extraction: is it not possible to also extract the OSB buttons of the MFDs, right? Do they eventually require some dedicated hardware panels? In practice on the second monitor one can visualize the MFD information, but for operating the relative buttons is it always necessary to directly working in the cockpit? -
Correct. You can see the same in the UI screen pic I posted …. it’s smaller than full resolution. But I do find it very usable, even with less-then-perfect eyesight.
MFD’s do not extract buttons; screens only. You can buy (?)Cougar MFD’s from Thrustmaster (IIRC). Without those, you can either click on the OSB with the mouse in the cockpit OR you can use the keyboard callbacks which, I think, are built in to both the stock keyfiles (BMS.key and Keystrokes.key).
-
Perfect, thanks.
Yes, now I obtain a two-monitor result very similar to that of your pics, so I assume the problem is solved
Thanks also for the clarification about the OSB buttons, now I have a clearer understanding of the situation.
