Yes please.

There is a white rectangle outside the map on the SCREEN sheet. Hide this sheet and you can see what is outside. Draw on a sheet that is after this sheet in the sheet order to draw on top of it.

The primary use of this sheet is to hide things like symbols that partially extend beyond the map border.

The Humble Bundle setup is a very good starting point, giving you everything you really need.

But if you want to expand the styles you have available to you, Symbol Set 4 and 5 offers a very nice dungeon and city style. Symbol set 1 is also nice for additional overland styles.

And you can get tons of new styles through the annuals. I love the annuals for their diversity.

Sounds like unnecessary work if it is just the ca3.mnu file that is broken.

A repair install should resore missing files, so I would try just to delete the ca3.mnu file from your data directory, and then run a repair on character artist. That'll probably restore that file. If that works, you'll want to do a re-install of the latest update after that.

Didn't really notice the straightness of it until you pointed it out. It's fine as it is.

RCV20 is just a macro with a single line, RCVDATA, in it. RCVDATA is a variable holding data sent to CC3+ via intercom. I guess you can populate this variable manually and then call the macro, but it is really a special macro made to handle intercom requests that are CC3+ commands.

The available documentation is the .pdf that comes with the XP toolkit. It is old and incomplete, but that's what is.

As for using C# from an XP, that is actually possible. @saunderl did once write a tutorial about that, but the site is no longer available and the wayback machine don't seem to have captured the actual tutorials. I've been considering looking into that myself, when time permits, but it is fairly low down on my priority list.

Won't help you now that you got it working, but I should probably put this into a blog article for future users.

Well, there are a few less entities, so it would be marginally faster, but in practice, nothing you would notice.

Thanks.

I developed that template under VS19, which is why it probably requires it by default, but it doesn't really take advantage of any new features or anything.

Technically, there is no reason at all to use VS19 for XP development, but it happened to be ready for release at about the same time as my first blog article, so I decided to use that, since that was the version people would find at the MS download site. I actually wrote the blog article while using the beta version, and released it on the same day VS19 was released.

If things look different inside CC3+ when compared to an export, that is usually a fill or effect scaling issue. If fills are not scaled, or if effects are scaled to view size, the output will be different since the "view" during an export is very different from the normal view.

Size of the export (in pixels) also matters a bit of course.