Stopping it from crashing

#1 Does the vehicle get removed? Ie did you add it to the MissionCleanUp sim group?

#2 Hmm, it's difficult to say where the problem is w/o the specifics, but if you're trying to debug the script, you can add echo() statements to follow the process.

#3 The thing is its definately a C++ problem, most likely memory.

Yes the vehicle does get removed with the MissionCleanUp.

The datablock itself is defined privately in the WheeledVehicle Class as:

WheeledVehicleEngine* engine;

And is defined by using %vehicle.setEngine(%engineDataBlock);
I have coded all the correct net coding and such for it and it works great in game, but when it comes to shutting down it crashs most of the time, so I am guess I haven't removed or cleared it correctly?
If so, where/how would I?

#4 I don't recall having to make an engine for the wheeled vehicle

there should be
wheeledvehicledata (the car it self)
springvehicleData( the car's springs)
wheeldata (the cars wheel)

now you can associate the engine throttle to each wheel, creating 2/4/x wheeled drive but add a unique engine, either you modified the code, the code has changed (which I haven't heard about), or you are doing something wrong. be sure you are creating the car, similar to the buggy demo.

#5 Thats what I am saying, I have modified the code and it loads a set datablock called wheeledvehicleengine, which gives an accurate torque curve.

I just don't know how to remove the datablock correctly when the object is removed/destroyed.

#6 Ahhhhhhhhhhhhhhhhhhhhh

Well that would go in the WheeledVehicle deconstructor, in C, I would presume look how wheels are removed and emulate it

#7 You shouldn't need to remove the datablock when the object is removed...