Extra Beacons Mod

gospadin · August 15, 2016

Posted version 4 (OP updated)

Added EL TORO and COYOTE, fixes for ST GEORGE (channel), VICTORVILLE (callsign), China Lake NAWS (beacon position), Fallon NAS (ID, channel, beacon position), Luke AFB (beacon position)

gospadin · August 17, 2016

PM sent.

Got your PM, and I understand your feedback now. Will integrate your suggestions tonight and re-release.

--gos

gospadin · August 18, 2016

Posted update with version 5. Works around the BEACON_TYPE_AIRPORT_HOMER_WITH_MARKER bug where they don't work properly when not attached to airports, and name all beacons to improve ABRIS/nav integration on the Ka-50.

Thanks Tarres!

--gos

gospadin · August 18, 2016

Version 6 posted, names the KTNX NDB to improve Ka-50 navigation. I missed this one in the last update, sorry.

--gos

Woogey · September 15, 2016

Where are you posting your mod at? I'm sure I missed it here somewhere.

Edited January 1, 2018 by Woogey

HiJack · September 15, 2016

Where are you posting your mod at? I'm sire I mossed it here somewhere.

First post Woogey ;)

HiJack · September 15, 2016

The L-39C uses NDB's to navigate. Have not tested it. I believe the Hawk can use both NDB's and VOR/TACAN to navigate. Not sure if they have it working properly yet.

gospadin · November 18, 2016

FYI, I am sure my mod is incompatible with today's 2.0.4 NTTR patch, but I'll get my mod fixed tonight and update this thread again when it's finished.

--gos

gospadin · November 19, 2016

Version 7 updated and attached to the first post.

removed DAGGETT, HECTOR, NEEDLES, SILVERBOW, GRAND CANYON, KINGMAN, CEDAR CITY, ST GEORGE, and COLORADO CITY as they're now part of the 2.0.4 NTTR base beacon list

I also updated the overall map picture as well.

Enjoy!

--gos

Pikey · December 10, 2016

Was there never a way of incorporating beacons.lua under the mission file under scripts and then its path relative to base? Seems a shame if not because the KA50 ARK could be inserted into mission and then these could be client-sided

gospadin · December 10, 2016

Was there never a way of incorporating beacons.lua under the mission file under scripts and then its path relative to base? Seems a shame if not because the KA50 ARK could be inserted into mission and then these could be client-sided

beacons are client side already

i never tested with having them in my saved games folder, if that's what you're asking

problem (i think) is having access to these beacons in the map load flow, not sure how i would spawn access of the additional beacons without some kind of modification to the base file

gospadin · May 27, 2017

Coming soon as I am done with the NDBs...

gospadin · May 27, 2017

First post updated with new version 8, includes full map photo.

Edited May 27, 2017 by gospadin

Xxx · June 12, 2017

First of all thanks for these Beacons.

In the Normandy map, although there a very few modules that can use the NDB's, they appear to work. What I can not get to work are the VOR's.

Again there are precious few modules that can utilise the VOR's. However trying out the Mirage VOR nav functions, the VOR's don't seem to work?

Given that the L39/Mig 21 use RSBN nav, it would be nice to see those?

Even better, the 109 and 190 have Radio Homer dials in the cockpits, I wonder if anyone can get those to work? If indeed they were ever intended to function?

Thanks again

Cheers.

gospadin · June 12, 2017

Again there are precious few modules that can utilise the VOR's. However trying out the Mirage VOR nav functions, the VOR's don't seem to work?

So there's definitely oddities with standalone VOR stations in the code, which isn't really a function of my mod per-say, but it's (I think) limitations in the base navigation code. I noticed similar issues flying with the A-10C before.

Can you give me a specific test case on a specific beacon (and how your cockpit is setup) and I'll look into it in more detail?

Given that the L39/Mig 21 use RSBN nav, it would be nice to see those?

So the L-39 can use NDBs for navigation, and I did add a bunch of those. As to RSBN, since there were never any RSBN stations in England or France, I don't really have plans to support those, sorry.

Note that the MiG-21 (which also has RSBN) doesn't use these beacons at all, it has its own hard-coded RSBN system built into the module itself. It doesn't care what beacons exist in beacons.lua.

Even better, the 109 and 190 have Radio Homer dials in the cockpits, I wonder if anyone can get those to work? If indeed they were ever intended to function?

So I read this page:

https://en.wikipedia.org/wiki/Luftwaffe_radio_equipment_(Funkger%C3%A4t)_of_World_War_II

...but details are scarce. If you have any information on which fields in Normandy might have had these installed, then I'd be happy to investigate adding them. I do own the ww2 planes, so I could do some testing myself if you had data.

As to low frequency/ADF in the P-51D/TF-51, apparently that's not simulated per Lino's equipment summary document.

--gos

Xxx · June 15, 2017

Hello there.

The only aircraft I could "test" with the VOR stations was the Mirage. Noticed that the VOR needle will not point to the stations. However with the INS in the Mirage, VOR is redundant anyway.

The Hawk VOR is useless. I can't get that module to work properly, even in NTTR.

The L39 NDB works well!

Noted re the lack of RSBN stations! It's interesting that ED has coded in all the Normandy airfields into the Mig 21. Obviously a purely fictitious scenario! However, if you like to play out a cold war scenario in Normandy, the Mig 21 can be navigated from airfield to airfield and it's great fun! I wonder how many know that the Mig21 has this added feature?

In respect of the 109, I saw the ADF gauge on the panel and wondered if it had any function? I think it's real use in WW2 would be limited, however the following would be a possible way it was used.

"FuG 28a: Y-Gerät transponder. Based on the Fug17 transceiver with additional components to send the response to the Y-Gerät ground station for the ground station to derive range. Also derived the azimuth signal and displayed the results on the ANF 2 display giving the pilot a left/right command. Operating frequency 24 - 28 MHz. 8 Watts transmit power. The unit also interfaced to the FuG 10 system in the aircraft so that voice communication with the pilot from the ground controllers via the Fug 28a was possible."

I was thinking that when you tune your radio to the airfield frequency, perhaps the RDF could be made to work?

Thanks again for your work, I know how hard it is to create mods!

Best regards

David

gospadin · June 15, 2017

I was thinking that when you tune your radio to the airfield frequency, perhaps the RDF could be made to work?

I know in the mission editor you can broadcast a .ogg or .mp3 file over AM radio, and at least in the Huey, you can home in on this signal. I haven't tested it in other modules.

Beacons placed like that are, I believe, separate from the beacons.lua that I edit in this mod.

--gos

gospadin · June 15, 2017

The Hawk VOR is useless. I can't get that module to work properly, even in NTTR.

As I think I said, Hawk navigation implements its beacons in the module itself, if I remember correctly, similar to how the MiG-21 works.

I guess M3 updated the MiG-21 for Normandy, while the Hawk hasn't yet been updated. I'm sure it'll get updated at some point.

--gos

funkyfranky · January 28, 2018

Is this still up-to-date? I think I noticed some (syntax) changes in the default beacons.

gospadin · January 28, 2018

Is this still up-to-date? I think I noticed some (syntax) changes in the default beacons.

Can you be more specific? I don't see the difference you're talking about.

The mod should still work properly.

--gos

funkyfranky · January 28, 2018

Can you be more specific? I don't see the difference you're talking about.

Sorry, yeah. Changes I noticed are:

- name --> display_name

- positions changed slightly (second component only)

- seneObjects parameter is different

gospadin · January 28, 2018

Sorry, yeah. Changes I noticed are:
- name --> display_name
- positions changed slightly (second component only)
- seneObjects parameter is different

Are you running the most recent version? the display_name stuff changed a long time ago.

positions (2nd parameter) is the elevation, which in a few cases has changed by a few centimeters. (positions are in meters)

sceneObjects parameter changes with each release, I try not to chase that too much.

--gos

funkyfranky · January 28, 2018

Are you running the most recent version? the display_name stuff changed a long time ago.

positions (2nd parameter) is the elevation, which in a few cases has changed by a few centimeters. (positions are in meters)

sceneObjects parameter changes with each release, I try not to chase that too much.

--gos

Yup, latest version of 2.2. Just deleted the Beacons.lua and ran a repair.

The newly created file starts like this

dofile('Scripts/Database/wsTypes.lua')
dofile('Scripts/World/Radio/BeaconTypes.lua')
dofile('Scripts/World/Radio/BeaconSites.lua')

local disableNauticalBeacons = true

local gettext = require("i_18n")
local       _ = gettext.translate

--WORLD BEACONS

beaconsTableFormat = 2
beacons = {
{
	[b]display_name[/b] = _('');
	beaconId = 'airfield1_0';
	type = BEACON_TYPE_ILS_GLIDESLOPE;
	callsign = 'ICRR';
	frequency = 108700000.000000;
	channel = 24;
	position = { -360394.218750, 952.944679, -76976.257813 };
	direction = -88.617531;
	positionGeo = { latitude = 36.585008, longitude = -115.691917 };
	sceneObjects = {'t:170590208'};
};

Sounds like the changes are not too important. Still strange that I get the "obsolete" display_name rather than name.

gospadin · January 28, 2018

Yup, latest version of 2.2. Just deleted the Beacons.lua and ran a repair.

The newly created file starts like this

dofile('Scripts/Database/wsTypes.lua')
dofile('Scripts/World/Radio/BeaconTypes.lua')
dofile('Scripts/World/Radio/BeaconSites.lua')

local disableNauticalBeacons = true

local gettext = require("i_18n")
local       _ = gettext.translate

--WORLD BEACONS

beaconsTableFormat = 2
beacons = {
{
	[b]display_name[/b] = _('');
	beaconId = 'airfield1_0';
	type = BEACON_TYPE_ILS_GLIDESLOPE;
	callsign = 'ICRR';
	frequency = 108700000.000000;
	channel = 24;
	position = { -360394.218750, 952.944679, -76976.257813 };
	direction = -88.617531;
	positionGeo = { latitude = 36.585008, longitude = -115.691917 };
	sceneObjects = {'t:170590208'};
};

Sounds like the changes are not too important. Still strange that I get the "obsolete" display_name rather than name.

Are you sure you're not using version 8 of my mod?

Version 8 had name.

Version 9 used display_name properly, aligned with the changed format.

Update: Okay just realized what was happening. I never updated the main download link to v9 (it only ever existed attached to a post mid-thread), so the top post still had v8 beacon data in it with the old format. This is now fixed for NTTR. I also don't have updated data for Normandy yet, will generate that this morning.

--gos

Edited January 28, 2018 by gospadin

funkyfranky · January 28, 2018

Update: Okay just realized what was happening. I never updated the main download link to v9 (it only ever existed attached to a post mid-thread), so the top post still had v8 beacon data in it with the old format. This is now fixed for NTTR. I also don't have updated data for Normandy yet, will generate that this morning.

Yes, that was the issue ;) Did not see v9 and was still using v8.

Thanks gos :thumbup: It's a very useful addition! :)

Sign In

Extra Beacons Mod

Recommended Posts

gospadin

gospadin

gospadin

gospadin

Woogey

HiJack

HiJack

gospadin

gospadin

Pikey

gospadin

gospadin

gospadin

Xxx

gospadin

Xxx

gospadin

gospadin

funkyfranky

gospadin

funkyfranky

gospadin

funkyfranky

gospadin

funkyfranky

Recently Browsing 0 members