Bug v1.00: Custom defined zoom miswrite OPTIONS.TXT

[GoodGuy]

ORIGINAL: MarkShot

At the moment, the most important determinant for game performance is CPU speed and not number of processors.

Hail thee [:)]
Speed? ... *cough* Not trying to be a smart ass, but I told you, hehe, 'member?

Sorry to hear that about that darn attack. How old are you, if you don't mind me asking?

[MarkShot]

Goodguy,

However, although at the time I could have gotten the 3.2Ghz dual processors instead of 2.9GHz quad processor, my quad is overclocked to 3.2GHz anyway. It turns out to be more than fast enough for anything I am playing. Mainly, I was gambling that someday in the future have four processors will be significantly better than two. So, I sacrificed maybe 10% actual clock speed improvement for a 200% threading potential improvement. Only time will tell if I gambled wisely.

I am 48. I had the heart attack and was discharged after two weeks hospitalization. Right after that I started work on the COTA Mini-Guide. Panther Games Beta Testers are not entitled to any sick leave. Given my health maybe it is time to find a new line of work.

[MarkShot]

Bump - map layers being grabable with the mouse still appear in v1.01.

[alexs]

Hi Mark,
I read this thread and assumed the only problem here to be the incorrect saving of zoom ratios. I've tested the issue, and yes if you set your zoom ratios to astronomical values, you'll have a problem. As far as i've read, Win32 apps can only allocate up to 2gb for each process, and depending on screen size and zoom ratios chosen etc, you are probably hitting that limit.

[MarkShot]

So, 6X at 1600x1200/16bits exceeds some internal limit. Fine, perhaps should prevent users from entering invalid combinations into the options. Thanks.