Flash, corrupt, crash!

CLUE: are you running windowed or full-screen? I would get the black screen or similar when full-screen and, like you, be forced to reboot to get the computer back. If you run it windowed, it's still going to crash, but you won't be locked up anymore.

I've since given up and am playing on my XP partition until my subscription runs out again.

Currently, my version is 1.0.4296; this is the install off the Going Rogue DVD. Crashing happens the same as it ALWAYS has. However, this same thing happened with version 1.0.3068, and the test client I installed was 1.0.3069, and I know that the last download install I had was more recent than that, probably 4000-something.

I think the version number is a red herring, quite honestly.

When I was able to get on and play I would run the game full screen. I also would pop out of full screen mode and play in window mode to see who is on ventrilo, check website for badges, etc...

Additionally, Nunix, did you try throwing out the preferences (Users > yourname > Library > Preferences > City of Heroes Preferences) yet?

If you're upgrading from an older version the cache in the preferences might still be corrupted (bad feature set).

Yes, cleared out everything even remotely related to COH on the drive between installs. Did a full power cycle.

I run CoH 1.0.4465, on an iMac with a 2.8GHz Intel Core 2 Duo chip and an ATI RadeonHD2600 card. As of now, the only time I've had CoH crashing was during my editing the items and/or the lighting in our SG base. Hope it helps. :-p

EDIT : My friend runs CoH 1.0.3070 on a 2.4GHz Intel Core 2 Duo iMac with the same ATI RadeonHD2600 card. He has the same item base graphic bug as I but no crashing issues yet.

None of my crashes have been quite so serious sounding as the ones you guys have described, mine will just freeze then crash after an hour or so of playing (usually sometimes I can get in a few hours of playtime before it crashes). I'll try to get my specs put up here in a few, thanks for the referral Manga!

Just had my first Assertion Failure sooooo here's my specs.

Model Name: MacBook Pro
Model Identifier: MacBookPro4,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.5 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 2 GB

Which CoH version do you have? To find out, click the application icon once and select Get Info from the Finder's File menu.

I cant find my version number, I think it may be because my game was purchased on and launches through steam.

Use Spotlight to find it - type "City of Heroes" in Spotlight and then click Show All (you don't want to click the application icon, it'll launch CoH without telling you where it is). Then use the Get Info command.

Yeah the Get Info page doesnt show anything about a version number.

Did you download CoH originally from Steam before or after Going Rogue went live?

I downloaded CoH from Steam after Going Rogue went live.

Ok, I called for support & the only thing they told me is to try running the game in safe mode.
Before I was able to play the game at 1265 x 800 or higher res but now the game will only show up in safe mode 800x600 res.
I don't understand why it was working fine before at a higher res & now only works in safe mode 2 weeks after GR went live.
If I set the res to be higher than 800x600 I'll get a black screen in window & full screen mode.

Did you see the instructions in this post?

http://boards.cityofheroes.com/showp...0&postcount=28

Thank You!! That fixed it.

Due to the number of issues in pre-4462 CoH builds I'll ask anyone who's having problems and did not already download the Going Rogue installer from your NCSoft Account page or the FTP site (ftp://client.coh.com/) to do so now.

If you have a black screen starting up the new client, throw out the preferences (Users > [yourname] > Library > Preferences > City of Heroes Preferences).

Follow the instructions in my guide (in the signature) to locate game files if you wish to save your screenshots, Mission Architect files, and Demorecords.

Soon I'll post a comprehensive list of I18 Mac client issues and that should clear up some of the mystery behind what I discovered so far.