CC3+ crashing when placing symbols
Lorelei
🖼️ 46 images Mapmaker
Well I spoke too soon. Everything within the CC3+ program seems to be working fine. However, I have a large file that contains all my symbols i have acquired over the past year on my desktop. Everytime i try to place one of those symbols in a new or existing map the program crashes. Any ideas what the problem is? I even tried to import the pngs through the symbol manager and that didn't seem to work either. I'm just batting a thousand here....
Comments
I'll get you a screen shot in a minute to show you where I mean...
I don't, however, have that many symbols in my user file. Could it be that there's some kind of limit - when the whatever it is that loads symbols just gives up and throws its hands in the air?
How many symbols are you talking about?
Sorry Lorelei!
Lorelei, out of curiosity, have you tried dragging and dropping a PNG from the folder onto the map?
~Dogtag
Sorry, im snippy, but i am very frustrated with this and tired of it. I'm going back to cc3 for now until these glitches are figured out. enough. I miss my annuals anyway and need to shake of the bad juju of the last day or so. Thanks
It's not just you!
You may want to check the layer and sheet of the image. If it's on a frozen layer, you may not be able to select it for editing.
~Dogtag
I started looking at this with Lorelei's posting. On my main computer, I have Ralf's last beta version installed, the one offered to beta testers as file name CC3PlusUpdate7a.exe with a date of July 22, time 7:31, Explorer file size 150,072 KB. This version works beautifully, and that seems to have been the verdict of the beta group too.
So ... I was rather astounded at what I got to read above when I got up this morning. After puzzling over the events described, I downloaded the public release this morning, file name CC3PlusUpdate7.exe with a date of July 23, time 8:42, Explorer file size also 150,072 KB.
Both of these releases show Version 3.73, so the version number doesn't help.
I still have the last beta on my main machine, and it works fine. I installed the public version on my laptop, and there I have the same problems that folks are mentioning above. It appears that some bug might have creeped into things between the last beta and the release version.
A BIT MORE TESTING:
When I run the "faulty" version on the laptop with "Run As Administrator," things seem to work all right some of the time. That is: I open up with RaA one time, everything's OK. The next time, again with RaA, the problems are back. The next time with RaA, maybe it works again, etc. I'm wondering if something in the code is bumping up against Windows functions somewhere.
If, indeed, there is a difference between the last beta and the release edition (file size the same?), perhaps a rollback to the last beta might be an interim solution for those having problems.
All users of Bogie's Mapping Objects, the Vintyri Cartographic Collection and/or the CSUAC:
If you install Update 8, before you do it, make a backup of the file fcw32.mnu in (Data Folders)\ProFantasy\CC3Plus. After running Update 8, copy your backup version back into (Data Folders)\ProFantasy\CC3Plus!
Update 8 overwrites your overland toolbar, killing all of the Bogie, CSUAC and Vintyri symbols in it.
I'll test this out later on today when i return home before D&D tonight and let ya'll know how it went. It's hotter than hades out there today on the east coast and im heading to the beach.
Btw.... I ALWAYS run every program, annual, or update as administrator, so i know that isn't an issue here.
Again, thanks for your help!
With apologies to Joe Slayton, I've deleted the comments I had here about purported problems that I had on my laptop with Upgrade 8. It occurred to me just this morning that I had caused those problems myself, and Update 8 had nothing to do with them. After installing Update 7 on the laptop, I made some changes to check something during the late beta testing phase with Bogies Mapping Objects. I forgot to remove those objects afterward, and they caused the problems that I mentioned, not Update 8. Removing those objects also caused the laptop to return to normal speed.
Again, apologies!