Search the archive:
YaBB - Yet another Bulletin Board
 
   
 
Pages: 1 2 3 
Send Topic Print
Major problem with CFS2 (Read 10737 times)
Reply #15 - Apr 23rd, 2011 at 3:39am

Tango_Romeo   Offline
Colonel
Campaign Cobbler
Tennessee

Gender: male
Posts: 1184
*****
 
You did not answer my questions.  Undecided

- Does this problem occur no matter what plane you are flying and no matter what opponent is involved?   You know like a Hellcat against a Zero, or a MiG against a B-29?  Huh

- Also, did you try removing Nibbio's effects?  Huh

Here's one more as well:

- Did you follow the Fox Four instructions about entering the CFS2.CFG file and setting Stress Damage=FalseHuh

Give us some info so we can help.   And BTW this problem has nothing to do with the AI MiGs...believe me.  Roll Eyes

 

Many Hands Make Small Work ... P-51 Contract Lost - Build Swifts

FLY FOX FOUR KOREA: http://www.simviation.com/lair/cfs2korea.htm GET FOX FOUR EXTRAS: http://www.simviation.com/lair/cfs2kwextras.htm
IP Logged
 
Reply #16 - Apr 23rd, 2011 at 2:45pm

investdude   Offline
Colonel
Chilliwack, BC Canada

Gender: male
Posts: 60
*****
 
Yes, TR, I did set Stress Damage=False in the CFS2.cfg file.  At the moment the problem is not happening except with the CA-27, after a reinstall.  I thought it was Nibbio's effects I had installed but now I'm not sure.  I'm trying to find the effects so I can properly remove them.  Not sure if I've found them yet.  Everything had been working fine for a long time, so I now don't think it is a problem with CFS2 itself, I think it may be a computer issue. Undecided  I'm working on it.  Thanks for all the help.
 
IP Logged
 
Reply #17 - Apr 23rd, 2011 at 6:38pm

Tango_Romeo   Offline
Colonel
Campaign Cobbler
Tennessee

Gender: male
Posts: 1184
*****
 
OK, just trying to make sure the bases get covered.   Troubleshooting via board posts is not the best way to go about it.  Cry

Keep us posted on your progress.  Smiley
 

Many Hands Make Small Work ... P-51 Contract Lost - Build Swifts

FLY FOX FOUR KOREA: http://www.simviation.com/lair/cfs2korea.htm GET FOX FOUR EXTRAS: http://www.simviation.com/lair/cfs2kwextras.htm
IP Logged
 
Reply #18 - Aug 3rd, 2011 at 7:43pm

investdude   Offline
Colonel
Chilliwack, BC Canada

Gender: male
Posts: 60
*****
 
UPDATE

After 3 ½ months, a reinstallation, a separate install, and many theories tested without success I have come to the end of my rope.  After enjoying CFS2 for 11 years it’s now impossible to fly Quick Combat or missions at all so CFS2 is basically unusable for me.  I know what is NOT causing the problem but not what is.  It appears to be associated with the ACONTAIN.DLL file.  If I reinstall the acontain.dll file from Disc1 the problem disappears for 1 or 2 shoot downs, then reoccurs with the following info:
Error Signature
App. Name CFS2.exe
App. Ver. 7.50.0.917
Mod. Name acontain.dll
Mod. Ver. 7.50.0.917
Offset 000044d2

It refers to an error report file but that file doesn’t exist.

I have 71 aircraft in my aircraft folder so it’s not the 100 aircraft bug.  I found some info online that acontain.dll has caused some problems with FS9 (unable to run) but nothing is mentioned about CFS2.  I’ve tried absolutely everything without success.  If anyone has any ideas at all, I’ll try anything, but I’ve run out of ideas myself and it looks as though, with much regret, I will have to close down CFS2 for ever. Cry
 
IP Logged
 
Reply #19 - Aug 3rd, 2011 at 8:33pm

The_Editor   Offline
Colonel
My god! Look at the size
of those sabrinas!
Llanelli, Wales

Gender: male
Posts: 83
*****
 
investdude wrote on Aug 3rd, 2011 at 7:43pm:
UPDATE

After 3 ½ months, a reinstallation, a separate install, and many theories tested without success I have come to the end of my rope.  After enjoying CFS2 for 11 years it’s now impossible to fly Quick Combat or missions at all so CFS2 is basically unusable for me.  I know what is NOT causing the problem but not what is.  It appears to be associated with the ACONTAIN.DLL file.  If I reinstall the acontain.dll file from Disc1 the problem disappears for 1 or 2 shoot downs, then reoccurs with the following info:
Error Signature
App. Name CFS2.exe
App. Ver. 7.50.0.917
Mod. Name acontain.dll
Mod. Ver. 7.50.0.917
Offset 000044d2

It refers to an error report file but that file doesn’t exist.

I have 71 aircraft in my aircraft folder so it’s not the 100 aircraft bug.  I found some info online that acontain.dll has caused some problems with FS9 (unable to run) but nothing is mentioned about CFS2.  I’ve tried absolutely everything without success.  If anyone has any ideas at all, I’ll try anything, but I’ve run out of ideas myself and it looks as though, with much regret, I will have to close down CFS2 for ever. Cry


Have you seen this thread?

http://flyawaysimulation.com/forum/topic/10455/mayday-mayday-mayday/
 

Eala Freya Fresena - Lewwer Duad üs Slaav
IP Logged
 
Reply #20 - Aug 4th, 2011 at 12:50am

investdude   Offline
Colonel
Chilliwack, BC Canada

Gender: male
Posts: 60
*****
 
Have you seen this thread?

Yes, but it pertains to FS9 and the link to another copy of acontain.dll doesn't work, so no help.
 
IP Logged
 
Reply #21 - Aug 4th, 2011 at 9:44am

H   Offline
Colonel
2003: the year NH couldn't
save face...
NH, USA

Gender: male
Posts: 6837
*****
 
This may not help but this type of problem isn't restricted to CFS2 (although I don't play CFS2 so often and it hasn't occured while doing so) -- I've encountered it a number of times with CFS1 missions (rarely engage Quick Combat). Sometimes I could play through the mission after a mission restart, more often needing a CFS restart, sometimes needing to reboot the computer to play through. I'm not sure it is of note but it seems to have begun only after connecting the computer to the internet (in the past I've had at least two used computers that I'd revamped -- new or reformatted hard drives -- and the game computer was never online and I don't recall any such problem). However, during this time I'd also added other programs to the system, so it may not be on-line internet related (unless you disable your network connection you may still be connected to the internet) but quite possibly some programs will take advantage of in stealth mode.
Basically, as has already been suggested, there may be a resource issue;  in a resource problem, it may be a corrupted file not within CFS/2.



Cool
 
IP Logged
 
Reply #22 - Aug 4th, 2011 at 9:45am

Dirtman   Offline
Colonel
Rabid Enthusiast / Plane
Insane
Toronto Canada

Gender: male
Posts: 40
*****
 
Yo investdude:

I'm getting in here a little late but a few things have come to mind after reading the previous posts in this thread so I've got some suggestions.  Please forgive me if I'm being "overly simple" here as I just want to cover ALL THE POSSIBILITIES that I think have not yet been addressed.


investdude wrote on Aug 3rd, 2011 at 7:43pm:
UPDATE

After 3 ½ months, a re-installation, a separate install, and many theories tested without success I have come to the end of my rope.  After enjoying CFS2 for 11 years it’s now impossible to fly Quick Combat or missions at all so CFS2 is basically unusable for me.  I know what is NOT causing the problem but not what is.  It appears to be associated with the ACONTAIN.DLL file.  If I reinstall the acontain.dll file from Disc1 the problem disappears for 1 or 2 shoot downs, then reoccurs with the following info:
Error Signature
App. Name CFS2.exe
App. Ver. 7.50.0.917
Mod. Name acontain.dll
Mod. Ver. 7.50.0.917
Offset 000044d2

It refers to an error report file but that file doesn’t exist.


(1)
In the main CFS2 folder, look for the file: error.LOG
- open it with "Notepad"

What does your "error.LOG" file say?  PLEASE post a copy of all info contained in it to this thread.



investdude wrote on Aug 3rd, 2011 at 7:43pm:
I have 71 aircraft in my aircraft folder so it’s not the 100 aircraft bug.
 

(2)
Fair enough BUT ... open each aircraft folder & count the TOTAL number of "texture" folders for each aircraft.

Any aircraft having more than one "texture" (or "skin") will count as an additional aircraft.  You might have 71 a/c folders, but if each one has 2 skins - then you actually have 142 a/c installed and therefore have exceeded the "100 plane limit". 

I'll bet you 10 "virtual beers" you'll find you actually have more than 71 a/c installed.



investdude wrote on Aug 3rd, 2011 at 7:43pm:
I found some info online that acontain.dll has caused some problems with FS9 (unable to run) but nothing is mentioned about CFS2.  I’ve tried absolutely everything without success.  If anyone has any ideas at all, I’ll try anything, but I’ve run out of ideas myself and it looks as though, with much regret, I will have to close down CFS2 for ever. Cry


I suspect the "acontain.dll" issue is the result of this problem rather than the cause.  If replacing it cures the problem temporarily - then something else is affecting it.

If the previous 2 suggestions do not help; then try this:

(3)
In the main CFS2 folder, locate and delete the six "INDEX" files. All will be regenerated the next time you open CFS2.

AIRWAY_INDEX
ICAO_INDEX
INDEX_FILE
LAT_INDEX
STR_INDEX
WAYPOINT_INDEX

Open CFS2 & recheck for the problem.  Does it still exist?

- if it's fixed; then yer buying the beers tonight !!
  Cheesy
- if not; then we'll need to move on to "Round 2"
  Wink

- Dirtman



 

CFS2 Fulfills my need to "peacefully" blow things up
IP Logged
 
Reply #23 - Aug 4th, 2011 at 12:52pm

investdude   Offline
Colonel
Chilliwack, BC Canada

Gender: male
Posts: 60
*****
 
Thanks for your input Dirtman!

I did as you suggested and here are the results:

(2) I checked all my aircraft folders.  A few, 5 or 6, have more than one texture folder, however, alternate texture folders have to be activated in the aircraft.cfg file and I have only one texture activated per aircraft.  If I want to change a texture I make the change in the aircraft.cfg file.

(3)  I deleted the 6 index files.  When I opened CFS2 it started to regenerate the files but then crashed.  When I opened it again the files were there okay.  I ran QC and as soon as I destroyed a Mig the sim crashed.

(1)  Here is the error log file:

[Mission file error]
error=Unable to init unit 1000
title=Quick Combat
filename=C:\Program Files\Microsoft Games\Combat Flight Simulator 2\qc

I wish I could be buying the beer! Tongue
 
IP Logged
 
Reply #24 - Aug 4th, 2011 at 1:46pm

H   Offline
Colonel
2003: the year NH couldn't
save face...
NH, USA

Gender: male
Posts: 6837
*****
 
Has this happened to you in mission play?



Cool
 
IP Logged
 
Reply #25 - Aug 4th, 2011 at 1:59pm

investdude   Offline
Colonel
Chilliwack, BC Canada

Gender: male
Posts: 60
*****
 
To H:

Yes, it's same problem in missions.
 
IP Logged
 
Reply #26 - Aug 4th, 2011 at 2:06pm

H   Offline
Colonel
2003: the year NH couldn't
save face...
NH, USA

Gender: male
Posts: 6837
*****
 
Just a thought... if you get a unit load error report, open the mission (.mis) file and see if it's listed and what the unit is.



Cool
 
IP Logged
 
Reply #27 - Aug 5th, 2011 at 8:35am

Dirtman   Offline
Colonel
Rabid Enthusiast / Plane
Insane
Toronto Canada

Gender: male
Posts: 40
*****
 
investdude wrote on Aug 4th, 2011 at 12:52pm:
Thanks for your input Dirtman!

I did as you suggested and here are the results:

(2) I checked all my aircraft folders.  A few, 5 or 6, have more than one texture folder, however, alternate texture folders have to be activated in the aircraft.cfg file and I have only one texture activated per aircraft.  If I want to change a texture I make the change in the aircraft.cfg file.


Good work!




investdude wrote on Aug 4th, 2011 at 12:52pm:
(3)  I deleted the 6 index files.  When I opened CFS2 it started to regenerate the files but then crashed.  When I opened it again the files were there okay.  I ran QC and as soon as I destroyed a Mig the sim crashed.


CFS2 should not have crashed during the INDEX file regeneration point - this could be a clue to the cause of the problem





investdude wrote on Aug 4th, 2011 at 12:52pm:
(1)  Here is the error log file:

[Mission file error]
error=Unable to init unit 1000
title=Quick Combat
filename=C:\Program Files\Microsoft Games\Combat Flight Simulator 2\qc


In QC, "unit 1000" is the player aircraft.  CFS2 seems to be trying to regenerate the PLAYER a/c.  This is odd UNLESS you are flying the same a/c (a MiG) as you are shooting down. I would be inclined to believe that this situation is what is causing CFS2 to crash

If this problem was only occurring in QC, I would suspect the QC mission file is damaged.  But you have said it happens in regular missions too ... so the common element here is either the MiG or the player aircraft.

First: Fly a regular mission using these a/c, let CFS2 crash and then recheck the "error.LOG" and post the info here. - let's see if the info (cause) is the same as in QC

I would substitute different player & target a/c & retest for the problem in both mission & QC.

Past this I would try:

- in the OBJECTS_DP folder: delete ALL CDP's again.

- in the SCENEDB folder: open ALL "scenery" sub-folders and delete ALL "filelist.dat"'s


- delete the 6 INDEX file once again.

Reopen QC & retest


investdude wrote on Aug 4th, 2011 at 12:52pm:
I wish I could be buying the beer! Tongue


Be patient ... you WILL!!!
   Grin


- Durt
 

CFS2 Fulfills my need to "peacefully" blow things up
IP Logged
 
Reply #28 - Aug 5th, 2011 at 4:42pm

investdude   Offline
Colonel
Chilliwack, BC Canada

Gender: male
Posts: 60
*****
 
Durt,

I started to follow your suggestions, flew a KW mission till I got a kill and the Sim crashed.  Then I noticed that the error.log file was dated middle of July and had not changed.  So I deleted the error.log file, assuming a new one would be generated at the next crash.  I flew a QC mission and killed 2 migs without a crash but on the next kill the Sim crashed.  But there was no error.log file regenerated.  The events.log file was current and correct.  So I don't understand what's going on.  I'm at work now, will be too busy to do anything for a day or so but I will keep working on it, try all your suggestions and report back ASAP.  Thanks for all your help.
 
IP Logged
 
Reply #29 - Aug 6th, 2011 at 4:42pm

investdude   Offline
Colonel
Chilliwack, BC Canada

Gender: male
Posts: 60
*****
 
Had a little bit of time today so here's what I've done:

I don't think the error.log file previously posted means very much since it was dated the middle of July. The question for me is why doesn't the sim generate another error.log file when it crashes?  I looked at the CFS2.cfg file under Preferences and it gives:
ERROR_FILE=
It should read ERROR_FILE=ERROR.LOG
so I changed it to read ERROR_FILE=ERROR.LOG and flew a QC, sim crashed but no error.log file. I have a backup copy of CFS2.cfg, so I checked it and it also showed under Preferences, ERROR_FILE=

I deleted all the CDPs in the OBJECTS_DP folder, all the filelist.dat files in SCENEDB folder and the 6 INDEX files.  This time when CFS2 was run it did NOT crash when it regenerated the 6 INDEX files. But otherwise there was no change.  I ran another QC and the sim crashed as usual.

BTW, I have a force feedback joystick and when When the crash occurs the force feedback runs continuously so at one time I thought it might be a forcefeedback problem but I got a non-forcefeedback stick and tried it and there was no difference except of course that the FF didn't run.

So it seems to me now that in order to be able to move forward I have to get the Sim to generate an error.log file so we can see what's happening but I don't know how to do that. Could it be that as far as the Sim is concerned the acontain.dll is doing what it's supposed to do and therefore there is no error?  I just don't know what's going on.
 
IP Logged
 
Pages: 1 2 3 
Send Topic Print