• 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.

Weird CTD issue...

MaskRider

MaskRider

Tiller of Soil
Hi guys,

I am experiencing kind of a strange phenom.

If I try to "Fly now" from the free flight start screen to certain airfields I get a couple of error messages and then a CTD. Mind you it is only for certain airfields. At the moment, just one that I am aware of, DEI Kornasoren or any of the airfields on Noemfoor Island. And this was happening before I started reworking it.

Whats also kind of odd, if I go to some other airfield and do a "world->go to" to Kornasoren or any of the other airfields on Noemfoor, everything is OK.

Anybody have experience with something like this?

Below is what the error messages look like. The one on top comes up first, then, if you click "OK", the one on the bottom. If you click "cancel" you just get a CTD.

Thanks,
MR

PS The loading bar gets about halfway accross before the message comes up.

PPS: If, you do the "world->Go to" to Kornasoren from another airfield and then end the flight and try to "Fly Now" to Kornasoren again from the FF Start screen, it works OK. However, if you close CFS2, open it again and try to "Fly Now" to Kornasoren out of the FF start screen-> CTD.
 

Attachments

  • cfs2-ctd-message.jpg
    cfs2-ctd-message.jpg
    81.8 KB · Views: 3
Dreadful!

Oh, Lord!....:cower:

I got the very same encrypted messages of 'the memory could not be "read"....' everytime I screwed up one of my GG-style exhaust effects, entering wrong numbers for one side of the aircraft vs. the other side. Copy n' paste errors for the sake of cutting down time, which changed a positive number to a negative or even placed two minus signs in front of an effect coordinate.

I also had the same problem when using a gauge I didn't know it was corrupt. In this case, it was not a constant behaviour, as my CFS2 would either CTD directly to an empty, black screen or spit out such error messages, before locking up altogether.

I think those CFS2 system messages do not actually mean anything, apart from CFS2 telling you that the error encountered was so unusual that a proper explanation is beyond any CFS2 capability to offer one.

The problem might not be caused by your new scenery. Have you tried different planes with the same scenery?

Did you recently change something in those planes, like an updated dp or panel.cfg? Your only option is tracing back carefully what you did before the problem flared up, if you remember it.

Cheers!
KH :ernaehrung004:
 
if you remember it.
Click to expand...

Hehe, not much chance of that happening!
stupid.png


Thanks for the ideas KH. Yeah, one of these days something is going to click and suddenly a light will go on. :icon_idea: Until that day, guess I'll just have to muddle along and live with it!

I did notice one thing when fooling around with the source files for the old Noemfoor airfields- the runway surfaces were coded incorrectly. But alas, even after correcting the problem persists. At the moment the coding of the Noemfoor airfields is a mongrel mix of old and new. After the rework is complete and all the coding is spanking new perhaps the problem will go away.

Cheers,
MR

PS I don't think it could be the planes. I fly a very limited selection and they have all be set up the same way for ever.
 
MR......

.......I just tried to go from that field and I get the same result, a CTD. Now I am nowhere qualified to offer a utterance on this subject to you, butttttttt.......... it seems if I try Kamiri or any of the other DEI fields for Noemfoor I get the same result. Those fields are identified in my index as GSL fields. Could there be a problem with the GSL?
 
Fibber said:
.......I just tried to go from that field and I get the same result, a CTD. Now I am nowhere qualified to offer a utterance on this subject to you, butttttttt.......... it seems if I try Kamiri or any of the other DEI fields for Noemfoor I get the same result. Those fields are identified in my index as GSL fields. Could there be a problem with the GSL?
Click to expand...

Hiya Fibber,

Thanks for checking that out.

The GSL in the name was just a short hand way to identify the scenery as having GSL scenery objects included. Must have been back in the olden days when GSL scenery was a recent development. I can't imagine that it is a issue with the GSL- or a scenery object there in the GSL. There isn't anything special there. Just normal CFS2 scenery objects. One way to find out though would be to fly there with an empty GSL loaded and see what happens.

I don't think its anything major. Its got to be something really simple. That coding error in the runway surface was odd. Yet it doesnt crash when you go there from another airfield. Its a mystery- for now anyway.

It does make testing out this new scenery for Noemfoor a bit of a pain.

Cheers,
Chris
 
You got me thinking about it Chris. Problems here also, but i wouldn't blame the GSL hookup. Like you, i can load it with some "convolutions", but it also conflicts with the '9th FS bases' Kornasoren. Landclass and coastlines are redrawn and the coords are different, puts the 9th FS base in the sea -- an understandable problem that can occur anywhere with two distinct scenery installs. So we know that we can't use this installation with the same sim install containing the 9th FS campaign. Also, i can't get any of the MR DEI_GSL_090912 bases to show in the scenery selection drop down, nor the advanced goto.

To add further drama, once activated, this entire install is one of the few which causes a new scenery temp file to regenerate every time i load the sim. They have two or three letter names like C1, BA, B3, etc., and they can really add up over time unless deleted. The sim re-indexes with every fresh loading...slow starts not good. Usually indicates a quirky scenery bgl -- airfield, landclass, waterclass, excludes, what have you. Looks like it could have been a good one, but i'm gonna have to put this package on the shelf for now Chris...hope you can find a cure.
 
Last edited:
Rule out gsl........

.....MR :wavey:, you can rule out GSL as a culprit. I tried it with and without GSL and same result....black screen. I will now go back in my corner and sulk.:biggrin-new:
 
Forgot to mention, my CTD's result in a message stating that the error was encountered by the facilities.dll module, which definitely indicates a bgl issue.
 
about "bad" bgls & hard code runway total ...

MR,

I got a similar thing when I redid your Woleai airstrip as part of my Carolines scenery. I couldn't QC or FF from it (CTD on loading scenery), but I could spawn away from it & then fly to it & land?:banghead:
In the end I assumed it was some mistake in the bgl (but I couldn't find it), or simply that CFS2 didn't like the idea of a runway crossing the corner intersection of LOD scenery areas (IIRC).

BC,

I had the issue you describe quite some time ago. I would create new airstrips & they wouldn't show. Then I noticed CFS2 "growing" temp scenery files, each time I ran the game. I concluded the hard code limit of 200 runways was the issue.
Once you get to 200 runways+, I see the following effects:

Free Flight & Quick Combat can be used, but not all runways show
The temp scenery files start to show - I think this is a correctly configured scenery.cfg forcing the game to make "additional" scenery files for use in the game.

So just like the 100 aircraft limit, you can happily fly missions & campaigns, but Mission Builder is a bust, & QC & FF begin to show "issues".:black_eyed:

I tried to reduce the number of runways & "live" scenery layers, but I don't think I ever got the temp files to stop being created. In the end I started a fresh install & added enough runways to stay below 200. I'm afraid I concluded that multiple installs were the way to go.

Not sure this helps any, but at least you have an idea why you're seeing what you're seeing...:monkies:
 
Usually indicates a quirky scenery bgl -- airfield, landclass, waterclass, excludes, what have you...Beartcat 241.
Click to expand...

Ok. I think Bearcat hit on the issue- although there may be some other glitches going on that I am unaware of. But for now, the CTD issue at Noemfoor is resolved. I found the culprit.

Part of my LWM scenery install includes placing 1 and possibly 2 different types of scenery bgls directly into the main CFS2 Scenery folder. These two types of bgls are usually named wm_scenery_name.bgl and 0_scenery_name_xcld.bgl. The first is the bgl that wipes out any existing land at the scenery location. The second is the exclude file that wipes out any stock CFS2 roads, rivers, shorelines- whatever. I usually put a 0 at the beginning of the xcld.bgl name so that it will be the first to load.

Just to see what would happen, I deleted all of the these bgls from the main CFS2 Scenery folder.

After doing so, I started CFS2 and was able to go to Noemfoor in FF no problem. Yey!! Plus, Bearcat241, CFS2 started much faster than usual!

So, now I knew that one of those deleted files was causing the problem.

I started a trouble-shooting routine of closing CFS2., adding the files back into the main CFS2 Scenery folder in blocks of 10 at a time, restarting CFS2, doing a "fly now" in FF to Noemfoor and waiting for a CTD to happen.

After the second reload of 10 files I got a crash! So then I started eliminating each of this last group of 10 bgls one at a time until I got a clean FF to Noemfoor.

Turns out the guilty party is a bgl named 0_noemfoor_xcld.Bgl. The date on the file is 11/21/2006.

Its likely that this is the only version of the file that currently exists since there wouldn't have been any logical reason to ever make another. I don't know if it was just this particular file or if it is an objection CFS2 may have with any sort of xcld file at this location- can't imagine such a thing- but I will make a new one and see what happens.

But for now if anyone who cares to take the time to dump this file from their main scenery folder would do so and post the results I would appreciate it!

Thanks

Cheers,
MR

BTW I went ahead and added the rest of the deleted wm_ and 0_ bgls back into the main Scenery foldder an all is still well. So, at least for now, problem solved.

PS: I don't think I will make another since that xcld was made for back in the pre-Rhumba mesh and masks days and was meant for getting rid of stock CFS2 roads, rivers and shorelines. No need for it now.
 
Hi MR,

Well I can verify your findings. Removing 0_noemfoor_xcld.Bgl solved the problem on my rig.

Initially the application error for me was, "Application Failure cfs2.exe 7.50.0.917 in terrain.dll 7.50.0.9 17 at offset 0000d3e9.. yadda yadda."

Not anymore.

Dave

PS; Now my install is also creating a ppath file. Not sure what this file is, but my other installs that are working correctly always creates this file.
 
dvslats said:
Hi MR,

Well I can verify your findings. Removing 0_noemfoor_xcld.Bgl solved the problem on my rig.

Initially the application error for me was, "Application Failure cfs2.exe 7.50.0.917 in terrain.dll 7.50.0.9 17 at offset 0000d3e9.. yadda yadda."

Not anymore.

Dave

PS; Now my install is also creating a ppath file. Not sure what this file is, but my other installs that are working correctly always creates this file.
Click to expand...

Thanks for checking it out, Dave. I appreciate it!

MR
 
Noemfoor emerging from the fog of the CTD Twighlight Zone!

Kornasoren in the foreground. Kamiri in the distance. Still have quite a bit more to do on Kornasorent- but the really challenging part is finished. One more airfield, Nambir, still to add. It will be way off around in the distance to the left. Its and easy one- just an emergency strip- nothing elaborate.
noemfoor-progress.jpg
 
Progress...keep us updated :encouragement:

And i can always modify my 9th FS campaign to use any of your bases that conflict with the defaults.

UncleT, i experienced the same barrier for the first time some years ago when i overloaded my first Med-NAfrika install with a buggy Italia 1SMV Scenery package. I think i was up to 64 layers at the time and the Italia 1SMV was the last straw for CFS2. I also concluded that there was a HC limit, so i reduced the layers to something like 20 for good measure. It was a start, but the Italia 1SMV package still wouldn't work despite everything i tried. But going back to what you said about the temp files continuing to regenerate even after cleanup measures, the remedy for that is to also delete all of the database index files in the main folder. Keeping them is forcing the sim to use leftover references to the old databases.
 
Bearcat241, UncleTgt, gentlemen,

I did a massive cleanup of my CFS2 install night before last. One of the things I did was to relocate a folder, My Terrain, from the CFS2 parent folder to the FSSC parent folder. I use My Terrain as my scenery testing folder. FSSC compiles to it and before I moved it I test flew new scenery from it. The move created one extra step. I now need to copy the freshly compiled bgls from the FSSC location to the CFS2 scenery folder I am working with. An extra step, but I thought it would help clean up some of the clutter. In any event, somehow or other for reasons I don't comprehend, CFS2 has figured out the path to My Terrain's new location and keeps creating an entry for in the scenery.cfg file as well as a filelist.dat file in the My Terrain/scenery folder itself- way over in the FSSC folder!

Question 1: What in the ...?

Question 2: Where do I find the database index files you mention so that I can delete them? What are they called?

Question 3: How do you know that these tmp files you mention are being generated? Does some sort of message appear on the screen. Is there someplace you go to look for them?

Thanks
MR
 
Bearcat........

...... deleting the index files in the main folder is something that I learned from TR many moons ago and do routinely. Posted it here in a TIPS section awhile back but I guess it was lost in time. Making the engine rebuild the indexes also seems to speed up the loading of the game.
I guess a batch index file remover wouldn't be a bad idea.
 
Hehe, Ok.

So, I am guessing that these are the database index files you refer to?

Just delete them and CFS2 will rebuild them?

Thanks,
MR
 

Attachments

  • cfs2indexfiles.jpg
    cfs2indexfiles.jpg
    49.7 KB · Views: 3
You must log in or register to reply here.
Back
Top