Wrong Mesh names

[RAVEN]

Question: What happens (asfar as flight) if the FM (Data.ini) has the wrong mesh name, (ModelNodeName=) And the wrong Parent Component Name? Besides the decals not showing if you use the mesh names from the FM. [i use the mesh names from the .out file for decals].

[Fubar512]

Question: What happens (asfar as flight) if the FM (Data.ini) has the wrong mesh name, (ModelNodeName=) And the wrong Parent Component Name? Besides the decals not showing if you use the mesh names from the FM. [i use the mesh names from the .out file for decals].

 

The FM is mostly virtual, though the use proper mesh names is important in as far as animations and physical damage modeling is concerned.

[RAVEN]

OK Thanks . I'm going to check the animations. AC In Question Is the P-51D-30 It looks like the FM is for the P-51D, but the .out's are diffrent.

[Wrench]

don't forget there's 2 different LODs for Wolf's Mustang ... v2 and v3. V3, the newer/better one has slightly different mapping, so some skin issues may present themselves (mostly around the prop blade and landing gear, and the exhaust stack not being mapped to anything -which was fixed by your's truely via a decal)

 

There's also another, even olde version still avialable here, thats completly different again (mapping is more like CFS/IL2), and most assuredly NOT compatable

 

wrench

kevin stein

Edited May 16, 2010 by Wrench