FusRoPotato Posted December 28, 2022 Posted December 28, 2022 (edited) Ok, standard FOV may vary person to person, but at just a mile away, this helicopter vanishes at some FOV around 70. I don't know how to exactly measure that. At 1080p, the helicopter doesn't completely vanish, but will change from being a 20 pixel object to a 1 pixel object. At higher resolutions, it appears to go from a 30 pixel object to a zero pixel object. No form of labels, dots, or anti-aliasing being used. If it matters, I'm on a GTX1080 with a 5800X3D and 32 gigs of ram. Zooming in will make it appear again so I can make it poof in an out of existence. It's a busy week for me, but I was planning on making a test mission tonight that has all player controllable aircraft lined up in distant rows to see if this affects anything else, but I suspect only the AH-64 for now. Other helicopters/planes seem to appear fine this patch, but I know that wasn't the case in earlier versions of 2.8. I have cleared fxo and metas for testing. Edited December 28, 2022 by FusRoPotato
Scaley Posted January 6, 2023 Posted January 6, 2023 On 12/28/2022 at 9:07 PM, FusRoPotato said: Ok, standard FOV may vary person to person, but at just a mile away, this helicopter vanishes at some FOV around 70. I don't know how to exactly measure that. At 1080p, the helicopter doesn't completely vanish, but will change from being a 20 pixel object to a 1 pixel object. At higher resolutions, it appears to go from a 30 pixel object to a zero pixel object. No form of labels, dots, or anti-aliasing being used. If it matters, I'm on a GTX1080 with a 5800X3D and 32 gigs of ram. Zooming in will make it appear again so I can make it poof in an out of existence. It's a busy week for me, but I was planning on making a test mission tonight that has all player controllable aircraft lined up in distant rows to see if this affects anything else, but I suspect only the AH-64 for now. Other helicopters/planes seem to appear fine this patch, but I know that wasn't the case in earlier versions of 2.8. I have cleared fxo and metas for testing. This is a known (although maybe not acknowledged, don't know) bug. The only way I've found to fix it is to edit graphics.lua and change the line lodMult = 1.0; to lodMult = 1.7; or similar increased number. There is one version of this line for each visibility setting, so you have to change the right one for the visibility setting you use (or change all of them). What it seems is happening is that the new Apache LOD maps render at odd distances, so at some distance & zoom combinations on level has stopped rendering, but the next one has not. You can get distances where you can see the aircraft zoomed in, then as you zoom out it disappears, but then you continue to zoom out and it reappears. I thought this would be fixable with the LOD distances in the Apache module itself but I've not been able to make that work. 476th vFighter Group Main Page -- YouTube -- Discord Scaley AV YouTube - More videos from the 476th
FusRoPotato Posted November 21, 2023 Author Posted November 21, 2023 This bug is still present btw, and now it is very easily reproducible because you can just move the LOD slider down to 0.2 and watch all nearby Apache's turn into floating rocket pods.
Flappie Posted November 23, 2023 Posted November 23, 2023 I cannot reproduce your issue. Please attach a short DCS track along with your option.lua file (from Saved Games/DCS.../Config). AH64.trk On holiday
FusRoPotato Posted November 27, 2023 Author Posted November 27, 2023 On 11/23/2023 at 3:43 PM, Flappie said: I cannot reproduce your issue. Please attach a short DCS track along with your option.lua file (from Saved Games/DCS.../Config). AH64.trk 49.3 kB · 2 downloads It's a little different now because it's more than just a mile, which is an improvement, but still within 3 and is more of a problem with reduced LOD settings. With the LOD set low enough, it can be made far more obvious. Either way, Try setting your LOD factor starting with 0.1. I've found it to show a void space for LOD values lower than 0.3, meaning there is a range where there is neither dot nor model. At 0.5, the model will disappear while there is dot beginning to become visible, but it is a sudden an obvious reduction of 90% of the visible pixels. heliViewTest.9.miz Then run this mission file. It is a frozen F-15C looking at a long line of Apache's that get further and further away. options.lua Here is the options.lua, but there shouldn't be anything relevant in here. The cause and fix for the problem is explained here:
Recommended Posts