borba_eagle Posted July 6, 2019 Posted July 6, 2019 Any one had this issue of the AUTO function not getting a square when pressing the OBS? I tried to found something in the BUGs reports and here but didn't found. If any one had this issue or it's working, please let me know that I'll try send a bug report. Thanks!
Harker Posted July 6, 2019 Posted July 6, 2019 I've had it happen to me on the ground, sometimes 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
Lordzarj Posted July 6, 2019 Posted July 6, 2019 It only happens to me if I try it before I have taxied 100 yards or so. Seems to need a certain distance from the init location. Whether this is intended or not I don't know.
Nooch Posted July 6, 2019 Posted July 6, 2019 The Auto function has never been working since the Hornet came out. I could press it and get a square but it would not cycle the waypoints automatically and do its job. Basically instead of switching to the next waypoint it would switch to waypoint 0 everytime... [sIGPIC][/sIGPIC]
Py Posted July 7, 2019 Posted July 7, 2019 I just tested it out, works perfectly for me. Try the super simple attached mission. All you have to do is press AUTO on the HSI page, for me it then automatically increments to WP1 and boxes SEQ1 and WPT. It increments near/just past each waypoint for me. If it doesn't work for you, maybe DCS needs a repair or a mod is breaking it? Or maybe something is different with a cold/ground start?test_WPT_AUTO.miz
Nooch Posted July 7, 2019 Posted July 7, 2019 Yup. Re-tested it today with an air start and it is working fine now for me as well. Looks like they have fixed it in a recent update. I remember the issue being still present not that long ago but that's my bad for calling it out, I should have tested again before posting. Still need to see what's up with a ground cold start though. [sIGPIC][/sIGPIC]
Harker Posted July 7, 2019 Posted July 7, 2019 For me, it has only not worked with a cold start and only for a little while, while stationary. Always works once I taxi and always while airborne. 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
Py Posted July 8, 2019 Posted July 8, 2019 I just tested with a cold start. It doesn't work until you move from the initial position, but then works almost the same as with an air start. The only difference is that it doesn't auto-increment to WP1 when you press AUTO after a cold start, while it does for an air start. Minimal track attached, showing how AUTO doesn't work until you move after a cold start. Just a minor bug, but might as well get it fixed.test_WPT_AUTO.trk
AvroLanc Posted July 8, 2019 Posted July 8, 2019 At a slight tangent to original problem: The AUTO option should enable a sequence cross track error indication in the bottom right of the HSI. This should be similar to the course deviation error when using the course knob. Course deviation shows the nm error followed by a C. For example 0.5C, 1.7C etc. This is correctly modeled. However, the Sequence deviation should show the nm error followed by an S. I.e 0.3S or -1.6S etc. There's no sequence cross track error indication currently modeled or displayed. Mentioned because a dev might be reading......
Recommended Posts