Norsegunar Posted July 4, 2016 Posted July 4, 2016 (edited) Hi All, Been practicing in the current Open Beta with the changed FM and L model. Can fly it around fine but I'm still having issues with the Auto Hover. In the Stable and Alpha I had a hard time getting auto hover to work, but that was mainly because I had a hard time with the twitchiness of the Gazelle. In the Open Beta, I'm not finding its twitchy like before and able to get in a decent hover, I still have some low speed drifting to tune out. But I can't seem to get Auto hover to work. I'm attaching some tracks from both the L and M models where I get into a hover, I am watching my ground speed via the NADIR's Ground Speed mode, have my VVI near zero and no Pitch or Roll. Click the button I have bound on my X-55 for Auto Hover, see the button on the cyclic move but nothing happens. Also pressing the Q button for Auto Hover. I'm not getting the notification on the Control overlay showing that I am in AUTO. Is anyone else having this issue or is it just pilot error ? Thanks Edit: So, I tested out Auto Hover in Open Alpha and Stable, I'm able to have it turn on the first time I click the Auto Hover Button. DCS Version: 1.5.4.54316 Steam: Stand Alone Map: Caucus SP/MP: SP Reproducible: Can't get Auto Hover to Work Step to Reproduce: Setup either M or L model at an Airfield in ME. Start ME, standard startup, take off, come to a stable hover attempt to turn on Auto Hover. Screenshot/Video available: No Video or Screen Shots Track Available: Attached Mission File: N/A Controllers: X-55 HOTAS Logitech G700 mouse and G13 Gaming keypad, Dell keyboard OS: Win 7 RAM: 16 GPU: AMD R9 280 Mods: Devrim English Cockpit, Starways Black Sea Map 2.0, Kuky's Vechile Dust and Smoke, TGP Color. Same Mods were run in Stable and Alpha (except Starways in Alpha)SA34L AutoHover Test.trkSA342M AutoHover Test.trk Edited July 6, 2016 by Norsegunar Adding more Info Specs: It's a computer...it runs DCS.... Audentes Fortuna Juvat [sIGPIC][/sIGPIC]
nomdeplume Posted July 5, 2016 Posted July 5, 2016 (edited) Took control after your first few attempts and couldn't get it to work either. Also noticed the magnetic brake trim was not working. I had that happen in the 2nd campaign mission with the -M (prior to the latest open beta updates). Not sure what causes it but in that one I had difficulty clicking in the right places when spinning up the gyros. Restarted your track, took control right at the start, went through my usual startup procedure and it all worked normally - so it's not the mission and is most likely something to do with the specifics of the startup. I've saved my track and attached it if you want to play "spot the meaningful difference", but I'll do a few more tests and see what I can figure out. Edit: after much testing I still can't work out how to reproduce this. :( Replayed the track, took control after startup, verified auto-hover wasn't working, landed, shut down, after a cold start the auto-hover was fine (magnetic brake trim still didn't seem to work though).SA34L AutoHover Test 2.trk Edited July 5, 2016 by nomdeplume 1
Len62 Posted July 5, 2016 Posted July 5, 2016 I started your track and immediately took control and did an autostart and had no problems getting into auto hover. Like nomedeplume said maybe something was missed in the start-up? I haven't quite got the manual start down yet, fairly new to the Gazelle.
drPhibes Posted July 5, 2016 Posted July 5, 2016 Strange indeed. I watched your 342M track until after startup, then took control, and I couldn't engage auto hover. Then I re-started, took control right away, followed my standard startup routine which consists of the same steps as you took, just in an other order (I usually put the NADIR in warm-up mode, set gyros to GM, switch on trim/pitot heating/mag brake/AP while waiting for the 20 sec. fuel pump priming). After that, auto hover works fine.
Deezle Posted July 5, 2016 Posted July 5, 2016 Check to make sure your throttle is reaching 100%, if it doesn't, autohover won't work. Intel 9600K@4.7GHz, Asus Z390, 64GB DDR4, EVGA RTX 3070, Custom Water Cooling, 970 EVO 1TB NVMe 34" UltraWide 3440x1440 Curved Monitor, 21" Touch Screen MFD monitor, TIR5 My Pit Build, Moza AB9 FFB w/WH Grip, TMWH Throttle, MFG Crosswinds W/Combat Pedals/Damper, Custom A-10C panels, Custom Helo Collective, SimShaker with Transducer
Rogue Trooper Posted July 5, 2016 Posted July 5, 2016 what was the original fault inducing start up procedure? Anything obviously different? HP G2 Reverb (Needs upgrading), Windows 10 VR settings: IPD is 64.5mm, High image quality, G2 reset to 60Hz refresh rate. set to OpenXR, but Open XR tool kit disabled. DCS: Pixel Density 1.0, Forced IPD at 55 (perceived world size), DLSS setting is quality at 1.0. VR Driver system: I9-9900KS 5Ghz CPU. XI Hero motherboard and RTX 3090 graphics card, 64 gigs Ram, No OC... Everything needs upgrading in this system!. Vaicom user and what a superb freebie it is! Virpil Mongoose T50M3 base & Mongoose CM2 Grip (not set for dead stick), Virpil TCS collective with counterbalance kit (woof woof). Virpil Apache Grip (OMG). MFG pedals with damper upgrade. Total controls Apache MPDs set to virtual Reality height. Simshaker Jet Pro vibration seat.. Uses data from DCS not sound... goodbye VRS.
nomdeplume Posted July 5, 2016 Posted July 5, 2016 what was the original fault inducing start up procedure? Anything obviously different? No idea still. There's a few things they did in a different order to my usual startup, but I've spent at least an hour trying variations of the start procedure to try to cause it to occur but had no luck. Originally I thought it might be related to enabling the trim and/or AP channels before the gyros are ready but that doesn't seem to be it.
Rogue Trooper Posted July 5, 2016 Posted July 5, 2016 I do not have 1.5 beta so I cannot test unfortunately... I need a 500Gb SSD. HP G2 Reverb (Needs upgrading), Windows 10 VR settings: IPD is 64.5mm, High image quality, G2 reset to 60Hz refresh rate. set to OpenXR, but Open XR tool kit disabled. DCS: Pixel Density 1.0, Forced IPD at 55 (perceived world size), DLSS setting is quality at 1.0. VR Driver system: I9-9900KS 5Ghz CPU. XI Hero motherboard and RTX 3090 graphics card, 64 gigs Ram, No OC... Everything needs upgrading in this system!. Vaicom user and what a superb freebie it is! Virpil Mongoose T50M3 base & Mongoose CM2 Grip (not set for dead stick), Virpil TCS collective with counterbalance kit (woof woof). Virpil Apache Grip (OMG). MFG pedals with damper upgrade. Total controls Apache MPDs set to virtual Reality height. Simshaker Jet Pro vibration seat.. Uses data from DCS not sound... goodbye VRS.
Norsegunar Posted July 6, 2016 Author Posted July 6, 2016 So, I did some more testing just a few minutes ago. And it's now has me puzzled. I removed my mods and Repaired my Open Beta, just in case it was a mod conflicted. Then tested the Auto Hover and it worked first time out. I reinstalled my Starways, Kuky's, Frenchy's and Devrim Cockpit mod. Tested again, Auto hover right after lift off. I was very deliberate in my start up. Because like nomdeplume I thought it might be turning on the AP before the Gyros were on. So I don't know what I did different this time then I do all the other times I start up the Gazelle. I then loaded up my track I had posted, took control right after start up. I turned off the AP then back on again to see if anything happened. The replay still want Auto hover. So I don't know what the issue is that caused the Auto Hover not to work in the replay. I'll have to do some more testing. I've included the track where I was able to get auto hover to work. I set up the camera so it wouldn't shift so the start up could be watched. :dunno:SA342L AutoHover Test Sucess.trk Specs: It's a computer...it runs DCS.... Audentes Fortuna Juvat [sIGPIC][/sIGPIC]
Norsegunar Posted July 6, 2016 Author Posted July 6, 2016 Did more testing with both the M and L models with different start ups from what i do as a normal start up, to flipping all the systems on after the first stage of the engine starts but before I bring it to pull throttle. Auto hover worked fine. So I don't know what happened in the track that caused it to not work. So I am just going to chalk this up to some random bug on my DCS and not a internal bug to the Gazelle. :dunno: Thanks for all the help and safe flying Specs: It's a computer...it runs DCS.... Audentes Fortuna Juvat [sIGPIC][/sIGPIC]
KoN Posted July 7, 2016 Posted July 7, 2016 i don`t think 1.5.3 stable has been updated only 1.5.4. OB , has had new FM and patch . i might be wrong . Gigabyte - X570UD ~ Ryzen - 5600X @ 4.7 - RTX-4070 SUPER - XPG 32:GB @ 3200 - VKB - Gunfighter 4 - STECs - Throttle - Crosswinds Rudders - Trackir 5 . I'm a dot . Pico Nero 3 link VR . @ 4k Win 11 Pro 64Bit . No longer Supporting DCS .
Norsegunar Posted July 8, 2016 Author Posted July 8, 2016 i don`t think 1.5.3 stable has been updated only 1.5.4. OB , has had new FM and patch . i might be wrong . I was having this issue in the Open Beta (1.5.4) but also tested it out in the Stable (1.5.3) and Open Alpha (2.0) to see if it was bug in Open Beta or an issue on my side with my controllers or keybindings ect. I never find a real answer on why it happened. It might have been a startup issue or something else, but no one really could point to an error. I have written it off and carried on flying since it seems to work now. Specs: It's a computer...it runs DCS.... Audentes Fortuna Juvat [sIGPIC][/sIGPIC]
Recommended Posts