CuppaManga

Yes.

Click the triangle next to the game's name (City of Heroes) and there's a Properties item at the end. Double-click that.

Are you using a non-Administrator account?

Delete the Alias in Applications first (drag it to the trash) and then drag the NCLauncher from the Desktop to Applications. After that create a new Alias of NCLauncher and drag THAT to the Desktop.

The situation is currently in Transgaming's hands (which is part of what Zwillinger said). I gave them a lot of information on what's broken, as I'm sure a lot of others may have - but the question isn't what's broken, it's where it's broken and how to fix it. Those last two steps lie entirely within Transgaming's domain.

If you're curious though:

The root cause of the crashes are because Cider is allocating video memory and forgetting to release it properly until it runs out of memory handles. It's also failing to handle that error correctly, so it freaks out and causes a massive crash. In the course of figuring this out, I also learned how to use Apple's Xcode memory debugging tools.

Because I know the root cause, I've been giving recommendations to keep memory allocations to a minimum: a) use /reloadgfx occasionally because it manually forces all that memory to release; b) set your World Detail and Character Detail to 100% or less; c) turn of Full-Screen Anti-Aliasing (FSAA); d) turn down reflection effects and shadows slightly; and e) turn off Geometry Buffers. With my own installation, it seems to keep the crashes down to maybe once or twice a night.

This root cause has nothing to do with the ATI bug that developed during the last issue release - that's due to some kind of incompatibility between the slightly newer Cider build and the newer ATI driver. I don't know why they didn't release a patch just for that - I can only assume they wish to hold it until the other bugs are fixed.

Also there's an issue with the way Cider handles the Windows swap file which causes it to be more laggy than the Windows client, and causes FSAA not to work properly.

As I said though, analyzing the problem this way doesn't solve the problem because Cider has a massive amount of code to look through, and some of it is so old it's likely nobody even remembers where this faulty code is exactly. The important part is *where* it is, and then how to fix it.

I know about the OAV's but I have yet to find them. I do have both the old and new series, both available on DVD.

That's exactly what I mean. Both Mac and iPad software are usually designed in Apple's Xcode. That environment makes it theoretically possible to have one code base and two targets (Mac and iPad). The "theoretically" part is where differences in hardware capabilities, OpenGL vs. OpenGL ES, etc come into play.

But I might. If Paragon would have made a full-fledged native Mac client instead of using Transgaming's software, I'd say *maybe* - because iPad apps are so similarly coded to Mac apps, and use the same tools (similarly, Android apps are based on Java using similar coding methods to iPad). The biggest hurdle is that OpenGL ES is a subset of the OpenGL that PC's/Macs use, and many of the graphics features CoH needs might not be available on the iPad (requiring a lot of re-coding). The second biggest hurdle, of course, is dedicating programming/testing/QA resources to it.

That's all a moot point, however, because CoH is coded using Microsoft Windows based tools, which would mean starting an entire new application nearly from scratch to support iPad or Android.

Then again, you never know what projects a couple Paragon devs have been secretly working on in that cubicle in the corner...

Until last week I thought I was the only CoH player who watched that.