UI fullscreen resolution

[sthalik]

I bought a pretty big display. When switching to the very small 4:3 resolution it makes a scary sound like old CRT’s did or old TV’s when changing the channel.

Also it looks really atrocious on the big screen.

Please run the UI in windowed mode while setting fullscreen for 3D! This isn’t hard! Would help not just me but get rid of 2D crashes as well.

[sthalik]

I’m thinking of making a DLL wrapper that forces windowed mode when creating a Direct3D 9 device. Is there anything that would prevent it from working, from Falcon’s perspective?

[Dee-Jay]

@sthalik:

I bought a pretty big display. When switching to the very small 4:3 resolution it makes a scary sound like old CRT’s did or old TV’s when changing the channel.

Also it looks really atrocious on the big screen.

Please run the UI in windowed mode while setting fullscreen for 3D! This isn’t hard! Would help not just me but get rid of 2D crashes as well.

IMO, it wouldn’t be a bad idea indeed as it would be more practical to use Mission Commander and Weapon Delivery Planner in parallel.

[Eagle-Eye]

There’s a simple way to do it already.

If you use a desktop shortcut, and open its properties, on Target, add -window, so it looks like this

"x:\Falcon BMS 4.33 U4\Launcher.exe" -window

That way, when you launch BMS, it looks like this (1080p resolution). Because BMS UI still is 1024*768, it’s obviously a lot smaller on higher resolutions:

Once you go through to 3D, however, it takes up the whole screen.

[Guest]

Yeah, essentially, run the sim in windowed mode. Some people report a slight drop in performance, but test on your system to see how it affects you. However, I’m guessing you’re asking for a way to have your cake and eat it too….

[Arty]

Just a flash that might help on the windowed fps drop.
In game booster there is an option that disables desktop… Just a long shot.

Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk

[sthalik]

@Eagle-Eye:

There’s a simple way to do it already.

If you use a desktop shortcut, and open its properties, on Target, add -window, so it looks like this

"x:\Falcon BMS 4.33 U4\Launcher.exe" -window

Once you go through to 3D, however, it takes up the whole screen.

3D mode doesn’t take the whole screen per se: even when forcing the borders off through a borderless tool, the window size is reduced by the window caption size.

Is there a technical reason why not do a D3D wrapper like this:

• check resolution on D3D9 device creation or reset
• if smaller or equal to 1024x768, force windowed on
• otherwise, all’s right in the world

Wish I had more time but this is happening in a while.

[Arty]

Well this would kill the majority of users on 1920x1080 also might affect and the guys having 3+ monitors for flights Wich is the second and then comes the guys with one or more very high resolutions monitors.
Surely the trend going to lower price higher resolution monitors is an issue but having such thing as an option than being a default would be better.

Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk

[Frederf]

@sthalik:

3D mode doesn’t take the whole screen per se: even when forcing the borders off through a borderless tool, the window size is reduced by the window caption size.

Is there a technical reason why not do a D3D wrapper like this:

• check resolution on D3D9 device creation or reset
• if smaller or equal to 1024x768, force windowed on
• otherwise, all’s right in the world

Wish I had more time but this is happening in a while.

Don’t use a (3rd party) borderless tool. Instead use the “Falcon BMS Display Extraction” (Display Extraction.exe) and set Borders checkbox unchecked. You will have 100% of your display resolution used without any losses to title bar or border pixels. Make sure not to “Enabled” any of the other extracted windows HUD, RWR, etc. unless you want them.

[roccio]

Using the way pointed by Frederf I have a 3D full screen windowed and in my case it runs even smoother than the fullscreen one.
I have two monitors, one or the Falcon 3d and one for cockpit extraction.

For the dll wrapper: it is not needed as changing size and position of a window is easily done with system calls, the only problem left is capturing the right mouse coorinates that are no scaled automatically.