ABRIS Nav Error - Fixing your position | DCS Ka-50 Black Shark III

Рет қаралды 1,396

Күн бұрын

A way to 'update' the ABRIS when it's not moving you, usually when you see "NAV ERROR" up top.
------------------------------------------------------------------------------------------------------------
To support the channel: www.buymeacoff...
and yes, I do run on coffee.
------------------------------------------------------------------------------------------------------------

Пікірлер: 22

@HobelDcs 9 ай бұрын

The master speaks, listens to him

@volkvoort 9 ай бұрын

lol. one of many, yourself included

@pack_rat 9 ай бұрын

Chizh once told me (in russian part of ED forum) there's no way for ABRIS to update coordinates from INU in real time. ABRIS just can't use INU as realtime coords source for itself. Ka-50 was mostly unfinished, after all. But. As far as I understand Ka-50 datalink, wingmen positions are transmitted by their INU coordinates (just like memorized targets are)! (Cause ABRIS works as display only in this case.)

@volkvoort 9 ай бұрын

Interesting. I know it gets heading and some other information from the Rubicon (and by extension the INU) rather than purely GPS. That page with the K-041 and "minutes to next INU update" or some similar language was interesting - though I know Chizh also said only the civilian ABRIS is patched in to automatically update an INU IIRC.

@pack_rat 9 ай бұрын

@@volkvoort It is impossible to tell exact heading by GPS alone (especially when stationary) - that's why ABRIS share compass with INU. Same goes to altitude readings - impossible to tell exactly by GPS alone, so - blah, blah... Found my question and Chizh's answer about INU realtime position readings for ABRIS, check PM on ED forum, please. Long story short: intended but never implemented. Maybe I could still find more from Chizh on this matter, but it will change nothing.

@volkvoort 9 ай бұрын

@@pack_rat Thanks - I just meant it's definitely integrated to fetch some readings from the INU/Rubicon/other systems, so possibly could/did fetch more readings. Whether it used them and how far that was integrated..... Will check DM a bit later.

@helldivermando 9 ай бұрын

Thank you 🙏 valuable as always. I was testing some GNSS navigation and settings recently as well; my original thought was that the nav error builds due to a low satellite elevation mask during terrain flight. I excluded some satellites and adjusted the elevation mask but haven’t gone deeper then that. What are your thoughts here?

@volkvoort 9 ай бұрын

You're ahead of me there - not sure I've seen many cases where it shows lower elevation or bad returns from satellites, rather than simply zero returns because something's not working. Was that adding their numbers to Exclude and running Save/Test one by one?

@helldivermando 9 ай бұрын

Yes, though not 100% that. When excluding Satellites you can leave the terrain mask unchanged, but just exclued specific satellites. When changing the terrain elevation mask, you exclude groups. The way I understand it, is that due to unprecise readings with satellites being low on the horizon, your position will not be represented accurate (sometimes you see the AC symbol bumping around when in hight zoom on the ABRIS). It gets worse when you are in terrain flight. This does not happen if you adjust the elevation mask. From what I tested it is modelled in DCS but like mentioned above I havent tested further. When I get any data or reliable readings, Ill reach out. And please keep up the content - your tutorials are great for beginners and intermediate. 👍

@volkvoort 9 ай бұрын

@@helldivermando Thanks. And that is very interesting on the low altitude. I know there have been funny stuff for VR people with it bouncing around/flickering/refresh rate issues, didn't notice a bounce with masking... but then again perhaps I just haven't flown NOE properly in a while, or kept looking out when it's jumping around location.

@inf3243 5 ай бұрын

Oof. I just fired up the Ka-50 after a long time away to check out the Kola map in style and suddenly having this NAV ERROR problem. Thought maybe I'd forgotten some part of the startup.

@volkvoort 5 ай бұрын

Might be your date is too early for satellite nav (think cut off was 1992).

@inf3243 5 ай бұрын

@@volkvoort Close. It was because the coalition I'd assigned in the mission editor didn't include Russia!

@volkvoort 5 ай бұрын

@@inf3243 Good spot - I forgot there was some requirement for I think specifically USA or Russia to be on your coalition side.

@l85a1rt4 9 ай бұрын

How you open that card from F10 map and than you can read it in cockpit??

@volkvoort 9 ай бұрын

If I recall correctly, hold left-alt and then left click on the F10 map. That popup then stays onscreen even when you return to the cockpit until you manually close it.