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

I'm out of ideas here, folks...

Rami

Rami

Administrator
Staff member
Good evening,

One, and only one of my installs has gone tits-up on me, and I can't figure out why. My Pacific install is generating some odd problems. (Not the Meridian / Iceberg install, Thank God)

I have a virgin install that I use for emergencies like this, but when I add all the files from my Pacific install systematically, including the objects_dp folder, the sim will not load properly. I have tried doing a "clean" start, but when I delete all the index files along with .cdp and filelist.dat files and fire up the sim, the STR_INDEX file and INDEX_FILE will not generate on their own. If they are added manually, then I can select bases and aircraft, but only the stock airfields show up, even though I have the scenery loaded in the .cfg file.

Additionally, weird files with random names, like 87C6, 37A, and 96F2 suddenly appear in the folder, without explanation.

I can't make heads or tails out of this, but all my other installs are completely normal. :dizzy:

Any ideas?
 
Hiya Rami,

Hmmm... sounds like a most vexing conundrum indeed.

When you say you are adding them systematically, do you mean that you are adding them one at a time- I am assuming that you have a bunch of individual add-on scenery folders that can be added one folder, or group of related folders, at a time- and then restarting after each addition?

When was the last time it was working? What was the last thing you did before everything went wonky? And don't be telling me it was adding my GSL version of Formosa! ;^)

Chris

PS It's got to be something really simple.
 
Reply...

Chris,

I'm sure it has nothing to do with Formosa. :costumed-smiley-034 It was working today when I was checking layout files. I haven't made any modifications to it whatsoever in the last couple of days, other than some minor GSL adjustments to various places in the Pacific. :dizzy:
 
Reply...

MaskRider,

I tested my virgin install, and it fires up fine with no issues, so whatever the culprit is has to be somewhere in my Pacific install.
 
Those random "code" fragments are kinda weird.

So this virgin install, the one you use for emergencies. After which addition of files from your pacific install does the virgin install stop booting up?

I am assuming that when you remove the files you have added from your pacific install the virgin install goes back to booting up okay? Yes?

Or am I missing something?

MR
 
Reply...

Chris,

I've nailed it down to the SCENEDB folder; I'm now adding them one at a time. :very_drunk:
 
BTW, if what I described above- swapping files from the pacific install into the virgin install- is not what you have been doing, then I would give it a shot. Make copies of all the folders in your Virgin install that might be affected then start swapping in files and folders from your pacific install, restarting after each addition, until you hit on the file or folder that makes the virgin install stop working.

Of course I have no idea how big your pacific install is. It may be so massive as to preclude such a time consuming exercise.

But it seems to me it must be something simple.

MR
 
Chris,

I've nailed it down to the SCENEDB folder; I'm now adding them one at a time.
very_drunk.png
Click to expand...

Andrew,

Ah, good. Be sure to let us know what it turns out to be.

Chris
 
Reply...

MaskRider,

Added in the airfields by Arndt, AF, UncleTgt's Carolines, New Britain and New Ireland airfields/scenery, and airfields by Devildog73, and Dog1, everything okay so far.

Saving the best for last. :wavey:
 
Reply...

MaskRider,

Apparently, with this install, I am not allowed to have more than 30 scenery layers in total. As long as I stay under this bright line, the sim works normally.

Odd, considering several ETO and MTO installs are over threshold.

Perhaps this has something in common with the wide variance of ships and/or objects you can have in the sim before getting CTD errors. :dizzy: :dizzy:
 
So you just need to deactivate a certain number of scenery layers and everything is fine?

Any scenery layers so longs as it keeps the total under 30?

MR
 
I guess what I am getting at is that lets say you have 36 available scenery layers. So long as you deactivate any random 6 layers everything is jake? There isn't any one particular one that will still cause the game to not boot up? In other words, it isn't the 6th deactivated layer that is the problem? And the preceding five are actually ok?
 
Reply...

MaskRider,

I've narrowed it down to the MR Philippines folder. It's not a hard 30 marker. I'm going to try downloading the Philippines airfield packages again.
 
Reply...

MaskRider,

There is something in the Philippines No2 package that is causing the problem. The only solution now is to go base-by-base to find out. However, my eyes are dropping as it's getting close to bedtime, so I will pick this up tomorrow and finishing isolating the problem.
 
Before dropping off. Do this please. Look at the bgl files in the scenery folder and tell me if they have API in the name?
 
Reply...

Chris,

Every single one. So far, I can eliminate Binalbagan and Borongan as troublemakers.

The .bgl files in the No1 pack are named the same way, with no problems.
 
I'm listening.

The reason I asked about API being in the file names was because I didn't recall naming them like that. It indicates that I intended to make a version that was going to be GSL.

I just looked through my old FSSC folders and sure enough I have created GSL version of the airfields- but only got so far as renaming scn files and deleting the macros. Never created any GSL layouts except for Nichols and Nielson fields in Manila.

Mine are all name the same too and work fine.

MR
 
You must log in or register to reply here.
Back
Top