Crysis Forum

Hello,
I brought your excellent Crossover Games 8 for Mac the other day. Although I understand that Crysis isn't supported, is it ever going to be?
I have tried it in the default XP and also a Vista bottle but it doesn't work. It loads absolutely fine and fast right up to the FMV of the plane flying trough the clouds then it either crashes out or hangs.
I have played Crysis fine via bootcamp using both XP Pro and a beta Windows 7 Ultimate running in 64bit.

I have a November 2008 Macbook Pro with a 2.53 Core 2 Duo, 4 Gig ram and both the 9400m graphics and the discrete 9600m GT with 512mb ram. I am running Snow Leopard latest version in full 64bit mode.

Is there anyway to get it to run? Should I try running Snow Leopard in 32 bit?

Thanks for any assistance you can give me
Mark

Hi,

As you may have seen, the database entry here for Crysis is fairly vacant;

http://www.codeweavers.com/compatibility/browse/name?app_id=3871

...however...

You can read about where Crysis is at with relation to mainstream Wine,
over at WineHQ -- a few different versions are listed;

http://appdb.winehq.org/objectManager.php?sClass=application&iId=5880

Typically speaking, as Wine matures and gets better at things, if
they can, some day any improvements may end up in crossover's port
of wine. The current incantation of COG-8.0's wine core, is circa
wine-1.1.24 or such if memory serves - some many times, things need
to get fixed in Wine first, before those changes reflect back here...
(of course, the converse is true as well...ie; improvements made here
in the crossover wine branch may end up in mainstream wine too).

Generally speaking if extra wine improvements and/or features can be
added, without breaking anything here that's currently working, it
usually happens. It appears like Crysis is one of those titles, that
is probably not working in COG/wine 'as expected'...sometimes, one just
has to wait for the wine to mature some more....hope this helps.

Cheers!

Ah I see, thanks Don. I shall keep an eye on other crossover sites as you said. I know there is the new Crossover 8.5? coming soon so that may have a bit of improvement? If not then maybe when DX10 is supported.

WineHQ is not 'another crossover site' as such ; codeweavers hosts
the WineHQ site, and are involved with supporting the Wine effort,
and use/contribute to the Wine source code...but these two sites
are essentially different individual projects.

The next crossover-games release is codenamed 'Zombie Mallard',
I don't know if that'll be referred to as crossover-games 9.0
or not...we'll have to wait and see. If that release will prove
any better at running Crysis or not, is one of those things you'll
have to try and see for yourself ultimately, but generally speaking
once a (any) title starts working with new releases on mainstream
Wine, chances are.. sooner or later... said title will start working
in crossover-games as well eventually.

Cheers!

Artist Formally Known as Dot wrote:

Hi,

As you may have seen, the database entry here for Crysis is fairly
vacant;

http://www.codeweavers.com/compatibility/browse/name?app_id=3871

...however...

You can read about where Crysis is at with relation to mainstream
Wine,
over at WineHQ -- a few different versions are listed;

http://appdb.winehq.org/objectManager.php?sClass=application&iId=5880

Typically speaking, as Wine matures and gets better at things, if

they can, some day any improvements may end up in crossover's port

of wine. The current incantation of COG-8.0's wine core, is circa
wine-1.1.24 or such if memory serves - some many times, things need

to get fixed in Wine first, before those changes reflect back
here...
(of course, the converse is true as well...ie; improvements made
here
in the crossover wine branch may end up in mainstream wine too).

Generally speaking if extra wine improvements and/or features can be

added, without breaking anything here that's currently working, it
usually happens. It appears like Crysis is one of those titles,
that
is probably not working in COG/wine 'as expected'...sometimes, one
just
has to wait for the wine to mature some more....hope this helps.

Cheers!

Hey Don, I hope you don't mind me quoting you. Having had my Crossover for a bit now, I have read a few comments on the WinHQ website. It seems that some people have come up with a couple of patches but there is no comment stating they work.
But there are some patches that have been posted to try. Is it possible to compile these patches and apply them to Crossover Games? Or is it best to just leave it and wait for the next releases of Crossover?

Mark Richards wrote:

Hey Don, I hope you don't mind me quoting you. Having had my
Crossover for a bit now, I have read a few comments on the WinHQ
website. It seems that some people have come up with a couple of
patches but there is no comment stating they work.
But there are some patches that have been posted to try. Is it
possible to compile these patches and apply them to Crossover Games?
Or is it best to just leave it and wait for the next releases of
Crossover?

Not sure if Don has seen this yet, but I'll swoop in and answer it for you.

Wine patches can be applied to CrossOver & CrossOver Games manually. But, it is not an easy task by any reckoning (did I just use that word?).

The problem is that patches to Wine are usually built on a specific version and of course apply well to that version. Usually CrossOver is behind the Wine version by 2 or more numbers. On top of that, while CrossOver is 'based' on a Wine version, it does not necessarily include all of the pieces of Wine so the piece of Wine a patch is for may or may not be present in CrossOver.

If your Wine foo is decent, you could compile Wine from the version of the patch. If that patch only affects one dll, you could pull that dll and drop it into CrossOver Games and HOPE it works. More than likely it will break other things or be unsuccessful. This is really not suggested practice and you are pretty much on your own if you decide to go down that path... this is why I say your Wine foo needs to be decent (at least decent).

It's best to wait for CrossOver Games to rev versions. If a patch works in Wine and is well written, it will more than likely be accepted. If it's accepted, it's only a matter of time before that work is pulled into CrossOver. IF there is a patch that is accepted that makes something work (or even if it's not accepted, sometimes our staff can offer the missing pieces to get patches accepted), you can always write to us (info@codeweavers.com) and ask that one of our developers take a look.

Caron Wills wrote:

Mark Richards wrote:

Hey Don, I hope you don't mind me quoting you. Having
had my Crossover for a bit now, I have read a few comments on the
WinHQ website. It seems that some people have come up with a
couple
of patches but there is no comment stating they work.
But there are some patches that have been posted to try. Is it
possible to compile these patches and apply them to Crossover
Games?
Or is it best to just leave it and wait for the next releases of
Crossover?

Not sure if Don has seen this yet, but I'll swoop in and answer it
for you.

Wine patches can be applied to CrossOver & CrossOver Games
manually. But, it is not an easy task by any reckoning (did I just
use that word?).

The all-powerful ninja swoop maneuver!! What style, what grace!!! ;)

What Caron says here is correct - technically it can be possible to apply 'out of tree'
patches, however this can be a non-trivial operation in practice, and is probably one
of those operations best undertaken with some reasonable knowledge of how the wine
source tree works, and how the various software components therein interact with each
other...ie; applying a patch to one section of wine code, may impact/break wine in
another area. Like Caron points out though, the moment you do this, you move crossover's
wine 'outside' it's known specifications, and you're on your own.

Equally, it's usually best to wait for the next Crossover Games release to appear. The
codeweavers devs know their wine code most intimately, and are those best qualified to
incorporate new wine developments and fixes. If, like Caron suggests, you can let the
codeweavers devs know about a patch or fixup which helps get a title running for you
in mainstream wine, then that is a good thing because it lets the devs know what to
look at improvement wise when working on the -next- release.

Personally, I think that approach is more beneficial than hacking wine for oneself,
because any improvements that -do- end up incorporated in crossover's wine, goes on
to help -everyone- in the crossover community, not just those versed enough to go
hacking their own wine trees...(wine trees? grape vines?...confusing 😉

Cheers!

Thanks guy's. I shall have more of a read of these patch's as they aren't a gaurnteed fix but it is the problem I am having with Crysis. It's a shame it's not got a lot of votes as people find the game boring because I love it!
I'll send an email to the address you've given once I've had a read.

Hiya, is there any update on Crysis yet? With the latest version of Crossover Games, Crysis will now run but crashes after the first intro video instead of half way through the second one.

According to WineHQ Wine 1.1.18 is still the best version for Crysis:

http://appdb.winehq.org/objectManager.php?bShowAll=true&bIsQueue=false&bIsRejected=false&sClass=version&sTitle=&sReturnTo=&iId=10107

Hi,
Right as Wine 1.2 has been launched it appears to feature MANY improvements. And someone has already got Crysis working fine!!!!

See here:
http://appdb.winehq.org/objectManager.php?sClass=application&iId=5880

So is there any chance on seeing these improvements in Crossover any tiem soon? Or can you add this new code in an update so I can play Crysis at last?

I should also mention I now have a core i7 MacBook Pro so would love to play the ganme in Mac OS even more.

The forthcoming CrossOver Games 9.1 will include Wine 1.2. We made a public beta of 9.1 available last week, which already includes Wine 1.2.

That Wine AppDB entry is a bit confusing, but CrossOver Games already includes support for the MouseWarpOverride=force_edge setting (it's already in 9.0). The other patch to force double buffering is not something we can put into CrossOver. It might fix Crysis, but it would surely break a great many other things.

I don't know what problem that's intended to solve. There might be another approach to fixing it. For example, under the registry key HKEY_CURRENT_USER/Software/Wine/AppDefaults/<whatever>.exe/Direct3D, try creating a string value named AlwaysOffscreen with the value "enable" (without the quotes). Obviously, replace "<whatever>" with the actual name of the Crysis .exe file name. (I don't know it, or I'd have put it in, myself.) You would create each key along that path that doesn't exist.

Ken Thomases wrote:

The forthcoming CrossOver Games 9.1 will include Wine 1.2. We made
a
[link=http://www.codeweavers.com/about/people/blogs/jwhite/2010/7/19/celebrating-wine-1-2-with-a-public-beta]public
beta of 9.1[/link] available last week, which already includes Wine
1.2.

That Wine AppDB entry is a bit confusing, but CrossOver Games
already includes support for the MouseWarpOverride=force_edge
setting (it's already in 9.0). The other patch to force double
buffering is not something we can put into CrossOver. It might fix
Crysis, but it would surely break a great many other things.

I don't know what problem that's intended to solve. There might be
another approach to fixing it. For example, under the registry key
HKEY_CURRENT_USER/Software/Wine/AppDefaults/<whatever>.exe/Direct3D,
try creating a string value named AlwaysOffscreen with the value
"enable" (without the quotes). Obviously, replace
"<whatever>" with the actual name of the Crysis .exe file
name. (I don't know it, or I'd have put it in, myself.) You would
create each key along that path that doesn't exist.

You are Gods!!!!! haha, just installed the beta, thanks, according to the guy who posted the information and tested Crysis the patch is for any installation or audio issues you may get. Apparently it still crashes on the beginning of a new game but it works fine from a saved game.

Hi, using your registry key and Crossover Games 9.1 beta I can now load into a game from a saved game, however, the gun sprite isn't drawn correctly and you can't spin all the way round, you have limited range of mouse movement.
Ant ideas as this is the closest I got ever.

Ken Thomases wrote:

I don't know what problem that's intended to solve.

I assume http://bugs.winehq.org/show_bug.cgi?id=18799, which is actually a regression. I'm not sure on the current status of that bug, you'd have to ask Stefan.

Any idea why the arm and gun sprites don't draw properly and why the mouse movement is limited?

The mouse movement is probably the general Wine mouse input bug, although the MouseWarpOverride option is probably meant to fix that specifically. I can't say much about the arm/gun sprites without at least a screenshot, but I imagine it'll take some debugging wined3d to fix either way.

I've taken a screen shot for you:

http://i775.photobucket.com/albums/yy37/markapolloa/crysisscreen2.jpg

That does look very broken. As a first guess I'd say something related to vertex/index buffers, but yeah we'd need to debug that, it doesn't look like something with an easy workaround I'm afraid.

Henri Verbeet wrote:

That does look very broken. As a first guess I'd say something
related to vertex/index buffers, but yeah we'd need to debug that,
it doesn't look like something with an easy workaround I'm afraid.

Any pointers to what I could try?

Not a lot, I'm afraid. The only reasonable thing I can think of is to try setting "UseGLSL" to either "enabled" or "disabled", but I don't expect it to make much of a difference.

Well, that cured the sprite problem fine, I can even delete the AlwaysOffscreen and it works fine. BUT, if I move around with the key's it's fine, when I use the mouse as soon as the mouse goes out of the window, which it does, the game crashes! grrrr, so very very very near.....

Any ideas?

Hey

if it is because the mouse is leaving the window you could try setting MouseWarpOverride to force in the registry

Instructions if you need them :D

Navigate to HKEY_CURRENT_USER/Software/Wine
Name the new key DirectInput
Right click anywhere in the area under where it says default and click new string
Name the String MouseWarpOverride then click ok then double click the new string and type force

Alex

i have not tried crysis on my mac yet if this works then i think i will :P

hmm, I tried that, made the folder both where you said and in the Crysis tree in the registry, the mouse didn't move but the saved game failed to load, it would stop after you press a key to start the game.

Should I raise a support ticket for this issue?

Mark Richards wrote:

Should I raise a support ticket for this issue?

Bump? Should I?

Mark Richards wrote:

Mark Richards wrote:

Should I raise a support ticket for this
issue?

Bump? Should I?

[/2 cents - seriously, this thread belongs in the C4 forum for crysis, I'll ask
CupCake Ninja if it's okay to get that done]

Hi Mark,

I've just read through this thread again, and I'm not so much confused as I am
certain there's more than one issue being discussed here....to the point where I'm
not even sure which part you want to bump?...<grin>...

Mouse pointer leaving window - that's must be close to winebug 6971, and if it is
that, it's still unfixed afaik and that's never going to change unless someone comes
up with a 'clean' patch, which StefanD told me had as much to do with X as it did
anything to do with wine itself or crossover -- even now over at wineHQ, crysis is
rated gold -- I've gotta agree with Ken here, that's damn misleading -- how can they
let an app get a gold when you've got to apply a couple of patches and build a non
pure wine binary?...that's loony, that's loonier than me even....{shrug}...

The other bug Henri points to http://bugs.winehq.org/show_bug.cgi?id=18799 is
possibly still unresolved as well....I'm not sure, next time I see StefanD online
I'll ask him. I very much doubt either of those patches will make it into the
crossover build tree any time soon (if at all). Ergo, your best bet currently here
to get crysis going on the Mac is to use a wine-1.2 tree with the associated 2
patches incorporated, and use that wine environment to run crysis (presuming the
9400M isn't going to freak out) and use crossover games for everything else...

Sometimes...many times indeed....some issues (or bugs) need to be resolved in the
mainstream wine tree before they can appear in the crossover wine build. Wrt the
mouse leaving emulated virtual desktop window (6971)...I need both hands and one
foot to have enough digits for the number of game I have affected by that - do
believe me, I think that bug is somewhere near nemesis level when you ask people
what bugs them most about what wine can't do yet (and that the situation itself
may be so because other things have to happen in other support libraries like
xlib or libgl first before the wine code can take advantage of extra functions
it doesn't currently have....but wants/needs)...we gnash our teeth at night,
take medication to sleep, we have nightmare of the mouse cursor leaving the main
wine window....someone should write a book about wine, bug 6971 would be a real
highlight chapter under the section 'Challenged by the Meandering Rodent'... 8)

For the now however, I would think your only resolve would be to use wine-1.2
with the patches applied (one supposes the patches don't break the osx build)
and run Crysis that way -- I've a similar situation with Juiced, wherein it
requires a patch to limit the wine core engine to only assign the win32 app
<2Gb of virtual memory -- I will never see a patch for that in any big hurry,
because it's actually a definition of -machine state- :: apparently even in
windows, if you have more than 2Gb ram installed on your motherboard, Juiced
will crash in exactly the same way it does in wine -- you have to smile about
that one though, because at least I can have a custom winebuild to run that
game and not have to physically remove ram sticks...I've even seen postings
from windows user in this regard, asking for a windows port of wine, just
so they can do the same sort of thing....go figure 8)

Now...I've only recently acquired an iMac to play with, and one of the very
first things I moved to do, was get a working wine pure environment going
under 10.6.4 (git tree, build environment, wine-1.3, some other 'nixy things
I'm used to having around in linux), and after getting some most excellent
tips and pointers from both Ninja Caron and Mac guru Ken, I found this whole
installation process to be very straight forward...more or less...almost a
doddle once these fine folks pointed me in the right direction but there were
a couple of issues (I used my linux experience to overcome them)...hmmm...

....it doesn't seem like we have a dedicated Mac-centric page here detailing
how to get wine pure up and running in OSX....I wonder if that's within bounds?
Just to get wine pure into OSX, I used Macports...see;

http://www.macports.org/install.php

I chose to install the X11 & Xcode packages as supplied by my Mac OSX install
DVD, and then use the software update tool to download the latest versions.
Once the updates are complete, then install the macports app itself. This will
give you the terminal command 'port' which you can use to install wine pure..
...the whole macport thing is pretty easy to use....imho....hmmm...I'm possibly
being a little presumptuous there aren't I?...especially when it's going to
come down to not just installing wine via macports, but actually having the
wine-1.2 source tree and patching and then configure/compile/install manually.
Maybe the port command can automate the application of patches as a prepend
to the target, I didn't check....anyhow, you'd probably be better to install
the wine-devel package at any rate (which will rope in wine-1.3) -- you would
probably need to patch that version too - the patches may no longer apply
cleanly though and/or found their way in and/or need diffing in blablabla...

...<grin>...talk about opening a can of worms...and totally OT wrt Crysis
here all things considered...but at least it clarifies the what/wheres and whys
of life...

@Mark -- if you want/need help with the macports/wine stuff, let me know

Cheers!

Hey Don

i think asking to have a mac centric page would be a great idea as i would love to know how to use terminal to install pure wine and custom patches

Alex

P.S. that is one long post :D

Alex Kornitzer wrote:

Hey Don

i think asking to have a mac centric page would be a great idea as i
would love to know how to use terminal to install pure wine and
custom patches

Alex

P.S. that is one long post :D

..."I'm not sure, I was asleep...or heavily sedated at the time..."

Hi Alex,

I think people get the wrong idea....or even become upset or disappointed...when folks
from one quarter of the wine users group say "IT WORKS!...if you compile in these patches"
and yet here we are, with arguably a more performant build of wine core in itself in/with
codeweaver's crossover products, and things don't work because it's not that simple as
getting those patches and compiling them into the >codeweavers< wine core....

As Caron and myself touch on earlier in this thread, is is possible to do this...apply
non-startdard, unapproved patches to the crossover wine source and recompile the wine
engine and/or part of it....but unless you really know what you're doing, it can be
anything less than trivial....and I think there's sort of sublime kind of innate respect
for keeping the crossover wine engine as 'pristine' as possible..."Only use factory approved
parts as supplied and fitted by our specialized engineers" idea, where as wine-devel tree
is more like "Arghhh me hearties, lets have at it with cutlass and sword!" material... 8)

Hence the long post....Mark was, imho, honestly of the belief that something could be done
about the issues with Crysis, in crossover, any time soon now....when in reality quite the
opposite is true. That said, I'd personally rather have him able to play Crysis in a modded
wine engine, that have him using bootcamp or what-have-you. Actually doing that, can be a
vertical learning curve for many users...if for now other reason than the Mac/OSX being -so-
user friendly, it's not often your average everyday Mac user even needs to ever compile any
software at all (let alone versions of same coming from the BSD/GPL licensing areas)...

,,I had a closer look at the port command (man port 8) ..it >does< have the facility to allow
one to apply patches (diff) to the source tree of a port tree about to be configured/compiled,
so "life's good" there as they say...you just gotta know what to do...

@Alex -- upon reflection, I can only see 'good' possibilities in having a blow-by-blow type
howto around to help crossover Mac users have specialized wine builds 'at their fingertips'
as it were -- us linux (and other OS) users have had that facility since day dot. The macports
way is -easier- all told from the end user's point of view...I'll PM you a copy of my notes
via email so you can try them out, let me know how they might be better etc etc..

@Mark -- if you want 'CC of those notes just post here

Cheers!

Hey Don

Thanks very much :D

Alex

Henri Verbeet wrote:

Ken Thomases wrote:

I don't know what problem that's intended to
solve.

I assume http://bugs.winehq.org/show_bug.cgi?id=18799, which is
actually a regression. I'm not sure on the current status of that
bug, you'd have to ask Stefan.

I had a chat with StefanD just now about this...quote;

<.stefand.>.. hmm, I think I concluded that this was a game bug
<.stefand.>.. accessing the data after unlock is not valid, even if you may get away with it on windows(and you may get away with it on GL)
<.stefand.>.. unfortunately GL is less forgiving here than windows is
<.stefand.>.. but considering the general reports of instability of this game I think we can say that windows isn't too forgiving either

Ergo, I think the current status of this bug is unchanged/stagnant

Cheers!