Hi,
Same issue here. No way to change size, location, delete/moving/recreate the file !!
Had this on Xbox after signing up for SU9 had to fully delete and reinstall full sim to fix
Do you have the same issue if you follow the OPās steps to reproduce it?
yes
Provide extra information to complete the original description of the issue:
I reinstalled msfs on a new computer which no longer had the same drive i used for manualcache before. Now itās stuck and iām unable to change locations for the cache to an existing drive. I also cannot just change drive letters of my drive without actually breaking windows or the new msfs installation to mock the existence of the old āmissingā drive.
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OPās steps to reproduce it?
Provide extra information to complete the original description of the issue:
Yes, after a bootsector failure and fresh install, cache grayed out. Cannot cache any location.
No mods. Stock install. Have been told a patch will follow. Any ideas anyone?
Nothing useful except to say it seems thereās several of us in the same boat. My cache was on a drive that no longer exists, and a full reinstall (uninstall on Steam, delete path on disk, delete AppData/Roaming folder, reinstall) persists the non-existent path that Iām not allowed to change. Evidently, this config is stored on our syncād profile which seemsā¦ suspect for something thatās going to be unique to each install on each machine.
I was told a patch would fix Thats not out yet. Wonderful.
2 Likes
Same to meā¦
Due to the slowness of MS servers for South America, rarely exceeding 10-15Mbps, Manual Cache is ESSENTIAL for flying with photogrammetry.
I had my favorite cities completely downloaded to the local disk, but I canāt even see them through the old menu anymore.
Iāve read that it is a known MSFS bug that users can no longer change the location of the manual cache. If needed, a work around to the change the size of the manual cache is to use āfsutil file createā to create a new cache file of the desired size. Note that this file must reside the manual cache directory and be named MANUALCACHE.CCC. Also, this creates an empty file thus any existing manual cache regions will be lost.
1 Like
Do you have the same issue if you follow the OPās steps to reproduce it?
Same issue, but triggered by removing the non-default location drive (D:) before changing setting to a new valid location.
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Manual cache is a joke.
We should be able to select a mass area and then decide whether to download that selection in low-med-hi res.
Not the other way around.
Same problem, somebody have a fix?
I had limited success by renaming an empty rolling cache and uploading to it however it created a memory leak and once I left the area a CTD quickly followed.
I expect that the MC is deliberately disabled while they work on a fix, understandable but IMO there should be a pinned notice explaining this.
1 Like
Okay, I followed the instructions from Raptor4400, on creating a manualcache.ccc file by copying the rollingcache.ccc file. Hereās my report on how it went.
The procedure does work, but there are some limitations:
a) you can only ācreateā a new ManualCache.ccc file in the primary MSFS Package directory [C:\Users\YOUR_NAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\MANUALCACHE.CCC]. If you create it in any other folder, on any other drive or partition, MSFS wonāt be able to access it.
b) You canāt increase the size like you can the rollingcache.ccc file, at least not within MSFS, so you better create it as big as you will ever need. It may be possible to add extra blocks of empty data to the end of the file with a hex editor, but I havenāt tried that yet, and doing it that way might cause MSFS to simply reject the file as ācorruptā or something.
c) The scenery at the edges of the area you define to cache donāt necessarily merge smoothly into the AI (default) scenery. Especially if there is water (the ocean, a bay, or a lake) beyond the edge of your cached area, there will be places where the cached scenery tiles are visible in the water as squares of a different color and elevation. Iām not sure what would happen if you were in a float plane or amphibian and hit one of these edges on a landing or takeoff roll, but if the elevation difference is big enough to see from hundreds of meters away, it might be big enough to crash the aircraft? When landing or taking off from glaciers in a ski-equipped plane, I have sometimes hit abrupt changes in elevation and crashed, so maybe the same thing can happen where the edges of cached scenery tiles exist in water?
As for visual quality: I downloaded at High Quality, all of the area of San Francisco south to just below the KSFO airport. From 1000ā AGL or higher, it looks really nice. But from lower down, 100ā~500ā AGL, in a slow plane like the Cub Crafter NX or the Zlin Savage or Shock Ultra, the merging of the photogrammetry with the AI model isnāt so attractive. The colors and patterns of bare ground and vegetation (soil, grass, parkland, trees etc) is greatly improved, but in urban areas, itās not so good. In San Francisco, downloading and caching the photogrammetry does get you a bunch of landmark buildings that arenāt in the AI scenery, like Coit Tower, the Transamerica pyramid, the Twin Peaks TV tower, and the Palace of Fine Arts, but there are downsides:
The facades of practically all of the buildings look terrible at distances closer than 300 feet, as if they had been painted with mud. Window frames are crooked or twisted, and the modelling of structures on steep hillsides is bad, really bad - buildings on Telegraph Hill, including the base of Coit Tower, look nothing like buildings, but more like Salvador Dali painted them while on a bad acid trip.
Fly close enough, and it can be plainly seen that trees are sprouting right out of the roofs of buildings. The algorithm obviously isnāt smart enough to realize that tree trunks are rooted in yards, or out on the sidewalks and in the road medians, not in the middle of the buildings.
Objects that the algorithm canāt interpret, because they were maybe unclear in the aerial photogrammetry, are sometimes depicted as weird geometrical shapes like pyramids, that look completely unnatuaral and out-of-place.
Along the land-edge of my download, in a strip about 3 miles wide between San Carlos and the KSFO airport, running the whole width of the peninsula from SF Bay to the ocean, the photogrammetry is low quality, and looks worse, WAY worse, than the AI scenery. I donāt know what to do about this, if thereās even anything that can be done.
My download, covering San Francisco and the north portion of San Mateo County down to just below KSFO, took 11.5 gB of data. Obviously, caching large areas, like all of Death Valley National Park for example (2.8 million acres), would probably be impractical except at Low quality; if you tried to cache an area that large even at Medium quality, you might need a cache file of several terabytes. Iāll try to quantify just how much data it takes to map, say, 10 square miles of non-urban land at Low, Medium, and High, and post the numbers later.
1 Like
There might be a workaround to the issue of losing your existing manual cache data if you create a new, larger manualcache.ccc file, by using a Hex editor and adding extra blocks of data to the end of your existing manual cache file. Hereās how it works:
-
I use āHexEdit 4.0ā, by Andrew Phillips. Itās open source and can be downloaded from many repositories on the Web.
-
Exit MSFS if itās running.
-
Open your manualcache.ccc file in HexEdit.
-
Place the cursor at the End-of-File by keying āCTRL-ENDā.
-
Pull down āEDIT > INSERT BLOCKā from the main menu.
-
In the āSpecified / Decimalā input box, place the number of bytes you want to add (I assume this would be at least 1 gB). To add 1 gB, use 1073741824 (hexidecimal 4000 0000). To add 2 gB, use 2147483648 (hexidecimal 8000 0000). To add 4 gB, use 4294967296 (hexidecimal 1 0000 0000).
-
In the āFill withā box, select Hex radio button, and ā00ā (as shown in the example), then click OK.
-
When the process completes (it might take several seconds to append a really big block), pull down āFile > Save Asā from the main menu, and save the file to a new name, in the same folder as the existing manualcache.ccc file.
-
Open Windows Explorer and navigate to the new file. Rename the existing manualcache.ccc file to manualcache.ccc.bak, and rename the new file to manualcache.ccc. You are doing this for safety, so that if MSFS chokes on the new file for some reason, you can simply delete it, and restore the original file without losing anything but a few minutes of time.
1 Like
Do you have the same issue if you follow the OPās steps to reproduce it?
Yes, same here.
Provide extra information to complete the original description of the issue:
The problem existed since the first installation in end of December 22
If relevant, provide additional screenshots/video:
looks identical
Same situation here, since December 2022.
Another one with the same issue here.
Fixed in Sim Update 12.