BMS hangs in x64 fine in x32
-
Hi,
What does it mean “Hang” ?
Please post your system spec and I also suggest to run some memtest or whatever it is called these days.
-
by hanging i mean that it starts up fine then i select 64 bit and then select any of the games modes eg Dogfight, Tactical Engagement then i select Commit or Takeoff and the music stops the cursor disappears and does nothing else. i have to alt ctrl del to kill it. 32 bit works fine. there are no error logs either.
my system is
i7
16gb ram
Nvidia GTX 980
2tb hddthanks for your time
-
by hanging i mean that it starts up fine then i select 64 bit and then select any of the games modes eg Dogfight, Tactical Engagement then i select Commit or Takeoff and the music stops the cursor disappears and does nothing else. i have to alt ctrl del to kill it. 32 bit works fine. there are no error logs either.
my system is
i7
16gb ram
Nvidia GTX 980
2tb hddthanks for your time
OK.
Please add to the launcher a -mono switch and then repeat that step, you should have a .xlog file created in the user/logs folder. Please copy the content of the xlog file here inside a code tags. This may tell where it’s hanging.
-
Do you have your graphic settings through nvidia control panel? this is a problem for some people…If you have your settings set up through NCP, Try removing the profile and see if this helps. I had this problem a few months ago. took out the profile and everything is running smooth as silk
-
I-Hawk, i have attached the xlog file, i have also attached the x32 xlog file for comparison as both files show warnings. as i have mentioned in my first post x32 works fine.
Tass, no i am not using any Nvidia profile.
Thanks -
Present Parameters: [color]BackBufferWidth 1920 BackBufferHeight 1080[/color] BackBufferFormat 22 [color]MultiSampleType 1 MultiSampleQuality 3[/color] SwapEffect 1 hDeviceWindow HWND=0x804d0 Windowed 0 EnableAutoDepthStencil 1 AutoDepthStencilFormat 75 Flags 2 FullScreen_RefreshRateInHz 60 PresentationInterval 0x1 BackBufferCount 2 Pre-device release CooperativeLevel OK D3D device refcount 3 [b]CreateDevice() failed! Unknown error (000000008876086C)! Device 0000000000000000[/b]
Well at least now we know where it fails loading. Device creation failed, the Device referred here is the SW reference to the Graphics HW (i.e your Video card).
And, if you compare it to the 32 bit version
Present Parameters: [color]BackBufferWidth 1024 BackBufferHeight 768[/color] BackBufferFormat 22 [color]MultiSampleType 0 MultiSampleQuality 0[/color] SwapEffect 1 hDeviceWindow HWND=0xb049a Windowed 0 EnableAutoDepthStencil 1 AutoDepthStencilFormat 75 Flags 2 FullScreen_RefreshRateInHz 0 PresentationInterval 0x1 BackBufferCount 1
I can see there are differences in Resolution and multi-sampling settings (I marked both in Red). Can you please try to apply same for both and see if with 32 it’s still loading OK?
-
so these two lines are resolution?
BackBufferWidth 1024
BackBufferHeight 768in the BMS setup-> graphics both x64 and x32 are set to 1920x1080 ill set it to 1024x768 and report back in the morning.
-
1024 x 768 is just the resolution of the 2d user interface. When you go to 3d your resolution will change to 1920 x 1080 as per your graphics settings.
When you took the snapshot of the 32-bit exe were you in the UI?
-
so these two lines are resolution?
BackBufferWidth 1024
BackBufferHeight 768in the BMS setup-> graphics both x64 and x32 are set to 1920x1080 ill set it to 1024x768 and report back in the morning.
1024 x 768 is just the resolution of the 2d user interface. When you go to 3d your resolution will change to 1920 x 1080 as per your graphics settings.
When you took the snapshot of the 32-bit exe were you in the UI?
Ha yes Darkman you are right, the 1024x768 is only for the UI, later in the log there are prints for the 3D resolution and it seems same on both logs, so this isn’t the issue. Warpig no need to check resolution.
I don’t know yet what to tell exactly here, other than device creation was failed, which is weird as that is the basic functionality that creates a D3D device reference to the HW.
What I suggest to do is (By this order):
1. Delete under user/config the dx9display.dsp file and try to run
2. Disable multi-sampling and retry
3. Set any setting in the Nvidia control panel that you may changed earlier
4. Install latest drivers after a FULL clean up of the old drivers versions you may have. I’m not an expert but there should be some drivers cleaning apps out there just for this purpose.
5. Test you Video card with other games and confirm it’s not suffering any problems.I hopw 1 of the above steps will find something.
-
Darkman im not sure what you mean by was i in the UI when i took the snapshot. the file is created automatically guess it doesn’t matter now anyway as its not the issue. i have already tried deleting the dx9display.dsp file, BMS created another one on launch but it still didnt work. i will try the other steps and see what happens there.
Thanks for your time guys. -
The UI is limited in the code to 1024 x 768, there is nothing you can do about that. 3d is set by you to your chosen resolution, i.e. 1920 x 1080 in your case. So if you were in the UI in 32-bit, but attempting to go to 3d in 64-bit then we’re comparing different resolutions and graphics settings
Don’t worry about it, I was just double-checking, but as you’ve confirmed that was the case just carry on with I-Hawk’s suggestions.
The only other things I’ve seen people post who specifically had 64-bit exe issues were due to Force-Feedback drivers, Bluetooth drivers, FaceTrackNoIR drivers, or Windows 10 updates. Have a look through this sub-forum if you’re still struggling as it’s quite possible someone else has posted a similar issue and what caused it for them. Drivers do seem to be a common theme, unless you’re beta-testing Windows 10 for Microsoft :rolleyes:
-
ive just done all the the suggestions which I-Hawk has made. its still not working.
Darkman, i did have FaceTrackNoIr but its uninstalled now, Bluetooth drivers, i read about that as a possible cause so i have already uninstalled the drivers.
To me, as it runs fine in 32 bit and not in 64 bit then it suggests that BMS is dependant on something 64 bit. the drivers which i have just installed are 64 bit but still no good. i forgot to mention, the the shortcut properties, i have Run as Administrator, Capability Mode Win 8 and disabled scaling. if its not the driver, what else could it be? what does it depend on? maybe try uninstalling dot net and reinstalling 4.6 again? but if 32 bit is ok then it may not make a difference. -
Win 8 compatibility mode??? Why?
Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk
-
if its not in win 8 capability mode then not even x32 works. i read the thread where you were having problems with the same issue. is yours sorted now?
-
if its not in win 8 capability mode then not even x32 works.
That’s interesting. On which version of windows are you?
What happens if you try to run DirectX Diagnostic tool? (Start and type “dxdiag”) - Do you see in the main window that everything looks OK?
Do you have other games that you can test? Do they work fine or require also to set some specific compatibility Windows mode?
-
my OS is Win 10 Home and Directx is ver 12. do you need to run yours in capability mode? in the morning i will double check to see if x32 will run without capability mode. ive tried so many things ive forgotten the settings ill make sure in the morning.
my other games Assetto Corsa x64, DCS, Arma 3 all run without problems.
-
Weird, I also have Win 10 Home (On my laptop) and 64-bit runs fine there without any issues and without setting any compatibility modes.
-
Weird, I also have Win 10 Home (On my laptop) and 64-bit runs fine there without any issues and without setting any compatibility modes.
me too.
-
After checking, i can confirm that BMS must be in capability mode or not even x32 will run. It will just freeze before leaving the UI and going into the game. I guess i could try this, uninstall then install the base game without any updates a test it, if it works install the U2 update and so on until it stops working. Also i could try 4.32 if its still avaialble and has x32 and x64?
Another option is to reinstall directx. What do you think? -
With given info and no specific solution or guidance, start testing one by one.
First a clean install would be what I would do.
Just in case use stock folders.
R u on a non English version of Windows?
Any force feedback input devices connected?Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk