Closed Subject9x closed 5 years ago
It's impossible to tell from the information provided here, but I would expect that one of your md3's contains an empty shader path or something along those lines. I'll try to make TB more robust against that.
It's impossible to tell from the information provided here, but I would expect that one of your md3's contains an empty shader path or something along those lines. I'll try to make TB more robust against that.
gotcha, I played around with the md3's that I exported and I noticed that some of the control files don't have a $skin value. I am using the .skin files to do different skins on the md3, which is probably what's causing the headache.
where does TB assume the model's shader path should be?
TB doesn‘t read the .skin files. It also does not support multi part md3 files connected by tags.
ah ok, thanks for the info. I'll keep tinkering with my .MD3s and will test again when you have the next release. You can close this issue if you want.
battleMETAL.zip dbg_trunch2-crash-5.txt dbg_trunch2-crash-5.log
Possibly its my .md3 files acting the mickey on this. I'm attaching my mod's .def file and .cfg file for reference too. Let me know what I can do to help debug :)
System Information
e.g. TrenchBroom V2.0.0-RC4 on Windows 10
Expected Behavior
load .md3 models from entity .def file
Steps to Reproduce
1) create battleMETAL game folder in /games 2) load a battleMETAL map 3) go to 'Entities' Tab
Crash Info