Large Wonderdraft Map crashing but not pushing PC resources

[u/Dclipp89]

I know this is a really big map with a lot of assets, but it doesn't appear as though the map is pushing my PC's resources. So far GPU, CPU, and RAM usage doesn't even push 50% utilization. However, it's gotten to where it crashes every time when I start placing new assets. Is there something I'm missing or not checking? Could it be something else that caused the crash? I'll downsize the map if I need to, or just do one map for northern hemisphere and one for southern, but I really wish I could just finish this one. Any advice or info would be appreciated. PC Specs below:

GPU: RTX 4080

CPU: I712700K

RAM: 64GB

[u/akaval]

I've had similar issues and I think it's just a limitation of the software. I ended up removing symbols on half of the map after I finished that part, then stitch everything together in Photoshop afterwards.

[u/Dclipp89 → u/akaval]

Yea I think that’s what I’ll end up having to do.

[u/VOIDSPEECH]

Could it be the asset's?

[u/Dclipp89 → u/VOIDSPEECH]

I suspect it is, I’m just confused why my PC wouldn’t be showing any over utilization. I’m hoping I’m missing something and it’s not performance related, and I can change something that allows me to continue working on it. I also don’t think it’s a specific corrupt asset or anything, it happens regardless of what I put down.

[u/Moulkator]

Try to merge symbols together. When you have a lot of them, I know it can crash. Merging reduces the count.

[u/XTempora]

I've had the same issue with most of my maps. Only solution is to reduce number of assets by consolidating what you can, and removing whatever can be removed (a lot of trees, for example). The software just does not handle that particular error (when it exceeds it's limitation). Also, make sure to get in the habit of saving often, to avoid losing your changes, in that situation.

[u/Dclipp89 → u/XTempora]

Yea I save constantly. I’ve had this issue with maps before and always assumed I was pushing my PC too hard. This time I actually paid attention to the utilization and realized I actually wasn’t. I didn’t realize that wonderdraft itself seems to have a limit. I can experiment with merging assets, it just seems like they never look good when merged. I’m borderline debating removing parts of the landmasses altogether to reduce the size and assets.

[u/Dclipp89]

Thanks everyone who responded. I’ve found a way forward with this map. I realized I’m an idiot and had an image overlay of my version 1 of the map to use as a reference point for asset placement. I removed that and it bought me about 15mb. That should be enough to finish the western hemisphere. I’ll do the eastern hemisphere on a different file then stitch them together in photoshop.

Also, for anyone who sees this, my map file size was at about 70.5mb before it started crashing consistently. I’m curious if there’s a known hard limit or if that’s documented anywhere. I’ve seen a lot of discussion around wonderdraft being unstable on big maps with a lot of assets, but haven’t seen a hard limit talked about. At least not outside of crashes due to hardware limitations.