LawnDart Posted April 27, 2005 Posted April 27, 2005 Discovered the other day that the only time the waypoints are accurate is if you fly directly along the course line between the waypoints. If you are offset from your course, parallel your course or fly perpendicular to the current navpoint immediately after crossing it the readout will not change and/or only change in reference to how far you've moved parallel to the course line. The only thing working 100% is the heading cue as to where to turn to go direct to a waypoint, but unless you fly towards it exactly on your course line from point A to B, it won't give you the correct ETA and distance. Try setting up a mission with waypoints 1 and 2 five miles apart and on a 360 degree course. Then select waypoint 2 and fly a heading of 090 (perpendicular) directly away from waypoint 2 after crossing i. It will still show your distance at 0.0 or close to it until you start moving along a north/southerly heading and then it will readout your north/south displacement from that waypoint, but you could be several hindered miles off to the east or west. I'd call this a major bug, unless this was intentional (in which case I wouldn't understand why)? Can't remember if 1.02 did the same thing, but this is definitely something I'd consider a bug in 1.1! 1 [sigpic]http://www.virtualthunderbirds.com/Signatures/sig_LD.jpg[/sigpic] Virtual Thunderbirds, LLC | Sponsored by Thrustmaster Corsair 750D Case | Corsair RM850i PSU | ASUS ROG MAXIMUS X CODE | 32GB Corsair DDR4 3200 | Intel i7-8086K | Corsair Hydro H100i v2 Cooler | EVGA GTX 1080 Ti FTW | Oculus Rift | X-Fi Titanium Fatal1ty | Samsung SSD 970 EVO 1TB NVMe | Samsung SSD 850 EVO 1TB | WD Caviar Black 2 x 1TB | TM HOTAS Warthog | TM Pendular Rudder | TM MFD Cougar Pack | 40" LG 1080p LED | Win10 |
LawnDart Posted April 29, 2005 Author Posted April 29, 2005 After some more testing, I have to conclude that the waypoints are inop in 1.1. They only display correct heading info. Time and distance are only accurate under certain circumstances. I originally thought it was only if you were on the line between point A to point B, since they obviously only display offset distance regardless of how far away you might be paralleling or sidetracking the course. Not only that, but I now also discovered that this only works if the course is a 360/180 course as our homebase airfield of Razdolnoye has. With the new missions and different runway headings I couldn't get a single waypoint(s) to display accurate distance and time UNLESS I flew towards it on a direct 360/180 course (different from the plotted course I had made in the editor). It's all messed up seems like (I yet smell another bug)! Could someone with 1.02 check and verify that this was not the case in the old version? I'm pretty sure the waypoints were working, but I currently have no way of checking... Make sure each waypoint has accurate distance and time regardless of the direction you approach it, that's all I'm really looking for! LawnDart [sigpic]http://www.virtualthunderbirds.com/Signatures/sig_LD.jpg[/sigpic] Virtual Thunderbirds, LLC | Sponsored by Thrustmaster Corsair 750D Case | Corsair RM850i PSU | ASUS ROG MAXIMUS X CODE | 32GB Corsair DDR4 3200 | Intel i7-8086K | Corsair Hydro H100i v2 Cooler | EVGA GTX 1080 Ti FTW | Oculus Rift | X-Fi Titanium Fatal1ty | Samsung SSD 970 EVO 1TB NVMe | Samsung SSD 850 EVO 1TB | WD Caviar Black 2 x 1TB | TM HOTAS Warthog | TM Pendular Rudder | TM MFD Cougar Pack | 40" LG 1080p LED | Win10 |
S77th-GOYA Posted April 29, 2005 Posted April 29, 2005 If you're flying the 15, the nav bug is well known. If you're building a mission, and distance is screwed up to a nav point, try moving that nav point a little in a random direction. Sometimes that will work. Also, the bug that has you go 350 degrees to the right to make a 10 degree left turn is still there for certain navs.
Recommended Posts