Hi,

Hi,

I think the photogrammetry and mesh bugs in World Update 11 are unacceptable.

I hope Asobo will rectify and fix the problem.

Regards.
 

 

9 hours ago, 109Sqn said:

So, for me at least, the CN Tower is fine either way, but this is hours after the download went live so it could well have been server overload for others as suggested.

That’s because you have the third party CYTZ with the custom CN Tower model installed.

Edited September 30, 20223 yr by Tuskin38

1 hour ago, abrams_tank said:

but it would probably be very tedious to do it.

It isn’t tedious at all. Every part of the WU is its own package in the content manager that you can delete separately. Just type photogrammetry into the search bar, find the Canada one and delete it.

Edited September 30, 20223 yr by Tuskin38

11 hours ago, Cpt_Piett said:

Just did a flight around Vancouver Island (CYAZ-CYVR). I didn't see any mesh anomalies. But Vancouver is an ugly word not allowed! Such a pity that they couldn't find better photogrammetry - the whole CBD is a mess. Objects floating in the air, wonky highways going into the city, terrible bridges and the whole harbour area is just... 🤐 I think Vancouver sadly is at the very top of the list when it comes to the worst PG cities in MSFS. 

EDIT: I'm open for the possibility of a server issue preventing PG from loading properly. If it's not though - I feel sorry on behalf of all simmers from Vancouver 😖

Holy 😵 Do they have a war at Vancouver and I didn't get it ??  Now this update is truly a disaster - at least at some areas.

At the Yukon area it also looks hoorible, endless elevation issues around, just crazy releasing something like that - IMO ! 🤔

You have to assume that once again nothing was tested before the release..

cheers 😏

Edited September 30, 20223 yr by pmplayer

40 minutes ago, Cpt_Piett said:

So the PG in Vancouver was actually ok before WU11?

It wasn't the best, but it was a whole lot better than it is after the WU.

16 minutes ago, pmplayer said:

Holy 😵 Do they have a war at Vancouver and I didn't get it ??  Now this update is truly a disaster - at least at some areas.

At the Yukon area it also looks hoorible, endless elevation issues around, just crazy releasing something like that - IMO ! 🤔

You have to assume that once again nothing was tested before the release..

cheers 😏

It's so terrible that either it's a huuuge blunder in terms of quality control. Like disastrously bad. Or - could it be a server issue? I would still not rule out that possibility. I'm going to be flying in Canada for the next few days anyway, so I'll keep my eyes open. Not ready to delete WU11 yet. 

4 minutes ago, Cpt_Piett said:

It's so terrible that either it's a huuuge blunder in terms of quality control. Like disastrously bad. Or - could it be a server issue? I would still not rule out that possibility. I'm going to be flying in Canada for the next few days anyway, so I'll keep my eyes open. Not ready to delete WU11 yet. 

The elevation issues will still be there even with WU11 deleted. The new elevation data is part of the base sim update not the world update.

Also some of them have existed since launch.

Edited September 30, 20223 yr by Tuskin38

4 minutes ago, Tuskin38 said:

The elevation issues will still be there even with WU11 deleted. The new elevation data is part of the base sim update not the world update.

Also some of them have existed since launch.

I can't really wrap my brain around this. Doesn't every WU come with updated and enhanced elevation data?

Ok I see what you mean. 

Edited September 30, 20223 yr by Cpt_Piett

10 hours ago, scotchegg said:

I immediately noticed in the update a lot of my settings had been altered, including many terrain detail ones being lowered.

 

I had some of my settings changed too.  It changed from full screen to windowed.  I don't like them doing this.

Roy

2 hours ago, lagaffe said:

Hi,

In view of the elevation errors encountered in Quebec, I thought of the problem that appeared in version 1.12.13.0 in December 2020 and the MappaMundi patch.
The latter had isolated DEM data from the previous version and injected them as patches via the Community and this had solved a lot of problems on Quebec.

This patch is still available on flightsim.to. https://flightsim.to/file/5167/scenery-glitch-fixes-for-update-1-12-13-0
I just tried it this morning and the river that feeds the Montmorency Falls is back at the right altitude.

PS: I haven't had time to check other places.

 

Hmm, someone working on a 190?

Yes, I do a FW 190 Replca and a Galloping Ghost P-51 Racer 😃

The 1-step-forward-2-steps-back dances Asobo used to do in the early days of MSFS has been pretty much ridden of now with SU releases and them going out of their way to slow down and focus on quality, and conducting open betas before release, etc... Perhaps something like that would be good for WU releases too, even a closed beta at the least. And no need to stick to planned WU release dates.. if stuff has to be fixed then delay as much as needed, if quality of photogrammetry or other terrain-related data is <= current data, then don't do an update at all for that region. At least WUs are optional and free so that's good, but introducing *regressions* where some parts of a WU make it worse than the current state of things, is not good at all.
 

Edited September 30, 20223 yr by lwt1971

1 hour ago, Cpt_Piett said:

It's so terrible that either it's a huuuge blunder in terms of quality control. Like disastrously bad. Or - could it be a server issue? I would still not rule out that possibility. I'm going to be flying in Canada for the next few days anyway, so I'll keep my eyes open. Not ready to delete WU11 yet. 

I am not deleting the WU11 either but hopefully Asobo has a heart for his customers and do a hotfix or other update for the update because you can't leave it like that - that is just not MSFS like !

 Hope the Asobo team sees all this in these pictures and does something about it. 🤔

This is not MSFS worthy..

cheers 😉

There is a mesh\elevation problem west of Toronto outside of the new photogrammetry area. It has been there since the first release of MSFS. It looks terrible especially on approach to the east runways at Pearson. 
 

Does anyone know where I can report this? I want asobo to fix it. 

6 minutes ago, fakeflyer737 said:

Does anyone know where I can report this? I want asobo to fix it. 

https://flightsimulator.zendesk.com/hc/en-us

https://forums.flightsimulator.com/c/bugs-and-issues/airports/203