Tango3B Posted December 21, 2020 Posted December 21, 2020 On 11/10/2020 at 8:57 AM, BIGNEWY said: Hi all, this has been reproduced and reported now. thanks Guys, I really hate having to revive this thread, AGAIN. This incerdibly annoying bug is sadly still present in the current DCS 2.5.6.59398 Open Beta. Meanwhile, we had three OB patches since it was confirmed by BN that their team of testers has been able to reproduce that bug. This is a major issue and a real p.i.t.a. in Pvp fights, guys. The radar scan centering is completely borked and needs fixing. Apparently nothing has been done so far. Can we please have an update on this by BN or 9L? Can we hope for the next OB patch? 1
ED Team BIGNEWY Posted December 21, 2020 ED Team Posted December 21, 2020 Hi, sorry I have no eta for a fix at the moment, and we have the January break until the 10th coming up so its unlikely to be addressed until next year. thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Tango3B Posted December 21, 2020 Posted December 21, 2020 1 hour ago, BIGNEWY said: Hi, sorry I have no eta for a fix at the moment, and we have the January break until the 10th coming up so its unlikely to be addressed until next year. thanks Thanks man. I'm already glad that you still have that bug on your radar and have not already forgotten about it. Let´s hope for next year then. And above all, enjoy your well-deserved vacation. 1
DoctorVixen Posted January 12, 2021 Posted January 12, 2021 (edited) The bug is quite annoying, especially when the autoscaling happens right after you fired a missile before it went pitbull. I've learned to avoid the rws mode, which is really a shame because it has it uses... fortunately i can stt from tws. The bug is ok to deal with if you know it's a bug and the autoscale makes the lock break, but the annoying thing is facing this bug and having to search forums what's wrong. After reading and looking at the dates nobody is getting the idea this is gonna be fixed any time soon, but there is only so much work you can do at once. I am sure it will be addressed. Also legacy code can make things hard sometimes to change things around. The only thing that is find sometimes hard to understand is why there is worked on so much different items at once. I'd say finish one module from early access to full release and iron out the bugs before beginning on the next module. It would save a lot of resource management, and will probably increase focus and development flow. Fortunately it seems ED has said to focus on the f18 and focus on a next module thereafter. However with the highly anticipated ah64... I won't be complaining if the range bug still exist and the apache is available :)\ Edited January 18, 2021 by DoctorVixen 2
Tango3B Posted January 25, 2021 Posted January 25, 2021 (edited) @DoctorVixen: Well, BN said they could reproduce the bug and will work on a fix. They obviously had other priorities in the past few patches, though and apparently it took their team some time to understand what caused this problem. Again, I have absolutely no doubt this will be addressed in one of the next patches. I wouldn't hold my breath for Wednesday, though. And yes, the process of actually fixing this major bug is indeed painfully slow considering how much of a problem this actually is when flying in a competitive environment. For the the time being please use the following workaround if you are not already doing so. Briefly lock the target in RWS (quicker target detection / less problems with target aspect) before RWS auto-scales and then immediately switch to TWS while keeping your target locked and see if TWS can hold the lock. If yes then continue the engagement in TWS if not then repeat until TWS is able to hold the lock. This DOES work and you won't constantly loose lock. You also don't need to STT your target. Again, this is a bit inconvenient but you'll get the desired result. Edited January 25, 2021 by Tango3B
DoctorVixen Posted January 27, 2021 Posted January 27, 2021 On 1/25/2021 at 2:22 PM, Tango3B said: @DoctorVixen: Well, BN said they could reproduce the bug and will work on a fix. They obviously had other priorities in the past few patches, though and apparently it took their team some time to understand what caused this problem. Again, I have absolutely no doubt this will be addressed in one of the next patches. I wouldn't hold my breath for Wednesday, though. And yes, the process of actually fixing this major bug is indeed painfully slow considering how much of a problem this actually is when flying in a competitive environment. For the the time being please use the following workaround if you are not already doing so. Briefly lock the target in RWS (quicker target detection / less problems with target aspect) before RWS auto-scales and then immediately switch to TWS while keeping your target locked and see if TWS can hold the lock. If yes then continue the engagement in TWS if not then repeat until TWS is able to hold the lock. This DOES work and you won't constantly loose lock. You also don't need to STT your target. Again, this is a bit inconvenient but you'll get the desired result. thx, i wasn't doing it exactly as u pointed out, not needing stt is a big plus so ill practise the workaround as you just told me.
Tango3B Posted January 28, 2021 Posted January 28, 2021 4 hours ago, DoctorVixen said: thx, i wasn't doing it exactly as u pointed out, not needing stt is a big plus so ill practise the workaround as you just told me. Yeah, you're still good to go with that workaround. Just tested it with the recent patch and the workaround is still applicable. Let me know if I should post a short YT vid to showcase these steps in case you've got any questions. Sadly, as I suspected, though the recent patch did not include the long awaited fix for this bug so we have to deal with this a little longer. I hope BN keeps us updated on the progress made by the team. Fingers crossed for the next patch, I guess. 1
DoctorVixen Posted January 29, 2021 Posted January 29, 2021 (edited) On 1/28/2021 at 3:29 AM, Tango3B said: Yeah, you're still good to go with that workaround. Just tested it with the recent patch and the workaround is still applicable. Let me know if I should post a short YT vid to showcase these steps in case you've got any questions. Sadly, as I suspected, though the recent patch did not include the long awaited fix for this bug so we have to deal with this a little longer. I hope BN keeps us updated on the progress made by the team. Fingers crossed for the next patch, I guess. I've done some testing, but it seems the lock often becomes stable a lot at about the 42 mile mark, resulting in instant lock loss because its switching to the 40 mile range , in which i can't seem to lock until it is well within the 40 mile range again. Have not noticed the lock being any better after switching from rws to tws either. i am back to the old workaround, just using tws only seems to work best. yes i am losing locks, but in RWS i am losing even more locks. I would be interested in a video though. Note i fly a lot on growling sidewinder, everyone always hiding in the mountains so keeping lock is hard anyway. And so is actually hitting, because of this. We have been waiting long and we need to wait longer. We can be nice and say we need to wait a little longer but I think we need to face the facts. The fact is that this bug is years old and reported numerous times, and that we hate this bug and want to see it fixed. The other fact is that ED knows about this bug but doesn't find it important enough to actually fix it. I mean c'mon it shouldn't take years to fix a bug, they have done 0 work on it, while saying they are working on it. Putting this bug at the bottom of some list is not my vision of working on a bug. About the priorities: This bug was here before the anouncement of for example the apache module being worked on. That their priority is making money and getting new customers and modules out and therefore don't see time to fix bugs existing customers are facing is no excuse, at least not for me. I get it, fixing bugs doesn't make the bank account bigger, it should however have priority. Good foundations can be built on better and faster. bugs in existing code find their ways into new code, that's just how it works. It's then even harder to fix then it was in the first place. Technical debt is called so for a reason, it IS a debt and it will bite you in the ass and demand payback sooner or later, we all hope later. Releasing a new early access (full fidelity ahem) module is what brings new money, and we all would buy it the day it's released, (and then wonder why the f*** this is sold as full fidelity, because we all know there is no such thing as early access full fidelity, it's just early access, and it might be full fidelity someday, but it might be early access for 10 years too, that's 10 years flying in a full fidelity priced low fidelity model) Actually the FC3 modules are also full fidelity, they only have to say they will implement the clickable cockpit someday and tadaa early acces full fidelity man. quadruple the pricing! That said i have no doubt that if ED says they are making a full fidelity model it will be so, and in the end you get quality. i bought the ka50 ages ago, i still play it, heck i started with flaming cliffs 1, 2 then 3 it's still here. There are no other games that are like that, so considering that, modules are really good value. the price is 100% worth it. so good thing and bad things. mostly good! Personally I think ED should be aiming in a different direction. We have Jets, Helo's and Vehicles now. The multiplayer aspect should be the focus together with the existing modules, and the work on the new engine and the clouds. It should do some videos promoting multiplayer, and some advertising. It should not matter if use steam or not. The multiplayer and flying together is the thing that has the greatest potential to let the playerbase BOOM ( and with booming playerbases come booming sales too). Compared to few years ago DCS is becoming something more and more people have heard of, flight sims in general are very popular at the moment (2020/2021). There are great opportunities now Edited January 29, 2021 by DoctorVixen 1
Tango3B Posted January 29, 2021 Posted January 29, 2021 @DoctorVixen Yeah, I will make a short vid this evening. Actually, I do fly on GS's Caucasus server, too. I'm that Viper81 guy, by the way. Infact, I did fly there yesterday evening and it worked quite well to say the least. I am just curious does "your" TWS also drop the lock when auto-scaling? "Mine" does not and keeps a stable lock unless the bandit isn't notching or in certain other unfavorable aspects for TWS which would then be normal, expected behavior. Just asking because I heard that a few guys on GS's server see the same behavior in TWS as in RWS-SAM when auto-scaling occurs which is strange. So, basically what I am asking you here is might that problem with your TWS lock have been aspect related like the target is maneuvering hard, is notching, you having bad closure rate and so on? Or did the target even break the LOS because you mentioned those guys low in the mountains? As I mentioned before be aware that TWS in the Viper has it's problems in that scenario. And that is correct behavior. TWS is by no means that glorious silver bullet that many guys want that mode to be. So, if you loosing lock in TWS is aspect related then you would need to go back RWS-SAM, lock the target in RWS and switch back to TWS. Basically, you would need to repeat that procedure every time.
Recommended Posts