dora Posted September 19, 2016 Posted September 19, 2016 Thank you very much, Zeus67 for this good news. Hope to be able to fly on 2.0.x version soon again. Many thanks for your involvement.
diditopgun Posted September 20, 2016 Posted September 20, 2016 :cheer3nc::cheer3nc::cheer3nc: It's possible to tell us what was the problem if it's not confidential ? I am just curious. :D [sIGPIC][/sIGPIC] Intel I7 8700K / RTX 3080 / 32Go DDR4 PC21300 G.Skill Ripjaws V / MSI Z370 Gaming Pro Carbon / Cooler Master Silent Pro Gold - 1000W / Noctua NH-D14 / Acer XB270HUDbmiprz 27" G-synch 144Hz / SSD Samsung 860EVO 250Go + 1To / Cooler Master HAF X / Warthog+VPC WarBRD / Thrustmaster TPR / Track-IR v5 + Track Clip Pro / Windows 11 64bits.
Zeus67 Posted September 20, 2016 Posted September 20, 2016 :cheer3nc::cheer3nc::cheer3nc: It's possible to tell us what was the problem if it's not confidential ? I am just curious. :D ED added ground ranging per our request to enabled TAS. The mode was active all the time, but while it never had a problem in 1.5.4 it seems that it does create a problem when using the new terrain features of 2.0.x. The solution was to create a special ground_ranging mode so that it is only active when you are using TAS. "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
diditopgun Posted September 20, 2016 Posted September 20, 2016 Ok thanks, that's interesting. :thumbup: [sIGPIC][/sIGPIC] Intel I7 8700K / RTX 3080 / 32Go DDR4 PC21300 G.Skill Ripjaws V / MSI Z370 Gaming Pro Carbon / Cooler Master Silent Pro Gold - 1000W / Noctua NH-D14 / Acer XB270HUDbmiprz 27" G-synch 144Hz / SSD Samsung 860EVO 250Go + 1To / Cooler Master HAF X / Warthog+VPC WarBRD / Thrustmaster TPR / Track-IR v5 + Track Clip Pro / Windows 11 64bits.
dora Posted September 20, 2016 Posted September 20, 2016 Thank you Zeus67 for your infos. As I understand it, the creation of a special "ground_ranging" mode will be in use each time we are going to use TAS, OK ? It sounds to me that instead of being active all the time, it will now be active only when we use TAS. I am afraid Stutters will then reapear again. Could you please clarify this point please.
Zeus67 Posted September 20, 2016 Posted September 20, 2016 Thank you Zeus67 for your infos. As I understand it, the creation of a special "ground_ranging" mode will be in use each time we are going to use TAS, OK ? It sounds to me that instead of being active all the time, it will now be active only when we use TAS. I am afraid Stutters will then reapear again. Could you please clarify this point please. We will test and see what happens. They shouldn't appear because the radar should not be looking for any target at all, just looking at the ground and returning the range. "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
dora Posted September 20, 2016 Posted September 20, 2016 Thank you for your fast answer. We will wait for the tests, I hope everything will be OK. Best regards to you all for your involvement in making this mirage 2000 a real pleasure to fly.
iVVChewy9141VVi Posted September 21, 2016 Posted September 21, 2016 ED added ground ranging per our request to enabled TAS. The mode was active all the time, but while it never had a problem in 1.5.4 it seems that it does create a problem when using the new terrain features of 2.0.x. The solution was to create a special ground_ranging mode so that it is only active when you are using TAS. Thanks so much for the Update! Glad to hear you guys fixed it. Can't wait to start flying the mirage again. THANKS!! :joystick::pilotfly:
fjacobsen Posted September 21, 2016 Posted September 21, 2016 :thumbup: Super duper that it seems the culprit has been found and a possible fix is in the pipeline. I wonder if this Ground ranging mode also is what affects the F-5E. FinnJ | i7-10700K 3.8-5.1Ghz | 64GB RAM | RTX 4070 12GB | 1x1TB M.2. NVMe SSD | 1x2TB M.2. NVMe SSD | 2x2TB SATA SSD | 1x2TB HDD 7200 RPM | Win10 Home 64bit | Meta Quest 3 |
Zeus67 Posted September 21, 2016 Posted September 21, 2016 :thumbup: Super duper that it seems the culprit has been found and a possible fix is in the pipeline. I wonder if this Ground ranging mode also is what affects the F-5E. FinnJ Probably since it uses the same basic radar functionality. "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
iVVChewy9141VVi Posted October 4, 2016 Posted October 4, 2016 Zeus67, Any Updates on the fix yet or still working on it. Really love the aircraft and can't wait to get more into using the radar once the problem is solved. But just wondering about the radar problem and how the progress is going. Thanks Chewy
Harke Posted October 7, 2016 Posted October 7, 2016 (edited) here some news for Zeus67 about this bug, radar in search mode is fixed but... the bug is alway here on TAS mode as you can see in this video Edited October 7, 2016 by Harke
Recommended Posts