Two problems with MTO upgrades

[Archive1]

I've just started to upgrade my old MTO campaigns with Rami's newer versions (Dodecanese, Western Desert, Malta-spitfires, etc) and have run into two problems that I did not get with the ETO upgrades I did:

1. Although I've carefully checked off - as I've downloaded and installed all the objects listed as needed - I still have four missing with the Malta-Spitfires campaign: inf_camo_net, jmk_inf_bouy_green/red, jmk_thor_combat and hog_islander_a - have I missed something somewhere?

2. I'm using the MTO master airbase.dat list provided and have cleared the ';' before the NDB listing for each airbase, but I get no response from the NDB input dial on any panel of any aircraft However, entering the Lat and Long data gives a correct indication for direction and distance and the gps100a entries are 'hot'. Any help with this?

Actually have one additional problem, but let's try to get these two fixed first.

BTW - have been working with CFS since it was released way back when, with lots of mission, scenery, aircraft mods, etc. (I mention this, not to brag, but just to let people know I'm not a beginner.)
Thanks - Archive1

[Shadow Wolf 07]

Archive1: #2 - the ADF/NDB signals should be imbedded in the SCA files of the scenery bgl and should show whether they are listed on the airbases.dat or not. It will only give you the bearing/heading but you'll have to work out or "guestimate" the distance yourself. This is where a scaled map comes in handy or even the map scale in the game, unless you are using GPS. Don't know why the NDB isn't working for you.

[kdriver]

Hi Archive1,

I wouldn't clear the semi-colons from the airbase.dat as that may corrupt the file and cause problems with missions. As Shadow Wolf says the NDB frequency and range are embedded in the scenery .bgl file for each airbase. Are you in radio range of the particular NDB to which you're tuned?

The two jmk ... missing objects are found here: http://www.geocities.jp/usio_no_ibuki/index.htm

As for the other two missing objects, I can't remember offhand but I'm sure Rami will know.

Kevin

[Shadow Wolf 07]

As kdriver intimates, knowing the distance to the NDB emitter is essential. As I recall the scenery builder has to set his choice of range for the NDB (in Flight Simulator Scenery Creator - FSSC) in nautical miles. In the past, most have chosen ranges of 85nm to 100nm. If you are outside that distance, you ADF "receiver" will not detect the signal. If you can pick up 2 or more known signals you can use resection to plot your position on a map and you'll know at what heading you have to fly to pick up the signal from your "target" base.

[highpockets]

AF_AA_Pak2.zip for info_camo_net

[Rami]

Good evening,

Archive:

JMK Thor combat: http://www.geocities.jp/usio_no_ibuk...hor_combat.zip

JMK buoys: http://www.geocities.jp/usio_no_ibuk...K_inf_Buoy.zip

Hog Islander: http://www.sim-outhouse.com/sohforum...tid=42&id=6341

[Archive1]

Arrrrgh! I’ve written a long reply twice now and it failed to go. Here’s a much, much shortened reply:

Have downloaded the objects – thanks all.

Have tested the NDBs at the airbase itself and at various altitudes – no joy.

Have used “;” and “*” to temporarily inactivate code when modifying panels and missions. One must remove the “;” or “*” to permit other code calling that line to read it. I think I’m right about this.

BGLs - Have both: SCENEDB/JHS_xxx/scenery/xxx.bgl (or whatever JHS_xxx one is using) AND SCENEDB/afdfiles/scenery/xxx.bgl where NDBs reside. Have tested airbases that are listed in each – nada.

Stumped. No problem like this with ETO upgrade.

Thanks guys. Archive1

[Archive1]

AF_AA_Pak2.zip for info_camo_net

Highpockets - you're almost as ancient as I am...just turned 80 last week. Thanks for the info. Watch your six.

-=Archive1=-

[Shadow Wolf 07]

Extract the zip below to any folder and then Install the: InstallVB6Runtime.EXE and the RAFadf-helper-for-CFS2-FULL.exe into your MTO Installation. Then try the ADF/NDB again. These priograms/utilities will not harm your computer or the install. These may make the ADF/NDB function work.

[highpockets]

Thanks Archive1!
Always watching my six--born too late to fly props in WWII and too poor to race cars, so here I am!

[Rami]

Always watching my six--born too late to fly props in WWII and too poor to race cars, so here I am!

Up here in Yankeeland, we call this "a day late and a dollar short."

[Archive1]

Thanks Archive1!
Always watching my six--born too late to fly props in WWII and too poor to race cars, so here I am!

Was a flight surgeon so depended on my front seat pilot to survive. But, hey, hard to watch the six with bifocals. A friend said that, "..at this age we always start a conversation with a recital...of medical problems. Enough...let's not discourage the young'uns. Be well, my friend.-=Archive1=-

[Archive1]

Extract the zip below to any folder and then Install the: InstallVB6Runtime.EXE and the RAFadf-helper-for-CFS2-FULL.exe into your MTO Installation. Then try the ADF/NDB again. These priograms/utilities will not harm your computer or the install. These may make the ADF/NDB function work.

Thanks. Will give it a try.

[Archive1]

Well, Fibber, problem is that I've had MD after my name for 50 years...old before my time maybe.
Thanks, Archive1

[Archive1]

Rami, highpockets, Shadow Wolf, et al

We older guys are slow, but persistent. I now have the NDB problem fixed.

My SCENEDB/runways file was filled with African CFS2 _xxx_AFD.bgl and CFS2_xxx_RUN.bgl files – where did they come from? Dunno. Deleted all of them (along with filelist, of course), but left the now-empty runways file itself in place.

My SCENEDB/afdfiles was also filled with African xxx.bgl stuff –have no idea where it came from (cfs2afd.bgl certainly came with original CFS2 program – getting rid of that eliminated all those Pacific theater airbases that were inappropriate for the MTO) – I cleaned everything out of this file too.

Now all the airbase NDBs work cleanly and only appropriate airbases appear, with the aircraft headed correctly.

Compared the Lat/Long, alt, heading of each mission airbase in Western Desert, Malta-Spitfires and Dodecanese campaigns and found only one discrepancy:

Quadra Sponda mission #5 does not exactly match the 8106 Barce Master airbase.dat for Lat/Long. Probably not very important, but I corrected it. Rami – hat’s off for precision.

However, although everything is cleaned up, and although am using the Master airbase.dat, the Advanced Information ‘map’ still does not work. No CTD, just get that bland, Pacific island generic view.

Any ideas why this still fails? I have Achim’s newest JHS_xxx and xxx.gsl files loaded (such as JHS_Italy, JHS_Greece, etc.) and am using the proper Master airbase.dat file.

Thanks for all the input. Archive1

[Archive1]

Sorry about the duplicates - having fits with the thread input.

[Shadow Wolf 07]

Like you, Archive1, for some reason, mine doesn't show other than the blank Solomons map when I hit M or open the advanced info key - even the goals and effects data are not listed missions in at least 2 installs. And I am using windows 7 which never gave me a problem before.

[Rami]

Rami, highpockets, Shadow Wolf, et al

We older guys are slow, but persistent. I now have the NDB problem fixed.

My SCENEDB/runways file was filled with African CFS2 _xxx_AFD.bgl and CFS2_xxx_RUN.bgl files – where did they come from? Dunno. Deleted all of them (along with filelist, of course), but left the now-empty runways file itself in place.

My SCENEDB/afdfiles was also filled with African xxx.bgl stuff –have no idea where it came from (cfs2afd.bgl certainly came with original CFS2 program – getting rid of that eliminated all those Pacific theater airbases that were inappropriate for the MTO) – I cleaned everything out of this file too.

Now all the airbase NDBs work cleanly and only appropriate airbases appear, with the aircraft headed correctly.

Compared the Lat/Long, alt, heading of each mission airbase in Western Desert, Malta-Spitfires and Dodecanese campaigns and found only one discrepancy:

Quadra Sponda mission #5 does not exactly match the 8106 Barce Master airbase.dat for Lat/Long. Probably not very important, but I corrected it. Rami – hat’s off for precision.

However, although everything is cleaned up, and although am using the Master airbase.dat, the Advanced Information ‘map’ still does not work. No CTD, just get that bland, Pacific island generic view.

Any ideas why this still fails? I have Achim’s newest JHS_xxx and xxx.gsl files loaded (such as JHS_Italy, JHS_Greece, etc.) and am using the proper Master airbase.dat file.

Thanks for all the input. Archive1

Archive1,

I'm not sure about why you might be having issues with the Advanced Info screen. I discussed this at length with Greg, (Shadow Wolf 07) because we are both running Windows 7. The only thing I can think of is that achim27619 told me once that for the airbase.dat file to work properly, there needs to be a little symbol below the last airbase.dat entry that looks like a square or an arrow. If that isn't in your file, that could cause some issues.

I am going to go through and just dust off the Med after I get done with Europe, so give me a week or two on Quarta Sponda.

[Archive1]

Rami:

Good point re: bit at end of airbase.dat, but I think I've been very careful of that since I used to modify my own list. Will check.

No hurry about the Sponda - just thought it was worth a comment.

Oh, and I'm using both XP and Win 7 on two different computers. Same issue.

[Rami]

Rami:

Good point re: bit at end of airbase.dat, but I think I've been very careful of that since I used to modify my own list. Will check.

No hurry about the Sponda - just thought it was worth a comment.

Oh, and I'm using both XP and Win 7 on two different computers. Same issue.

Archive1,

Just so you can see I'm not blowing smoke, here is a screenshot of my flying a mission off Crete with the Advanced Info screen working on my desktop.

[Archive1]

Rami - no thought of that. Checked the thingy at the end of the airbase.dat...it's there. Tried again tonight, still no advanced infor map. Dunno. Will explore.
Thanks, -=Archive1=-

[Archive1]

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]

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]

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?

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?

[kdriver]

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.