As it turns out, windows mode was not necessary. I also turned off windows for the instruments display in “cockpit display extraction”, because each individual window, for a given cockpit instrument, was appearing I could see before entering into the main 3D world. What solved the original issue was setting the “Falcon BMS.exe” compatibility for DPI status management. I think the issue is that I have the windows scaling set to %125 for other than Falcon BMS. So the compatibility for managing the DPI scaling to “application” for the executable is the solution.
Latest posts made by dodgerdog
-
RE: 3440x1440 display sometimes loads, but not always
-
RE: 3440x1440 display sometimes loads, but not always
Thanks for the clarification - I did make the DPI scaling change to the “Falcon BMS.exe” executable.
-
RE: 3440x1440 display sometimes loads, but not always
Thanks white_fang - actually, the changes you suggest I try out did a treat. I’m all set - thank you all for helping me solve this issue.
-
RE: 3440x1440 display sometimes loads, but not always
Eagle-Eye and sthalik - YES, a positive result. Making your suggested setting changes for the Falcon BMS shortcut, display extractor, and config file solved the problem. Additionally, I had to change Window 10 display "scale and layout from 125% to 100%. For regular use, the display scale of %125 is preferable. QUESTION: Is there a way to set the display scale to %100 just for Falcon BMS in the Nvidea Control Panel or something?
Thanks! -
RE: 3440x1440 display sometimes loads, but not always
eurybaric - I just tried making the change you suggest, but then I loose the jet as mouse cursor in the Falcon UI - good though though.
I tried adding -window as a parameter to the BMS desktop shortcut, can see window is confirmed in the BMS control panel. However, when launching Falcon into the 3D world, the display shifts down and to the right lower quadrant of the display, and can not be repositioned to center. I should also mention, that when Falcon is started after a system reboot, the game comes up in the 3D world, and displays properly for 3440X1440, but eventually reverts back to the issue on subsequent launches into the 3D world. I’ve also tried several other display settings in the Falcon graphics settings to no avail. Any other ideas I can try - appreciated.
-
RE: 3440x1440 display sometimes loads, but not always
Thanks for the replies. Curious about running Falcon in a window, and will see if the manual explains how to configure accordingly. I would like to run Falcon in the monitor’s native 3D size - meaning 3400X1440, because it looks awesome to me. If there is something I’m missing in the replies I’ve read, please do clarify as it seems to me I’m not the only person having this sort of issue.
-
3440x1440 display sometimes loads, but not always
I’m trying to get this g-sync ultra wide monitor to display falcon in 3440x1440 100Hz. Sometimes the game will load, and display correctly, but mostly not - most always loads the game in the same size as the Falcon UI. Falcon is the only game where I’m having this problem. Is there a setting in the config file or something with FOV that I need to set so that 3440x1440 displays as desired? The monitor is a asus rog pg348q, graphic card is 1060 6MB on a ryzen 1800x with 32GB of ram. I’ve tried updating the graphic card drivers to the latest version 398.36 to no avail, and I’ve also tried configuring the Falcon exexcutable nvidea settings both configured or none - either way, makes no difference.
-
DwVAC (voice activated command) vs. VA (voice attack) pros and cons
Hello, Well I’m trying to resurrect my interest in Falcon, and have been working diligently to get up to date - last time I was active with Falcon was when the FreeBirds VFW were around, and my computer was an XP. So aside from the Cougar setup - which I’m happy to say is modded nicely, and alive and well, I’ve determined that what I used for AI comms with “Game Commander” just will not function reliably with WIN10. That said, I’m looking for a comparison between VAC and VA, and was hoping somebody could advise on pros/cons or point me to where this topic or a list comparison exists before pouring into all the profile/build with implementing either VAC or VA. Thanks, DD
-
RE: Microstick LOCK/UNLOCK compiles for only MIX or MIY
OK… never mind as I’ve found the problem. For some strange reason, this statement “USE HAT1_SENSITIVITY (20)” will not co-mingle nicely. So I’ve remarked the culprit as I’d rather have the microstick LOCK/UNLOCK funtionality, and now radar cursors as analog will even slew diagonally, and more accurately.
-
Microstick LOCK/UNLOCK compiles for only MIX or MIY
Hello, I am hoping somebody can help me figure out how to get the Foxy compiler to successfully compile LOCK/UNLOCK for both MIX and MIY. Currently, I’m only able to get the compiler to successfully compile either MIX or MIY, but not both. When trying (see below) to define lock/unlock for both MIX and MIY, I get this cryptic compiler error stating I have max exceeded number of logical flags or more than 48 which does not make any sense. Here’s a snippet of the Foxy statement, and attaching a screenshot of the compiler error:
USE SWAP (TOEBRAKES, MICROSTICK)
Rem ** USE SWAP TOEBRAKES AS MICROSTICK configured Cougar CCP, and in the Falcon UI for the purpose of Radar Cursor controls
MIX /I LOCK (MIX, LASTVALUE) 6 25 ( 1 2 3 4 6 10 12 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98) MSY(2-) MSY(2+) MSY(0)
/O UNLOCK (MIX)
MIY /I LOCK (MIY, LASTVALUE) 6 25 ( 1 2 3 4 6 10 12 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98) MSX(2-) MSX(2+) MSX(0)
/O UNLOCK (MIY)NOTE: What I am trying to accomplish is a solution whereby I can configure L and R toebrakes within Falcon BMS 4.33 for Radar Cursor as an analog mouse using the UNLOCK function, and S3 (out) button to use the microstick as a digital mouse or LOCK (MIX and MIY, LASTVALUE).