Thanks to people that replied to my comment. I tried what Rift
suggested to do and it still gives me the same problem. I hope
Codeweavers gets this resolved soon as I just payed for this
software 4 days ago and left feeling like I got ripped off. I might
just go buy a PC to resolve this crossover issue and ask for a
refund. You would think that Codeweavers would have Beta tested the
patch or acknowledge that there is problem with there software
working with RIft. They should drop there status from Silver to
Copper : )
Hi,
It is near impossible, here, for Codeweavers to have done anything to 'prepare' for what
has happened with Rift -- the 1.2 update was literally released overnight, and software
companies typically do not 'pre release' game patches for testing purposes to anyone, let
alone 3rd-party software providers using Wine technologies to run that software without
using Windows <grin> ... it just doesn't happen, m'kay? =) Crossover/Wine are always
playing a game of 'catch up' as it were, and when any given Windows app/game changes it's
software makeup dramatically from 'it works' to 'it no longer works', one has to play a
game of 'catch up' again and these things take time depending on the nature of the changes.
The situation with Rift, is a none too extraordinary example of what many long term users
of Crossover/Wine have seen many times before -- a new game comes out, it works in CXG but
has bugs, and Windows users have bugs as well... the game publisher releases an update to
address the bug for Windows users, and we hope these patches work in CXG as well -- some
do, some don't, and others can break the whole show for us. It becomes increasingly difficult
when more than one patch is released, or, Windows users are still experiencing problems/bugs
after the patches, which infers there are more patches to come yet... so any wine dev who
sits down to try and 'fix' whatever's wrong, is faced with an ever moving target.
With new releases especially, I always take the view that everything is extremely 'volatile'
for as long as there is unrest and complaint in the Windows user forums/fraternity of a new
game title. For as long as those folks are unhappy, you can bet you're not looking at 'the
final product' ; that might appear in 7 patches time or whenever the Windows users are all happy.
I mean, it's a bit of a grim view, but realistic none the less.
What actually -does- surprise me with Rift, is the inclusion of code to detect it's trying to
be run in a Wine based environment and inform the user of that fact ; considering the Rift coders
would've gone out of their way to include that in the latest patch, I would wonder what that
signifies. Probably a lot of people are going to scream and shout about it being 'Anti-Wine' or
such, but I'd be more likely to think "Thank you Rift coders, for letting us know you have to
take the Rift code into places unsupported by Wine currently to keep things going in Windows."
I see they've got a business to run too, and it's a new venture as such, AND you can't have
that flounder along the way ... whatever their motivations might be here, I'd rather know about
it sooner, rather than later, if for no other reason than saving others from wasting their time.
I guess, it also ups the ante on the wine devs to 'do the impossible' ... challenge.. =)
Talking about impossible ... the situation with Rift was that (the way this has all progressed)
for both Crossover and Wine, for reasons totally beyond that technology's control. There is
another example of this effect - DRM implementations. This has happened to me several times
(and again right now as it happens), wherein you're testing a win32 game that's in beta, and it
all runs perfectly up until the time of release, but -at- release some DRM mechanism is deployed
that kills the whole show - most disappointing, 'coz you know the actual game code runs fine.
Also as I say above, there are other games that have traveled this same route here, in that
patches introduced to fix Windows related problems, effectively breaks them in CXG/Wine at the
same time, due to the patches relying on features not yet present in winecore ... until they
stop patching the thing, nobody has any idea of what to fix next... for all we know, Rift may
be headed for the need of some late model .NET framework Crossover/Wine doesn't support yet...
In any event, I do know the Codeweavers devs would be looking into it ; I don't know if they've
made any progress with the problem (cause, it keeps changing) ; nor have I any idea if there's
any fix/CXG release planned to address whatever the problem is - I am, however, considerate of
this above. What I do know, is that Codeweavers has a very amicable policy regarding refunds
(especially so in instances such as this where things happen beyond anyone's control), and so
you can always rest assured that an email to info@codeweavers.com requesting a refund will be
handled in a quick and cheerful manner.
Cheers!