posted 06-06- 07:37 AM
I haven't had a lot of time to work on this plane due to travel, but I sat down for 15 minutes with it this morning to try to get it up and flying on my machine.Every attempt to start up the hanger mission (which works fine on Jay's machine) CDT's on mine. Can someone list the things that will cause the causes of CDT's that are mission related?
I had been in the process of re-writing the loadouts and getting ready to split the plane into to, the B-3 (which is that the model is for) and the more common B-2 version. In the process I renamed the folder and the .sm file. I also looked inside the .sm and found all sorts of references to the older name, including this one right at the top...
/borg/Art/sdoe/media/aircraft/hs129/hs129.sm
That appears to be a complete path, anyone know what that's all about?
There are also a number of other references to the name in the file, should I change all of these? Does anyone know if the string length is saved into the file as well?
I also renamed the .MIS file to the same thing (hs129b3.mis), is that correct? How does the game engine find the mission it wants, is it the one with the same _.sm_ name, or the one with the same name as the _folder_ it's in?
Inside the mission I found only two references to the name of the plane, here:
langUS ( msnName "Hs 129" )
and here:
msnJG400 ( msnCount 1 msnAircraft "Hs129" msnFormation "strVIC" msnLoadOut "Guns" [snip]
I assume the former is a display-only string, does it need to be changed? What about the second one?
Of course I have changed all of these references, but still no luck.