Cueball Posted March 28, 2019 Posted March 28, 2019 I have recently switched to the open beta version of DCS World. While doing a cold start (AUTO) from the deck of a carrier. When the start up is complete and I taxi over to the catapult, everything is fine. All that needs to be aligned is aligned. As soon as I launch the flight path indicator shoots off the the left of the HUD and stays there along with all heading readings freeze to 000. The same goes for the lower middle map display (no course rotation at all). But if I launch the mission with the plane starting hot all works fine. I have tested this several times with the same results. I would appreciate any input into fixing this.
Ramsay Posted March 28, 2019 Posted March 28, 2019 Please post a track file i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Cueball Posted March 28, 2019 Author Posted March 28, 2019 Will do. Stupid question, where do I find it?
Harker Posted March 28, 2019 Posted March 28, 2019 C:\Users\<Your User Name>\Saved Games\DCS\Tracks The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
discwalker Posted March 28, 2019 Posted March 28, 2019 Currently you must set INS knob to NAV manually after auto start INS alignment: https://forums.eagle.ru/showthread.php?t=237364 GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD
Cueball Posted March 28, 2019 Author Posted March 28, 2019 I will try this then follow up. I'm sure it will be something as small as this. I just never had this issue before. I am also aware as development progresses there will be more thing we will have to do the won't be setup to be defaulted any longer. I noticed this when I came to arming dumb bombs.
GeneralDynamics Posted March 29, 2019 Posted March 29, 2019 Velocity vector locked after 2.5.4.29004 Open Beta update DCS 2.5.4.29004 Instant Action, Caucuses, Cold Start After AutoStart, taxi to runway and takeoff, velocity vector is locked in position at about 1 degree above level flight and does not traverse the pitch ladder when climbing or diving. Screen shot attached showing the position of the velocity vector - it never changes from this position relative to the pitch ladder. System Specs: Win 10 x64 Pro, ASUS Maximus X Formula, i9-9900K @ 4.7 GHz, 32GB Corsair Dominator Platinum 3200 MHz, NZXT Kraken X73 AIO Cooler, Titan X Pascal GPU, EVGA Supernova 1000W P2 PSU, C: 1TB Samsung 960 Pro m.2 PCIe SSD, D: 1TB Samsung 850 Pro SATA SSD, HT Omega Claro PCIe 7.1 Sound, Denon AVR-1709 7.1 Receiver, 46" Sharp Aquos Quattron Main Screen, 27" Acer T272HL TouchScreen + Helios, TrackIR 5, ThrustMaster HOTAS Warthog, Crosswinds pedals, SimShaker
Harker Posted March 29, 2019 Posted March 29, 2019 Does it happen with a normal cold start? The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
GeneralDynamics Posted March 29, 2019 Posted March 29, 2019 (edited) Didn't try a normal cold start since I haven't dug into the procedure that deeply yet, on my to do list. But I can tell you it does not occur in the free flight Instant Action mission. Based on that, it does seem to be possibly related to a change in the AutoStart procedure. I didn't include a track file because I didn't think ED would want the entire track of the AutoStart. But if ED would like a track file, I'll be happy to record one showing the behavior. Edit: added track file. You'll notice that I updated to hotfix 2.5.4.29079 to see if that would fix the issue (it did not) but this started with DCS 2.5.4.29004.Velocity vector issue.trk Edited March 29, 2019 by GeneralDynamics System Specs: Win 10 x64 Pro, ASUS Maximus X Formula, i9-9900K @ 4.7 GHz, 32GB Corsair Dominator Platinum 3200 MHz, NZXT Kraken X73 AIO Cooler, Titan X Pascal GPU, EVGA Supernova 1000W P2 PSU, C: 1TB Samsung 960 Pro m.2 PCIe SSD, D: 1TB Samsung 850 Pro SATA SSD, HT Omega Claro PCIe 7.1 Sound, Denon AVR-1709 7.1 Receiver, 46" Sharp Aquos Quattron Main Screen, 27" Acer T272HL TouchScreen + Helios, TrackIR 5, ThrustMaster HOTAS Warthog, Crosswinds pedals, SimShaker
Cueball Posted March 29, 2019 Author Posted March 29, 2019 (edited) Currently you must set INS knob to NAV manually after auto start INS alignment: https://forums.eagle.ru/showthread.php?t=237364 I just finished testing this. Discwalker is correct the INS knob stayed in the CV setting after the auto start was complete. So I turned the knob to NAV and HUD and map switched to the proper headings. In an attempt to see if when the INS needed to be in NAV mode I turned it back to CV then launched from the carrier. This time the flight path indicator shot to the right and the heading were stuck at roughly 170 degrees which was the heading it switched to after turning it to NAV. I took off and switched it to NAV and it did nothing. Both heading and FPI were still stuck. Next test determined that the INS knob MUST be switched to NAV before moving the aircraft. As soon as the auto-start was complete I switched the INS to NAV and left it alone. I launched and all was fine and working. So lesson learned and thank you all for your feed back. Unless the devs change this in the auto-start feature remember this if cold starting the F-18C. TURN the INS to NAV prior to moving the plane. If you start the mission with a hot plane you will be fine. RAMSAY: I don't have the TRACK files I looked for then and it was just 3 old ones from 2018. Edited March 29, 2019 by Cueball
GeneralDynamics Posted March 29, 2019 Posted March 29, 2019 (edited) I can confirm that setting the INS knob to NAV after AutoStart completes also resolved my issue. Thanks! If anyone is interested in seeing the behavior after taking off with the INS knob in the GND position, I added a track to my post on the previous page. Edited March 29, 2019 by GeneralDynamics System Specs: Win 10 x64 Pro, ASUS Maximus X Formula, i9-9900K @ 4.7 GHz, 32GB Corsair Dominator Platinum 3200 MHz, NZXT Kraken X73 AIO Cooler, Titan X Pascal GPU, EVGA Supernova 1000W P2 PSU, C: 1TB Samsung 960 Pro m.2 PCIe SSD, D: 1TB Samsung 850 Pro SATA SSD, HT Omega Claro PCIe 7.1 Sound, Denon AVR-1709 7.1 Receiver, 46" Sharp Aquos Quattron Main Screen, 27" Acer T272HL TouchScreen + Helios, TrackIR 5, ThrustMaster HOTAS Warthog, Crosswinds pedals, SimShaker
Cueball Posted March 29, 2019 Author Posted March 29, 2019 Yes it is the same for ground take off as well. I tested it after my last positing.
Wolve03 Posted March 29, 2019 Posted March 29, 2019 (edited) (Possible Bug) - Compass stuck on take off, if starting cold and dark F/A-18C, spawned cold and dark on the ground. Got the aircraft loaded, manual start, compass working during taxi. And then stuck as soon as I took off. This includes compass on the HUD, HSI, SA pages... all. HUD is also stuck in updating target boxes on the HUD. Same issue with the HMD. Uses the HUD heading as reference. Tried again, 3 times with auto-start, and same results. Fully reproducible on my end, testing with a cold ground start. Both in MP and SP. Started hot on the taxi way, works perfectly fine. Compass working through taxi to take off and beyond. couldn't test in combat due to time constraints Does someone else also see this issue? EDIT: v2.5.4.29079 Edited March 29, 2019 by Wolve03
fencible Posted April 2, 2019 Posted April 2, 2019 F/A-18C, spawned cold and dark on the ground. Got the aircraft loaded, manual start, compass working during taxi. And then stuck as soon as I took off. This includes compass on the HUD, HSI, SA pages... all. HUD is also stuck in updating target boxes on the HUD. Same issue with the HMD. Uses the HUD heading as reference. Tried again, 3 times with auto-start, and same results. Fully reproducible on my end, testing with a cold ground start. Both in MP and SP. Started hot on the taxi way, works perfectly fine. Compass working through taxi to take off and beyond. couldn't test in combat due to time constraints Does someone else also see this issue? EDIT: v2.5.4.29079 Yes, this is happening to me after cold starts on the ground. My HUD velocity vector and compass tape freeze in the manner described by others in this thread. This happens every time now for me from cold starts (have not tried other types of start).
MarkLazzo Posted April 3, 2019 Posted April 3, 2019 Same here. Cold start, manual, taxi and take off with heading tape stucked in initial heading, HSI and SA page freezed as well. After awhile in the air it got back on track, right heading and support pages working fine. I'll try to provide a trk file as soon as I'm able. I also noticed that the INS countdown go a bit crazy, it accelerate during alignment and ends up finishing in about 15 secs or something. Inviato dal mio Lenovo P2a42 utilizzando Tapatalk
Brute4ce Posted July 11, 2019 Posted July 11, 2019 Heading Tape, HSI & SA compass freeze with INS setting IFA I also noticed the Heading Tape, HSI & SA freeze when INS knob is set to IFA (which is what the training videos tell you to do :music_whistling:). It was working before. Reporting version is Open Beta 2.5.5.33184.20190711 FA18C CAUC Carrier Cold and Dark - HSI, HUD compass not working.trk
Tholozor Posted July 12, 2019 Posted July 12, 2019 IFA is currently not hooked up while the INS simulation is being improved, leave it in NAV for now. REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
Brute4ce Posted July 22, 2019 Posted July 22, 2019 IFA is currently not hooked up while the INS simulation is being improved, leave it in NAV for now. Thanks Tholozor! Will do.
Recommended Posts