INS

[diditopgun]

Today I played with the INS. Fun and interesting ! :pilotfly:

 

First I start a standard alignement and enter my present position and see as expected the 1s arc bug.

 

While INS is aligning I try with success to enter a 7th waypoint to my original 6 waypoint flight plan. Great ! But it looks like an issue occur: DEST key don't allow me to select other waypoints anymore.

I wait the INS finish full alignment, switch to NAV mode and then DEST key is working again.

 

Later in flight I realize that my new 7th waypoint coordinates are exact and are not affected by the 1s arc bug.

 

TR/VS: remaining time with the update now show 0.02 for 2min instead of 2.00

 

CP/PD: when I enter a 2.5° slope it correct it to 2.0 as if it don't care of the decimal. Runway heading works fine as the synthetic runway.

 

BAD: I didn't find the way to use it. Distance/bearing to offset waypoint indicate strange values:

When I enter 2nm and 195° it display 20000.0 and 19500.0 .....

The BAD key isn't supposed to select the offset waypoint as destination and VAD mode in HSI to show bearing and distance ?

 

MRC key: I don't understand too how it works.

Edited June 26, 2016 by diditopgun

[westr]

select next waypoint on the INS doesn't seem to be working. I selected INS doesn't need alignment in the special tab in settings menu. But could not select any pre planned WP's.

I tried flying to WP1 from Takeoff. When I got to the WP it switched to WP2. So It works doing it like that but it doesn't seem to work if you try and select WP's.

[Azrayen]

The BAD key isn't supposed to select the offset waypoint as destination

Yes it is supposed to. Dunno if implemented yet, didn't try that.

 

and VAD mode in HSI to show bearing and distance ?

No. VAD and BAD are different things. VAD not implemented AFAIK (for now).

To use BAD is like to use BUT, just a * should be displayed next to the BUT number in the HUD.

 

MRC key: I don't understand too how it works.

I suppose you mean MRQ?

Doesn't seem to work ATM.

[diditopgun]

No. VAD and BAD are different things. VAD not implemented AFAIK (for now).

To use BAD is like to use BUT, just a * should be displayed next to the BUT number in the HUD.

 

In the manual it says VAD give Offset bearing and distance... Maybe it's an outdated information.

 

I suppose you mean MRQ?

Doesn't seem to work ATM.

 

Yes MRQ but in cockpit it's MRC on the key.

[Zeus67]

The BAD, MRQ (Yes, it says MRC) and REC buttons are not active at this time.

[Azrayen]

In the manual it says VAD give Offset bearing and distance... Maybe it's an outdated information.

It's not outdated. VAD and BAD use the same "logic" (= offsetting) but, again, are different things.

BAD = relates to a BUT. INS system.

VAD = relates to a TACAN beacon. Independent from the INS. Not implemented yet. http://forums.eagle.ru/showthread.php?p=2691022#post2691022

[diditopgun]

Ok thanks.

[Pikey]

OP you also mentioend glideslope - enter the figures with a preceeding 0 to fill the blanks, the decimal is already there.

 

Synthetic runway not working yet according to Zeus, he's fixing the arc ll issue first.

[diditopgun]

I did.

 

In fact synthetic runway and ILS work same as 1.5.3, they don't care of INS CP/PD.

[Zodiac]

cant change wp anymore after the update

[nomdeplume]

cant change wp anymore after the update

This is known, you'll have to do it the 'hard way' for now:

 

Press DEST on INS panel, then enter the two digit waypoint number (for waypints <10, enter a leading 0), after the second digit the destination waypoint will immediately update.

 

INS panel only displays the PREP waypoint details, you can copy the current DEST waypoint there easily by double-pressing the PREP button.

[Zaz0]

About the INU, I don't know if it's intended, but allways I check "WP 00" LAT LONG at VEI mode, is different to LAT LONG data obtained at F10 view, like actual manual we got (and because I'm not happy with the coordinates), I correct them, and sometimes I imput some of them they has changed some arc-seconds... like this:

 

My imput -> N42.10.004 -> INS Key

Displayed -> N42.10.005

 

I don't know if I doing something wrong or this is correct behaviour...

 

PS: I have INU need to aling allways and Giro Drift enables options ON.

 

Thanks for your work!!

[Zeus67]

About the INU, I don't know if it's intended, but allways I check "WP 00" LAT LONG at VEI mode, is different to LAT LONG data obtained at F10 view, like actual manual we got (and because I'm not happy with the coordinates), I correct them, and sometimes I imput some of them they has changed some arc-seconds... like this:

 

My imput -> N42.10.004 -> INS Key

Displayed -> N42.10.005

 

I don't know if I doing something wrong or this is correct behaviour...

 

PS: I have INU need to aling allways and Giro Drift enables options ON.

 

Thanks for your work!!

 

Known bug. DCS generates a 1 arc-second error for present position. I am trying to squash it but for the time being, the error is so small as to be easily dismissable.

[Zaz0]

Note the first part of my post too Zeus, it's a difference between default WP 00 coordinates at INU and F10 option, and there isn't only a digit, I saw even a minute error, it could be possible?

[Whisper]

AFAIK done on purpose to have initial coordinates entered manually

[nomdeplume]

Regarding the previous two posts, yes the inaccuracy of the initial position is intentional.

 

From an earlier post in this thread:

 

When you start the aircraft with an unaligned INS, the Present Position (PP) coordinates will be off by a random amount no larger than 10,000 meters.

 

I think the idea is to give a sense of purpose to entering the initial position without making it mandatory.

 

The max. 10 km offset is large enough that you'll get some value from entering the proper position, especially for ground attack missions and the like; but it's also small enough that for a lot of "I just want to get in the air and shoot things down" cases it will be irrelevant.

[Zaz0]

Copy that, I missed it

 

Thanks!

[Frederf]

Regarding the previous two posts, yes the inaccuracy of the initial position is intentional.

 

From an earlier post in this thread:

 

 

 

I think the idea is to give a sense of purpose to entering the initial position without making it mandatory.

 

The max. 10 km offset is large enough that you'll get some value from entering the proper position, especially for ground attack missions and the like; but it's also small enough that for a lot of "I just want to get in the air and shoot things down" cases it will be irrelevant.

 

I wondered if it was intentional. Entering position before align is fun but I was unable to alter the elevation. Also I couldn't set 2.5 degree GS for my landing waypoint and the APP mode wasn't working as I remember nor ILS.

[Azrayen]

but I was unable to alter the elevation.

Answered here: http://forums.eagle.ru/showthread.php?t=169091

 

Also I couldn't set 2.5 degree GS for my landing waypoint and the APP mode wasn't working as I remember nor ILS.

APP mode is still WIP.

CP/PD not available yet.

[Oesau]

Not often I can't work things out (especially when there is a manual with step by step instructions) but here we go.

 

For a Standard INS alignment (following the steps on page 90) I never get the the ALN, PRET etc lights to come on the PCN. The LCD displays are active (with lat/log data showing) so the unit is powered (along with ground power).

 

INS Does not require alignment - off (unchecked)

Disable Gyro drift - off (unchecked)

 

I'm a little lost at the moment so any direction/help would be appreciated

Edited June 29, 2016 by Oesau
updated in game settings detail

[Azrayen]

I have enabled align always & Giro Drift enables options ON within the special settings menu.

 

Uh? The options are the contrary... "No alignment needed" and "Disable gyro drift". So when those simplification options are ON, this DE-ACTIVATES some INS related features (to make it simpler for beginners/casual pilots).

=> If you want to perform the full thing as IRL, please make sure to leave those options OFF.

 

If you've already done that, please describe what you do precisely (or make a short track and attach is there) so we have a chance to find what's wrong.

 

++

[Oesau]

Uh? The options are the contrary... "No alignment needed" and "Disable gyro drift". So when those simplification options are ON, this DE-ACTIVATES some INS related features (to make it simpler for beginners/casual pilots).

=> If you want to perform the full thing as IRL, please make sure to leave those options OFF.

 

If you've already done that, please describe what you do precisely (or make a short track and attach is there) so we have a chance to find what's wrong.

 

++

 

You are right - I've corrected my post indicating that in the settings menu the INS does not need alignment and disable gyro drift are unchecked (off).

 

However I've worked out what the issue was, the English cockpit mod was not displaying the ALN or PRET lights... (my mistake)

[ZHeN]

Once I aligned INS and forgot to turn PSM knob to NAV in the end.

I didn't move the plane (didn't even start the engine).

After aligning I needed to enter coordinates for my new WP04.

After I did it, I turned the PSM knob to NAV and INS said it needed re-aligning - why???

And I couldn't even start over the aligning procedure ... VAL button just didn't light up ... why ?

Edited July 1, 2016 by ZHeN

[Zeus67]

Once I aligned INS and forgot to turn PSM knob to NAV in the end.

I didn't move the plane (didn't even start the engine).

After aligning I needed to enter coordinates for my new WP04.

After I did it, I turned the PSM knob to NAV and INS said it needed re-aligning - why???

And I couldn't even start over the aligning procedure ... VAL button just didn't light up ... why ?

 

I'll check.

[Cantiga]

Now INS drift works, but HUD NAV marker indicates different position than HSI needle and distance.

is that normal?