• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA Corrupt modeldef

Zeiten

Resource contributor
Messages
444
Country
norway
Hi.

Think I've have a corrupt modeldef.xml file now.

The problem is that any new part that are animated and tagged does not show in the sim anymore.

Tried a little test now with a part that was showing and working.
Made a second copy and tagged the same part with the same animation tag and the new part does not show in the sim.

Have not got any warning during export or in the buildlog.txt file after converting to mdl.

This thing is driving me mad and was wondering if you have any tips in regard finding the problem?

Cheers
 
Hey Zeiten,

Wozza taught me a cool trick. Open the ModelDef XML file in Windows Explorer and it 'should' show you the fault. I believe Safari will do the same thing and 'should' show you the exact line that is at fault.


Hope that helps.


For me, having had alot of these faults in the past, I would backup the XML often so I could back track.

Another thing you can do is to copy the file off (make a backup) and then start deleting sections (if you created alot of sections) until the file starts working again. (Track down the bad animation section).


Bill
 
Thanks.

Thats what I was affraid of.
The file opens just fine in opera so then its just a matter of deleting off sections of codes.

Backup you say... Think the last one is from 2 months ago.
You know the feeling of hey, im starting to get grips of this. I dont need no backup anymore... Well.
My fault..

Cheers :rolleyes:
 
Is it possible that it's the max file that been corrupted?

2 parts that was missing was found another place in the model all twisted and stretched.

Took one part that was working
- Removed the animation from that part
- Saved the file and exported.
The part showed up in FSX.

Reanimated the part using the same code and it still showed after another re export.

Deleted that part, made a copy of another part and re tagged the new part with the old code and now it does not show anymore.

Can't come up with a logical explanation to why this is happening.
All I can tell is that 1 week ago I moved to a new rig, but the problem fist started last night.
 
First; using Opera should not show the issue. You need to use 'Microsoft IE' to find the faults. Sometimes, Apple Safari will find them. Opera usually will not. So use IE to find fault points in XML code.


Second. When a part stretches during its animation, it has done two things; a scaled part has gotten through the compile without a crash --and-- where a part cannot scale through an animation, but it did. So.... If you can get that part back via older save points, bring it back in, click Hierarchy tab and select 'Reset Scale' in the right control box menu. When its scale is cleared, it should operate properly.


Give those a try.
 
Opera will in fact show any faults in the XML, but thats not the case here.

Tried using some older save points with some sort of success.

The parts thats was missing are now showing, BUT after some more work on the model new parts are starting to missing.

Are there any limit to the exporter in regards to number of parts or animations?
 
Watch out for spelling and code tag errors.

MakeMDL refuses to parse any entries beyond a corrupted one. XToMDL might behave similarly.
 
Thats a good point. I have had parts not animate that had the same exact name that other parts had... like l_tire and l_tire, door handle and door handle. The exporter usually will warn you when parts have duplicate names.. Adding numbers to the back will help.

Give Microsoft IE a try. This is the last time I ask. ;)
 
The funny thing is that after I used an older backup file and keept working onward I used an copy of a cylinder to be used to display EPR setting.

It was 3 cylinders total.
2 of them showed up and the last one did not.
Even If they all used the same "clone" and same code as I controlled then using different keyframes.

Bill, no difference when checking the XML in IE.
It opens just fine without any error.

Sometimes before I have some error and misspelling and then the exporter fails and I can usually find the error with buildlog.txt, but now it's nada.
 
Why not give up on the cloning a part approach and just make a new part? Sometimes parts get an "attitude" ;)
 
Maybe a far shot, but are you using the mirror tool from the top menu by chance?
This one doesn't do too well. If you need to mirror stuff better use the mirror modifier from the dropdown list.
 
No, are not using the mirror tool from the menu list :(
 
Last edited:
Hmm, has your part a skinned mesh animation?

Other than that, standard methods of fixing a corrupted geometry goes as follows:
- unlink the offending part from all parents and children, convert to e-poly or e-mesh, go to the utilites tab and hit the "reset xform" button, next convert to e-poly or e-mesh again. downside is that you need to re-align your pivot again if it's not aligned to world by default.

....or.....

Create a box or any other basic primitive and attach the offending part to it, next select it in subobject mode "element" and detach it again.
If you want to keep the parts original pivot orientation align the box first using the align command from the "edit" menu with the reference coordinates system set to world. Make sure to also check the rotation checkboxes in the align dialogue.

If all the above doesn't help it's a good bet to say that there's something wrong with your export module or your modedef. :eek:
 
No, no skinned mesh.

I really don't think there are anything wrong with any of the parts.
Yesterday I was making 3 planar to be used in visual conditions.
Made 3 copies and as many times before only the 1. one was showing.
Deleted the second and third one and created 2 new planar and tagged them with the same code and still no show.

But today after a recompile of the model all parts show again.
To me its a mystery :S

But at least now it's working again.
Something magical fixed it over night :p
 
Back
Top