Thanks for giving it a try!
I really can't tell exactly what it is! (I used the following to initialize the card in Hardware-Mode
phy start 1,0,1
phy set timing 1.0/60.0, 6, 0
Where the help says:
1st parameter: Soft-/Hardware-Mode selection (1= hardware)
2nd para: 0 = rigid-body-scene
3rd para: 1 = enable mutlithreading
phy set timing:
1st para: maxTimeStep#
2nd para: maxIterations
3rd para: method (0 = fixed time steps; 1 = variable)
I also used a 3Ds-object (the bar with angled sides):
load object "Media/balken3.3ds", objID
phy make rigid body dynamic mesh objID, matNr
I suppose that this object/dynamic-mesh is causing the bug somehow!
Did you tried it in Software-Mode?
The first thing you get asked isn't the "number of boxes", it's the box-size!!! The bigger the value the less boxes are there! Have a look into the "...MANUAL.txt" and you see under part "4. Configuration-Options on StartUp", "The 1st Question" a list that shows some of the box-sizes and in what box-numbers it results!
(I made a small update V. 1.2: now it uses a box instead of a mesh!
Maybe the bug is "solved" now! By pressing "b" you can load the new bar that caused the problem! When you load it, the game should crash as before! )
Thanks for the experiment!
AMD 64X2 4800+ (939); 2GB; GF 6800LE (@12PS, 6VS; 380 MHz, RAM: 434 MHz)
DP-Sw-Mode-Comp-Entry (updated to V. 1.2):