Mac OS X Leopard (10.5)

[cotharyus]

I assume you're running leopard? What build are you using? Building your own from the latest SVN? Downloaded from my website?

Basically, if you've got shaders off, and it won't crash when you run it from command line (even if you're not using gdb?) then you're seeing something I haven't seen before. Now, if it only won't crash when you're using gdb, I can believe that - I'm fighting this bug right now, and the only thing I can tell you is, some cars will work on some tracks when the game is run normally, but everything seems to work just fine when you run through gdb, which is making it hard to figure out what's going on. This is the problem that's been documented several times over in the development section and has a place in Abs1nth's thread about OS X development. I'm still playing with things, I've sent a report to Apple, and I'm not giving up. All I can tell you is if you want to play with it just to play, play through gdb - then you're a step up on the game if something stupid happens, you can get everyone a backtrace.

[kidrock]

whats gdb lol.... im building my own from the latest SVN.... do i need to rebuild after turning shaders off in preferences? i assumed no because it doesn't affect the build files... just the preferences.

[cotharyus]

No, you don't need to rebuild after changing game preferences. What kind of Mac do you have?

gdb is a debugging program. If the game should crash while it's connected to gdb, you can get all sorts of useful information. Open a terminal and type man gdb

[joevenzon]

Here's the 10 second tutorial on gdb:

Code:

gdb some/path/to/vdrift

(replace "some/path/to/vdrift" with the actual path to the vdrift executable... for me it's build/vdrift)

at the (gdb) prompt, do this:

Code:

run

after the program quits or there's a crash, you'll be back at the (gdb) prompt. if it crashed, do this:

Code:

bt

(if there was no crash it'll just say "No stack.")

to quit gdb, then just do:

Code:

quit