No. The viewer product was discontinued. The problems with a viewer for CC3/CC3+ is that maps rely on artwork installed on the users computer, the .fcw files themselves doesn't have this embedded. This means a viewer would require the exact same installation of artwork as the actual product, which has rendered the concept of a viewer a bit difficult. The original viewer concept was from back in the CC2 days where all artwork were vector artwork that could be embedded into the map files themselves.

To view .fcw files you will need to have CC3+ installed, as well as the same add-ons that were used to create the maps so that you have the same art resources avilable.

If you're interested in trying out CC3+, there is a 14-day money back guarantee, but otherwise I recommend you ask the person sending you the files to export them as an image or print them to a pdf file instead.

Also note that the trick by clicking the :CC2SYMICOND: button only works if you have started a map in the appropriate style (i.e CC3 Mike Schley Overland or SS4 Dungeons of Schley styles). Otherwise you will need to load them manually as JulianDracos describes.

If you want to keep the temporary files (the tiles) when using the large exports annual scripts, you can just comment out the line that deletes them from the @Annual\Issue 129 - Large Exports\tile.cmd script:

DEL /q tile*.png

(This line appears two places in the script due to branching paths)

Do remember that this also means you need to manually clean them out before doing the next export however, or the stitching process will get confused.

And if you just want the tiles generated, and not stitch them together at all, you can comment out the two lines in the script starting with magick mogrify and magick montage.

And yea, you do absolutely need to use png when working with large images, as stated above, jpg cannot do these image sizes. But if you just export things as tiles from CC3+, you could switch that export to jpg to get jpg files instead of png tiles, since each tile is small enough, it's only when stitched together it becomes too large.

In the final deep zoom images I have made for the atlas (like Sanctuary) I exported as png from CC3+, but the final tiles used by the deep zoom script itself are jpg images as this gives much better performance due to smaller file sizes.

They way I am envisioning a huge ship like this isn't huge individual areas dedicated to one thing, but more like divided up into "residential zone A", "residential zone B" and so on, where each individual zone have all the services needed for that zone, such as kitchens, storage, living quarters, recreation, security and more. Each zone being more or less self-contained (maybe even designed to be able to be isolated in the case of an emergency.

Actually similar to how a city today works. You don't find all the kitchens of the city in one corner, they are distributed out so people have access to a local restaurant without crossing the entire city.

Outside the residential zones which contains everything needed for the citicens, you may have some large engineering sections (but even a lot of that would probably be part of a residential zone, you can't risk having all the oxygen production in one part of the ship), maybe a huge hangar deck for the main transport ships bringing supplies and people on board. Maybe a command section, but that again probably would just be a tiny spec at this scale.

Yes. If it is already a symbol in the drawing, go to Symbols -> Symbol Manager, select the symbols from the list, and use the save as catalog to create a new catalog with the symbols.

If it isn't already a symbol, but just loose entities, you can define them as a symbol first using Symbols -> Define Symbol, and then you can export it to a symbol catalog file as described above.

To add it to an existing catalog, do as above, then open up the existing catalog for editing by opening it up using file -> open as opposed to just open it in the symbol catalog window, then go to Symbols -> Symbol Manager, hit Import, and pick the catalog file you created above.