Hamblue Posted February 19, 2013 Posted February 19, 2013 If you have nav system damage, after repair it's not a bad idea to reset it and let it go through alignment from scratch. In reality that's what would happen anyhow. Asus Sabertooth P67 Motherboard 2600k CPU, 16 gig DDR3, 1600. Samsung 830, 256 gig hard drive, GTX780 Video Card, Warthog Hotas, Razer Mamba mouse. Saitek Combat Rudder Pedals. Trackir 5, Verizon FIOS 25Meg Up/Down
KLR Rico Posted February 19, 2013 Posted February 19, 2013 I've run into the same problem. I'm pretty sure that the issue is that the initial coordinates in the CDU are used again when you realign. Unfortunately, the initial coordinates can't be changed... the only solution is to park on the same place you started when doing the alignment, which is not possible if you start in a HAS.... I haven't found another work around yet. i5-4670K@4.5GHz / 16 GB RAM / SSD / GTX1080 Rift CV1 / G-seat / modded FFB HOTAS
wess24m Posted April 18, 2013 Posted April 18, 2013 I've run into the same problem. I'm pretty sure that the issue is that the initial coordinates in the CDU are used again when you realign. Unfortunately, the initial coordinates can't be changed... the only solution is to park on the same place you started when doing the alignment, which is not possible if you start in a HAS.... I haven't found another work around yet. get your lat long from your position on the f10 map and input them i to the cdu alignment page during first alignment the cdu is using lat longs from your virtual data cartridge.
Recommended Posts