Braid Forum

Starts at a black screen with the following log:

fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS)
fixme:system:SystemParametersInfoW Unimplemented action: 53 (SPI_SETTOGGLEKEYS)
fixme:system:SystemParametersInfoW Unimplemented action: 51 (SPI_SETFILTERKEYS)
Can't bind to root surface with no fullscreen context.
fixme:d3d:IWineD3DImpl_FillGLCaps OpenGL implementation supports 16 vertex samplers and 16 total samplers
fixme:d3d:IWineD3DImpl_FillGLCaps Expected vertex samplers + MAX_TEXTURES(=8) > combined_samplers
fixme:win:EnumDisplayDevicesW ((null),0,0x33eea8,0x00000000), stub!
fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
...
fixme:wave:wodDsCreate DirectSound not implemented
fixme:wave:wodDsCreate The (slower) DirectSound HEL mode will be used instead.
fixme:wave:wodDsCreate DirectSound not implemented
fixme:wave:wodDsCreate The (slower) DirectSound HEL mode will be used instead.
fixme:d3d_surface:IWineD3DVolumeImpl_LockBox (0x212a90) : pBox=0x0 stub
wine: Unhandled page fault on execute access to 0x00000000 at address 0x0 (thread 0018), starting debugger...
Unhandled exception: page fault on execute access to 0x00000000 in 32-bit code (0x00000000).
Register dump:
 CS:0017 SS:001f DS:001f ES:001f FS:1007 GS:0037
 EIP:00000000 ESP:0033f4c0 EBP:01105400 EFLAGS:00010202(   - 00      - -RI1)
 EAX:00000001 EBX:00000001 ECX:00000000 EDX:00000000
 ESI:00000013 EDI:01152360
Stack dump:
0x0033f4c0:  fffffffe 50632e11 0033ff58 00000001
0x0033f4d0:  00000000 002f002e 4001844f f432e21c
0x0033f4e0:  3ffaba71 00370036 00390038 003b003a
0x0033f4f0:  003d003c cb44e7e5 05f1a84c 6c30813d
0x0033f500:  068d5f77 1373b83a 8b3db6e4 c806c58a
0x0033f510:  de659014 672c4058 b87d9dad 510e4dcf
0200: sel=1007 base=7ffc0000 limit=0000ffff 32-bit rw-
Backtrace:
=>0 0x00000000 (0x01105400)
0x00000000: -- no code accessible --
Modules:
Module    Address            Debug info    Name (17 modules)
PE      400000-  aee000    Deferred        braid
PE      af0000-  eb8000    Deferred        d3dx9_39
PE    50260000-50264000    Deferred        dsound
PE    502b0000-502b4000    Deferred        advapi32
PE    50510000-5055d000    Deferred        winmm
PE    505a0000-505b5000    Deferred        user32
PE    506e0000-506e4000    Deferred        gdi32
PE    50780000-50784000    Deferred        rpcrt4
PE    519d0000-519d4000    Deferred        ole32
PE    51b00000-51b04000    Deferred        msvcrt
PE    51b70000-51c4c000    Deferred        shell32
PE    51ce0000-51ce6000    Deferred        shlwapi
PE    51d40000-51d52000    Deferred        comctl32
PE    51e00000-51e04000    Deferred        ws2_32
PE    51e30000-51e34000    Deferred        d3d9
PE    7b810000-7b889000    Deferred        kernel32
PE    7bc10000-7bc14000    Deferred        ntdll
Threads:
process  tid      prio (all id:s are in hex)
00000008 
    00000009    0
0000000c 
    00000014    0
    00000013    0
    00000012    0
    0000000e    0
    0000000d    0
0000000f 
    00000016    0
    00000015    0
    00000011    0
    00000010    0
00000017 (D) Y:\Applications\PC Games\Braid\braid.exe
    0000001f    1
    0000001e   15
    0000001c    0
    00000019    0
    00000018    0 <==
0000001a 
    0000001b    0
Backtrace:
=>0 0x00000000 (0x01105400)
X connection to :2.0 broken (explicit kill or server shutdown).
X connection to :2.0 broken (explicit kill or server shutdown).

Since it froze on the black screen, I forced quit CrossOver Games, so some of the log may be influenced by that.

The log doesn't clearly indicate the cause of the crash. Something is trying to execute code at the zero address. This often means that the program is trying to use some function which isn't available. Unfortunately, there's no indication which function it meant to be executing.

Since it froze on the black screen, I forced quit CrossOver Games,
so some of the log may be influenced by that.

You shouldn't have to force quit CrossOver just because a game has crashed while in full-screen mode. In CrossOver's Window menu, there's a Restore Display item. Although the menu isn't visible in full-screen mode, you can still access it using the keyboard shortcut, Command-Option-R. That will kick CrossOver out of full-screen mode, and then you can quit or force quit the bottle from the Manage Bottles window, and then quit CrossOver cleanly if you still want to.

It works in the newest nightly builds of crossover games in a WinXP bottle without any configuration changes. I'll come back here when it is released and post a new rating for it.

I am getting an error about not having Pixel Shader 2.0
This is running on a Macbook Pro (with Nvidia 8600MT card) which should support pS2.0

any suggestions?

Which version of CrossOver are you running?

jason kravitz wrote:

I am getting an error about not having Pixel Shader 2.0
This is running on a Macbook Pro (with Nvidia 8600MT card) which
should support pS2.0

any suggestions?

i get the same thing. Running 7.2 on a leopard 10.5.6 on a macbook pro. It starts off wanting to install Direct X before it started the game.

It does not seem to run on 7.2, it just brings up a black screen. It is working on the testing builds of the next version, and should work in the next release. If the game complains about d3dx9_39.dll, you can just use a search engine to find/download it and copy it into the same folder as the braid exe. But if you do that it 7.2, you'll probably end up at the black screen I mentioned earlier.

You can try setting this registry key:

Open the Crossover Run-Window

Select the bottle Braid is installed in and then type regedit in the command field.

Add the key "HKEY_CURRENT_USER/Software/Wine/Direct3D/OffscreenRenderingMode" and set the value to "fbo" (Key and value without "")

If there is no Direct3D, create it.

Using Braid through Steam gets you some stuff set up for free. If you're not using it through Steam, you will want to install DirectX yourself. You can do that by showing/unhiding service packs and dependencies in the CrossOver Installer Wizard, and then selecting the DirectX runtime from the list of software packages.

On the Mac, if you get complaints about Pixel Shader 2.0, you'll have to enable GLSL. You can do that by running "regedit" and, under the key [HKEY_CURRENT_USER\Software\Wine\AppDefaults\braid.exe\Direct3D] add a string value named "useGLSL" with value "enabled". You'll have to create the "braid.exe" key, and the Direct3D key under that.

Im trying to get this working with Crossover Games 8.0.0 (Mac 10.5.8 on 17" MBP), and it hoses up the system pretty good. The mouse moves, but everything else on the display is completely locked up (clock dosnt update, nothing is clickable, etc). If I log in remotely using SSH, I can see the various wine process from Crossover, but cannot kill them (they go zombie if I try). Nothing short of a reboot gets the system back to usable. I cant find any log files that might give a hint either... any ideas? I installed and launched from Steam.

Jay, those are the symptoms of a window server lockup. Basically, CrossOver has tripped over a bug in the graphics driver which has taken down the Mac OS X window server. We'd avoid tripping over the bug if we can identify it, but we can't always and it's pretty hard to figure out.

Snow Leopard has fixed at least some of these graphics driver bugs.

For at least one program, we found a kludgy workaround. In the registry, you can add a value under the key [HKEY_CURRENT_USER\Software\Wine\AppDefaults\braid.exe\Direct3D] -- you'll need to create the last couple of keys. Create a string value named "DisabledExtensions" and set its value to "GL_ARB_pixel_buffer_object GL_EXT_framebuffer_object". That may avoid the lockup, but there's no guarantee. And there's no guarantee that Braid will work properly with those extensions disabled.

Edited to add: the Braid demo via Steam worked well for me in my testing of CrossOver Games 8 on Snow Leopard on a Mac with an Nvidia GeForce 8800 GT.

I'm having the same issue as Jay Kline when launching the Braid Demo. My system stops responding and I have to perform a hard reset of my computer. This is with CrossOver Games 8.0.0 on Mac OS X 10.5.8. Submitted support ticket 759970.

Jay Kline wrote:

Im trying to get this working with Crossover Games 8.0.0 (Mac 10.5.8
on 17" MBP), and it hoses up the system pretty good. The mouse
moves, but everything else on the display is completely locked up
(clock dosnt update, nothing is clickable, etc). If I log in
remotely using SSH, I can see the various wine process from
Crossover, but cannot kill them (they go zombie if I try). Nothing
short of a reboot gets the system back to usable. I cant find any
log files that might give a hint either... any ideas? I installed
and launched from Steam.

I have the exact same problem here, same CxG and same OS.

However, this problem is in the Braid demo, not the full version. I really want to buy the full version this weekend on Steam (it's on sale for just five bucks), so if someone could help me or tell me that it works in Snow Leopard or with the regedit thing soon, that would be awesome.

I bought the full version, and not surprisingly it does the same exact thing. (Except preparing the game took longer.) Has anyone tried the regedit thing? I'll probably do it, but I don't want to end up changing some advanced preference and not being able to change it back. If you could tell me how to undo that just in case, that would be very helpful.

If you need to undo it, you can just delete the DisabledExtensions value. Also, the change is Braid-specific, so it won't impact any other program. Since Braid is unusable for you, there's little risk of making things worse. 😊

It's odd, but Braid (via Steam) is working great for me with no tweaks at all under CrossOver Games 8.0.0 on my MacBook Pro. Maybe Steam is helping? What other variables might be in play?

Yay! Cool, thanks. I'll give it a go.

Which version of Mac OS?

And it failed for me and I was running it in Steam, so that's not the case.

PS:
People, we are cramming like at least three or four different conversations into a single thread, and it's more convenient for everybody to split em up into separate threads. So if you have a new unrelated question or comment, please make a new thread, ok?

UPDATE:
I opened regedit (I've never done this before, by the way), but there's no braid.exe folder inside the AppDefaults folder. Do I need to create it or something?

Nick McCurdy wrote:

Which version of Mac OS?

10.6.1

Oh, Snow Leopard. Someone mentioned that Leopard fixes some video driver bugs. So you have a bug fix in Snow Leopard that I don't have because I'm running Leopard. :|

Nick McCurdy wrote:

I opened regedit (I've never done this before, by the way), but
there's no braid.exe folder inside the AppDefaults folder. Do I need
to create it or something?

Yes. From the Edit menu, select New > Key. Name it braid.exe. Then select the key you just created, if it isn't automatically selected for you. Do Edit > New > Key again, name this one Direct3D. Select that. Do Edit > New > String Value to create the DisabledExtensions value.

Oooo great, thanks. The game loaded without a window system freeze, but I got a black screen like that other guy. However, besides the black screen, I think the game is working, as I can hear the menu music it and I can hear it when I press escape to toggle the menu. I'm going to try that other tweak that's listed above now.

UPDATE:
Thanks, it's working now! :D
This game is amazing. Hard, though.

I tried it in A Macbook Pro with an nvidia 8600 using 10.5.8 via Steam using crossover games 8.1.2. The computer froze on game launch while it was synchronizing the game progress data from steam(I mean after it had downloaded 100% of course when it launched for the first time it sync your progress from playing on another computer). I repeated it three times to the same result.

When you say crash, could this be another window server crash? Please read earlier on in this thread.

I tried the registry thing (both the glsl and the extentions key/value pairs but the computer kept freezing). Maybe its the fact that i am on 10.5 and not 10.6.

Well I'm on 10.5 and the registry thingy fixed the game for me. :|
Maybe you have a different graphics card. I have an Invidia GeForce 8600M GT.

This is strange. My MPB 'wears' the 8600 as well. Thus, essentially we have the exactly same configuration:

• OSX 10.5
• Macbook pro with 8600
• Crossover games 8.1.2
• The game is installed and launched from Steam

I create the 2 keys(braid.exe and Direct3D) and then i add the key value/pair DisabledExtensions=GL_ARB_pixel_buffer_object GL_EXT_framebuffer_object
after i tried this i also added the key/value pair useGLSL=enabled

Have you also set the OffscreenRenderingMode=fbo ?

Ken Thomases wrote:

Yes. From the Edit menu, select New > Key. Name it braid.exe.
Then select the key you just created, if it isn't automatically
selected for you. Do Edit > New > Key again, name this one
Direct3D. Select that. Do Edit > New > String Value to create the
DisabledExtensions value.

This registry edit worked perfectly for me.

Running Steam version of Braid, CXG 8.1.3 on MacBook Pro OS X 10.5.8 with nVidia 8600M GT.

Has this been solved yet with the latest version of CxG? Can it run without the registry edit?
points at new thread