Panthir Posted June 9, 2019 Share Posted June 9, 2019 Thank you very much for this. Your suggestion fixed my problems. I'll update my bug report, hopefully this info leads to ED figuring this out quicker. Some additional info: I noticed my mission was already in year 2011. I edited it to 1988. Saved. Fly. It's still not working. Re-edited the mission, changed date to 2019. Saved. Fly. Fixed! Hot start is fixed right off. Cold start in the hornet takes +54 seconds after you get 0.5 OK before the coordinates update, map shows up, and waypoints have proper distances. At that point you can move to NAV. Interestingly, I haven't had to edit any other mission after doing this. Now all missions I have tried, even those with the default date of Jun 1 2011, work fine. I did some more narrowing down and it appears the magic date and time is 3/28/1994 at 00:00:00. Anything AFTER this date and time and INS works fine. Anything before and including this time and it doesn't work. Yes, 3/28/94 at 00:00:00 doesn't work, but a mission time of 00:00:01 does work. If you start at 00:00:00 it does NOT start working once you hit 00:00:01. I will try this fix and I will give feedback My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27" My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE. My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic. Link to comment Share on other sites More sharing options...
Panthir Posted June 9, 2019 Share Posted June 9, 2019 Found the solution at least for my case. I deleted the F-18C folder in Mods/Aircrafts and I repaired DCS. Everything now works exactly as described "Cold start in the hornet takes +54 seconds after you get 0.5 OK before the coordinates update, map shows up, and waypoints have proper distances. At that point you can move to NAV" My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27" My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE. My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic. Link to comment Share on other sites More sharing options...
mechanicos Posted June 9, 2019 Share Posted June 9, 2019 Found the solution at least for my case. I deleted the F-18C folder in Mods/Aircrafts and I repaired DCS. Everything now works exactly as described "Cold start in the hornet takes +54 seconds after you get 0.5 OK before the coordinates update, map shows up, and waypoints have proper distances. At that point you can move to NAV" Thank you Panthir , that worked for me either, finally i got a propertly alignment even on a carrier deck Link to comment Share on other sites More sharing options...
Furia Posted June 9, 2019 Share Posted June 9, 2019 (edited) Found the solution at least for my case. I deleted the F-18C folder in Mods/Aircrafts and I repaired DCS. Everything now works exactly as described "Cold start in the hornet takes +54 seconds after you get 0.5 OK before the coordinates update, map shows up, and waypoints have proper distances. At that point you can move to NAV" I have updated the Bug Thread https://forums.eagle.ru/showthread.php?p=3942741#post3942741 Sadly your propossed solution does not work.I have tried it with no success. The failure is related to how the mission is edited If the Hornet is USA and the mission date is relatively modern, then it INS works nicely. See the Bug report for more detailled info Edited June 9, 2019 by Furia [sIGPIC]http://menorca.infotelecom.es/~raulurbina/ESA/banner_furia.png[/sIGPIC] Link to comment Share on other sites More sharing options...
Ironwulf Posted June 9, 2019 Share Posted June 9, 2019 I have no problem with an RAAF Hornet once the date was fixed. Note however I changed the date back to pre-2000 and it still worked, so would agree its something to do with ME saving. Link to comment Share on other sites More sharing options...
33rd_Elvis Posted June 15, 2019 Share Posted June 15, 2019 In my case the INS don´t work when i take RED coalition. And in BLUE coaltion it´s work. :dunno: Aircrafts: F-16C | TF-51 | M2000C | F/A-18C | AV-8B | Viggen | KA-50 | A-10C | UH-1 | Mi-8 | Maps: Caucasus | Persian Gulf | NTTR | Normandy | Syria System: AMD Ryzen 3700X | 32GB Ram | AMD Radeon RX 5700 XT | Win10 64Bit | 1TB 970 EVO M.2 SSD Equipment: TrackIR 5_Trackclip Pro |TM Warthog HOTAS | Oculus Rift S Link to comment Share on other sites More sharing options...
unknown Posted June 15, 2019 Share Posted June 15, 2019 In my case the INS don´t work when i take RED coalition. And in BLUE coaltion it´s work. :dunno: Reported bug :beer: Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
Recommended Posts