Crashing when changing fill

Has anyone else had this, and were they able to overcome it, if so how?
I am attempting to change the fill on a Relief/Contour entity from a solid colour to a bit map fill (in this case land dark green)
I select the entity using select by colour (93 in this case). This picks up the polygons fine. Then setting the change fill pattern to land dark green the program crashes. It does not crash if I change the polygon from one colour to another but is crashing all the time when using a bitmap fill.
It generated this message
An unhandled win32 exception occurred in fcw32.exe (1016)

Any suggestions?

PS I have done this on two different machines with the same result. The only odd thing about the file was that I copied a bunch of symbols, rivers etc from a smaller map into this one which is a larger area.

Comments

  • My guess is something is wrong with the map -- maybe something got corrupted when you copied. Can you post the map here so we can take a look at it? Maybe we can figure out what the problem is.

    Steve
  • I reexported a version of the map from FT3 using less contours so that I could get the CC3 map files down to a more reasonable size (the original export was over 2MB) in case that was the problem. Then tried to change the fill style of colour 93 to Land Dark Green. Crash. I also tried it with other fills, as far as I can tell this only occurs with the bitmap fills.It is also only crashing when colour 93 is selected. I can alter the bit map fill of colour 94 for example. Something about that contour with colour 93. I changed its colour to 94 then tried the bitmap fill..crash. So its something with that part of the relief/contour.

    Anyway I have attached a copy of the map as exported by FT3 to see if anyone can make something of the problem.
  • MonsenMonsen Administrator 🖼️ 81 images Cartographer
    Seems like the problem is with you contours being multipolies. Multipolies can be somewhat problematic, and in your case, the multipolies were made up from a large number of entities, which is probably the reason for the crash.
    In the export settings in FT, there is an option to have the contour lines multiplies. You may wish to try exporting your map with this option off.
  • I'll give that a try, thanks Monsen. Here's hoping.
  • Tried it. Sort of worked, then on a hunch tried the same thing with the original map. Here's what I did. I reexported from FT3 two versions of the map one with polys on the other off.
    Changed the fill pattern for both from solid colour to bitmap. This worked on both versions! while the maps were in the original size as exported from FT3. However both produced a program crash when either the zoom expanses or zoom out buttons were pressed. So sort of stuck now.
  • RalfRalf Administrator, ProFantasy 🖼️ 18 images Mapmaker
    What happens if you reduce the detail level a little in the export settings in FT3? Edit or duplicate the Camapign Cartographer Export setting you are using. On the third page (Detail Level) move the slider one notch to the left. Then export. Does that help?
  • I have tried reducing the detail level slider (to 896), reducing the editing size from 5120 to 4096, exporting with and without polys. It crashed on all of these. Yet another map section of the same region but zoomed in by a factor of 2 worked fine.

    One thing I did notice was that a number of sheets had been duplicated (Political Borders and Cartouches) in the CC3 file. This did not occur with the zoomed in section when I exported this to CC3.
  • 23 days later
  • edited April 2012
    Got the fill to work if when I exported, the detail level slider was reduced to 512 any higher and CC3 still crashed when I tried to change to a bitmap fill. Odd.

    Oh yes the duplicated sheets - Cartouches and Political Borders are still being generated.
  • edited April 2012
    OK mostly finished the map, I do have some duplicate symbols sitting on the Temporary layer. Turned effects on and then tried to print to A3. Program gets as far as the pop up saying printing then crashes. The program continually crashes. I've just about given up on CC3 it seems to crash at every opportunity.
    Anyway I have attached the map in case someone can tell me what is wrong with it and how to fix it.
  • I copied the fcw file to another machine and tried loading it into CC3 on that machine. Would not even load. Came up with the visual basic debugger message
    Unhandled exception at 0x0045523c in fcw32.exe: 0xC0000005: Access violation reading location 0x000002f5.

    Don't know if that will help.
  • MonsenMonsen Administrator 🖼️ 81 images Cartographer
    I get a crash to desktop myself when trying to load your map. I suggest you contact ProFantasy Tech Support directly, and ask them to have a look at the file.
  • Interestingly enough if I open CC3 first and use the open file dialogue the image of the files appears in the preview box but when you then click open CC3 crashes. This is something that I am getting very frustrated with especially as I am using it for a number of commercial projects.

    I have one more thing to try since I have a copy which will open on the original computer. Based on the discussion above it looks like the problem will be on the Relief Contours layer. I am wondering if I reexport the map portion from FT3 at the lower slider rate whether I will be able to copy everything except that layer over to a new map. I'll let you know how this goes.
  • OK here is a copy of the fcw file with the bitmap fills replaced with solid colours. This is not quite what I was after but it did print without crashing. Some of the effects when applied to the Land sheet still cause a crash, but the problem was definately with the entities on the Relief/Contours layer (It could be that the system I am using has insufficient processing power or ram to cope?. a 1.8MHz CPU and 4G of ram).

    I did try copying everything over to a new iteration of the map with a much lower FT3 slider setting and this seemed to work but the difference between the two coastlines, lakes etc were to much of a pain to correct.
Sign In or Register to comment.