-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
-
IMPORTANT DOWNLOADING INFORMATION - ALL MEMBERS PLEASE READ
Please see this thread for updates. Update Thread
SOH ADMINISTRATION
Two problems with MTO upgrades
- Thread starter Archive1
- Start date
Rami (Shadow wolf)
Rami your insert shows all four : Briefing, Goals, Events, Stats and a description of the mission. Mine shows only the squares for Briefing and Goals (but not 'hot') with not even blocks for Events and Stats and nothing in the large block for mission description. Regardless of the map information
Where does the Advanced Info come from in the program? In other words, where can one find the code? Anybody know?
Rami your insert shows all four : Briefing, Goals, Events, Stats and a description of the mission. Mine shows only the squares for Briefing and Goals (but not 'hot') with not even blocks for Events and Stats and nothing in the large block for mission description. Regardless of the map information
Where does the Advanced Info come from in the program? In other words, where can one find the code? Anybody know?
Reply...
Archive1,
As far as my understanding of CFS2 goes, the "modules" folder holds the key. I'm wondering if perhaps it boils down to the cfsmap.dll and mplanner.dll files. Mine are 428kb and 488kb, respectively. Perhaps this doesn't check out the same on your end?
Archive1,
As far as my understanding of CFS2 goes, the "modules" folder holds the key. I'm wondering if perhaps it boils down to the cfsmap.dll and mplanner.dll files. Mine are 428kb and 488kb, respectively. Perhaps this doesn't check out the same on your end?
Shadow Wolf 07
SOH-CM-2025
Mine displays the same info or lack of info. I'm thinking it might come from using my airbase.dat file with the new basses added onto the end rather that the one that's included in the campaign pack. This results in having different runway and Id numbers but the same base than the original mission file indicates. Could this possibly be the reason?
I've found nearly any error in the airbases.dat file will cause the above problems as well as in Mission Builder. I spent ages trying to track down a similar problem, in the end finding a square bracket "]" was missing.
Missing airbase numbers or duplicate airbase ID numbers will probably cause headaches.
I use a single airbases.dat file for my ETO/MTO/EF installations. I use Achim's/Rami's ID numbers as much as possible. I find having one file makes it easier for amendments and tracking down duplications or other errors.
In an ideal CFS 2 world, every airbase, regardless of who made it, would have its own specific ID number.
Missing airbase numbers or duplicate airbase ID numbers will probably cause headaches.
I use a single airbases.dat file for my ETO/MTO/EF installations. I use Achim's/Rami's ID numbers as much as possible. I find having one file makes it easier for amendments and tracking down duplications or other errors.
In an ideal CFS 2 world, every airbase, regardless of who made it, would have its own specific ID number.
Rami, highpockets, Shadow Wolf 07:
I have tried several approaches to the lack of the Advanced Inf problem in the MTO series:
1. I swapped out the MODULES/cfsmap.dll and mplanner.dll from the CFS2/MTO program that I’m using with two *.dll files from a ‘clean’ CFS install –maybe there was some corruption of those two files. Nope.
2. Maybe the Scenery Library placement of the JHS_*** files needed to be changed – either up down. Did both. Nope.
3. Used the same ‘Crete’ MTO airbase.dat file that Rami must have used in his graphic reply. His worked, well…Nope.
4. Would the scenery.cfg file be a problem. Looks OK, but where’s the evil genii? Put a few files into the SCENEDB/afdfiles and SCENEDB/runways that I had cleared of old stuff to make sure that there was something resident in them, since they are both required in the scenery.cfg file. Nope.
Clearly the main MTO airbase.dat file is OK. I presume that’s the one Rami uses, and it worked for him. I have gone through much of that dat file and do not find any of the usual routine errors – wrong sequence, wrong ID number, lost symbols…etc. Again, a clean file. And, no, I’ve not made any edits to it.
Now, yes of course, one can fly the program and missions without this function, but it is frustrating to just give up on a clearly solvable problem for which there must be a solution.
-=Archive1=-
I have tried several approaches to the lack of the Advanced Inf problem in the MTO series:
1. I swapped out the MODULES/cfsmap.dll and mplanner.dll from the CFS2/MTO program that I’m using with two *.dll files from a ‘clean’ CFS install –maybe there was some corruption of those two files. Nope.
2. Maybe the Scenery Library placement of the JHS_*** files needed to be changed – either up down. Did both. Nope.
3. Used the same ‘Crete’ MTO airbase.dat file that Rami must have used in his graphic reply. His worked, well…Nope.
4. Would the scenery.cfg file be a problem. Looks OK, but where’s the evil genii? Put a few files into the SCENEDB/afdfiles and SCENEDB/runways that I had cleared of old stuff to make sure that there was something resident in them, since they are both required in the scenery.cfg file. Nope.
Clearly the main MTO airbase.dat file is OK. I presume that’s the one Rami uses, and it worked for him. I have gone through much of that dat file and do not find any of the usual routine errors – wrong sequence, wrong ID number, lost symbols…etc. Again, a clean file. And, no, I’ve not made any edits to it.
Now, yes of course, one can fly the program and missions without this function, but it is frustrating to just give up on a clearly solvable problem for which there must be a solution.
-=Archive1=-
highpockets
SOH-CM-2025
don't know if this helps. My mto View attachment 11587View attachment 11588
Sarg Willy
SOH-CM-2014
Here,s a long shot , what are your screen display settings , We know mission builder and map display can creat a problem if too high a resolution is used , try 800x600 ,,
Rami: Here 'tis_
Am dismayed at taking so much of your time with this. But appreciated.
Archive1
[General]
Title=CFS2 World
Description=CFS 2 Scenery data
Cache_Size=10M
Clean_on_Exit=TRUE
[Area.001]
Title=Default Scenery
Local=scenery
Active=TRUE
Layer=2
Required=TRUE
Remote=
[Area.002]
Title=Terrain
Local=Scenedb\world
Active=TRUE
Texture_ID=1
Layer=1
Required=TRUE
Remote=
[Area.003]
Title=CFS1 Library
Local=Scenedb\library
Active=TRUE
Layer=5
Remote=
Required=FALSE
[Area.004]
Title=Airport Facilities Data
Local=Scenedb\AFDFiles
Active=TRUE
Layer=9
Required=TRUE
Remote=
[Area.005]
Title=Scenery Ships
Local=Scenedb\Ships
Active=TRUE
Layer=11
Remote=
Required=FALSE
[Area.006]
Title=Aircraft Weapons
Local=Scenedb\weapons
Active=TRUE
Layer=12
Required=TRUE
Remote=
[Area.007]
Title=Vehicles
Local=Scenedb\veh
Active=TRUE
Layer=13
Required=TRUE
Remote=
[Area.008]
Title=Effects
Local=Scenedb\fx
Active=TRUE
Layer=14
Required=TRUE
Remote=
[Area.009]
Title=Runways
Local=Scenedb\runways
Active=TRUE
Layer=15
Required=TRUE
Remote=
[Area.010]
Title=Buildings
Local=Scenedb\inf
Active=TRUE
Layer=16
Required=TRUE
Remote=
[Area.011]
Title=FS2000_props
Local=Scenedb\fs2kprop
Active=TRUE
Layer=17
Required=TRUE
Remote=
[Area.012]
Title=Africa
Local=SCENEDB\Africa
Remote=
Active=TRUE
Required=FALSE
Layer=3
[Area.015]
Title=Malta_BSK_V2
Local=SCENEDB\Malta_BSK_V2
Remote=
Active=TRUE
Required=FALSE
Layer=10
[Area.016]
Title=JHS_Italy
Local=SCENEDB\JHS_Italy
Remote=
Active=TRUE
Required=FALSE
Layer=8
[Area.017]
Title=JHS_North_Africa
Local=SCENEDB\JHS_North_Africa
Remote=
Active=TRUE
Required=FALSE
Layer=7
[Area.018]
Title=JHS_Greece
Local=SCENEDB\JHS_Greece
Remote=
Active=TRUE
Required=FALSE
Layer=4
[Area.019]
Title=JHS_Albania
Local=SCENEDB\JHS_Albania
Remote=
Active=TRUE
Required=FALSE
Layer=6
Am dismayed at taking so much of your time with this. But appreciated.
Archive1
[General]
Title=CFS2 World
Description=CFS 2 Scenery data
Cache_Size=10M
Clean_on_Exit=TRUE
[Area.001]
Title=Default Scenery
Local=scenery
Active=TRUE
Layer=2
Required=TRUE
Remote=
[Area.002]
Title=Terrain
Local=Scenedb\world
Active=TRUE
Texture_ID=1
Layer=1
Required=TRUE
Remote=
[Area.003]
Title=CFS1 Library
Local=Scenedb\library
Active=TRUE
Layer=5
Remote=
Required=FALSE
[Area.004]
Title=Airport Facilities Data
Local=Scenedb\AFDFiles
Active=TRUE
Layer=9
Required=TRUE
Remote=
[Area.005]
Title=Scenery Ships
Local=Scenedb\Ships
Active=TRUE
Layer=11
Remote=
Required=FALSE
[Area.006]
Title=Aircraft Weapons
Local=Scenedb\weapons
Active=TRUE
Layer=12
Required=TRUE
Remote=
[Area.007]
Title=Vehicles
Local=Scenedb\veh
Active=TRUE
Layer=13
Required=TRUE
Remote=
[Area.008]
Title=Effects
Local=Scenedb\fx
Active=TRUE
Layer=14
Required=TRUE
Remote=
[Area.009]
Title=Runways
Local=Scenedb\runways
Active=TRUE
Layer=15
Required=TRUE
Remote=
[Area.010]
Title=Buildings
Local=Scenedb\inf
Active=TRUE
Layer=16
Required=TRUE
Remote=
[Area.011]
Title=FS2000_props
Local=Scenedb\fs2kprop
Active=TRUE
Layer=17
Required=TRUE
Remote=
[Area.012]
Title=Africa
Local=SCENEDB\Africa
Remote=
Active=TRUE
Required=FALSE
Layer=3
[Area.015]
Title=Malta_BSK_V2
Local=SCENEDB\Malta_BSK_V2
Remote=
Active=TRUE
Required=FALSE
Layer=10
[Area.016]
Title=JHS_Italy
Local=SCENEDB\JHS_Italy
Remote=
Active=TRUE
Required=FALSE
Layer=8
[Area.017]
Title=JHS_North_Africa
Local=SCENEDB\JHS_North_Africa
Remote=
Active=TRUE
Required=FALSE
Layer=7
[Area.018]
Title=JHS_Greece
Local=SCENEDB\JHS_Greece
Remote=
Active=TRUE
Required=FALSE
Layer=4
[Area.019]
Title=JHS_Albania
Local=SCENEDB\JHS_Albania
Remote=
Active=TRUE
Required=FALSE
Layer=6
Reply...
Archive1,
Ah...but you see, kemosahbee, many years ago, it was I who was asking the questions. (Ask bearcat241 or Talon, they'll tell you) In addition, I am a teacher, and it has become engrained for me to want to help others along, provided they're willing to try on their own, which you so clearly are.
Back to business...
I noticed two major issues here. The attached "scenery.cfg" file corrects the errors and puts the layers in the correct, sequential order. Because you had a gap between [Area.012] and [Area.015], that meant that any scenery below (with higher numbers) than [Area.012] was not being recognized by CFS2.
The other major issue, (also corrected) is that the "area" and "layer" numbers, with the exception of areas 1 and 2, should always be the same. (E.g. Area 3, Layer 3, etc.)
This should help correct some of the basic issues.
By the way, are you using this to help you along?
http://www.sim-outhouse.com/sohforums/local_links.php?action=jump&catid=49&id=2932
I don't know what kind of scenery issues you may have been having, but that's bound to be part of it.
Archive1,
Ah...but you see, kemosahbee, many years ago, it was I who was asking the questions. (Ask bearcat241 or Talon, they'll tell you) In addition, I am a teacher, and it has become engrained for me to want to help others along, provided they're willing to try on their own, which you so clearly are.
Back to business...
I noticed two major issues here. The attached "scenery.cfg" file corrects the errors and puts the layers in the correct, sequential order. Because you had a gap between [Area.012] and [Area.015], that meant that any scenery below (with higher numbers) than [Area.012] was not being recognized by CFS2.
The other major issue, (also corrected) is that the "area" and "layer" numbers, with the exception of areas 1 and 2, should always be the same. (E.g. Area 3, Layer 3, etc.)
This should help correct some of the basic issues.
By the way, are you using this to help you along?
http://www.sim-outhouse.com/sohforums/local_links.php?action=jump&catid=49&id=2932
I don't know what kind of scenery issues you may have been having, but that's bound to be part of it.
Rami: Interesting…I have installed all (repeat all) the SCENEDB/xxx scenery files as I usually do via the Scenery Library mechanism. I believed that this install process updated the scenery.cfg file correctly; at least as far as sequencing things properly. So I ask myself, how did a ‘gap’ appear? I have indeed moved the Library files up and down in an attempt to see if that would help: But again, I used the program’s Scenery Library process for doing so. At no time have I directly edited the scenery.cfg file itself.
Re: am I using this stuff? Absolutely.
I have thought my next step would be to start with a clean install and then swap out parts with sections of the MTO install and see when the Advanced Info bit failed. At least then would have a clue in what area to start looking for problems. Would have to think through the order of the swaps to make it work, of course.
Will stuff the new scenery.cfg into the program tonight and see what happens. May be the problem is solved. If so it does leave my query in the first paragraph on point though, doesn’t it? Or do I misunderstand the accuracy of the Scenery Library mechanism and should one always check the scenery.cfg file after adding (or deleting I suppose) a listing? Answer – of course.
Most appreciative, Teach. Have done a great deal of that myself in the medical field. Know the rewards and frustrations. Sincere, thanks.
-=Archive1=-
Kdriver - have to look. Back later - thanks
Re: am I using this stuff? Absolutely.
I have thought my next step would be to start with a clean install and then swap out parts with sections of the MTO install and see when the Advanced Info bit failed. At least then would have a clue in what area to start looking for problems. Would have to think through the order of the swaps to make it work, of course.
Will stuff the new scenery.cfg into the program tonight and see what happens. May be the problem is solved. If so it does leave my query in the first paragraph on point though, doesn’t it? Or do I misunderstand the accuracy of the Scenery Library mechanism and should one always check the scenery.cfg file after adding (or deleting I suppose) a listing? Answer – of course.
Most appreciative, Teach. Have done a great deal of that myself in the medical field. Know the rewards and frustrations. Sincere, thanks.
-=Archive1=-
Kdriver - have to look. Back later - thanks
Rami and all:
Problem was that the INFO/airbases was a txt file, not .dat file - converted and problem was solved. Here's how for those who don't know:
Converting a *.txt or *.rtf file to a *.dat file
Launch the program called Notepad by
double-clicking on the Notepad icon or by finding it in your list of programs.
Usually find it under the "Accessories" heading.
Click on “File" then choose "Open."
Open the file (INFO/airbases) that you want to convert to a data file.
Make any changes you want to make to the file,
then choose "Save As..."
Find the "Save as Type" option in the menu box. From the dropdown
menu choose "All files."
Delete the default name in the "File
Name" field, including the extension. Type in the name of the file you
want to save and add .dat to the end of the file name. In this case save as
“airbases.dat”.
Click save. It will now appear in the INFO file as
“airbases” and when you click “properties’ is will be shown as “airbases.dat”.
Rename the original “airbases” file which was the
.txt file that caused the Advanced Info problem something like
airbases_txt_file. Or delete it.
Any comments?
-=Archive1=-
Problem was that the INFO/airbases was a txt file, not .dat file - converted and problem was solved. Here's how for those who don't know:
Converting a *.txt or *.rtf file to a *.dat file
Launch the program called Notepad by
double-clicking on the Notepad icon or by finding it in your list of programs.
Usually find it under the "Accessories" heading.
Click on “File" then choose "Open."
Open the file (INFO/airbases) that you want to convert to a data file.
Make any changes you want to make to the file,
then choose "Save As..."
Find the "Save as Type" option in the menu box. From the dropdown
menu choose "All files."
Delete the default name in the "File
Name" field, including the extension. Type in the name of the file you
want to save and add .dat to the end of the file name. In this case save as
“airbases.dat”.
Click save. It will now appear in the INFO file as
“airbases” and when you click “properties’ is will be shown as “airbases.dat”.
Rename the original “airbases” file which was the
.txt file that caused the Advanced Info problem something like
airbases_txt_file. Or delete it.
Any comments?
-=Archive1=-
To all…esp Rami…many thanks for the assistance:
Had to take some time away to work out some real world chores.
To Rami: yes you did mention the *.txt vrs. *.dat problem with the airbase file that I belatedly discovered. Just was keeping too many balls in the air at once trying to solve the problem. Now all is well and I’m solving problems with other CFS2 theater problems.
kdriver: you mentioned Malta. Have no problems with it. Great scenery.
What have we (I) learned? (Never liked committee meetings without a summary at the end.)
1. Make sure you are using airbase.dat not airbase.txt – convert it if necessary if you have edited the master theater airbase list.
2. If you change the Scenery Library, check the scenery.cfg file – it will need editing.
3. Clean out old files in the SCENEDB/runways and afdfiles unless you want airbases from the Pacific showing up in the MTO/EFTO…etc
4. Edit (that is clean up) files in the SCENEDB folder – there may be stuff there that conflicts with a new JHS_* file – same for the GSL folder.
5. Make a master list of your own into which you put all the objects that you collect as you install each of Rami’s campaign updates – same for aircraft, scenery files. Will save massive time in the future.
Now would like to find out how to do some artwork on the airbase *.bgl files and add some objects. But that’s another thread.
Also, once again, learned that the SOH crowd is still as helpful and courteous as ever.
-=Archive1=-
Had to take some time away to work out some real world chores.
To Rami: yes you did mention the *.txt vrs. *.dat problem with the airbase file that I belatedly discovered. Just was keeping too many balls in the air at once trying to solve the problem. Now all is well and I’m solving problems with other CFS2 theater problems.
kdriver: you mentioned Malta. Have no problems with it. Great scenery.
What have we (I) learned? (Never liked committee meetings without a summary at the end.)
1. Make sure you are using airbase.dat not airbase.txt – convert it if necessary if you have edited the master theater airbase list.
2. If you change the Scenery Library, check the scenery.cfg file – it will need editing.
3. Clean out old files in the SCENEDB/runways and afdfiles unless you want airbases from the Pacific showing up in the MTO/EFTO…etc
4. Edit (that is clean up) files in the SCENEDB folder – there may be stuff there that conflicts with a new JHS_* file – same for the GSL folder.
5. Make a master list of your own into which you put all the objects that you collect as you install each of Rami’s campaign updates – same for aircraft, scenery files. Will save massive time in the future.
Now would like to find out how to do some artwork on the airbase *.bgl files and add some objects. But that’s another thread.
Also, once again, learned that the SOH crowd is still as helpful and courteous as ever.
-=Archive1=-
