Rift Forum

I just found out about Crossover Games today; I installed the trial version of 10.1.2 on my mid-2011 Macbook Air and downloaded Rift.

The game starts and runs, and I can get all the way through the sign-in and character creation. But as soon as I enter the world, it renders everything, I can see my dude standing there, and then the machine's GUI is dead. The mouse moves (but keeps the Rift cursor even if I move it onto the Mac menu bar), and the screen will dim after a period of inactivity (and brighten again if you then move the mouse).

One time I was able to ssh into the machine remotely and tried to kill all the Crossover processes. This failed, they all went to state "E?" according to PS. (That's "exiting.") Even "reboot" couldn't get the machine back.

Once this happens, and it is 100% reproducible, the machine has to be power-cycled.

So far I have tried:

• The UseGLSL thing.
• The CX_LEAK_XPLUGIN_SURFACES thing.
• Running Rift in windowed mode

Rift defaults to the Low Quality renderer (LegacyRenderer = true) as soon as it starts, so everything has been done using that.

Crossover Games sounds like a great idea, and I would definitely buy it... if I could get it to work. :(

I would really appreciate any help or advice... I'm a little out of my depth here.

what type of graphics hardware have you got on your MacBook Air? GPU (and the drivers for your GPU, which are dependent on OS X version) are the primary factor in determining how well you'll be able to RIFT to work for you. The "Graphics Card Compatibility" section, here, has a bit more about that:

http://www.codeweavers.com/compatibility/browse/name/?app_id=8390;tips=1

All 2011 Macbook Airs have the exact same Intel HD 3000 graphics adapter.

I feel your linked criticism/blame of the HD 3000 unfairly (and incorrectly) lumps it into the same category as previous, less-capable Intel integrated offerings, which certainly did deserve their bad reputation.

While no barnstormer, the HD 3000 is certainly a capable enough card for this situation, as evidenced by how well Rift runs under VMware Fusion and Boot Camp on the exact same machine. That it runs decently (if slowly) under Fusion, a very conservative business-oriented full-virtualization solution not known for gaming focus or performance, seems to put the problem squarely on Crossover's doorstep.

This also doesn't really look like that type of issue, either. There is no corruption, or tearing, distorted polys, missing textures, crashes, or any of the traditional "this card can't cut it" problems. Everything renders fine and then just stops.

I'm happy to help debug the issue if I can, but if all Apple's bestselling notebook deserves is "blame the hardware" then obviously that's a waste of time.

To give more technical information about what is happening, Rift enters the world and renders the first frame (correctly), and then stops with all the behavior described earlier.

I again logged in remotely and ran it and top showed that one of the (many) wineloader processes was using ~102% CPU for a minute or two after the hang.

Here's that process while it was doing that:

$ ps axlww | fgrep 1775
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
501 1775 1 0 97 0 1882944 486504 - Rs ?? 1:15.61 /Applications/CrossOver Games.app/Contents/SharedSupport/CrossOverGames/bin/wineloader .\rift.exe -k 00000464:00000468 -l English -s 208.94.27.63:6520;208.94.27.63:6521;208.94.27.31:6520;208.94.27.31:6521;208.94.27.47:6520;208.94.27.47:6521;208.94.27.79:6520;208.94.27.79:6521

Note it is running (STAT contains R). After awhile, it appears to give up, and CPU drops to 0%, and this process effectively dies but cannot exit (STAT = ?Es):

jdw@roge:~$ ps axlww | fgrep 1775
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
501 1775 1 0 0 0 0 0 - ?Es ?? 0:00.00 (wineloader)

At this point, a power cycle is required to get the GUI back. (But the ssh sessions continue uninterrupted.)

JDW wrote:

There is no corruption, or tearing, distorted polys, missing
textures, crashes, or any of the traditional "this card can't cut
it" problems. Everything renders fine and then just stops.

Confirmed. 13" Mid-2011 MacBook Air. Can sit at character screen all day with high frame rates, as soon as I ender world it shows up, runs for 2 seconds and then crashes entire system.

This issue has been forwarded to the Official CodeWeavers Ticket System. If you have observed this issue and would like to report it as well, please open a support ticket or send an email to info@codeweavers.com with a description of what you are seeing and a link to this post.

Thank you!
The CodeWeavers Team

Has this issue been looked into? I'm running on a MacBook Pro 13" 2011 Edition with Intel HD 3000 Graphics aswell and as soon as I get into game, it crashes my entire system, everything is frozen except the mouse, my computer can obviously handle it, as of right now I play over bootcamp on windows 7 with mediumish settings. If I could get this to work on OS X Lion I would happily purchase CrossOver. Please let me know what is happening with this issue.

So is this issue going to be resolved or not? If not I will not be purchasing your product.

I'm afraid we are at the mercy of the graphics drivers for this issue, and therefore for the forseeable future it will not be possible to successfully run RIFT on a MacBook Air via Crossover Games.