It doesn't have anything with it being an object or not. CC3+ needs to be able to tell where the edges of entities on the sheet is when applying effects. When CC3+ computes effects, it makes a render of the complete stack of sheets up to and including the current sheet in the rendering process, and then compares the image it gets with the same pass done with the below sheet. Pixels that are exactly the same between the two renders will be areas where the latest sheet didn't have any entities, so we are seeing the sheet below through these points, while pixels that have changed represent areas that the current sheet covers. Edges are identified as borders between where pixels change and not. Effects are then applied to the image, and CC3+ continues one with the next sheet in the stack

This may seem complicated since CC3+ should just know where the entities are, right? Well, that would be the case if it wasn't for the effects, because once you start applying these it gets quite complicated and CC3+ needs to actually do these renders to calculate where the effects stretches to. And multiple effects on a sheet also interacts with each other, making this quite complicated.

So, this isn't some arbitrary rule that can just be turned off. Changing this would mean completely changing the way CC3+ renders the drawing.

Also, as the last step after installing everything, always (re-)install the latest update.

Looks like a dungeon style would be most appropriate. Something like the SS2 Bitmap A style perhaps?

Modern Floorplans is from SS3: Modern.

I think you may be looking in the wrong place for the files. FilterTest2.dll is found in the Filters directory inside the data directory (C:\ProgramData\Profantasy\CC3Plus\Filters), but this is not where the actual dll's reside (unsure why that test dll is there at all). The actual dll files are inside the Filters subdir in the CC3+ installation directory (C:\Program Files (x86)\ProFantasy\CC3Plus\Filters) (and there is no FilterTest2.dll there).

Try creating a new map and see if there is any difference.

Elexios the first is now in the atlas.

You can use the macro commands GOLAYER and GOSHEET (or LAYER and SSET if you prefer an error message instead of creating a new layer/sheet if it doesn't exist)

Using them by themselves may not speed up things too much since you need to specify the name, but you can then define your own named macros using something short and easy to go to a predefined sheet directly. And if you want the same command to just go to the next in a list, you should be able to set that up by using a variable to keep track of state and then using a conditional to activate the next sheet.

You can also add your macro commands to the CC3+ menus. This allows you to easily activate it from a menu, but maybe of equal interest, you can add shortcut keys to any menu command. Read more about menu editing.

Lastly, you can also use the SNEXT/SPREV to go to the next/previous sheet in the list. (There's no equivalent for layers)

Looks like the entity is simply too complicated here because of too much fractalization of the walls. The existing entity has 32632 nodes. That's bordeline what the tools can handle.

I recommend you reduce the node count of your entity somewhat. Try using the SIMPLIFY command on it (I suggest trying with a simplification distance of 0.1), this should reduce the node count significantly.

For your particular map there, you'll also need to consider how to handle "holes", (i.e. solid walls in the middle of the map). A standard CC3+ polygon cannot have holes in it, which you seemed to have noticed by the area up near that entrance to 10 not being closed properly. This is something you probably should consider right now before doing any more work.

There are three ways to handle holes. The one is through the use of a multipoly, where you draw the base floor only following the outer outline, and then you draw the inner walls as their own polygons and merge everything together using a multipoly. This works, but the multipoly cannot be edited by the drawing tool edit command once joined (without splitting it up again, then editing, and then joining it back together), so this approach works best if you plan for this and do the actual outline first.

The second way is basically draw the inner walls as their own polygons on top of the floor, usin an appropriate filling for the walls, and just accepting that the floor doesn't have holes where these walls are, but instead a wall covering that part of the floor.

The third way is through the use of the color key sheet effect. As with the other options, the main floor needs to follow the outer outline of the floor, and then all the inner walls are drawn in a distinct solid color on the same sheet as the floor, and the effect is used to "knock out" those parts, creating the visual appearance of holes.

I have to agree with Sue, making them inside CC3+ gives the best results.

The important thing to keep in mind when you try to use intermediate formats like .dxf/.dwg is that dxf/.dwg may not support all the features from Inkscape, and CC3+ may not support all the features from that dxf file again, resulting in a file that will probably be severely lacking compared to the original in Inkscape. Working with vectors isn't like working with images, where it will look identical whether you save it in .bmp, .jpg, .png or .gif, on the contrary, it's probably going to look quite different. Basic shape will be usually preserved, but all the more fancy stuff are likely to not survive the conversion. (Think of it as saving a fancy word document to plain text. Word supports it, but it looses all formatting like fonts, colors and lots more.)

Both of those should be easy enough to do, depending on what products you have.

For the cottage, any dungeon style should do, but Symbol Set 4 do come with Schely's forlorn cottage set, so if you have SS4, that's probably a good option. If not DD3 also works fine. But even without any additional add-ons, you have access to several dungeon styles, such as the Jon Roberts dungeon, or the more limited CC3 dungeon.

The isometric view do require Perspectives 3 to pull of properly. Check the essentials guide to get started, or if you also have the Tome, you can check out the first Perspectives tutorial there.