I learned early on never to question the motives of developers.
Latest posts made by slaintemaith
-
RE: Keyboard commands for MAP Switch do not function.
-
RE: Keyboard commands for MAP Switch do not function.
Not sure how that makes this any less of a bug.
Not a priority, of course; but it never was a priority. -
Keyboard commands for MAP Switch do not function.
When creating keybinds for the MAP switch, although in the setup screen, the key command will show it bound to the MAP switch actions ON, OFF, or TOGGLE, in-game none of the commands affect the MAP switch.
Version
4.34.0 (x64)Build
19631Detailed Description
Always, when creating keybinds for the MAP switch, although in the setup screen the key command will show it bound to the MAP switch actions ON, OFF, or TOGGLE and highlight the commanded function, in-game none of the commands affect the position of the MAP switch.Pictures
Would it help to post a picture of a non-moving switch?Example files
N/ACrash logs
N/AReproducibility Procedure
1. Launch Falcon
2. Select “Launch”
3. Select “Setup”
4. Select “Controllers”
5. Assign a free keyboard command to any MAP Switch Function (on/off/toggle)
6. Test said function by typing those key commands. Note that they work.
7. Click “Save”
8. Type “Bad MAP”
9. Click “Save”
10. Click “Apply”
11. Click “OK”
12. Select “Tactical Engagement”
13. Select any mission that has a Falcon, and that can cold start on the ramp.
14. Click “Commit”
15. Click “Takeoff”
16. Click “Ramp” if it is not already selected.
17. When loaded in cockpit, type one of the assigned key-commands to actuate the MAP switchObserved Behavior:
Switch-y-no-move-y.Expected Behavior
Switch should actuate in a manner as commanded by the keypresses. -
RE: Something with nVidia, Win 10, 4K, and Falcon. Dunno what.
AH-HA! It was Frederf’s idea what fixed it! Although “perform scaling on” needed to be set to GPU rather than “Display,” that stretched both the UI wrappers and the in-flight resolutions.
I owe you a frosty beverage of your choice, sir.
Thanks everyone else as well for trying to help out–although no cigars or beers are bought as second-prizes. -
RE: Something with nVidia, Win 10, 4K, and Falcon. Dunno what.
I’ve had this running before with the same gfx card and the same PC. And it fit the full screen. (Even the setup screens) I have no idea what’s wonky with it now. (New monitor, but it achieves the same resolutions)
I’ve tried the nVidia options (all of those listed)
Nada.
Dunno where the winders options might be. -
RE: Something with nVidia, Win 10, 4K, and Falcon. Dunno what.
Right click on your shortcut, compatibilty and disable fullscreen optimization. Also the menu resolution is fixed to 1024x768. The graphic settings aka resolution is only for once 3D is loaded aka ingame.
I had hopes for this, but: nope. Also, this is untrue. The game is set for 3840 x 2160, but this is what I have in flight.
-
RE: Something with nVidia, Win 10, 4K, and Falcon. Dunno what.
@Cloud:
In your User/Config folder you could delete the dx9display.dsp file and relaunch to see if that has any effect.
It regenerates when BMS is launched.
C9
No effect, I’m afraid.
-
RE: Something with nVidia, Win 10, 4K, and Falcon. Dunno what.
Still not clear if you’re talking about the menu or in-game.
The menu/2D planning is fixed to a low resolution.
In-game should be as set in the Graphics settings.
Sure, but it should still stretch to fit my screen, no matter what the size is.
It doesn’t. -
RE: Something with nVidia, Win 10, 4K, and Falcon. Dunno what.
No matter what resolution I set it to in the game, it remains the same. Is there a file I need to edit somewhere?!
-
Something with nVidia, Win 10, 4K, and Falcon. Dunno what.
I’m using an nVidia 1080.
Windows 10
I have no idea why this is saying it’s in 3840x2160 when it is clearly NOT.Also, when I exit, it marfs up all the other windows I might have open.
Help?