JayRoo Posted January 18, 2020 Share Posted January 18, 2020 I currently have another bug thread out regarding navigation and ins issues, but I don't know if this one is related so i'm making a separate post. Master Arm on air to ground on select a Mk82 for example mode and fuzing set up example of what I see: when in straight and level flight, the bomb fall line extends from the bottom of my velocity vector straight horizontal to the left and parallel to the horizon line. any thoughts? thanks in advance! Link to comment Share on other sites More sharing options...
Gianky Posted January 18, 2020 Share Posted January 18, 2020 I had the same issue, in the Hornet battle group delta campaign, before the last patch. I'm pretty sure I had aligned the INS correctly, map and navigation directions were functioning well. No idea if the issue is related to the mission date. I had Mk-83s, set for CCIP, nose MFuz, inst Efuz and single bomb release. Link to comment Share on other sites More sharing options...
JayRoo Posted January 18, 2020 Author Share Posted January 18, 2020 (edited) Here's a clip of me showing what I'm seeing. Sorry for the VR and low quality commentary audio. I don't have good recording equipment. https://youtu.be/jyFouIt4Nzc Edited January 18, 2020 by Strider Link to comment Share on other sites More sharing options...
Gianky Posted January 18, 2020 Share Posted January 18, 2020 That's more or less what I'm seeing, the only difference being that in my case the bomb line isn't perfectly horizontal, when in level flight, it has a 20-30 degrees of downward inclination, to the right of the flight path marker. Link to comment Share on other sites More sharing options...
NoJoe Posted January 18, 2020 Share Posted January 18, 2020 I have noticed this too in a mission (Hornet over PG, based on Mbot's dynamic campaign, I believe it was) whose date was set to the late 90s or early 2000s. After I opened the mission in the mission editor, changed the date to 2019, and re-saved it, the issue was gone. I'm not sure if it was the act of simply re-saving the mission, or if changing the date was the fix. Not sure if that's related, but worth checking. Link to comment Share on other sites More sharing options...
JayRoo Posted January 18, 2020 Author Share Posted January 18, 2020 Oooo. Not a bad idea Joe. Ill change up the mission date in the mission editor and save and retry when i can. Thanks for the tip. Link to comment Share on other sites More sharing options...
JayRoo Posted January 19, 2020 Author Share Posted January 19, 2020 [sOLVED] thank you for the suggestion NoJoe. The mission was set in 1989 and i emptied the description, changed the date and the time of day just to be sure and saved it as a new name and it worked. Super weird. Thank you for taking the time to post. It worked this time. Thanks! Link to comment Share on other sites More sharing options...
QuiGon Posted January 21, 2020 Share Posted January 21, 2020 It's probably because you didn't perform a proper INS alignment, because in missions with date prior 1994 GPS is missing which requires some manual input for a proper INS alignment. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing! Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted January 21, 2020 ED Team Share Posted January 21, 2020 Thanks for letting us know it is solved. closed Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
Recommended Posts