Author Topic: Blender DTS Exporting causing a crash?  (Read 2107 times)

So recently, me and The Corp. sent over models for the Blockombat Pack and they crash Blockland apparently. What ahppens is that the console loads the .cs and then it crashes. The thing is, is that it worked fine before, but I recently had a change in computer. The old computer had forgeted up installs and it was easier to export (I never needed detail32 or shape empties, lol) and it worked fine. I got this new computer and did EVERYTHING right this time. Now its harder to get this running for Blockland. We both use Blender and we have done EVERYTHING correctly (at least to my knowledge). I need to know EXACTLY the processes in the exporting of DTS's (e.g. what things should be on/off in the export menu). I think we exported it wrong and some processes got forgeted up. I have done everything in my power to keep everything par none to the tutorial. PLEASE help, this is irritating.

I think we should export a shape script.

EDIT-Just asked FrogFreak for help.
« Last Edit: June 10, 2011, 08:52:55 PM by The Corporation »

I think we should export a shape script.

EDIT-Just asked FrogFreak for help.

Shape script does nothing. It just makes a little script txt thing. I tried it myself.

Parent ALL your bones to detail32. Get back to me if that doesn't fix it.

detail32 is an empty to which all bones should be parented and detail32 should be parented to shape empty. Also try replacing the sword model instead of a custom script and see if it works.

EVERYTHING is on the Detail32, I have no doubts whatsoever on that. The thing is that it crashes trying to load up the .cs, but it isnt the script, it's it attempting to access something it can't, therefore it crashes for some reason. I have a feeling it might be x64 bit Blender with a x64 bit Python 2.6.3. Perhaps x64 bit just hates torque. FML.

EVERYTHING is on the Detail32, I have no doubts whatsoever on that. The thing is that it crashes trying to load up the .cs, but it isnt the script, it's it attempting to access something it can't, therefore it crashes for some reason. I have a feeling it might be x64 bit Blender with a x64 bit Python 2.6.3. Perhaps x64 bit just hates torque. FML.
No. Only the bones should be parented to detail32. The model itself doesn't have to be. 64 bit works just fine. I have Win7 64bit.

No. Only the bones should be parented to detail32. The model itself doesn't have to be. 64 bit works just fine. I have Win7 64bit.

Oh. Whoops.

EVERYTHING is on the Detail32, I have no doubts whatsoever on that. The thing is that it crashes trying to load up the .cs, but it isnt the script, it's it attempting to access something it can't, therefore it crashes for some reason. I have a feeling it might be x64 bit Blender with a x64 bit Python 2.6.3. Perhaps x64 bit just hates torque. FML.

I remember having the same problems. I have a 64-bit system too (Win7) but I'm using the 32-bit Blender for exporting, because when I exported with the 64-bit version, the models crashed BL. So you should probably try the 32-bit version too and see if it works.

How on earth would exporting the model with a 64-bit modeling program affect the model itself in any way?

How on earth would exporting the model with a 64-bit modeling program affect the model itself in any way?

OS compatibility with the exporter.

OS compatibility with the exporter.
Sure that could cause Blender to crash, but if your models crash BL there is something wrong with the model not the fact that you have 32/64 bit system.

Sure that could cause Blender to crash, but if your models crash BL there is something wrong with the model not the fact that you have 32/64 bit system.

Ok, only the bones are parented, but my textures wont export becaues they aren't in the UV/Materials list. :C

Ok, only the bones are parented, but my textures wont export becaues they aren't in the UV/Materials list. :C

Parent the model to detail32.

Parent the model to detail32.

Ok stop giving me to different stories. I have parented EVERYTHING together before hand. Does the mesh need to be one contiguous model?