Jump to content

RSBN Channels (+1 again)...


slicker55

Recommended Posts

Trying to sort this mess out...

 

I have made a set of RSBN charts specifically for the MIG21 (one for each map) extrapolating the RSBN preset numbers directly from the Beacons.lua

 

I've made a custom mission to practice RSBN/PRMG landings at various runways on the Caucasus map and now I'm finding the RSBN presets are 'sometimes' +1 out

 

The keyword here is 'sometimes'... I can live with consistency - don't mind changing the values in my charts but why is the RSBN channel correct one minute and not the next?

 

I know RSBN discrepancies have cropped up in the past but has this ever been fixed?

 

:book:

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

Trying to sort this mess out...

 

I have made a set of RSBN charts specifically for the MIG21 (one for each map) extrapolating the RSBN preset numbers directly from the Beacons.lua

Not sure why you'd use beacons.lua, when it's been explained that the MiG-21 uses it's own files - R_NAV_data_Caucasus.lua, etc.

 

ED's 'beacons.lua' RSBN's are only applicable to the L-39, as previously explained.

 

I know RSBN discrepancies have cropped up in the past but has this ever been fixed?

IIRC, there was discussion of making the MiG-21 compatible with ED's generic beacons.lua map files but it has yet to happen.

i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

@Ramsay,

 

Of course, you are right, my mistake, got my knickers in a twist, it was the R_NAV_data_Caucasus.lua I used and not the Beacons.lua as perviously stated - apologies

 

I have now updated my reference material - thanks for clarifying everything - I hope they do align the MIG with the generic set - makes sense. I wonder why they didn't do that from the outset?

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

@Ramsay,

 

Of course, you are right, my mistake, got my knickers in a twist, it was the R_NAV_data_Caucasus.lua I used and not the Beacons.lua as perviously stated - apologies

 

I have now updated my reference material - thanks for clarifying everything - I hope they do align the MIG with the generic set - makes sense. I wonder why they didn't do that from the outset?

 

I suspect because the L-39 didn't exist when the aircraft module was developed, so they had no choice but to do their own thing. The MiG-21 was pretty much the first true third party module (originally an evolution of a third party mod for LOMAC/FC). When it was started, DCS had the Ka-50, A-10C, and P-51D. So nearly everything the MiG-21 needed had to be provided by the third party developers: weapons, radar, navigation systems, etc.

 

But now that the L-39 has been out for some time, it would make sense for ED's implementation to be used by any and all third parties. Presumably, Magnitude/Leatherneck has other priorities and no real incentive to go back and change their module to comply with ED's implementation.

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

@streakeagle

 

Appreciate your input...

 

I am doing my best to fully understand what you're saying ... please bear with me... I am really interested in this topic - sorry to harp on - wife say's I need to get out more...

 

Let's start with the premise, the true RSBN values are defined by ED in the map data.

 

First, was this data available in the map at the time the MIG was developed and if so, why didn't the developers simply use that data instead of creating a set of presets which were not properly aligned with the default values?

 

Please don't take any offence (none intended) but I don't get why the development and release of L-39 is relevant to the MIG21 other than to note that it uses the default data (as all modules should in my opinion)

 

Of course, you may mean that ED didn't define the default presets until the L-39 came along?

 

But then, if that was the case, prior to the L-39, RSBN wouldn't have been available across the board surely?

 

.

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

Let's start with the premise, the true RSBN values are defined by ED in the map data.

 

First, was this data available in the map at the time the MIG was developed and if so, why didn't the developers simply use that data instead of creating a set of presets which were not properly aligned with the default values?

IIRC RSBN, TACAN, PMRG and ILS weren't differentiated, with RED/BLUE FC3 aircraft using a common system.

 

The MiG-21 was coded with it's own RSBN/PMRG beacons/data (2014).

 

ED then differentiated FC3 systems and the Su-25T could no longer land using western ILS's and RSBN/PMRG refined further for the L-39 release (2015).

 

Please don't take any offence (none intended) but I don't get why the development and release of L-39 is relevant to the MIG21 other than to note that it uses the default data (as all modules should in my opinion)

 

Of course, you may mean that ED didn't define the default presets until the L-39 came along?

 

But then, if that was the case, prior to the L-39, RSBN wouldn't have been available across the board surely?

It wasn't


Edited by Ramsay
spelling

i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

... a chink is appearing in my cumulonimbus and I am starting to see the light!

 

:lol:

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

@Frederf

interesting

 

I have now cross-checked the values set in the MIG's R_NAV_data_Caucasus.lua and still have to increase each by +1 to get them to work in the cockpit

 

e.g Anapa is --1 (in the R_NAV_data_Caucasus.lua)

 

but, you need to dial in 02 on the RSBN in the cockpit to get it to work

 

happy enough that it is, at least, working but would still like to know why the vales in the code don't align with what's actually required in the cockpit...

 

I must be missing something, somewhere!

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

@Frederf

 

No mods

 

The RSBN / PRMG counters in my cockpit start at 00

 

Please clarify what you mean by 'both branches' - do you have more than one version of DCS installed?

 

I only have 2.5 installed

 

Again, just to clarify.. what number do you dial in for the RSBN at Anapa?

 

And, have you tested this recently?

 

I seem to recall this +1 issue is like, old news... I'm pretty sure I read about it ages ago (literally a few years back)

 

 

.

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

@Frederf

 

Very helpful - thanks - will investigate further

 

Just checked - I'm on OB 24984

 

I was just about to try your suggestion (post #10) but before I do, I should mention the +1 issue applies to all four maps!

 

 

Did you mean delete / repair

 

R_NAV_data_Caucasus.lua

 

or

 

R_NAV_data.lua

 

 

Update:

 

I checked and can see

 

R_NAV_data.lua

 

and

 

R_NAV_data-OLD.lua

 

 

I tried deleting and repairing both of these .lua's but +1 issue is the same

 

Will wait to hear if you meant the other .lua's

 

 

.


Edited by slicker55
clarify

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

@Frederf

 

OK, will follow your advice and let you know how I get on

 

Thanks again

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

  • 2 months later...

@Frederf

SOLVED: The problem arises with the Helios profile

At startup, RSBN/PRMG channels appear in sync with the cockpit but when the channel number is changed using the knob in the Helios profile, the +1 discrepancy occurs.

I have discovered that turning the knob in the Helios profile anti-clockwise so that it goes from 00 to 99 and then back to and beyond 00 fixes the issue - only need to do this once (at the start of the flight) everything is then properly in sync.

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...