Autosave deliberately save to a separate file to make sure to not accidentally overwrite your actual map file with what is perhaps unwanted changes, for example when testing things.. This is how autosave works in most software. I guess a more correct name would be "recovery save" or something like that, but autosave has just stuck in most software as the common term. It is not a replacement for manual saves, just an extra layer of security, so yes, you should always manually save before exiting. (Personally, I have autosave on, but the dialog off, so it autosaves silently in the background, which is what most other software does by default)

Something has happened that corrupted the current coordinates, so when zooming, it causes CC3+ to multiply numbers with illegal values, which won't work very well unfortunately.

The easy way to fix it is to just do a View -> Zooms -> To all Text, then pick any text entry in your map. That puts you back into proper coordinates, and zooms should now work fine.

The right click -> Run as Admin is old legacy advice which doesn't make a difference at all with modern installers. All modern program installers automatically make themselves admin if needed, this is why you see that UAC prompt that asks you if this installer should be allowed to make changes to your computer, what that really means is that the installer have just requested admin permissions.

You can see it on the program icon for the installer if it will run automatically as admin or not. Look for the blue/yellow admin shield on the icon:

As for running CC3+ itself as an admin, that should be completely unnecessary. The old CC3 needed it because it kept all it's data files in the installation folder where normal users can't write, but CC3+ changed that by introducing the data folder and sets it up with write access for all users.

Technically, they can be any size, because you need to enter the size in the png import dialog when importing the symbols into the symbol catalog. The most important thing is actually to A) know what your size represents, i.e what distance on your map 1 pixel represents, and B) keep internal scaling consistent. If 5' object is 500 pixles, then a 10' object needs to be 1000 pixels.

However, there are standard guidelines used for official PF artwork. Here are the pixels per drawing unit used for the VH version of the symbols. Don't think about the other resolutions, CC3+ will create those from the VH originals:

• Overland: 20
• City: 40
• Dungeon: 100

Note that if you follow these values, they also need to be entered into the import png dialog when importing the symbols, don't just leave it at the default option of 40.

Keep in mind that a drawing unit varies between map types. For overland, it is a mile, for city and dungeon it is a foot. (All symbols are made in imperial, then scaled for use in metric maps).

So as an example, if you wish to create a city symbol that will be 30 feet by 20 feet, the pixel dimensions for the VH version should be 1200 by 800.

Symbols usually have their snap point (origin) set based on the intended use of that particular symbol. Especially things that are meant to go against a wall or next to another symbol have edge snaps.

The main downside in general here is of course that symbols may have more than one appropriate way of being used. And of course, sometimes the origin point is just plain and simple wrong.

I recommend doing as Sue suggest, just turn off snap whenever you need to place a symbol that doesn't snap like you want it to. Personally, I usually work without snaps when placing symbols anyway, it tend to be a little bit to regular if all the chairs are in the middle of their square and so on. Snap for symbols is mostly needed when you need that perfect alignment.