"Debug Assertion" error
"Debug Assertion" error
BE 2.2.8 is giving me a "Debug Assertion" error (as seen in this post) whenever I try to open a high-vert file (such as the body model of one of my trucks). Any info on a missing file, etc.?
'Debug Assertion' applies to all problems binedit encounters and isn't really any help unless I have the model that's giving you the problem so I can debug it.
Model size shouldn't be the problem because i've opened models with over 50,000 faces before. I suspect it 'might' be a bug within the model data that's associated with it (info/bfc's). ... Try going to your models folder, locate the problem bin, highlight it and give it a new name... just add a 1 or subtract a letter, then try and open that one in binedit.
Model size shouldn't be the problem because i've opened models with over 50,000 faces before. I suspect it 'might' be a bug within the model data that's associated with it (info/bfc's). ... Try going to your models folder, locate the problem bin, highlight it and give it a new name... just add a 1 or subtract a letter, then try and open that one in binedit.
The problem with that method is that you'll loose any saved face and vert groups. You can always rename it back to the original name to regain the lost groups... but it'll crash again :/ ... D2S brought this problem up a while back and I 'think' I have the problem worked out within binedit but haven't had the chance to verify it 100%.
I'm not sure exactly what the cause is yet and probably will not know until it happens to me (again) so I can backtrack and trace the cause.
As a safety go to File/Prefferences and under the Model Data tab check the Create .info Files box. That is unchecked by default and should serve as a backup to the binary (.bfc) data of your model when checked. .info files can be imported to the .bfc incase you're forced to rename a model due to the error.
As a safety go to File/Prefferences and under the Model Data tab check the Create .info Files box. That is unchecked by default and should serve as a backup to the binary (.bfc) data of your model when checked. .info files can be imported to the .bfc incase you're forced to rename a model due to the error.
- alexmastro
- Member
- Posts: 28
- Joined: Fri Aug 03, 2007 11:39 pm