Graphical problems in region view

[nestorga 0]

Hello,

I recently decided to pick up SC4 Deluxe again.. it's been a few years. I've discovered, to my dismay, that a rather strange graphical problem occurs in the region view. The bottom parts of large cities appear to be "cut off." There is a picture attached which shows what I mean.

The strangest part about this is that the problem also occurred on my old computer, which has strikingly different hardware than my new one. Here are the specs of the new machine:

CPU - Core 2 Duo E8400 overclocked to 4.11GHz (100% stable for 24/7)

RAM - 4GB though only 3.25 show up in XP pro (SP2)

GPU - NVIDIA 8800GTS 512 (G92)

HDD - 2x500GB Seagates in RAID 1

Display - 20" 1600x1200 LCD, 60Hz refresh rate

The old machine was an AMD Athlon XP 2800+ with a gig of ram and an ATI 9600XT 128MB graphics card... as you can probably see, I'm struggling to find the common thread that links the two systems. Perhaps XP, but the strangest part about this is that I haven't seen the problem posted anywhere.

My virtual memory is currently set to 4096-4096. I'm running the latest graphics drivers from NVIDIA as well as the 1.1.638 patch yet the problem persists... I'd appreciate any help in this matter.

Thanks!

[CaptCity 4,683]

I think I have seen this mentioned once or twice. If I remember correctly, it had to do with rendering cities at resolutions 1600x1200 or higher. I think if you lower the resolution and then open and save the cities, the region image clears up. I'll see if I can dig up a thread. Maybe someone can give a bit more precise solution.

Edit: Might check out this thread...

[nestorga 0]

You're absolutely right - it was the resolution. I thought resolution didn't affect my problem, but since the thumbnails were generated at 1600x1200, they are messed up until loaded and saved in another resolution.

Say I want to take a regional screenshot - is there any way I can automate the process of reloading each city? Maybe I'm lazy, but it doesn't hurt to ask.

Shame that EA/Maxis never addressed this issue in a patch

Thanks a bunch!