whatisthisidonteven:


1x resolution, widowed: Runs fine
2x resolution widowed: see image
fullscreen: crash


Model Name: MacBook Pro
Model Identifier: MacBookPro6,2
Processor Name: Intel Core i5
Processor Speed: 2.53 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache (per core): 256 KB
L3 Cache: 3 MB
Memory: 4 GB

I believe that the NVIDIA GeForce GT 330M card is responsible for the bizarre behaviour, but I'm not sure.

Well, seeing as how CC doesn't even touch the graphics card, I'm not sure that the graphics card would be the problem.

@Joe: Cortex doesn't use hardware accelerated graphics, but everything displayed on your screen at one time or another passes through your graphics card. This may be a problem where Cortex is sending the graphics card images in a format that it doesn't understand.

It's cuz it's a Mac.

Lol Whitty.
On subject, I'll have my macbook-pro-using friend test his for me again, but I think it worked for him already perfectly fine.
It looks like you guys have nearly the same machine, all stats but CPU are equal. He's got an i7 2.66 GHZ.
Back with results in a few hours.

OP, make sure the resolution is O.K. with your monitor. Don't force 13480725x2353453 if it only takes up to 10000x12500.

Well, I tried it again today and she works. I think it might have been an issue with a shell script I had running through geektool. Weak explanation, but the best I can think of...

What kind of script could you possibly be running that changes the behavior of your graphics that much?
Oh, and report back was positive, I could not get the issues replicated on another macbook.

It was supposed to monitor application's memory usage, but was buggy in the weirdest ways.
Anyways, can your friend go fullscreen? That still causes a crash for me.

I can't see how that shell command would interfere. I've been using geektool for battery, time, and top five processes.
On a related note, the program "XRG" does a wonderful job displaying that sort of data.

We didn't test fullscreen because we never use it, but I'll ask him to try that.
Incidentally, is your resolution in CC set to the same resolution of your monitor?
It is possible that the game is setting a resolution that your monitor does not support. You can change the preference for that in base/settings.ini, I have it set to the same width as my screen, but 20 pixels shorter (to compensate for the window's title bar and menu bar).

It crashes on fullscreen even with a fresh DL, so it's not a resolution issue.

EDIT:
ALRIGHT. DISREGARD EVERYTHING I SAID ABOUT THE SHELL SCRIPT.
I think I've got the issues pinned now, as I can reproduce it off a fresh DL.

Have your friend disable post processing and pixel glows, and run the game in 2x mode. You should get the exact same behaviour as me.
You should also be able to produce a crash by trying to run fullscreen.

Allright, I'll pass that on.
For what it's worth, I cannot duplicate this at all on my '08 Macbook Black (Core2 Duo)

Solution: don't use a mac

Har har, not a solution -Duh

lol moron thinks win32 is a better platform than unix because popular opinion says it is herp derp etc boring.

Exalion had similar graphics hilarity pissing around with his settings.ini if I recall correctly. If you caused this by trying to increase performance you'd be better off reading http://www.datarealms.com/forum/viewtop ... =4&t=14593

I just found out today that CC both doesn't use multiple cores OR graphics cards. Would CC run way faster if it did?