• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

A few questions

E

e.a.wicklund

Members +
I'm getting back into CFS2 after many years. I used to troubleshoot such issues with ease, but I've forgotten a lot. So please forgive some probably easy questions.

1. I have a P-40N which works great. But after exiting the mission, CFS2 does a CTD. What would cause that?

2. I downloaded another P-40N which doesn't show up to select. How to fix?

3. There was a list, I believe, where you had to enter installed aircraft to make them show up in the enemies list. What was that?

4. I got the default P-39 flyable, but I'm wondering is there a way to add a VC cockpit?
 
1. I'm not sure but something in the back of my head thinks DP hitbox and part linking related.

2. Check the Panel and Sound. If all that is in the folder is a .cfg open it with notepad and make sure you have the aircraft the the alias that the is looking for or change the .cfg text to use one the the aircraft you have.

3. The B24 Guy has you covered and then some has he has made VCs for all AI aircraft. http://www.sim-outhouse.com/sohforums/local_links_search.php?action=show&userid=105&sort=d
 
Indeed. Thanks Allen for the link. Already downloaded from there.

I am still unable to get this P-40N to appear. Sound is aliased to the P-38F, so that's okay. Panel seems fine. I tried placing a panel from a working plane in there and that didn't help.

What should I try next?
 
Check the aircraft.cfg. Make sure the sim= line is listing the name of the airfile. Also is the aircraft an AI only?
 
e.a..........

........maybe out in left field here but make sure that your P38 is titled exactly like it appears in the sound alias or vice versa. Had that problem before made the alias and the plane the id'ed the same way and the plane then worked.
 
Cripes! I just figured it out, but it's not what you'd expect. First lines of the aircraft.cfg are:

[fltsim.2]
title=Kittyhawk Mk.IV RAAF
sim=P-40N_RAAF
model=
panel=
sound=
texture=currawong
checklists=P-40n_CHECK

...see it?...

It should be:

[fltsim.0]

Finally! I can fly this baby. Thanks for jumping in to help.
 
Hey, one more thing. Both of these P-40N's are Krystoff Malinowskis. They fly great but cause CTD after the mission quits. What would be causing that? How can I fix it?
 
Hi e.a.wicklund,

Sounds like the g-lightstates or crash-check problem only way to fix is with hex edit or disassembly reassembly with SCASM.

Point me to the download and I would be happy to check it out.

Regards,
B24Guy
 
The B24 Guy said:
Hi e.a.wicklund,

Sounds like the g-lightstates or crash-check problem only way to fix is with hex edit or disassembly reassembly with SCASM.

Point me to the download and I would be happy to check it out.

Regards,
B24Guy
Click to expand...

Hi B24

It's the crash check.... there's no lightstates.



Cheers mav
 
e.a.wicklund said:
Okay. I'm not familiar with the Crash Check. How do you fix that?
Click to expand...

Like B24 said.... by hexing and scasm.

B24 has generously offered to help.... so point to download.... i can tell you now it was a PIA to do..... it does error when decompiled.

I fixed mine but also modded it so dont have org anymore.... but once fixed its good
 

Attachments

  • Untitled11.jpg
    Untitled11.jpg
    49.8 KB · Views: 1
If CFS2 gives you a CTD when exiting a free flight or quick combat session, you may want to check the allegiance number in the plane's DP file. If you are not using the extended Country.cfg file, and if the allegiance of this aircraft is set to anything else than 1, 2, 3 or 4, the game will crash.
 
Roxane-21 said:
If CFS2 gives you a CTD when exiting a free flight or quick combat session, you may want to check the allegiance number in the plane's DP file. If you are not using the extended Country.cfg file, and if the allegiance of this aircraft is set to anything else than 1, 2, 3 or 4, the game will crash.
Click to expand...

Ha! That's got it. I still have a very basic install with the standard country.cfg file. Allegiance of the plane was set to 10 (New Zealand?)
I put it to 1 and no more CTD! Out-freakin'-standing, Roxane. Thank you kindly!

Also thanks to B24Guy and your kind offer. Got it worked out it after all.

Much thanks to everyone.
 
Think 10 is for Australia.... mine was set to 3 but changed to 10...... no ctd issue.... guess its mystery to me.

Good it worked out on your end.
 
Roxane-21 said:
If CFS2 gives you a CTD when exiting a free flight or quick combat session, you may want to check the allegiance number in the plane's DP file. If you are not using the extended Country.cfg file, and if the allegiance of this aircraft is set to anything else than 1, 2, 3 or 4, the game will crash.
Click to expand...


Nice Work :applause::applause::applause:
 
You must log in or register to reply here.
Back
Top