Once I make an NVIDIA profile for 64bit BMS it will not load anymore.

[Yassy]

32-bit executable runs fine (with a seperate profile in the NVIDIA control panel), but the 64-bit executable ceases to load once I have created a profile in the NVIDIA control panel for it.
I have tested every option on or off seperately to see if it was a certain setting that would cause it, but the only way to get BMS 64-bit loaded up again, is to delete the profile from the NVIDIA control panel altogether.

There is no error message or window showing. The launcher just closes and that’s it. Falcon BMS.exe doesn’t show up as a process in Windows Task Manager either after the launcher closes, so I assume the executable just crashes.

If I can provide more details, please let me know.

[Yassy]

Any ideas why this would happen?
I run the latest WHQL drivers from
Nvidia.

[Icarus]

Try a profile with nothing in it and see if it works. BMS for me doesn’t like supersampling.

Try nvidia inspector instead. Thats what I use.

[Yassy]

An empty profile with stock settings has the same result; the sim doesn’t load.
As soon as I delete the profile from list everything works again.

The odd thing is that 32bit doesn’t suffer from this problem.

[Red_Baron]

Could just be because its an old sim. I have tried making profiles for other older sims like Battle of Britain II and Wings Over Fladers Field and they do not seem to like these 3rd party “sprusing up” graphic enhancers. And either crash or freeze at a black screen when the profile is on.

[Icarus]

Works fine for me in 64 bit with vVidia Inspector. Try that. Just watch for supersampling issues.

[Echo7]

The NVIDIA profiles work fine for me. I’m using driver version 353.62.

Edit: Also try to delete dx9display.dsp from the config folder.

[Yassy]

@Echo7:

The NVIDIA profiles work fine for me. I’m using driver version 353.62.

Edit: Also try to delete dx9display.dsp from the config folder.

Thanks for the suggestion.
I am running Nvidia’s 358.50 drivers. Deleting the dx9display.dsp file doesn’t change anything. 32-bit loads fine with an nvidia control panel profile (for falcon bms.exe in the x86 folder). 64-bit doesn’t load with an nvidia control panel profile (for falcon bms.exe in the x64 folder).
When I press Launch in the Launcher window, the launcher window closes and nothing further happens.

[TxMtb]

That is weird, I’m using 358.59 and having no issues. Have a profile in the Nvidia Control Panel and Nvidia Inspector also.

[TeeSquare]

I had same problem. Instead of browsing for the BMS exe file, select the BMS icon from the list in the window. The profile didn’t disappear when I did it that way.

[Yassy]

There are two icons in the list.
One points to the 32bit executable, which works fine with a profile.
The other points to the 64bit executable, which does not work.

Perhaps your profile points to the 32bit executable whereas you run the 64bit executable?
The icons in the profiler points to some executable no matter what. There is no magic there.

[Stubbies2003]

@Yassy:

There are two icons in the list.
One points to the 32bit executable, which works fine with a profile.
The other points to the 64bit executable, which does not work.

Perhaps your profile points to the 32bit executable whereas you run the 64bit executable?
The icons in the profiler points to some executable no matter what. There is no magic there.

I had a goofy issue with my setup for a bit but not to that level. I was running 355.98 when I first played around with 4.33 and if I turned on AA at all in the NVidia CP for the 64 bit executable the launcher would go to the UI screen but it was completely black. The UI was running as the F-16 mouse cursor was there and I could hear the UI sounds as I moused over the areas where the top menu items would be. I could also exit the UI normally by hitting the exit button that I couldn’t see in the UI. Turning off AA made things work normally.

As a part of my testing I upgraded the driver to 358.50 and then AA could be selected no problem in the CP. Very odd that a month update of the driver could have that kind of effect on an old sim like this but hey it works.

[TeeSquare]

I used the 64 bit. The only other thing I did was delete my other profile that pointed to another version of 433. After that I used the icon exited nvidia then re-opened it and the profile was saved. Then I was able to adjust settings and be sure it wouldn’t disappear.

[Saruman]

358.89 drivers here. Same problem as the OP.