CC3 climate view
jbclaypool
Newcomer
I exported an FT3 map to CC3. Things look ok except in climate view it has this weird projection effect.
The other views don't do this, well altitude view does it a little.
My question is how to get rid of it.
Comments
What happen if you zoom out a bit? Does it always go to the top left of the window, or does it stop somewhere?
Is it possible to select that rogue entity, for example by using the delete or change properties command on it, by selecting it somewhere on the part that is outside the map, or does CC3+ behave like it is nothing there?
What kind of computer are you running this on now? Is it a regular 64-bit machine with an Intel or Amd CPU, or are you running it on an Arm-based computer, such as using a virtual Windows machine on a Mac or one of the newer Arm-based Windows machines?
Goes away eventually by zooming out. Always seems to go to the top left of the window. Attempting to select it seems to select the whole map.
My computer runs with AMD Ryzen 7, 64Gb RAM, Nvidia 4060 16Gb, WD 2Tb ssd. Win11.
Now that I think about it, this has showed up before when I try to export from FT3 to CC3.
Could you attach the .fcw here? I'd like to have a little look at it, and see if I can replicate the problem on my computer and have a look at those problematic polygons and maybe send it off to the devloper.
I'll do it when I get home. Is there a file size limit on attachments?
Unfortunately, the file is too big to attach here (13Mb). I can compress it to just get it to 5Mb, but compressed files are not allowed...which I fully understand.
While home I tried dropping the FT3 world resolution to 4000x2000. This changed the appearance of the glitch projection somewhat, but didn't eliminate it. And only dropped the CC3 file size to 10Mb.
CC3+ files generated from FT tends to get a bit big, because of all the nodes.
The forum should support attachments up to 5MB, and it does allow compressed files, but only .zip. (This is done intentionally to encourage people to use that format. Not because it is the best compression-wise, but because every modern OS has built-in support for it, so a .zip file is usable by everyone without looking for additional software.)
You can just email me the file though, you'll find my email in my profile. I am pretty sure the attachment limit for email on google is 20MB.
I talked to the developer, and the issue here is that the underlying windows API functions that handle the actual painting to the screen is hitting their limits, the multipoly simply gets too complex in this case.
The only option is to reduce the number of nodes in the underlying polygons. to reduce the complexity.
Ok. I reduced the multipoly to various levels--it seems to be better in multiples of 4, i.e., 256, 512, 1024, but doesn't really go away. But it does go away if I use the select and zoom button to zoom in on the area where it appears to project from. So I'll just do that.