[FAQ] Ryzom in Linux (The Unofficial HOW-TO)

[cloudy97]

Currently the game wont work at all in Cedega (see the last few pages in this thread) because of a code that Cedega, based on old Wine, can't handle. You would have much better luck with a recent version of Wine. I don't use ATI, so I don't know how well that works.

I believe the client was originally supposed to have a Linux client and even be open source. But that never happened, so Wine is your best option. Read Katriell's howto for a recent install procedure.

[zyrom]

The latest wine releases are bragging that the d3d support is much better, and ATI = d3d, but alas i do not own an ATI card so i can tell if Ryzom would run on top of that, would be interesting to know though.

The linux client was once mentioned in an interview with David C. the original creator of Ryzom in connection with the underlaying technology NEL that is
OpenSource, but it has gone the same way as many other intersing ideas that David had, ie nowere. Probably partly becouse the financial situation that Nevrax ended up in , and the need to concentrate its resources on more profit enhancing activities. I would not expect it to materialize "any time soon(tm)" if ever, especially taking into account the "fix" that broke the cedega compatibility and that was later fixed but never introduced into the client.

[ecobear]

Thanks for the reply, I already tried Wine, and it didn't work. Hopefully in the near future I might get lucky, but probably not for a long time. Good thing I am use to this. Thanks once again.

[cloudy97]

I upgraded my Ubuntu to the latest binary Wine from WineHQ and I get a pop up saying "Can't initialize the mouse". Any ideas what may cause it, does it mean Wine isn't compiled with OpenGL support?

My client.cfg have the "HardwareCursor = 1;" option.

[blaah]

I upgraded my Ubuntu to the latest binary Wine from WineHQ and I get a pop up saying "Can't initialize the mouse".

try running wineprefixcreate. i remember similar error one day when i played with cvs versions... or it sould be possible to wipe wine config you currently have and start fresh (PS, make sure you dont wipe drive_c directory and ryzom with it
you only need to set 2 things in wineconf. Win98 and msvcrt=native.

Any ideas what may cause it, does it mean Wine isn't compiled with OpenGL support?

that would give "Cant open window"

Thanks for the reply, I already tried Wine, and it didn't work. Hopefully in the near future I might get lucky, but probably not for a long time. Good thing I am use to this. Thanks once again.

wine version 0.9.15 (or 0.9.17) and ati binary drivers 8.26.18 should work.
whats the error message wine or ryzom gives ?

[cloudy97]

Thanks, I renamed my old .wine and that did the trick

[katriell]

SETREPEAT="50 37 64 62 109 113"
for k in $SETREPEAT; do
xset r $k
done

...Doesn't work in Ubuntu 6.10?

[zyrom]

what version of wine are you running...

as of the .17 version there has been a patch that causes trouble with that.

[katriell]

0.9.22 apparently. o_O Which I don't recall upgrading to.

[blaah]

...Doesn't work in Ubuntu 6.10?

you need to recompile wine yourself. just pull sources with "apt-get source wine", apply patch and start compiling (dpkg-buildpackage -b -uc in wine source directory).
you get nice deb packages that you can install.

ohh yeah, if you don't want all that development junk in your system, just install ubuntu to chroot directory and compile there

i could give you precompiled deb packages i think. i have them for ubuntu~6.06, but running ubuntu 6.10.
send pm and i send you link.

Code: Select all

diff -urN a/dlls/dinput/keyboard.c b/dlls/dinput/keyboard.c
--- a/dlls/dinput/keyboard.c    2006-09-28 20:35:07.000000000 +0300
+++ b/dlls/dinput/keyboard.c    2006-10-14 00:37:32.000000000 +0300
@@ -93,8 +93,8 @@
     new_diks = hook->flags & LLKHF_UP ? 0 : 0x80;
 
     /* returns now if key event already known */
-    if (new_diks == DInputKeyState[dik_code])
-        return CallNextHookEx(0, code, wparam, lparam);
+    //if (new_diks == DInputKeyState[dik_code])
+    //    return CallNextHookEx(0, code, wparam, lparam);
 
     DInputKeyState[dik_code] = new_diks;
     TRACE(" setting %02X to %02X\n", dik_code, DInputKeyState[dik_code]);