lwalter Posted May 3, 2020 Posted May 3, 2020 Yesterday, I played one of the missions coming with the F16, where you have to bomb anti-ship missiles located on an island of the Persian Gulf. I went through normal INS alignement and waited until "ALIGN" flashed on the HUD, before moving the INS switch to "NAV". The HSD was displaying the waypoints properly. The DED was showing the waypoint with correct long/lat and elevation. However in the HUD, the diamond supposed to show the waypoint was always stuck in the middle. The distance and time info to waypoint in the bottom right of the HUD where always stuck to 000, except the waypoint number. Has it every happening to anybody else? Or does it ring a bell to somebody about something wrong I may have done? I have a track file, but it's over 30 MB large. I don't know if I can upload it here. iMac Retina 5K, 27-inch, i7 4 GHz, 32 GB RAM, AMD R9 M395X 4 GB | Thrustmaster HOTAS Warthog | Cougar MFD | MFG Crosswind | EDTracker Pro | Realteus ForceFeel DCS World | Bf109 | Fw190 A8/D9 | P47 | P51 | Spitfire | I16 | C101 | L39 | F86F | MiG15 | MiG19 | MiG21 | FC3 | A10C | AJS37 | AV8BNA | F5 | F14 | F16 | F/A18 | M2000 | JF17 | Christen Eagle | Yak52 | SA342 | UH1H | Mi8 | Ka50 | Combined Arms | NS430 | Persian Gulf | Normandy | Channel | Syria | NTTR | WWII Assets
Svend_Dellepude Posted May 3, 2020 Posted May 3, 2020 Did you confirm your position within 2 minutes of starting alignment? [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
lwalter Posted May 3, 2020 Author Posted May 3, 2020 Did you confirm your position within 2 minutes of starting alignment? Do you have anything special to do to confirm your position? The default coordinates were fine. iMac Retina 5K, 27-inch, i7 4 GHz, 32 GB RAM, AMD R9 M395X 4 GB | Thrustmaster HOTAS Warthog | Cougar MFD | MFG Crosswind | EDTracker Pro | Realteus ForceFeel DCS World | Bf109 | Fw190 A8/D9 | P47 | P51 | Spitfire | I16 | C101 | L39 | F86F | MiG15 | MiG19 | MiG21 | FC3 | A10C | AJS37 | AV8BNA | F5 | F14 | F16 | F/A18 | M2000 | JF17 | Christen Eagle | Yak52 | SA342 | UH1H | Mi8 | Ka50 | Combined Arms | NS430 | Persian Gulf | Normandy | Channel | Syria | NTTR | WWII Assets
Deano87 Posted May 3, 2020 Posted May 3, 2020 Do you have anything special to do to confirm your position? The default coordinates were fine. You have to go through each line of coords and confirm them with the ENTR button on the ICP. This only needs to be done on a full 8 min alignment. If you do a stored heading alignment it doesn’t need to be done. Proud owner of: PointCTRL VR : Finger Trackers for VR -- Real Simulator : FSSB R3L Force Sensing Stick. -- Deltasim : Force Sensor WH Slew Upgrade -- Mach3Ti Ring : Real Flown Mach 3 SR-71 Titanium, made into an amazing ring. My Fathers Aviation Memoirs: 50 Years of Flying Fun - From Hunter to Spitfire and back again.
lwalter Posted May 3, 2020 Author Posted May 3, 2020 You have to go through each line of coords and confirm them with the ENTR button on the ICP. This only needs to be done on a full 8 min alignment. If you do a stored heading alignment it doesn’t need to be done. I think you got it. I usually do stored alignment and this time I went through full alignment and didn't confirm the coordinates... Thanks Svend and Deano! I have a side question: how come the HSD would still work properly? iMac Retina 5K, 27-inch, i7 4 GHz, 32 GB RAM, AMD R9 M395X 4 GB | Thrustmaster HOTAS Warthog | Cougar MFD | MFG Crosswind | EDTracker Pro | Realteus ForceFeel DCS World | Bf109 | Fw190 A8/D9 | P47 | P51 | Spitfire | I16 | C101 | L39 | F86F | MiG15 | MiG19 | MiG21 | FC3 | A10C | AJS37 | AV8BNA | F5 | F14 | F16 | F/A18 | M2000 | JF17 | Christen Eagle | Yak52 | SA342 | UH1H | Mi8 | Ka50 | Combined Arms | NS430 | Persian Gulf | Normandy | Channel | Syria | NTTR | WWII Assets
Recommended Posts