October 9, 20205 yr Do you remember that tall building bug introduced in the last patch? Of course you do. And now the same guy who found the solution to that one has figured out what is wrong with the tree LOD. As of now there is no fix for it, because this has to be done on the developer side, but if his suspicions and findings are correct, then he saved Asobo's developers some serious time finding the cause. https://forums.flightsimulator.com/t/lod-problems-trees-fix-revisited/296923
October 9, 20205 yr Thanks so much for this. See this is what get's me. Someone was complaining the trees were too high, Asobo went to resolve it and affected the rendering distance (I didn't think anything was wrong with the trees). Lesson in this is you can't please everyone. That being said Asobo should know their own code and together with QA tester should have caught this was a problem. Edited October 9, 20205 yr by Dillon FS2020 Alienware Aurora R11 10th Gen Intel Core i7 10700F - Windows 11 Home 32GB Ram NVIDIA GeForce RTX 4070 Ti Super OC 16GB - Pimax Crystal Light VR
October 9, 20205 yr Interesting, from a development point of view. I think I read that the pop in is more noticeable when you don't have wide screen (Lens Correction) enabled. That might explain why some users are distracted by this bug and other users not as much. Come to think of it, I'm suddenly annoyed by the nomenclature Lens Correction. Richard Chafey i7-8700K @4.8GHz - 32Gb @3200 - ASUS ROG Maximus X Hero - EVGA RTX3090 - 3840x2160 Res - KBSim Gunfighter - Thrustmaster Warthog dual throttles - Crosswind V3 pedals MSFS 2020, DCS
October 9, 20205 yr Commercial Member This man is a trooper, amazing to see the dedication of some of "us".
October 9, 20205 yr 7 hours ago, Farlis said: And now the same guy who found the solution to that one has figured out what is wrong with the tree LOD. As of now there is no fix for it, because this has to be done on the developer side, but if his suspicions and findings are correct, then he saved Asobo's developers some serious time finding the cause. Brilliant work by this guy, I'd urge everyone to go and upvote that post! Cheers, Søren DissingIntel i9-13900K @5.6-5.8 Ghz | ASUS ROG RYUJIN III | ASUS ROG Astral RTX 5090 OC | ASUS ROG Maximus Z790 Hero | 64Gb DDR5 @5600 | 1Tb Samsung M.2 980 PRO (Win11), 1Tb Samsung M.2 980 PRO, | ASUS ROG Helios 601 | 32” ASUS PG32UCDM 240hz 4K | Chaseplane | TM TCA Captain's Edition, Winwing FCU + EFIS L/R, Tobii 5 | Win 11 Pro 64 | MSFS 2024 | BA Virtual | PSXT, RealTraffic w/ AIG models
October 9, 20205 yr 1 hour ago, SierraDelta said: Brilliant work by this guy, I'd urge everyone to go and upvote that post! Thanks for reminding me! Asobo needs to hire this guy. Passionate members like this need to be on the team. Problem is they might clash with the those that aren't as passionate and the management team who as we all know in every place we work make decisions sometimes that make no since. FS2020 Alienware Aurora R11 10th Gen Intel Core i7 10700F - Windows 11 Home 32GB Ram NVIDIA GeForce RTX 4070 Ti Super OC 16GB - Pimax Crystal Light VR
October 9, 20205 yr Yeah, interesting and very very well done by this person, however.. this has taken a dedicated person 2 weeks to discover (assuming this is the true fix and has no knock on implications which will need to be checked as well). As Asobo said at the last update.. many of these bugs are caused by interlinking systems and tracking them is hard, as is preparing a fix that has no other side effects. Perhaps this can be an example for people calling fo a quick hotfix for a problem, when in all reality, there is no such thing as a quick hotfix for many issues in a development of this size. It also comes with a "careful what you wish for" warning, as this was a change shouted for by people when it wasn't really that needed in the grand scheme of things. It also shows that a "simple" change to fix something (ie tree height) is far from simple and breaks other stuff. This one is almost a self wished for bug that had worse far reaching consequences than the initial issue. Graham System specs... CPU AMD5950, GPU AMD6900XT, ROG crosshair VIII Hero motherboard, Corsair 64 gig LPX 3600 mem, Air cooling on GPU, Kraken x pump cooling on CPU. Samsung G7 curved 27" monitor at 2k resolution ULTRA default settings.
October 9, 20205 yr This is a nice find by CptLucky8. Please go in and upvote that thread so Asobo can read it and figure out why the LOD has changed in the last few patches. i5-12400, RTX 3060 Ti, 32 GB RAM
October 9, 20205 yr 3 hours ago, abrams_tank said: This is a nice find by CptLucky8. Please go in and upvote that thread so Asobo can read it and figure out why the LOD has changed in the last few patches. Umm, not sure. He's nailed it but this is not something that can be fixed in Soft Code. It's a Hard Code Issue. I'm sure ASOBO have read it and are certainly examining very closely - but, with the view to fix "the admitted Bug". CptLucky8 has abandoned the Thread with good reason. He's a very intelligent guy and a great IT system analyst. But, he knows when to leave it ASOBO. We should do the same. This is a fix that I have no doubt will come in the next patch.
October 14, 20205 yr I thank you all for your very kind words! It is always a pleasure to lend a useful hand to the community whenever I can, and I'll certainly continue doing so in the future. Jean-Luc aka CptLucky8 Edited October 14, 20205 yr by RXP
October 14, 20205 yr 31 minutes ago, RXP said: I thank you all for your very kind words! It is always a pleasure to lend a useful hand the community whenever I can, and I'll certainly continue doing so in the future. Jean-Luc aka CptLucky8 By bringing the GTN and GNS to this sim? Hahaha! | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
Archived
This topic is now archived and is closed to further replies.