For
x#=(rnd(10000)-5000)/70
z#=(rnd(10000)-5000)/70
try changing 70 to 70.0 and see if it makes a difference.
bubble.x could be a malformatted X file.
Can you attach that X file, or do you want to keep it private? If you want to keep it private, look through it towards the end and see if there is something that looks similar to:
Animation {
{Plane003_frame}
AnimationKey {
0;
1;
0;4;1.000000, 0.000000, 0.000000, 0.000000;;;
}
AnimationKey {
1;
1;
0;3;1.000000, 1.000000, 1.000000;;;
}
AnimationKey {
2;
1;
0;3;-0.026182,-0.229621,-0.117997;;;
}
}
Often a badly formatted animation set will cause a crash.
But there are many other things so posting the entire file would track that down.
Also, if the x file uses a texture, check for a template like:
Material Cube_Material_0 {
0.800000; 0.800000; 0.800000; 1.000000;;
0.500000;
1.000000; 1.000000; 1.000000;;
0.000000; 0.000000; 0.000000;;
TextureFileName {
"number.bmp";
}
}
After TextureFileName, there should be the name of the texture and it should be a .bmp file. Any other type may not sit well with DarkBASIC. Also, if you have MS Paint - yes MS pain specifically, often you .bmp file in it and then just save it. This will guarantee that the .bmp is formatted properly. Some high end graphics editing programs have a lot of options for outputting a .bmp file and the result may not be a pure Windows DIB which DirectX 7 can't deal with.
I'm just guessing the X file is your problem. Could your code
t=4 to bubbles+3
be that bubbles is way too high or way to low out of the range of object number?
Enjoy your day.
