Maybe you should try to run the game in window mode : edit shortcut and ad -window to the target (….Launcher.exe" -window) - then in “cockpit display extraction” select “main” and uncheck “borders”. It helped me for Vsync really working, maybe nothing to do with your problem…
Latest posts made by toutenglisse
RE: Screen res forces frame rate, disables Freesync?
RE: BMS not fully utilising my GTX 1070
Hi razo, there is Something you can easy try and wich works for other games (DCS, gta5,…) when gpu is at low usage while fps are bad : do a new nvidia driver install with custom settings : only drivers and complete new install (will delete all old files) - the problem in these cases being GeForce experience.
So in some games (others works ok) without GeForce experience installed your gpu will now load fully before experiencing fps drops - with 60hz vsync on you should have 60fps until the gpu hit 100% usage - maybe you have the case with bms. Maybe it’s not your problem ?
RE: Cockpit pan is not smooth
Hi, maybe it’s the same thing that occured to me when i recently update my 4.33 to u1/u2/u3. I used to play fullscreen vsync on but with updates bms was no longer smooth (but with same stable 60fps). The solution for me was to run the game in window mode with no borders (that looks the same as fullscreen in flight).
To give it a try : right mouse click on the shortcut bms 4.33 U1 - select properties - add -window to target (for me it gives : “C:\Pierre\Jeux\Falcon BMS 4.33 U1\Launcher.exe” -window) - than launch it and select “cockpit display extractor” - choose “main” display and uncheck “borders”.
RE: Skin selection issue
a last check - I’ve just uninstalled everything (bms 4.33 with no updates and bms 4.33 with U1/U2/U3 updates) - than I installed a fresh new bms 4.33 with the 3 updates and re-do the simple test.
When in flight the skin of my f16cm40 is not the one i’ve choosen (and the issue is for any Aircraft that has several skins… f14 or others). In bms 4.33 with no updates the skin in flight is the one i’ve choosen (whatever the Aircraft). So there is an issue and it seems to be related with updates 1-2-3.
RE: Skin selection issue
OK, thanks for the answer but ….
To verifie if it’s not a so called “psycho” effect i’ve just re-install BMS 4.33 with no updates and try the same test : i create a simple TE with only 1 F16cm block 40, i open the arming screen and selected another skin than the first one (I selected the one with a checkerboard and a horse and number 5 on the tail), than i save the TE and launch it and … in flight (3d) or in the loadout page during briefing the skin of my plane is the one i selected during creation of TE.
When launching the game again OK the skin is not saved in the TE but when i select a skin it’s the one with wich i fly in 3d (in BMS 4.33 with no updates) - in contrary with my U3 install it doesn’t work anymore : the skin i choose isn’t the one i fly with.
If i am the only one that have this issue with this simple test than ok it’s a problem with my installation but it seems to me that this issue is not so old …
RE: Skin selection issue
thanks for answer. Sorry if i’m not clear (but we can’t speak french i guess)
“Skinsets are not saved with TE” - Ok that might be the problem (means that .dds file numbers must be replaced to access another skin for a moddel ?)
“When i change a skin, it does indeed change the skin and i can see that in the arming screen and in 3D” - …. I don’t … that’s what i call an issue : I can’t fly with any other skin than the first (for a plane that has severals). In facts :
I create a simple TE with just 1 flight 1 plane (a f16cm block 40) training. arming window i select weapons and for exemple the second skin of this plane. I save, exit, launch that created TE and in flight (3D) the skin of my plane is the first and not the second one.
If it’s normal Ok i can do with it (replacing .dds files of a skin for another) but i don’t think it’s normal.
thanks again and sorry i maybe make you losing your time with that ^^
Skin selection issue
when i select a plane with more than 1 skin (for exemple f16cm block 40) and choose any other than the first skin, it always in flight shows the first skin of the plane. it also can be seen in the payload preview screen of the briefing.
than i edit the TE i have just created and see that the plane wears its first skin, while i saved the TE with another skin.
No matter Hi-res textures or not.
(I use a fresh new bms install up to date)
RE: 4.33U1 Noticable decrease in performance
davidzill - I don’t know if you still have this problem but - thanks to him - Arty gave me solution in his “hot list” :
with bms 4.33 U1/U2/U3 - at least on my rig (win10 i5 4460 gtx970 16gb) - the game needs to be launched in window mode with no bordure (procedure in BMS-manual.pdf chapter 3.2.5)
so add suffix -window to command line (target) of the bms U1 shortcut, and than launch it and in “cockpit display extractor” choose “main” display and uncheck “borders”
result is exact same thing as fullscreen when in flight but without any stutters and with perfect smoothness.
Many thanks Arty - the solution to my problem was on your “Hot List”.
I launched the game in window mode with no bordure and…. problem is gone. The game now runs 60fps vsync-on flawless with the smoothness expected.
(win10 - i5 4460 - gtx970 - 16gb - sidewinder FFB2 - thrustmaster TWCS - thrustmaster rgt pedals)
Hi ! thanks it’s very nice (i was a good fan of aegean on 4.32)
there are some features you made that should be implemented in bms (3d objects variety and quantity like buildings and antennas , rockets cone-trails after launch, etc ….)
Textures are great like creta isle - around souda Airport it’s great - but in some central aeras like middle of turkey there are large zones with no variety in textures but certainely WIP…
I use your theatre in 4.33 with no updates because with U1/U2/U3 i have constant stuttering while fps counter shows 60fps … and sometime in your theatre there are stuttering phases : 60 fps but smoothness of like 30fps - it’s in my own experience on my system and i don’t know what causes that.