It is true that PS have more filters, but most of what you need is doable straight from CC3+, and can often be done with less work since you can manipulate how the entities are rendered, instead of just working with the composite image.

Keep in mind that CC3+ isn't a bitmap editor like GIMP is, so some things have to be done in a completely different way, for example you can see he has filled in the interior of your rubble symbols with a light grey and added some grey splotches to serve as shading for the staircase.

I can't really go into details about everything, that would make a very long forum post, but here is how you can do several of the things in CC3+ that have been done with this map.

First of all, the walls have been given a shadow. This serves to enhance and let them stand out, and can be done with the wall shadow effect. I am not sure if your map actually have wall entities, bit difficult to see, but an easy way to produce the walls is to take a copy of the background sheet as well as your floors, place those copies on the WALLS sheet and multipoly them together. This will result in a large polygon with holes in it matching your floors. Now, you can add wall shadows to that.

The grid seems to have been made a bit thinner and made grey (or transparent, gives the same end result) instead of black to give a less intrusive feel. Grids are usually zero-width lines, so to make it nice and thin, it is best to export a somewhat high resolution image in the first place. Images, as opposed to CC3+ drawings, have a finite number of pixels.

The numbering have all been erased and replaced with smaller text. No reason why you can't do that right in CC3+. The original map also seems to have white circles around the numbers. Not sure if that is from an effect or an actual circle, but this was removed in the cleanup, but if you don't need them, no need to have them in CC3+ in the first place.

The symbols seems to be slightly blurred in the final version. This can easily be done with the blur effect in CC3+.

The symbols have also been filled with a grey color in the fixed version. This is slightly more difficult in CC3+ since you can't fill areas the same way as with a bitmap editor, but what you can do is to overlay a partially transparent gray polygon in CC3+. You'll need to draw all these small polys and make sure they fit the symbol though.

Looking at the modified map, it is also clear that multiple things have been done with with it, this isn't a one click job from some filter, so even if the processes do take some manual work in CC3+, it isn't like they wouldn't do the same in GIMP/PS/etc either.

As for the export, 300ppi @ 8.5x11 is just 2550 x 3300 pixels. Shouldn't be an issue exporting that from CC3+. And the export settings dialog allows you to either input the pixel values directly, OR you can input 300 ppi into the dialog and the print size in inches, both options work just fine. You find the export options dialog by clicking Options AFTER selecting an image file type in the save as dialog, but before clicking save.

As Sue says, it would be nice to see what you are after. CC3+ can do a lot, and personally, I never post-process in an image editor, but it is often a manner of choice. People very proficient in PS or GIMP and new to CC3+ often resort to doing it that way because they find it easier to attack from the known angle rather than learn something new. And while CC3+ have lots of options, there are also some task an image editor can do better/easier in post, although I find these few. But knowing what you are after is important, 'clean up' isn't a spesific process, it is just a general term than can mean just about anything.

What size of image are you after here? 300 dpi by itself doesn't really mean anything without also knowing what dimensions you need.

Feel free to post wishes. It is always nice to know what the community thinks and wants. Please do be aware that some wishes may not be feasible due to technical limitations, so popularity here doesn't necessarily mean it will be implemented, and for the same reasons, not implementing a suggestion doesn't mean you are ignored.

ProFantasy staff, including the main developer, do read these boards, so suggestions will certainly be noticed when posted here.

Because of memory restrictions, CC3+ cannot compute the entire export image in one go, but must do it in parts. This is what you see when CC3+ reports that it is on Pass X of Y in the export progress dialog. Unfortunately, this also means that it can't include effects originating from entities outside the export area of the current pass (if it could, it wouldn't be necessary to split it into passes in the first place)

However, the default setting is quite conservative to allow machines with even a very low memory to export high resolution images, and this leads to many passes, which both leads to a bigger chance of effects being cut off this way, as well as the export taking quite a bit more time.

You can change the size of each rendering pass by typing in EXPORTSETMPPP on the command line and hitting enter. CC3+ will then prompt you (on the command line) for the new setting, with the old setting being displayed in square brackets. The exact number you can use here depends a bit on your computer and the complexity of the map, but 40000000 is good settings for almost every computer. Just type in this number on the command line and hit enter to set it (Make sure to use the right number of zeros). Note that it is unlikely that you can go far beyond 40000000 on any computer, no matter the amount of memory. I've been able to use 60000000 in some cases, but not consistently.

With this setting increased, you'll find that CC3+ uses far fewer passes. A map that used 40 passes before will now use around 4 passes instead, which is both much faster, and much less likely to interfere with effects.

This setting is permanent, so you only have to set it once, and CC3+ will remember it for the future. If you have any problems, you can just run the command again and set a lower value. 4000000 is the default. Also note that this setting do require that CC3+ gets allocated a contiguous range of memory from your computer, so if CC3+ starts telling you that there are not enough memory for export while using a value for this setting that has worked in the past setting this, a simple restart of CC3+ and/or your computer will usually help. If not, try a lower number, like 20000000 which is still much higher than the default.

Looking at your maps, one thing that strikes me is your use of font sizes. I think they would have a much better visual presentation if you spent some time normalizing font sizes.

For example, on some maps, the labels for locations are as large as the map/area title itself, for example your Danger Hills map (I assume danger hills is the name of the entire area. If not, the map should have a proper map name.)

In other maps, for example the Traraise Faire Caves ground levels, features have different sizes, such as area 2, redoubt, having a much larger size than the rest. Western Hill Fort also have some of these, some buildings have larger labels than others.

Generally, maps looks better with a consistent visual for the text size, ensuring that all locations of the same type (like numbered locations in a dungeons, buildings, etc) have the same size, and with labels covering larger areas being a bit bigger than labels for individual locations, with map titles being the largest of them all.