kelpie Posted June 7, 2017 Posted June 7, 2017 (edited) I noticed in DCS 2.1 whenever I align the INS it always points south. When I skip to the next waypoint it continues to point south or moves just slightly. In 1.5.6 the INS aligns ok. But 2.1 is off. I'm having problems with other planes too in 2.1, so I don't know if the problem is with 2.1, my installation of DCS, or just that 2.1 had changes that the 3rd party developers haven't noticed or addressed yet. Is anyone else having this issue too? If not then I can only assume it's my installation. I already repaired my DCS 2.1 installation but the issue remains. Additional Information: In DCS 1.5.6 when I land the M2000C at a different airfield than where I took off from, refuel, and then realign the INS it does the same thing. Edited June 8, 2017 by kelpie Modules: Owned: P-51D, F/A-18C, AJS-37, NTTR, F-5E, M-2000C, Bf 109, Fw 190 D-9, F-86F, Mig-15Bis, A-10C, Combined Arms, Mi-8Mtv2, UH-1H, Black Shark 2, Mig-21Bis, FC3, F-14A/B, Mig-19, Spitfire, JF-17, Persian Gulf Would Like to See: Mig-29K, Su-24, Mig-25, J-8II, J-10 , Tornado __________________ Specifications: Windows 10 64Bit, i7-7700K 4.2Ghz, GTX 1080, 16Gb RAM, T.flight Stick X
dwpenney Posted June 28, 2017 Posted June 28, 2017 I ran a test mission in DCS World 2.1 last night on the Navada map and the INS was pointing correctly (HSI and HUD indications). Are you sure that you entered the INS Start values correctly? Ie: selecting N and E/W before entering the numbers? Fridge ---------- Things which do you no good in aviation: 1) Altitude above you; 2) Runway behind you; 3) Fuel in the truck; 4) The airspeed you don't have.
kelpie Posted July 20, 2017 Author Posted July 20, 2017 I ran a test mission in DCS World 2.1 last night on the Navada map and the INS was pointing correctly (HSI and HUD indications). Are you sure that you entered the INS Start values correctly? Ie: selecting N and E/W before entering the numbers? Yup, everything is entered correctly. I double checked all of that. I also repaired 2.1 in case it was my install that was having the problem but that didn't help either. If you're running it ok then there must be an issue on my end. :doh: I just don't know what it could be. Modules: Owned: P-51D, F/A-18C, AJS-37, NTTR, F-5E, M-2000C, Bf 109, Fw 190 D-9, F-86F, Mig-15Bis, A-10C, Combined Arms, Mi-8Mtv2, UH-1H, Black Shark 2, Mig-21Bis, FC3, F-14A/B, Mig-19, Spitfire, JF-17, Persian Gulf Would Like to See: Mig-29K, Su-24, Mig-25, J-8II, J-10 , Tornado __________________ Specifications: Windows 10 64Bit, i7-7700K 4.2Ghz, GTX 1080, 16Gb RAM, T.flight Stick X
Azrayen Posted July 20, 2017 Posted July 20, 2017 99% of chances that it's an input error, either on the initial position (00 before start) or in the active waypoint position. What was the range?
kelpie Posted July 20, 2017 Author Posted July 20, 2017 Ok, got it fixed. I needed to do a second repair on DCS 2.1 and now it's working perfectly. ;) Modules: Owned: P-51D, F/A-18C, AJS-37, NTTR, F-5E, M-2000C, Bf 109, Fw 190 D-9, F-86F, Mig-15Bis, A-10C, Combined Arms, Mi-8Mtv2, UH-1H, Black Shark 2, Mig-21Bis, FC3, F-14A/B, Mig-19, Spitfire, JF-17, Persian Gulf Would Like to See: Mig-29K, Su-24, Mig-25, J-8II, J-10 , Tornado __________________ Specifications: Windows 10 64Bit, i7-7700K 4.2Ghz, GTX 1080, 16Gb RAM, T.flight Stick X
Recommended Posts