Rift Forum

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

1.2 Fails on OS X?

So I guess you guys have not seen the Facebook announcement:

Coming May 15—CrossOver Platinum. With 10 features you've never seen before with CrossOver! Press release to drop sometime tomorrow.

Maybe that will fix some issues. Please have a little patience, less hate, more love and... oh ponies!!!

exsactly the same! always error 1206 and i eventually press play and the games starts. hope CW will fix that , really enjoy playing the game

To run the selfpatchlive.exe file on a mac, go to manage bottles in the codeweaver menu and select the bottle with the rift files in it. Click the advanced option at the top and select 'open C: drive in Finder. Then go to program files, rift game, and scroll down to the bottom to find the file. This didn't work for me, but hopefully it does for you! 😊

Henry wrote:

I submitted a ticket to Rift to make them aware of the issue and
they replied with the following:The recent patch has caused problems
for some of our players. To remedy this and get you back into the
game, you will need to run the Self Patcher. To do so, simply follow
these instructions:

  1. Open the Rift folder (usually located in your C: drive)
  2. Find the file "Self Patch Live.exe"
  3. Run the Self Patcher as an administrator (right-click and select
    "run as administrator")

This should resolve your issue and get you back into playing Rift. I
have set this ticket to "waiting", so please let us know whether or
not this procedure worked for you.

I know how to do this on a PC but I'm a dummy when it comes to MAC.
I'm new to MAC and was wondering if anyone knows if this can be done
on a MAC.

One way to do it is to open up Crossover Games, then go to the top bar and click on "Programs", then in that menu, click on "Run Command..." . It should then bring up a little window letting you select a bottle (which, in this case, you should pick the one that you installed RIFT into) and another box that lets you select the command to run. Next to that box, click "Browse" and it should open up a window showing you the C drive for the bottle. From there, just nagivate to the RIFT install folder and look for the Self Patch Live.exe and double-click it to choose it. It should bring you back to the previous window; click the "Run" button and it should run it.

Hibba.

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 : )

I thought about going the "buy a PC for gaming" route, but instead bit the bullet and just got Windows 7 and installed it via boot camp instead. I asked those on the Rift forums if anybody was running RIFT on a new iMac this way, and got a reply from someone who said he does the same and plays in high graphics with no problems and good FPS. So, currently I am re-downloading the game and I'll post back here to let you now if it's doable. Would be cheaper than buying a PC. That being said, if they do not fix this issue I will request a refund myself. They are supposedly making some announcement tomorrow i take it (their announcement of their new platinum crossover) tomorrow sounds to me like an additional purchase from the sounds of it, but we shall see if we get this included or not, and whether or not it fixes these issues anyways. Sure this software has been great for a lot of people, so far I am just not one of them :)

Henry wrote:

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 : )

It looks like we got an acknowledgement that they are aware of it today. Please see the sticky thread at the top of the RIFT forums by Caron Jensen.

Hibba.

Henry wrote:

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!

yet another hotfix added today by trion...
now getting an error saying "Invalid parameters recieved"

Normally, I wouldn't steal any thunder from our Marketing Team but I believe the Rift situation is a large exception.

The announcement they will be making today is not a fix for Rift; not yet.

I probably do the exact same thing each of you do some time during the day. When a game like Rift is broken, the first thing I do is check with our developers to see if any progress came overnight. I not only read our forums, but I also read any information I can get at WineHQ and sometimes I also read information and forums in places like WineSkin (not to mention the actual forums for the game in question, in this case the Trion/Rift forums). Anywhere I can get some information that might be helpful, a lead on the problem at hand.

Yesterday, I made a formal announcement in this entry for Rift stating that we know it is broken (as pointed out in this thread by Harry Davis, thank you!). Some feel that this announcement came late, but there are some reasons I believe it came just when it should. First, the day the 1.2 patch was released for Rift had quite a few different errors coming from the Rift Client. The most interesting was that it reported 'The Region you play in is not yet updated. To continue and play, a full reinstall is necessary, start recovery now?'. Reverting to the earlier version of Rift (1.12), made it playable in-house. The theory from this error message was that the Rift Team was still in the process of patching Rift and that they were likely experiencing some trouble. We were getting this message late into the day on Tuesday.

Wednesday morning we started as we always do and found that Rift had it's first hotfix for the 1.2 patch. This hot fix introduced the error that 'Wine is an unsupported configuration' for Rift. While a little disheartening, it was also encouraging. I can go into why but I think Don's summary above explains it well. At any rate, that's when I made the announcement.

Today, there is a second hot fix for Rift. It does not get it running in Wine or CrossOver Games (we've tried both this morning, hoping that the fix would be coming from Trion seeing as how they acknowledged Wine yesterday...^_^). Our developers have been working on this problem since it started occurring on Tuesday. They have looked at preliminary log files even when we were not sure if the problem was our bug or an update problem with Rift.

I understand the frustration. I want to let each person know that we are working hard on this issue. As soon as we have something we believe works, we will let people know. The fastest way to get that news is to create a Support Ticket or send an email to info@codeweavers.com and reference bug number 8333.

I also want to express that if anyone gets to the point where they are tired of waiting, we are happy to give a refund to you for CrossOver Games; we always have been. We are not in the practice of holding onto anyone's money that is dissatisfied with our product.

Finally, we are not dropping the Silver rating on Rift just yet. This is because we are still treating it like it is a 'Silver' application... it has a bad bug that now prevents it from being played. Because it is 'Silver' we have every intention of fixing that bug. The only reason we would drop it's medal rating is if we got to a point where we believed we could not fix this bug. As far as the other existing bugs go with Rift, they are on our radar and we will continue work on them once Rift is running again.

Cheers!

kLash wrote:

yet another hotfix added today by trion...
now getting an error saying "Invalid parameters recieved"

Haha...see what I mean? Now, go have a snoop at how well that hotfix was
received by the Windows community, and you might get an idea of when, what
will happen next. That error however, I've seen numerous times stemming
from wininet.dll.so - but I don't have the game so I'm guessing wildly =)

Thanks for the update

Cheers!

Dude what you gotta realise is that previously when it wasn't working for us... (just the send report crap showing up) it WASN'T working for Windows users either.
That means it wasn't anybody's fault, the game just f*cked up.
I only said what I said to point to the fact that another hotfix has been released from Trion.

I'll admit I am really pissed that this game is no longer working on CodeWeavers. I mean I only got to play the game for 1 day... I can't partition the hard drive because the computer isn't mine, and parallels and/or Bootcamp = moar money.

But a lot of people don't understand the fact that this is a pay to play game, meaning everyday you play this game you're getting your money's worth.
What if this process takes a month? If you only played the game for 1 day out of a month which cost you 30-40 pound... you'll be upset!

I'm not gonna throw a tantrum or anything, I'm just really anxious to get back in the game, games like these I can hit level cap in like a week. But the rest of the time I'm would like to spend spec'ing my char and stuff. And I'm not saying you're not doing the same thing. I guess its just one of those situations where you're pissed cos you just got the game and you wana play it all night long and you know nothing can stop you doing so.. :P

On another note I really appreciate Codeweavers and the devs what they're doing. I'm not a software expert (i'm actually hardware) so stuff such as programming and that doesn't really fly into the knowledge side of my brain. But just by reading some of the stuff (mainly the stuff which looks like scripts & command cycles) i know a lot of effort, love, passion and hard work has been put into what I've paid for, and thats why I'm not turning a blind eye to it and asking for a refund. I admire the amount of work that was put into this, and I think if the least I can do is sit patiently and wait, and chill a bit. I'll happily do so.
So thanks a lot to those who are working on fixing this.

kLash

Maybe that will fix some issues. Please have a little patience, less hate, more love and... oh ponies!!!

ok so ... I just spent $60 buying the game rift, and another $40 to buy crossover ... and you want me to be patient for a maybe

I'd like to know if I'm out $100 or not ... I have yet to get Rift working on my mac

noah Richardson wrote:

Maybe that will fix some issues. Please have a little patience, less
hate, more love and... oh ponies!!!

ok so ... I just spent $60 buying the game rift, and another $40 to
buy crossover ... and you want me to be patient for a maybe

I'd like to know if I'm out $100 or not ... I have yet to get Rift
working on my mac

If you NOT logged in on your Rift account then you're subscription isn't activated yet. So your 30 days doesn't start ticking.
So for now you're good ;)

I can log in and I downloaded the patch ... I can log in to the game now but at the 'loading' screen it the game crashes and sends an error report at about 15%

noah Richardson wrote:

I can log in and I downloaded the patch ... I can log in to the game
now but at the 'loading' screen it the game crashes and sends an
error report at about 15%

Please, file a Support Ticket (info@codeweavers.com will get you the same effect).

51 to 66 of 66

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi02LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzMxNDM1MjAzLCJjc3JmX3Rva2VuIjoicFo3WVU4a2VtQk00Y2dOZCIsImdkcHIiOjB9