All the autogen trees in Connecticut (at least east of Hartford) and most in Rhode Island are being rendered as grass! I thought I broke my trees, but when I go back to where I've seen trees work in the past, they are still there. I even landed on the "tree grass" to prove that MFS actually thinks the trees are grass (and there is actual grass being rendered). Photogrammetry trees are fine, but it's JUST photogrammetry. Switching photogrammetry off results in fields of tree grass.

Has anyone else experienced this? What's going on??

If your trees are grass for more than six hours, please contact your doctor.

It makes me sad 😓

@Keto Ketchup I'm beginning to think my friend you have an unstable system. You've had at least three threads now of oddball anomalies from blank spaces of trees following you to now trees being rendered as grass..

Edited September 6, 20205 yr by styckx

2 minutes ago, styckx said:

@Keto Ketchup I'm beginning to think my friend you have an unstable system. You've had at least three threads now of oddball anomalies from blank spaces of trees following you to now trees being rendered as grass..

So trees are trees for you east of Hartford, CT? Like I said, trees are trees in other parts of the world where I've been (eastern MA, for example). This specific problem is very predictable, which is not how unstable works. Now if in one session there were trees and the next there was grass and the next elephants start falling from the sky (like Skyrim), and if all my other games had similar problems, I'd be more likely to question my hardware. But so far I'm not seeing any indications this is a hardware issue.

Now perhaps it's a problem with the installation of MSFS or something wonky with a config file, this would not surprise me. I already cleared my cache, thinking it might be corrupted, but that did nothing. The LAST thing I want to do is reinstall this monster, not with this slow Internet of mine!

Anyway, I'm hoping somebody else can replicate this and then offer a fix that's not so drastic as reinstall or buy a new computer.

8 minutes ago, styckx said:

@Keto Ketchup I'm beginning to think my friend you have an unstable system. You've had at least three threads now of oddball anomalies from blank spaces of trees following you to now trees being rendered as grass..

"oddball anomalies" 

whats odd is these convulated installs - xbox this xbox that this account that account - please what a mess to run one game

Had to re-buy simulator from steam so theres 130$ down the drain - MS version is so intrusive - wouldnt run couldnt open folder all kinds of write protection

Uninstall it and try to reinstall it - guess what MS wont let me reinstall it what a joke - then they tell me to re-load windows on a new pc I just built yah right all set - so !@##$%^ off

42 minutes ago, styckx said:

@Keto Ketchup I'm beginning to think my friend you have an unstable system. You've had at least three threads now of oddball anomalies from blank spaces of trees following you to now trees being rendered as grass..

One thing I will try is updating my Nvidia driver. It's not the "MSFS ready" version, but I hadn't had any major problems until I flew to CT. Who knows, where MSFS uses the GPU to decompress scenery data, maybe the older driver is what is confusing trees for grass... I'll let you all know what happens.

UPDATE - Nope, no difference!

Edited September 6, 20205 yr by Keto Ketchup
update

7 minutes ago, Richard Sennett said:

whats odd is these convulated installs - xbox this xbox that this account that account - please what a mess to run one game

You need one free account.  It's not exactly this:

1 hour ago, Keto Ketchup said:

All the autogen trees in Connecticut (at least east of Hartford) and most in Rhode Island are being rendered as grass! I thought I broke my trees, but when I go back to where I've seen trees work in the past, they are still there. I even landed on the "tree grass" to prove that MFS actually thinks the trees are grass (and there is actual grass being rendered). Photogrammetry trees are fine, but it's JUST photogrammetry. Switching photogrammetry off results in fields of tree grass.

Has anyone else experienced this? What's going on??

I do not have MSFS, but have been following the MSFS posts regularly here and on Flightsim.com to help make my decision to purchase or not. This topic was brought up there as well. I think it was called “trees in New England” and the poster was having the same issues west of Boston.

John C.

Edited September 6, 20205 yr by johncott

I set out west from Hartford, finally coming to this magic line:

I'm going to manually delete my rolling cache and take off from Hartford again. If it's still broken, then I can only assuming the terrain data itself is broken in this area. According to @johncott I am not the only one to have this problem after all. Unfortunately a quick Google search didn't reward me with any answers... 🤷‍♂️

21 minutes ago, johncott said:

I do not have MSFS, but have been following the MSFS posts regularly here and on Flightsim.com to help make my decision to purchase or not. This topic was brought up there as well. I think it was called “trees in New England” and the poster was having the same issues west of Boston.

John C.

Thanks for the tip! I followed your lead and found this very recent post:

"I've been flying around a few places in Europe and the USA. My graphics are set at High (the automatic install setting).

I've found that for me a large swathe of central Massachusetts (and parts of adjoining States) has no 3D trees - just ground texture. Going East (he meant "west") from Boston the trees start to go blocky, then patchy, before failing entirely around about W71.3. After that there's nothing until well past Northampton MA, until about W73, when they start again on a N/S line like a tile edge. The problem extends South into Connecticut, but I haven't had time to see how far North it goes. This is a large area!

I thought it might be just me, but it's there every time I check, so maybe it's a real bug for everyone? I don't know how to report it and I haven't seen anyone else reporting this - so is this only me with my hardware? I don't see this problem elsewhere that I've flown over. Jump to Northampton MA and take a look..."

Unfortunately no answers have been given on that forum, either. I tried deleting and disabling rolling cache, but this did nothing to solve the problem. I guess I'm just going to have to leave New England. The more ground I cover (I fly everywhere I want to go, no teleporting), the more I'm amazed at just how broken the "world" is in this game. Fingers crossed it will all be fixed soon! If I keep running into these issues, I'm going to postpone my cross-country fix.

Edited September 6, 20205 yr by Keto Ketchup
clarity

2 hours ago, Keto Ketchup said:

All the autogen trees in Connecticut (at least east of Hartford) and most in Rhode Island are being rendered as grass! I thought I broke my trees, but when I go back to where I've seen trees work in the past, they are still there. I even landed on the "tree grass" to prove that MFS actually thinks the trees are grass (and there is actual grass being rendered). Photogrammetry trees are fine, but it's JUST photogrammetry. Switching photogrammetry off results in fields of tree grass.

Has anyone else experienced this? What's going on??

I have flown around DXR, BID (RI), BDL, 11N, OXC and others, and the areas that should have trees do have trees from my perspective.

Edited September 6, 20205 yr by RustyFlyer

1 hour ago, RustyFlyer said:

I have flown around DXR, BID (RI), BDL, 11N, OXC and others, and the areas that should have trees do have trees from my perspective.

I think all (at least the first three) of those airports are in photogrammetry zones. If you leave BDL and fly south to Hartford, you should soon transition from photogrammetry to autogen, where the lack of trees is very obvious due to the "wall" separating the two zones. It's the autogen trees that are missing in central CT.

On a side-note, I sure wish they had extended the photogrammetry corridor from Springfield all the way down to Hartford. Hartford seems a very odd omission as a photorealism candidate.  

Edited September 6, 20205 yr by Keto Ketchup

I am having this problem as well.  Thought I was going nuts.  But it's not just one person's problem.  I haven't done any tinkering with settings (left things pretty much as recommended at first launch), nor have I installed any addons of any kind.  Just grass and buildings, no trees.  Haven't noticed this at any other location, although I've stayed pretty much in the eastern US so far.

2 hours ago, RustyFlyer said:

I have flown around DXR, BID (RI), BDL, 11N, OXC and others, and the areas that should have trees do have trees from my perspective.

DXR has trees on my system as well.  You have to go farther east.  I don't recall seeing the exact line as posted above, but when I landed at Hartford there were no trees.  At first you may not notice it because the ground textures are so good.  At altitude it looks like there are trees, but it's just the flat textures.

Edited September 7, 20205 yr by bcuomo