March 14, 20215 yr I've posted this "over there": This is (yet another) example of an Issue that should NOT require a certain Number of Votes before it is taken seriously by the Devs and action is taken, it’s obviously a backwards step or a Bug that’s appeared which requires immediate attention and not left to linger like the Terrain Spikes issue. I find the whole reasoning to Vote on Bugs amazingly redundant especially when these Bugs are introduced with an Update, they should not of been introduced in the first place and should blatantly be of a high priority to fix. Pico Neo3 Link VR - Windows 11 64bit, Gigabyte Z590 Aorus Elite Mobo, i7-10700KF CPU, Gigabyte RX 9070 XT OC 16gb (AMD GPU), 32gig Corsair 3600mhz RAM, SSD x2 + M.2 SSD 1tb x1 Saitek X45 HOTAS - Saitek Pro Rudder Pedals - Logitech Flight Yoke - Homemade 3 Button & 8-directional Joystick Box, SNES Controller (used as a Button Box - Additional USB Numpad (used as a Button Box)
March 14, 20215 yr 1 minute ago, MarcG said: I've posted this "over there": This is (yet another) example of an Issue that should NOT require a certain Number of Votes before it is taken seriously by the Devs and action is taken, it’s obviously a backwards step or a Bug that’s appeared which requires immediate attention and not left to linger like the Terrain Spikes issue. I find the whole reasoning to Vote on Bugs amazingly redundant especially when these Bugs are introduced with an Update, they should not of been introduced in the first place and should blatantly be of a high priority to fix. What he said...😶 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
March 14, 20215 yr 1 minute ago, MarcG said: I've posted this "over there": This is (yet another) example of an Issue that should NOT require a certain Number of Votes before it is taken seriously by the Devs and action is taken, it’s obviously a backwards step or a Bug that’s appeared which requires immediate attention and not left to linger like the Terrain Spikes issue. I find the whole reasoning to Vote on Bugs amazingly redundant especially when these Bugs are introduced with an Update, they should not of been introduced in the first place and should blatantly be of a high priority to fix. The question of the day is though. Do they give a word not allowed? Apart from storing some pdf's for my second career my rig is 100% dedicated to this sim. I in retrospect im thinking this is probably not for me and as Dillon said this is going in the direction of flight. I also have an xbox series x and i had absolutely no intention of running the sim on it so its pc or bust. If the sim is predominantly going to cater to xbox at the detriment to pc then hopefully another company can step up to the plate and in the mean time ill try to find something else to play to justify the 5 grand i've spent on hardware alone. Could have bought a nice new Scott foil 20 or Trek Madone SLR with that!! AMD Ryzen 9800X3D/ Asus ROG Strix B650E F Gaming WiFi / Asrock Taichi 9070XT / 32GB G.Skill Trident Z5 Neo DDR5 6000 / 2x ADATA XPG 8200 Pro NVME / Arctic Liquid Freezer II 280 / Seasonic Vertex 1000w PSU / Lian Li LanCool II Mesh Performance / Asus VG34VQL3A / Topping E70 Velvet DAC & L70 Amp /Sennheiser HD660s2 Thrustmaster Boeing Yoke + TCA Sidestick + TFRP Rudders
March 14, 20215 yr 5 minutes ago, Maxis said: The question of the day is though. Do they give a word not allowed? Apart from storing some pdf's for my second career my rig is 100% dedicated to this sim. I in retrospect im thinking this is probably not for me and as Dillon said this is going in the direction of flight. I also have an xbox series x and i had absolutely no intention of running the sim on it so its pc or bust. If the sim is predominantly going to cater to xbox at the detriment to pc then hopefully another company can step up to the plate and in the mean time ill try to find something else to play to justify the 5 grand i've spent on hardware alone. Could have bought a nice new Scott foil 20 or Trek Madone SLR with that!! I don't buy "the Xbox Conspiracy" theory, purely because Asobo have shown in the past they are incapable of Quality Assurance prior to every Update released, to me this Tree LOD just smacks of the same ineptitude as other new Bugs & Issues that have plagued the Sim. What annoys me is a small dev team is capable of Hotfixing in hours if not days yet Asobo clearly are trying their best to avoid the need to Hotfix anything, so we get stuck for weeks/months with issues - the Flaps bug being the real only time they've stepped up and even that took well over a week. There can be so many reasons for the poor state of the updates, ultimately it's their name on the Sim so for me it's up to them to simply get better as IMO they have been fundamentally very poor in certain areas. If it does ultimately boil down to the Xbox need to "dumb" down the Sim then I'd be very surprised, but for me I just don't buy that. Pico Neo3 Link VR - Windows 11 64bit, Gigabyte Z590 Aorus Elite Mobo, i7-10700KF CPU, Gigabyte RX 9070 XT OC 16gb (AMD GPU), 32gig Corsair 3600mhz RAM, SSD x2 + M.2 SSD 1tb x1 Saitek X45 HOTAS - Saitek Pro Rudder Pedals - Logitech Flight Yoke - Homemade 3 Button & 8-directional Joystick Box, SNES Controller (used as a Button Box - Additional USB Numpad (used as a Button Box)
March 14, 20215 yr 1 hour ago, bobcat999 said: Fair enough, but with the lack of feedback we get, there is bound to be so much speculation - it leaves a vacuum for it. People are trying to find answers, and even give Asobo a helping hand if they can find the source of the issues. Most things start with a theory, or there is nothing! Absolutely you are correct. The problem for me is the number of theories that have no factual basis. Xbox is the reason for the problems, Xbox will eventually will lead to the demise of MSFS.... Well since this thread is about tree distance..I quit using that fix quite a while ago, but after experimenting for a couple of days I found that I can mostly get rid of the update induced stutters by keeping vsync at 30 in the sim just as before, lowering the LOD setting from 200 to 100 and lowering rendering from 130 to 120. Not a great tradeoff but at least I can fly. I wonder if Asobo has even acknowledged that there is a performance problem. As with all of the "bugs" some have it and others don't. In the past I've been mostly lucky but not this time.
March 14, 20215 yr 11 minutes ago, MarcG said: I don't buy "the Xbox Conspiracy" theory, purely because Asobo have shown in the past they are incapable of Quality Assurance prior to every Update released, to me this Tree LOD just smacks of the same ineptitude as other new Bugs & Issues that have plagued the Sim. What annoys me is a small dev team is capable of Hotfixing in hours if not days yet Asobo clearly are trying their best to avoid the need to Hotfix anything, so we get stuck for weeks/months with issues - the Flaps bug being the real only time they've stepped up and even that took well over a week. There can be so many reasons for the poor state of the updates, ultimately it's their name on the Sim so for me it's up to them to simply get better as IMO they have been fundamentally very poor in certain areas. If it does ultimately boil down to the Xbox need to "dumb" down the Sim then I'd be very surprised, but for me I just don't buy that. Didn't buy it either at first but between them chatting about optimizations for xbox in the last q and a and their absolutely woeful QA process i now have to give some credence to the xbox theory and not put it all on bad QA and question what their main goals and targets are. Edited March 14, 20215 yr by Maxis AMD Ryzen 9800X3D/ Asus ROG Strix B650E F Gaming WiFi / Asrock Taichi 9070XT / 32GB G.Skill Trident Z5 Neo DDR5 6000 / 2x ADATA XPG 8200 Pro NVME / Arctic Liquid Freezer II 280 / Seasonic Vertex 1000w PSU / Lian Li LanCool II Mesh Performance / Asus VG34VQL3A / Topping E70 Velvet DAC & L70 Amp /Sennheiser HD660s2 Thrustmaster Boeing Yoke + TCA Sidestick + TFRP Rudders
March 14, 20215 yr Trainee from Asobo just messed up with ultra, high and medium trees distance 😉 On my side, I tried different LOD in the UserCfg.opt (and turn the file on readonly) without any impact on trees distance... Any idea ???
March 14, 20215 yr 1 hour ago, Virtual Flight Realm said: Trainee from Asobo just messed up with ultra, high and medium trees distance 😉 On my side, I tried different LOD in the UserCfg.opt (and turn the file on readonly) without any impact on trees distance... Any idea ??? I'd say quite hacking and push for Asobo to fix the issue.😐 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
March 14, 20215 yr 3 hours ago, MarcG said: I've posted this "over there": This is (yet another) example of an Issue that should NOT require a certain Number of Votes before it is taken seriously by the Devs and action is taken, it’s obviously a backwards step or a Bug that’s appeared which requires immediate attention and not left to linger like the Terrain Spikes issue. I find the whole reasoning to Vote on Bugs amazingly redundant especially when these Bugs are introduced with an Update, they should not of been introduced in the first place and should blatantly be of a high priority to fix. Yes. I agree with your sentiments entirely and share them 100%. We shouldn't have to Vote to fix something that wasn't broken in the first place. BUT, by voting you and I know that ASOBO will run their eye across the Wish lists "over there" and see the sheer amount of people who HAVE voted. Also, in the posts on that Thread your sentiments are echoed. They know they've messed up and VOTING is another string to our bow of calling them out and leveraging them to do a Hotfix. We're trying to do all we can to bring pressure to bear where it needs to be to get action. So, please, others reading this thread MarcG has posted, head over here; share your thoughts (about just what you have said here) on the Thread BUT DO PLEASE VOTE; https://forums.flightsimulator.com/t/please-add-a-vegetation-render-distance-slider/377547/11 It's another angle we're coming at ASOBO with that shouts; "THIS IS JUST NOT GOOD ENOUGH!" Edited March 14, 20215 yr by Will Fly For Cheese
March 14, 20215 yr In fact the slider is/was there ultra, high, medium, ... to display trees at several distances Before the update 3
March 14, 20215 yr 4 hours ago, Dillon said: Add to that no real QA oversite plan both inhouse and out using the community as 2nd tier testing before a mass update is put out. We all shouldn't be forces to update until most can verify there's no issues. Would this have caught the tree issue? Don't those type of testers have to run without mods? So wouldn't they have already been use to seeing a very limited tree draw distance? 47 minutes ago, Virtual Flight Realm said: In fact the slider is/was there ultra, high, medium, ... to display trees at several distances Before the update 3 You are confusing tree texture quality with tree draw distance. Edited March 14, 20215 yr by Phantoms James
March 14, 20215 yr I won't enter any conspiracy theory about the Xbox, I have my own idea like everyone else. However, I've spent countless times documenting and alerting about the Tree LOD problems, and the Terrain LOD problems, and they never acknowledge nor answered. It was just a few weeks ago someone finally took on his shoulders looking closer at the sqrt(distance) problem I've been documenting and there is indeed a sqrt(distance) problem which at least I know they know about. What does it has to do with trees? I believe it is just another mishap when merging branches like the double flaps strength bug in the previous update, not something they are intentionally reducing the quality off for Xbox.
Archived
This topic is now archived and is closed to further replies.