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

Airbase NDB setting conflicts

Archive1

Charter Member
I have been updating several older campaigns with the newer ones uploaded (mostly) by Rami. These contain revised Achim's airbase files for the Info/airbase.dat lists. I have found a few conflicts for the NDB frequencies listed for some of the airbases - for example: UK-Bodney (344) and UK-Luton (344); GE-Ainring (322) and UK-Manston (322) and UK-Scampton (322); FR-LeHavre (438) and UK-Birchem Newton (438), etc.

How can these NDB frequencies be changed to eliminate the conflicts? Merely changing the last line of the airbase file in Info does not result in an 'active' NDB that the panel will recognize and respond to.

Perhaps this is a question for Achim alone, but there may be others who can answer it.
 
From what I remember in airbase building, the NDB frequency is imbeded in the SCASM file, from which the base BGL is created. Unless a new, replacement base is buiilt fron a new SCASM/BGL, there probably isn't a way to change the freq. The range of the NDB is only 60-120 nautical miles, depending on what the author chose. So if your plane and the 2 bases are far enough apart, there might not be a conflict problem :kilroy:.

Use a map and dead reconing until you get within range of the base you want...
 
Wolf:
As I thought...that the code was buried somewhere deep in the guts of the airbase itself. And your notation that the NDB distance is short is a good reminder. Certainly no conflict GE/UK/FR and perhaps not in the UK itself.
Just thought if there were an easy way to correct it, I'd do it. Not so.
Thanks.
-=dcp=-
 
Wolf:
As I thought...that the code was buried somewhere deep in the guts of the airbase itself. And your notation that the NDB distance is short is a good reminder. Certainly no conflict GE/UK/FR and perhaps not in the UK itself.
Just thought if there were an easy way to correct it, I'd do it. Not so.
Thanks.
-=dcp=-

If you feel inclined to do a little scasm editing, I don't think it is too difficult to change the NDB. Always backup the originals in any case. Two programs are required:

BGLAnalyze by Winfried Orthmann at the http://www.avsim.com file library.

and

SCASM 2.96 compiler at http://www.scasm.de/txt/download.htm

Here is the scasm code from the bgl decompile with BGLAnayze, use SCASM to recompile to bgl file.
 
As well as the method mentioned by Oglivie, an even simpler and quicker way is to edit the bgl file directly with frehed hex editor. The NDB frequency shows up near the end of the file as 4 digits, e.g. the frequency for Goose Bay is 302 but it will appear as 0203.
 
Been a long, long time since I've worked at this level, ie, compilers et al, but I may give it a try...let's hear it for backed up files and clutzy incompetent 'programmers'.
We'll see ...maybe a glass or two of scotch will help the courage quotient. Although it may dampen the competence level.
Thanks.
 
You're welcome Archive1. Glad to help you out. Post if you have more questions with the edits.

Cheers,
O
 
Back
Top