City Update I: Germany

[jimjones]

Who forgot to remove the photogrammetry version of the bridge? The Cologne Cathedral is superb.

 

[grunau_baby]

Allready ranted about the bridges in another thread (Junkers F13). The new cities are nice to have finally, but they messed up the bridges. We have mainly suspension bridges in these cities here. (cologne, düsseldorf, bonn), but all those are now completely missing their cables structures

example in Bonn

The bridges within 3D-Cities are - at least for me - one of the weakest points with (global) MSFS scenery. They should put some more work into it and provide modelled bridges in those photoreal areas.

Alex

 

[Priller]

I saw the screenshots you guys posted and so I refrained from installing it. A ptty, because I was in Köln a couple of weeks ago... Oh well!

Priller

 

[Priller]

I saw the screenshots you guys posted and so I refrained from installing it. A ptty, because I was in Köln a couple of weeks ago... Oh well!

There seem to be issues with the trainstation as well.

Priller

 

[grunau_baby]

It´s mainly those bridges for me! And some unpleasant 3D artefacts in Düsseldorf on the rhine surface in the city. The hohenzollern bridge as seen above looks allright on my install, no photoreal overlapping.

What I also noticed is that the photoreal area of Dortmund abruptly ends in the western part of the city leaving the western outskirts all gerneric just west of the city center while covering a vast area to the east, even far outside Dortmund itself.

All in all it looks half baked and rushed. Could have used some more refinement before release.

 

[jimjones]

Since grunau_baby's install did not show the hohenzollern bridge problem it probably is working for others and mine has failed. It is just another of one of those isolated failures among a half a dozen others I've experienced.


Hopefully it works correctly for everyone else and my experience with the bridge should not influence others to refrain from installing.

 

[Dangerous Beans]

I just downloaded it and it was only 1.31Kb, is that correct or did something go wrong my end?

 

[Priller]

I just downloaded it and it was only 1.31Kb, is that correct or did something go wrong my end?

Only one way to find out! Can you take a screenshot of the Hohenzollern bridge in Cologne so we can compare?

Cheers,

Priller

 

[Dangerous Beans]

OK I think I got the right one. I had to look it up in Google Earth.



Its fully custom on my system, no weird merge of photogrammetry and custom, or autogen.
I flew along the river a bit in the area and there are a couple of custom bridges but mostly photogrammetry ones, I didn't see any autogen ones within the photogrammetry area.

I just looked in my Content Manager and although I saw 1.31Kb for the download it says its 492 bytes installed.
It just seemed very odd to me.

 

[ak416]

It's worth clearing your rolling cache and rebuilding it when installing new scenery as sometimes older bits of scenery can "linger" in the cache and cause errors. Secondly, from what I understand, photogrammetry is all stored in the cloud and not downloaded to your system, so the small file size is normal and is basically just a flag that tells the server "yes, I want to download this".

 

[jimjones]

It's worth clearing your rolling cache and rebuilding it when installing new scenery as sometimes older bits of scenery can "linger" in the cache and cause errors. Secondly, from what I understand, photogrammetry is all stored in the cloud and not downloaded to your system, so the small file size is normal and is basically just a flag that tells the server "yes, I want to download this".

Please explain how to clear rolling cache. Sorry if this is a stupid request. It is something I've never encountered B/4.
Thanks, Jim

 

[Dangerous Beans]

Please explain how to clear rolling cache. Sorry if this is a stupid request. It is something I've never encountered B/4.
Thanks, Jim

In the General Options there's a tab for Data, Rolling Cache is near the bottom of the page, you can turn it on or off and also define how big it is and where you want it if you want it on a different drive for instance.

 

[jimjones]

Thanks DB for your info. I had not scrolled down the Data screen to see the cache section. As it turns out I had no rolling cache defined. So, the suggestion to empty mine did not improve the conflicting photoreal and handcrafted bridge problem. I can live that and enjoy the photoreal of the cities.

All suggestions were appreciated.

 

[Tom Clayton]

You may want to take the issue to the Official Forum. There are people there that know the sim inside and out, and may have the answer you need.
https://forums.flightsimulator.com

 

[DennyA]

Even if you don't have a rolling cache defined, you can still use the erase cache function -- MSFS always keeps a cache of recent data even if you don't have rolling cache enabled. Worth trying.

 

[grunau_baby]

If it´s not the rolling cache, did you clear the scenery indexes and the content.xml when installing the update?

Set all your folder to vissible and within the "Appdata / Roaming / Microsoft Flight Simulator" you´ll find the content.xml. Delete this and delete ALL files in the subfolder "SceneryIndexes".

Then restart MSFS and let it build a new directory.

I do this prior and after every update and it all updates went smooth for me.

Alex

 

[Stearman]

In fact, in "Appdata / Roaming / Microsoft Flight Simulator" you'll also find a file named ROLLINGCACHE.CCC (usually quite large), along with the Content.xml mentioned by someone else.

You can delete it straightforward along with the Content.xml with no problem whatsoever: MSFS will create them again upon next start. That's the easiest way to clear the cache.

In fact, deleting both from time to time is a good practice, in order to keep things tidy.

 

[FlameOut]

I've used this to clear out suspected trouble with my MSFS install, but my pathway is different. I have the Premium Edition if that counts for anything.


C:\Users\Flame\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache


Where ...\Flame\.... is my username.