lwalter Posted June 19, 2020 Posted June 19, 2020 I'm using the latest open beta. Until the last 2 or 3 open beta updates, the trees in Caucasus were all really nicely rendered. Lately, I have noticed that there are now these ugly and simplistic 2D-like trees appearing. It seems to be only 1 sort of trees as all the other ones still look nice. Is it something others have noticed lately? Note that I haven't changed settings or hardware. I attached a screenshot. Granted the screenshot doesn't look as nice as in-game (I don't know why) but you can definitely see the "2D" trees. iMac Retina 5K, 27-inch, i7 4 GHz, 32 GB RAM, AMD R9 M395X 4 GB | Thrustmaster HOTAS Warthog | Cougar MFD | MFG Crosswind | EDTracker Pro | Realteus ForceFeel DCS World | Bf109 | Fw190 A8/D9 | P47 | P51 | Spitfire | I16 | C101 | L39 | F86F | MiG15 | MiG19 | MiG21 | FC3 | A10C | AJS37 | AV8BNA | F5 | F14 | F16 | F/A18 | M2000 | JF17 | Christen Eagle | Yak52 | SA342 | UH1H | Mi8 | Ka50 | Combined Arms | NS430 | Persian Gulf | Normandy | Channel | Syria | NTTR | WWII Assets
Motomouse Posted June 19, 2020 Posted June 19, 2020 (edited) There is a shading error, propably a plane of this tree model has a wrong normal setting. Edited June 20, 2020 by Motomouse VIC-20@1.108 MHz, onboard GPU, 5KB RAM, μυωπία goggles, Competition Pro HOTAS
JasonJ Posted June 20, 2020 Posted June 20, 2020 (edited) Before the last Stable release the betas were having big FPS issues over April/May/June. Then the last beta came and went stable (2.5.6) It was at this exact time I also noticed the tree models at the medium distance range (viewed at low altitude) became simpler LOD (level of detail) and look more ugly. Also the near/close range Trees viewed at about 2000ft altitude also have distracting constant pop-in/pop-out. Very disappoint. I make sure all new releases/betas I delete all fxo/metashaders2 files in user files and let them rebuild. ....AND also I delete core shaders - "C:\Program Files\Eagle Dynamics\DCS World\Mods\terrains\Caucasus\misc\metacache\dcs" \nevada \PG etc and dcs_repair these. I deduced to myself the Tree LOD was reduced/changed to help ramp up the frames for a stable release 2.5.6 that was initially struggling with framerate. I mean, the FPS impoved the same time the trees changed their LOD. I know other things were also problematic, TGP, HSI, FLIR screen etc all were eating FPS & were improved. But noticed the last FPS improvement the same time stable 2.5.6 was released and the trees looked worse. Sorry if not true but, I observed this, it was quite obvious. BTW: I have trees visibility at 100% and Visible Range at HIGH. I do hope Motomouse is correct and it can be fixed with no impact on Framerate. But I am have come to terms with that it (maybe?) was necessary to make 2.5.6 at least playable with better FPS, especially in VR. I shed a tear at the lesser looking trees and then the tears blur my vision so the bad trees are harder to see and I don't notice so much :cry: NB : New hotfix for VR users - lots of tears Edited June 20, 2020 by JasonJ Sim Rig || Pics 2010 | PC 2019 || 8600K @ 4.8GHz | RTX2080ti OC | 32GB RAM @3000 | 500GB SSD | Win10 64bit | PC 2010 || 2600K @ 3.4GHz | Zotac GTX680 | 8GB RAM | Win7 64bit Ultimate SP1 | Cockpit || Joystick: T.16000M | Pedals: Logitech G25 | Throttle & Collective: Logitech Attack3 Modded | Button Box: G25 Shifter | Cockpit || HP Reverb VR | Custom Frame & Seat | 3x Bass Shaker | 2:1 Game Sound | 2x Rear Head Rest Speakers Comms/Music |
unknown Posted June 20, 2020 Posted June 20, 2020 This is a reported LOD bug with the trees since at least january 2020, not just since the latest patch(s). https://forums.eagle.ru/showthread.php?t=260918 Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings
JasonJ Posted June 20, 2020 Posted June 20, 2020 My point being, it (trees) was okay-ish in OB before it went to stable this month. Then a big difference appeared when we went stable - as pointed out by our OP lwalter But thanks for pointing out it has been reported. Sim Rig || Pics 2010 | PC 2019 || 8600K @ 4.8GHz | RTX2080ti OC | 32GB RAM @3000 | 500GB SSD | Win10 64bit | PC 2010 || 2600K @ 3.4GHz | Zotac GTX680 | 8GB RAM | Win7 64bit Ultimate SP1 | Cockpit || Joystick: T.16000M | Pedals: Logitech G25 | Throttle & Collective: Logitech Attack3 Modded | Button Box: G25 Shifter | Cockpit || HP Reverb VR | Custom Frame & Seat | 3x Bass Shaker | 2:1 Game Sound | 2x Rear Head Rest Speakers Comms/Music |
unknown Posted June 20, 2020 Posted June 20, 2020 My point being, it (trees) was okay-ish in OB before it went to stable this month. Then a big difference appeared when we went stable - as pointed out by our OP lwalter But thanks for pointing out it has been reported. If you are using the stable version then you would only notice this bug/problem after the latest stable update because the last stable update before that was sometime last year? (i don't use stable). But it's in OB version since january of this year, but it seems to only affect one type of tree....so if you not know it its likely you miss seeing it if you don't spend much of your time down at tree top level. Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings
prccowboy Posted June 20, 2020 Posted June 20, 2020 I actually have had this since speedtrees were released 2 years ago, see: https://forums.eagle.ru/showthread.php?t=201459
lwalter Posted June 20, 2020 Author Posted June 20, 2020 I can't argue whether these "2D trees" already existed before 2.5.6 or not. Maybe I never noticed them before, but for sure I noticed them since early of June without changing any graphic settings. If I'd like to see "3D tress" instead, which setting or settings should I update? Here are my main current settings: - Textures: high for both - Visib range: low - Shadows: flat only - clutter/grass: 1000 - tree visib: 80% iMac Retina 5K, 27-inch, i7 4 GHz, 32 GB RAM, AMD R9 M395X 4 GB | Thrustmaster HOTAS Warthog | Cougar MFD | MFG Crosswind | EDTracker Pro | Realteus ForceFeel DCS World | Bf109 | Fw190 A8/D9 | P47 | P51 | Spitfire | I16 | C101 | L39 | F86F | MiG15 | MiG19 | MiG21 | FC3 | A10C | AJS37 | AV8BNA | F5 | F14 | F16 | F/A18 | M2000 | JF17 | Christen Eagle | Yak52 | SA342 | UH1H | Mi8 | Ka50 | Combined Arms | NS430 | Persian Gulf | Normandy | Channel | Syria | NTTR | WWII Assets
Northstar98 Posted June 20, 2020 Posted June 20, 2020 (edited) I definitely noticed that trees in new 2.5.6 stable, compared to the old 2.5.5 stable looked worse, to me they seem washed out + the level of detail. EDIT: Messing around with my terrain object shadows (switched from flat to default) made a massive improvement in close (now the trees cast shadows on themselves), just hoping it isn't too nasty on my system. Edited June 20, 2020 by Northstar98 Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk. Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas. System: GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV. Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.
JasonJ Posted June 20, 2020 Posted June 20, 2020 (edited) I can't argue whether these "2D trees" already existed before 2.5.6 or not. Maybe I never noticed them before, but for sure I noticed them since early of June without changing any graphic settings. If I'd like to see "3D tress" instead, which setting or settings should I update? Here are my main current settings: - Textures: high for both - Visib range: low - Shadows: flat only - clutter/grass: 1000 - tree visib: 80% I had found both these settings change the look of the trees: -Visible Range -Trees Visibility My settings -Visible Range HIGH -Trees Visibility 100% And never saw low-def trees in 2.5.5 (at least they were just out of my perceivable range) You could try that to reduce the problem somewhat. The Trees Visibility % is easy to experiment with because you can change the slider while in game and see the results while changing the slider. Do this one first and make a mental note what changes in the trees. Visibly range changes requires restart. Now with the problem seemingly worse in 2.5.6, you might even need to increase Visibility Range to HIGH or even Ultra or Extreme if your Rig can handle it. Possibly this setting may not even fix it since many users saying it's been around for a long time. At least try out HIGH. I think the difference between Ultra/Extreme isn't much noticeable, but you need to test to see. You can always put it back if no better or your frame rate is struggling. I think like myself, you were on a setting which low-def trees weren't so noticeable to you. Now on 2.5.6 something is different and exaggerates the LOD more at your current settings somewhat. So you gotta maybe tweak your trees up to 100% to get back were you were. Edited June 20, 2020 by JasonJ Sim Rig || Pics 2010 | PC 2019 || 8600K @ 4.8GHz | RTX2080ti OC | 32GB RAM @3000 | 500GB SSD | Win10 64bit | PC 2010 || 2600K @ 3.4GHz | Zotac GTX680 | 8GB RAM | Win7 64bit Ultimate SP1 | Cockpit || Joystick: T.16000M | Pedals: Logitech G25 | Throttle & Collective: Logitech Attack3 Modded | Button Box: G25 Shifter | Cockpit || HP Reverb VR | Custom Frame & Seat | 3x Bass Shaker | 2:1 Game Sound | 2x Rear Head Rest Speakers Comms/Music |
JasonJ Posted June 20, 2020 Posted June 20, 2020 I definitely noticed that trees in new 2.5.6 stable, compared to the old 2.5.5 stable looked worse, to me they seem washed out + the level of detail. Washed out: The new lighting effects in 2.5.6 are quite different. Try knocking down your gamma in DCS a few points, you can adjust while playing in game. (I had to go down a touch) But the new lighting effects makes the trees look a bit more realistic at dawn/dusk. And agree, a little more washed out in the bright daylight. Sim Rig || Pics 2010 | PC 2019 || 8600K @ 4.8GHz | RTX2080ti OC | 32GB RAM @3000 | 500GB SSD | Win10 64bit | PC 2010 || 2600K @ 3.4GHz | Zotac GTX680 | 8GB RAM | Win7 64bit Ultimate SP1 | Cockpit || Joystick: T.16000M | Pedals: Logitech G25 | Throttle & Collective: Logitech Attack3 Modded | Button Box: G25 Shifter | Cockpit || HP Reverb VR | Custom Frame & Seat | 3x Bass Shaker | 2:1 Game Sound | 2x Rear Head Rest Speakers Comms/Music |
ED Team BIGNEWY Posted June 20, 2020 ED Team Posted June 20, 2020 Hi all the tree issue is reported. thank you 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
lwalter Posted June 20, 2020 Author Posted June 20, 2020 (edited) Thanks JasonJ! I tried comparing visibility range low and visibility range extreme, when trees visibility is at lowest (30%) Whether in low or extreme, I get these "2D trees". The only difference in extreme is that when I get closer to them, they transform into "3D trees". It doesn't do that in visibility low or really when you almost touching the tree. ----However, when I put tree visibility to 100%, in visibility range extreme, I seem to have no more "2D trees". With visibility range low, even with 100% tree visibility, still "2D trees". ----I may now have to find a sweet spot for both these settings. EDIT: Actually, even with visibility range extreme and 100% tree visibility, I can see the "2D trees". It's just that they're further away and they change to 3D trees from further away than when in visibility range low, but they're still too easy to spot :( Edited June 20, 2020 by lwalter iMac Retina 5K, 27-inch, i7 4 GHz, 32 GB RAM, AMD R9 M395X 4 GB | Thrustmaster HOTAS Warthog | Cougar MFD | MFG Crosswind | EDTracker Pro | Realteus ForceFeel DCS World | Bf109 | Fw190 A8/D9 | P47 | P51 | Spitfire | I16 | C101 | L39 | F86F | MiG15 | MiG19 | MiG21 | FC3 | A10C | AJS37 | AV8BNA | F5 | F14 | F16 | F/A18 | M2000 | JF17 | Christen Eagle | Yak52 | SA342 | UH1H | Mi8 | Ka50 | Combined Arms | NS430 | Persian Gulf | Normandy | Channel | Syria | NTTR | WWII Assets
Recommended Posts