These values and their use can be a bit hard to understand, so let me throw in some explanations and see if that clears things up. Let me know if things still doesn't seem to work as expected after taking this into account.

• Inclination is only used for roof shading, not the shadows cast from the buildings. No matter what you set for inclination, the length of the shadows will be the same, but (assuming you use a city style that supports shading - most do) you should see a bit variation in the shading of the roof. This is combined with the steepness of the roof, so the actual effect can vary, but you should see parts of the roof getting lighter/darker when changing this, but it will have no effect on the shadows cast on the ground by the building
• The blur/transparency setting are only for dungeon lighting. It is possible to use in city maps as well, but it will have no effect as long as you don't have any configured light sources in your map, and the appropriate Point Light shadow effects set up on your sheets (which are not in city maps by default). Without this setup, these settings do absolutely nothing for your map.
• Azimuth, on the other hand is directly used by the "Wall Shadow, Directional" effect, IF the effect is configured to use global sun instead of a fix angle (It usually is). Thus this setting will change the direction of the shadows cast by the buildings.

That's a limitation in how computers store numbers.

Basically, because computers use binary internally to represent numbers, there will always be errors in precision for decimal numbers. Computers store these numbers smartly, so if the number before the decimal point is small, you get more precision, but since you have a somewhat large number (5 digits), it means that you loose out on precision on the decimal part. (Float can store 7 digits precicely)

There are different data types that can be used that offer different degrees of precision. CC3+ is using a float type to store these numbers, which is less precise than a double, but also uses less memory. Float was selected for the code back in the day, because it gave the best memory performance compared to the needs for very high precision.

In short, this is just how computers work.

If you are interested, here's a code example that shows exactly what happens:

#include <iomanip>
#include <iostream>
using namespace std;

int main() 
{
 float f = 18888.62110;
 double d = 18888.62110;

 cout << endl << "18888.62110" << endl;
 cout << "Float: " << setprecision(10) << f << endl;
 cout << "Double: "<< setprecision(10) << d << endl;

 f = 18.62110;
 d = 18.62110;

 cout << endl << "18.62110" << endl;
 cout << "Float: " << setprecision(7) << f << endl;
 cout << "Double: "<< setprecision(7) << d << endl;
}

Output:

18888.62110
Float: 18888.62109
Double: 18888.6211

18.62110
Float: 18.6211
Double: 18.6211

When CC3+ is installed, it installs 2 folders, the program files, and the data directory.

The program files folder is extremely tiny (less than 50MB), and is always installed on the C drive. (c:\program files(x86)\ProFantasy\CC3Plus)

The data directory is installed to wherever you pick in the installer.

You can move the install folder away from C, but I do not recommend messing with it. It is extremely tiny, and does not take any real space at all on a modern drive, even if you have a real old tiny one.

Also make sure you don't combine my instructions the wrong way. If you don't select anything with your mouse but then changes to combine-> and, you won't be able to select anything because that means it will only match one criteria, not both, so either:

1. Start the command -> select the entities by mouse -> right click/Combine/And -> right click/more/entity tag/type tag number
2. Start the command -> DO NOT select anything by mouse -> right click/more/entity tag/type tag number

If I understand you right, the issue is that you select the item with your mouse first. Selections are cumulative, so what happened is that you selected both entities, then by using the entity tag method, you just selected one of them again, leading it to still be selected.

Two ways to handle this:

• Either not select it with your mouse first at all
• Or,right click and set the Combine selection option to And (Both), which means an entity is only selected if it matches both criteria (mouse selection AND entity tag in this case)

(You can also do a combine by Not, and remove one from the selection by using the other entity's tag)