diditopgun

It looks like even in VEI. mode we cant change WP00 altitude. I can edit the data but when I click on INSERT the value come back to default one (which is altitude at standard QNH by default). Only way to change it is by the atmospheric pressure rotary knob on the altimeter.

I am back from a 01H20 flight to test gyro drift and I see no drift... Waypoint is perfectly on the landmark I chose. What's wrong ? :huh:

Yes I did a location mistake.... I switch between too much internet forums and tabs, sorry ^^

Hi all ! :) Here are some informations about INS given by a real Mirage crew member (thanks to him and sorry for my English, I try to do my best) on Check-six french forum: It's done on Park group because it needs 400Hz to feed the inertial unit. We avoids to do it while engine running due to vibrations. ----------------------------------------- Have to always check the heading in the INS in DCI 100so The ALCM is a particular alignment mode for takeoff on alert, mainly used by the PO (Permanence Opérationnelle - Quick Reaction Alerte). You must have done previously an ALN, so, did not have move the plane after his return to parking. An ALCM requires having the coordinates lat / lon / alt and exact heading. An ALN, normal ALIgnment, always takes 8mn, whatever the heading inserted. To determine the heading, the INS uses the the latitude's cosinus and measures the Earth's rotation speed. Maybe it can help you Zeus ?

It both illuminates the ground but not the Il-78 (and maybe other aircraft, i didn't test) at night so it's impossible to refuel without seeing the basket...

Yes of course. I only report that the TDC position relative to bullseye actually give us wrong numbers:

Hi Zeus ! Yes I agree it should operate this way, but actualy only TDC position relative to aircraft is correct. TDC position from bullseye is wrong.

I turned it off and engine and battery too. Same issue ;)

Mhmm ! OK, thanks for the trick.

What an idea ! Simmers always find incredible ways to find bug, devs might be crazy. :megalol:

I don't understand what you did but funny effect ! :laugh:

Hi ! I set waypoint altitude on the ground at landmark to look at INS drift (too short flight I think because I didn't see any visible drift btu that's not the matter). What I saw is the crosshair position ahead landmark when I am far and when I close up it finally go to the landmark position when I am near to overfly it: So I first thought the crosshair was maybe under ground level altitude. But after further tests it looks like not. If I set the waypoint at 700ft (ground level is 597ft) and fly in level flight, crosshair is at bridge table level when I am far. And at about 3nm, crosshair start rising up to reach its altitude above the bridge at 700ft: Rather strange isn't it ? :noexpression:

Yes I try it too. After landing and shutting down the aircraft (engine and battery), when I start up again INS was still aligned and can't launch any kind of ALCM or ALM.

+1

+1

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

:cheer3nc:

Ok thanks.

In the manual it says VAD give Offset bearing and distance... Maybe it's an outdated information. Yes MRQ but in cockpit it's MRC on the key.

Aaah ! Thanks ! :thumbup:

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.

Ok thanks ! Waiting for BA2/BAH answer. ^^

Hi ! Selection of waypoint 00 on VTB set our aircraft as the bullseye position and bullseye infos are distance and azimut of the TDC from it. Ok I have no problem with that. But if I select any other waypoint from the original flight plan or added in flight, the distance/azimut infos on the VTB look totally wrong and link to nothing coherent. Exemple: the bullseye is 6nm in front of me bearing 212. I put my TDC at this position and bullseye infos show 371/296 ... :huh: WIP ?

Hi ! It looks like the selection of LEN or RAP fire rate don't have any effect whatever A/A and A/G or TOT and PAR are selected.

Hi ! When I do the PA test the green light stay on even after I put the switch off et close the cover. The PA red light stay on too on the warning panel. I do something wrong or it's a bug ? (no problem with the CDVE test switch)