CuppaManga

You can use VMWare with Boot Camp, it'll handle modifying it for you.

I currently use VMWare for that, but I haven't tried it with Crossover Games 10 yet.

I'm attempting to gather as much information as possible on Mac clients that crash very frequently, in an effort to hopefully find some kind of pattern. At the very least, maybe it'll help Support and the Devs too. After you post, make sure you also send a Support request at help.ncsoft.com, because they have a tracking database.

When you reply, mention what kind of crashes you get, when they happen, and also the model of your Mac, how much RAM it has, which type of video it has, and whether you're running Snow Leopard (10.6) or Leopard (10.5).

I'm going to try again to build a pattern of Macs that are crashing in an effort to fix as many of these problems at once (or at least help the devs and support track it down). While I do that, make sure to send a Support request at help.ncsoft.com so they can keep parallel tracking of all this.

I'm going to try again to build a pattern of Macs that are crashing in an effort to fix as many of these problems at once (or at least help the devs and support track it down). While I do that, make sure to send a Support request at help.ncsoft.com so they can keep parallel tracking of all this.

The issue you're describing is a Patch Server issue caused by the upcoming patch being published too early on some PS's. They'll fix it eventually.

It's the Geometry Buffers setting - turn it off.

How is it screwed up?

The guides in my signature have some tips for making the game client a little more stable, including turning off Geometry Buffers. Otherwise, what model of Mac are you using?

Hit-and-run posts are always fun.

A warning for the benefit of everyone else, though:

I have a Macbook Pro, but I also built my own gaming PC. It's a *lot* of work, and while assembly really isn't that difficult you have to know what you're doing, be unafraid, and also know the quality of the parts you're ordering. Even I don't know that last one for sure - I find out by asking around. And even then, I sometimes have to deal with epic hardware failures on the PC. The point is, it's very easy for your custom gaming rig to turn into a nightmare; you can't just throw parts into a box and achieve perfection. In fact, it's getting harder to build a decent PC yourself due to established component makers switching to cheaper manufacturing methods that sacrifice quality and reliability to become more price competitive.

This is why I say prices are *comparable* between PC and Mac for gaming. Most people don't bother with all that, they let the brand-names do the assembly and reliability testing, and get a nice warranty with the purchase. I prefer Apple computers because they've proven, in my case, to be reliable and have very good warranty/service coverage. And they have to be, because every tiny failure by Apple is broadcast on every news outlet in the world for weeks. So you as a customer may as well take advantage of that.

That said, I don't want to tell people what to like. If you're comfortable with one particular platform, stick with it. If you like to build your own PC, have fun. I only know what I like, and I don't mind helping anyone who's willing to give it a try.

I'm not with Paragon but I can offer some somewhat handy advice to slow the crashes to a bare minimum (I don't have any crashes, but I also have an nVidia-based Mac, most of the crashes seem to be with ATI).

First, though, you'll need to tell me which Mac model/year you're using and which video type and model you have. Then turn off Geometry Buffers, Ambient Occlusion, and FSAA (they aggravate the problem), and then turn World Detail and Character Detail to no higher than 100%.

And then run a simple little test:

Create a new user on your Mac (set it as an Administrative user). Log in, and then try playing CoH for a bit. See if it crashes about the same or less often. This will tell me if you have anything loaded into memory that might be causing problems with CoH.

Lastly, next time it does crash during the above test, copy and paste the last 10 lines of Console (Applications > Utilities > Console) into a reply here.

Which contact gives that one?

If I knew the mission name and contact I'd try it myself and see if it crashes on both platforms.

If it happens twice with the same mission, there might be something wrong with it not related to the Mac client. Which mission was it?

Don't know yet, only the devs know.

Also check ebay - your existing Mac might be worth something, you might get some of the money you spent on the new one back.

The processor isn't upgradable, but the video is - so you're better off getting the most powerful processor you can.

First I should say processors became really complicated at some point. There's a balance of multiple cores (Quad Core or Dual Core) and rated speed.

The "i" series (i3, i5, i7) processors are focused for consumer desktops - so they're focused on power efficiency via variable speeds. That means they don't run at the full rated speed all the time. They come in Quad-Core (4 processors in one) and Dual Core (2 processors in one) - the dual-core seems to be rated at a higher speed, but they perform about the same.

Xenon is server/workhorse focused model, which runs at full speed nearly all the time, power requirements are less relevant. I've only seen Quad-Core models of these, so the speeds can be compared directly with each other.

Probably a slower rated Xenon would outrun a speedier Core i5 but it's hard to tell, and it would probably be very close.

Check the "Special Deals" section of store.apple.com - you'll see refurbished Mac Pros there pretty often. You might be able to compromise that way and get a newer model for close to the price of a previous generation one.

Latest build is v1.0.4462, currently up for download from your PlayNC account page. I can't say for sure if it'll work better, but it might.

I see what you did - you made a COPY of the application instead of an Alias. The desktop icon should have a black curved arrow in the lower left corner if it's an Alias - otherwise it's a copy.

The CoH files within the package should behave identically to the Windows version. I haven't tried editing the quick menu so I don't know why it didn't work.

I've already tracked down the cause of that kernel panic - fortunately it's very rare. It's caused by a runaway memory allocation that doesn't stop in response to errors, which eventually uses up all the memory handles and triggers a panic.

The only part I haven't figured out yet is what exactly triggers it.

There seems to be quite a few instability issues with CoH in general and ATI video (there are problems on the Windows version too).