Full screen
-
-
No prob here with ATL+TAB even in full screen mode. ALT + ENTER is also working fine on ly side to switch from windowed mode and full screen mode.
But huh, yeah, that is where trouble comes in… ALT + NUM-ENTER is SetRWRSearch callback - well , not anymore, now it cycles window - fullscreen (as it should by windows design).
- fix is easy just remap that callback to something other, like ALT+NUM8
-BUT!!! Dee-Jay… that means that now windows(os) is primary controller for keyboard shortcuts actions, not BMS as before … that probably came with new directx implementation
That means that whole another can of worms will open with funny shortcuts like ALT-CTRL-INS/DEL … as windows have their own actions for some of them - since now windows is primary… we’ll see
There will be remapping … Think about what fun with SHIFT-DEL when you erase whole your desktop without recycle bin . heheYou should cross check for volatile key-combo commands in windows and blacklist them for use in BMS. Probably not much work there but just to keep in mind.
-
This is why we need your feedback indeed.
Personally, I don’t use combo (or VERY few) … aliment all is DX on my side. The other actions I do are through mouse and 3D pit. -
does anyone have any idea about my problem? Why the sound goes away when I want to change the window size to full screen?
-
All are on my sig.
Specific version of Windows 10? Latest/recent NVidia drivers? Is your monitor G-Sync?
And there are some OS settings which no doubt play into this … here are the ones I know of (and my settings, in parens) …
- Falcon BMS.exe file Compatibility tab: “Disable fullscreen optimizations” (me: checked… but, behavior seems to me to be the same with it both on and off)
- Windows 10 global Game Mode settings (me: ON… and I have Falcon BMS.exe enlisted for high-performance mode)
- Windows 10 global Graphics Settings: Hardware-accelerated GPU scheduling (me: ON)
- Windows 10 global Graphics Settings: Variable refresh rate (me: ON)
In my spare time I’ll toggle some of these things off/on and see if I can’t nail down what’s causing the problem. If I find out I’ll report back here … and maybe reach out to some MS/DX game dev forums to figure out what’s up with this.
-
ALT + NUM-ENTER is SetRWRSearch callback - well , not anymore, now it cycles window - fullscreen (as it should by windows design).
I think it’s [Alt+Return], viz. DX keyboard scancode 0x1C…? (NumEnter is DX scancode 0x9C.) Or do they both do same… either way, I’m not trying to be nitty, I take your point - [Alt+Return] is bound to AFResetTrim in the default keyfiles, which I actually do use all the time! (But I’ve had that remapped to a joystick button for ages.)
Edit: yes apparently this tramples both [alt-0x1C] and [alt-0x9C]
That means that whole another can of worms will open with funny shortcuts like ALT-CTRL-INS/DEL … as windows have their own actions for some of them - since now windows is primary… we’ll see
There will be remapping … Think about what fun with SHIFT-DEL when you erase whole your desktop without recycle bin . heheYou should cross check for volatile key-combo commands in windows and blacklist them for use in BMS. Probably not much work there but just to keep in mind.
Agreed … although it’s not quite as bad as you may fear. There are only a few globally un-interceptable keyboard commands in Windows. [ctrl+alt+delete] is the most well known… there’s [ctrl+shift+escape] to start taskmgr. and of course [alt+tab] to cycle among foreground application. [ctrl+escape] to open start menu… most of the others are some variation of the [windows-logo] key like [win+R] to open the run dialog, so those don’t come into direct conflict with BMS
Things like cut/copy/paste are entirely controlled by individual applications. (They may seem universal, but really it’s only by convention. And the shell/desktop is just like any another application, in that regard.)
lol there are some obscure, hard-to-define conflicts like accessibility key gestures eg. holding down the [shift] key for about 10 seconds will open a prompt to activate Windows Accessiblity “sticky keys”. I think I’ve run afoul of that, in BMS or some other game, and so I have all those accessibility key activations turned off.
-
I’ve flipped each of these settings, all together and individually, and I still haven’t been able to alt+tab out of BMS in fullscreen mode. The behavior changes a lot … eg. I can sometimes get the taskbar to show up, or even the alt+tab preview pane … but never actually able to swap back to the desktop or any other app. Weird.
Combing some of my developer resources, I found this surprisingly specific and insightful article on the pitfalls of porting an app from DX9 to DX11, especially when it comes to managing full-screen mode. Maybe something helpful for the BMS dev team to review… but still I have no idea why some Win10+Nvidia systems work ok and some do not.
-
I am on Amd(Rx580) and all is OK … well from limited sp campaign “testing” … ~4hrs pure flight
You are correct , ALT+ENTER(“return” - jeez where you come from, Amiga??:p LOL) is NOT same as ALT+NUMENTER but obviously in “directx” eyes… it IS - controls window/fullsreen switching
For ALT-TAB , I’ve read somewhere that guy was having luck , first he did ALT-ENTER switch to windowed mode (from fullscreen) and then ALT-TAB …
…I THINK that was/is also original behavior - but I don’t practice that much in fear of ctd - which never happened as I recall … but… you know… why push itCheers
here - something to check versus key-cuts in BMS , … think that only first drop-down is “crucial” for general key-combos in windows , so at least , less keys to worry about … we won’t be using WIN+…
have anyone tried ALT+F4 <- that is really MAN RANGE UP for FCR… or HSD in BMS
-
You are correct , ALT+ENTER(“return” - jeez where you come from, Amiga??:p LOL)
Don’t bash my Amiga heritage! lol
The keyboard shortcuts on that list are a big hodgepodge. Some are implemented OS-wide, and some are implemented by the application by convention. Some of the OS-wide ones are interceptable/overridable (PrtScn is a good example in BMS) and some are not.
I have many years of Windows app development experience, so I know way too much about things like keyboard input and event-routing, but I have almost zero experience with DirectX game development, so I’m enjoying the opportunity to learn more about things like swap-chains and pixel shaders… while simultaneously learning how to fly an F-16
-
This is why we need your feedback indeed.
Personally, I don’t use combo (or VERY few) … aliment all is DX on my side. The other actions I do are through mouse and 3D pit.Dee-Jay…
I 've did some exhaustive keys testing … and … Ring-a-ding-ding… NO PROBLEMS… - only ALT+ENTER and ALT+NUMENTER cycles between fullscreen and window , other then that , even SHIFT+DEL or ALT+F4 are out of equation , - they are primary bound to BMS rather then os(windows)
So, I don’t see any problem here, SetRWRSearch will have to find new key, already moved mine to ALT+NUM4 which is free by default.
Cheers