FSIC Messageboard
  SDOE General
  Problems with the Hs 129

Post New Topic  Post A Reply
profile | register | preferences | faq | search

UBBFriend: Email This Page to Someone! next newest topic | next oldest topic
Author Topic:   Problems with the Hs 129
Maury Markowitz
Pilot
posted 06-06- 07:37 AM     Click Here to See the Profile for Maury Markowitz   Click Here to Email Maury Markowitz     Edit/Delete Message   Reply w/Quote
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.

IP: Logged

Pachy
Pilot
posted 06-06- 07:45 AM     Click Here to See the Profile for Pachy   Click Here to Email Pachy     Edit/Delete Message   Reply w/Quote
Check the squadron. JG400 is definitely not a squad that came with the game. You should not create missions with it, unless installing your plane also installs the squad. If I remember well this squad was installed by the Me 163.

IP: Logged

Aladar
Pilot
posted 06-06- 09:22 AM     Click Here to See the Profile for Aladar   Click Here to Email Aladar     Edit/Delete Message   Reply w/Quote
Pachy is correct, JG400 is a squadron I included in my 163 Pack, unless you don't have the 163 pack I dont see why it should mess up like that though.

IP: Logged

Maury Markowitz
Pilot
posted 06-06- 09:46 AM     Click Here to See the Profile for Maury Markowitz   Click Here to Email Maury Markowitz     Edit/Delete Message   Reply w/Quote
quote:
Originally posted by Aladar:
Pachy is correct, JG400 is a squadron I included in my 163 Pack, unless you don't have the 163 pack I dont see why it should mess up like that though.

Ok guys, I'll try another squad. Or maybe I'll make a schlatjager squad at some point.

You're right that this shouldn't cause a CDT but it seems to me that _mot_ CDT problems I've seen reported here are mission related.

Anyone know about the internals of the SM though? Do I need to change thos references from "hs129" to "hs129b3" if I rename the folder?

Maury

IP: Logged

wakeup tailgunner
JAG
posted 06-06- 10:47 AM     Click Here to See the Profile for wakeup tailgunner   Click Here to Email wakeup tailgunner     Edit/Delete Message   Reply w/Quote
If you change the directory name, you will have to change any texture references to point to the new folder. Also, if you have a hangar mission, this must be renamed to match. Otherwise, you should be o.k.

------------------
=V67=

IP: Logged

Maury Markowitz
Pilot
posted 06-06- 12:24 PM     Click Here to See the Profile for Maury Markowitz   Click Here to Email Maury Markowitz     Edit/Delete Message   Reply w/Quote
quote:
Originally posted by wakeup tailgunner:
If you change the directory name, you will have to change any texture references to point to the new folder. Also, if you have a hangar mission, this must be renamed to match. Otherwise, you should be o.k.

Ok, so it SHOULD work. I'll assume the problem is squadron related then. But when you say the mission should be renamed to match, match what exactly? The name of the folder it's in, or the name of the .sm file?

Maury

IP: Logged

wakeup tailgunner
JAG
posted 06-06- 02:00 PM     Click Here to See the Profile for wakeup tailgunner   Click Here to Email wakeup tailgunner     Edit/Delete Message   Reply w/Quote
for the hangar mission, it must have the same name as the folder.

------------------
=V67=

IP: Logged

All times are CT (US)

next newest topic | next oldest topic

Administrative Options: Close Topic | Archive/Move | Delete Topic
Post New Topic  Post A Reply
Hop to:

Contact Us | Fighter Squadron Information Center

(This site Copyright (c) 1999 Inertia LLC)

Powered by Infopop www.infopop.com © 2000
Ultimate Bulletin Board 5.45c