Tried to install the latest release today via Wineskin getting following error log
-
Any thoughts? I can start the game and get to the briefing/settings windows but if I try to fly it just quits.
fixme:thread:GetThreadUILanguage : stub, returning default language. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d948, 0x0 0x33d970 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d948 0x0 0x33d970) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d948, 0x66a680 0x33d970 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d948 0x66a680 0x33d970) returning a dummy value (current locale) fixme:thread:GetThreadUILanguage : stub, returning default language. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d94c, 0x0 0x33d974 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d94c 0x0 0x33d974) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d94c, 0x76a680 0x33d974 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d94c 0x76a680 0x33d974) returning a dummy value (current locale) err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:dwmapi:DwmIsCompositionEnabled 0x33f9f8 err:winediag:wined3d_dll_init The GLSL shader backend has been disabled. You get to keep all the pieces if it breaks. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fbec 4 stub fixme:ver:GetCurrentPackageId (0x33f96c 0x0): stub err:winediag:query_gpu_description Invalid GPU override 1002:68b8 specified, ignoring. fixme:win:EnumDisplayDevicesW ((null),0,0x33f21c,0x00000000), stub! error: xp_attach_gl_context returned: 2 X Error of failed request: 0 Major opcode of failed request: 148 (GLX) Minor opcode of failed request: 26 (X_GLXMakeContextCurrent) Serial number of failed request: 925 Current serial number in output stream: 925
-
Bms 4.33 was working ? Surprised you got as far as you have with the new protection system in 4.33.1
-
Hmmm, I thought I installed 4.33.1. How could I doublecheck which version I installed?
-
Go to the …\docs folder and check the BMS manual, it always states which version you have.
-
Ok yea, I have 4.33.1. I installed the original 4.0 version first so maybe that’s why the protection system isn’t a problem?
-
Your right about that. Clever stuff that it can link between 2 individual win32 programmes. My curiosity about was 4.33 working OK before the upgrade was based on your previous posts about successfully running BMS on your Mac.
-
Your right about that. Clever stuff that it can link between 2 individual win32 programmes. My curiosity about was 4.33 working OK before the upgrade was based on your previous posts about successfully running BMS on your Mac.
If you install into the same “wine bottle” (AKA .winedir) this should not be a problem.
I’d be very interested to find out what kind of hardware you’re using in WINE successfully with BMS.
Uwe
-
I’ve successfully installed and run 4.32 on Wineskin on a mac but am having trouble with 4.33.1. Crashes when you try to fly.
-
So has anyone successfully gotten 4.33.1 to work in Wine?
-
Craab I’m having the same issue with 4.33.1 crashing when I try to fly. Have you been able to find a solution anywhere by chance?
-
Have u tried window mode?
Sent from TapaTalk
-
Arty, what’s window mode? dssers101, I haven’t found a solution yet.
-
Hey, I’ve made some progress screwing around with windowed mode and got it to work sort of by shuvving it in a 1024x768 window. I have a 1920x1200 display and ATI Radeon 5770 1024mb graphics card. What resolution would be appropriate in my situation and what would work… why might it not be working fullscreen? I have 14gb of RAM on board so that shouldn’t be a problem.
-
Windows mode only pertains to 2D and the pre-3D menus. Once in 3D it changes to the reso that you set.
What would be appropriate would be what you prefer. Me, I’d set it to the native reso of my display. It’s all preference in this case.
It’s cool that you got it sorted!!!
C9
-
Glad u found out.
Sent from TapaTalk
-
So is this a “yes, it works” sort of comment when running BMS in WINE? Would be awesome and one reason less to keep the win7 partition around… how about facetracknor, voice attack, falcon MFD server, display extraction etc?
Cheers, Uwe
-
Arty, thank you for all that you do on this forum - Craab, I deleted and reinstalled 4.33.1 and it seems to be working fine for me now in full screen and loading all missions.
-
I don’t do anything.
I just gather the wisdom of the expert guys here and try to make it available. Also based on their knowledge and my (fading) memory I try to pass it to others in need.This is nothing compared to others.
-
yup, I’ve got this working fine now in full screen. the windowed mode settings helped and seem key.
-
yup, I’ve got this working fine now in full screen. the windowed mode settings helped and seem key.
Hi craab, sorry to drag up an old thread but I’m battling with this scenario at the moment using Crossover with El Capitan attempting to run BMS4.33U1 and getting exactly the same results as you reported here and in your other thread. In short, the launch menu loads but when I click launch the window goes to a black screen and I get the same error messages. I installed clean after installing stock Falcon 4.0 (which runs ok). I’ve tried the following without effect:
- Turned off all graphics enhancements in BMS config (shaders, high-def tiles etc).
- Turned off triple buffering
- Attempted to run in X11 window (not Mac native drivers)
- Attempted to run in virtual window with resolutions set to 800x600, 1024x768, 1920x1080
- Defined my GPU card vendor and device IDs plus VRAM in Windows registry (log reported these were invalid and overode them but think this is normal on Crossover)
- Attempted to use “-nomovie” and “-window” flags when launching BMS.exe
- Attempted to install the “.pak” file another user recommended to you.
I wonder if you could provide a little more detail as to how you got things running or would be prepared to package up a Wineskin wrapper for your config so I can try that out. Ideally I’d like to get it running in Crossover as its simpler but there may be some small but important difference between the distros that’s stopping it from working. I don’t have the GPU detection options in Crossover that Wine provides so perhaps that’s it.
Hope you’re able to help and still going strong on your Mac build!
- Attempted to manually specify my GPU vendor and device IDs