Ryzom

Posted: **Sun Mar 04, 2007 8:30 am**

I was just comparing the client.cfg file in my Ryzom folder with yours in the Rally folder, and realised that it must have failed to copy over. Given that Ryzom seemed to patch itself okay, is patch.pl required anymore? Is this something which wine-0.9.32 finally put right?

maryen wrote:...what did you enter as your home directory?

I just hit enter to use the default directories, since I had had no success previously when trying to type in something like "ryzom", expecting that it would create a folder if there wasn't already one by that name. The error then was that the python script successfully deleted the downloaded installer, but then continued as if it was still there, "detecting" it, but bound to fall over because it plainly wasn't there anymore.

maryen wrote:
jamela wrote:So I opened rally.py and saved as "original rally.py", then deleted everything from "def yesno..." to "def install_ryzom..." and saved that. Then ran rally.py again, duh (spot another stupid mistake, hehe)
...
Installer detected, continuing ...
Looking good now
what did you change?

lol, nothing, that was my mistake

. I removed a big chunk of "original rally.py", saved it, then ran the unchanged rally.py, hehehe.

This is great, I'm gradually learning some practical linux skill. I was scratching my head for ages looking for ~/.wine in my file browser

.

Posted: **Sun Mar 04, 2007 8:55 am**

maryen wrote:http://rapidshare.com/files/19256601/Rally_v1.21.tar.gz

I made a change where the installer will detect if you already have the game installed and just patch it to run with wine. Also fixed a bunch of bugs, including the one that stopped you from downloading the game :/.

Tried your update :

Welcome to the unofficial Ryzom installer for linux, Rally!
(press enter to start installation or type "uninstall" to remove a previous Ryzom installation)
*I hit enter*
Enter the location within your home folder where the installer is or where you want it to be downloaded.
(press enter to select default)
Input:/home/jamie: P
*I hit enter*
default
Please wait, checking for installer...
No installer detected, downloading new install...

At which point I quit it.

Making a backup of my Ryzom folder now, then I'll move a ryzom installer into the "Rally v1.21" folder and try rally.py again.

Okay, I should have moved "Ryzom Installer" folder in too

. Unpacking ...

InstallShield Wizard finds a previous installation and asks if I want to Modify, Repair or Remove. Selected Modify.

I seem to get all the same problem messages as previously, down to fixme:msi:MsiGetMode 3 6, then it diverges:

Code: Select all

fixme:msi:MsiGetMode 3 6
fixme:msi:ACTION_CustomAction msidbCustomActionTypeNoImpersonate not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeNoImpersonate not handled
err:msi:remove_tracked_tempfiles failed to delete L"C:\\windows\\temp\\msif946.tmp"
err:msi:msiobj_release Invalid handle!
err:ntdll:RtlpWaitForCriticalSection section 0x110020 "heap.c: main process heap section" wait timed out in thread 0030, blocked by 001d, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x110020 "heap.c: main process heap section" wait timed out in thread 0030, blocked by 001d, retrying (60 sec)
wine: Critical section 00110020 wait failed at address 0x7ef904e0 (thread 0030), starting debugger...
err:ntdll:RtlpWaitForCriticalSection section 0x110020 "heap.c: main process heap section" wait timed out in thread 0030, blocked by 001d, retrying (60 sec)

Cancelled it. I'll try blaah's now.

Selected scripts only, like you said, and default directory. Launched from the desktop icon and the fonts look fine, checking textures integrity now. Got a curious strip of corrupted graphic across the top of the load screen, and down left hand side, which looks rather like residue from the display last time I was in Yrkanis and crashed. Maybe due to difference in window size? No big deal and I'm sure it'll go away as I get things configured.

While graphically it all looked right, I crashed out after a few seconds as before. I'll Remove and retry from fresh. Maybe later

.

Posted: **Sun Mar 04, 2007 3:55 pm**

jamela wrote:While graphically it all looked right, I crashed out after a few seconds as before. I'll Remove and retry from fresh. Maybe later .

for that crash, maybe you could try to disable / turn low items in ryzom config ? (it should work now with that mfc42.dll) or to try to get wine packages for you linux distro (if you compiled it itself from source, then it probably went to /usr/local/bin and /usr/local/lib, you should remove them then)

Posted: **Sun Mar 04, 2007 9:43 pm**

The client.cfg files which both you and maryen supplied seem to have everything disabled or set to minimum levels, from what I can tell, and I have been using those. The ubuntu specific version of wine is still 0.9.31, which was part of my confusion on Friday night, until I realised. I did try to find the previous version, but couldn't, so was very happy to follow katriell's and maryen's procedure to compile 0.9.32 from source. Do you mean that mfc42.dll supplied by your installer script might have gone into the wrong directory if I compiled wine myself?

Just logged into Silan and was able to walk around for a few seconds before it crashed. NeL debug window has cited an access violation exception every time, I think - "the thread attempted to read from or write to a virtual address for which it does not have the appropriate access". Client.log is full of "file not found" or "does not exist" warnings, but still reports a successful login before complaining that "guild name" and a few other things cannot be found. The last line, or one of the last lines, in each client.log warns "CSystemInfo::getVideoInfo : No primary display device found", and I am wondering if this might be related to the memory access violation.

Blaah, I get none of the terminal feedback when using your installation script, that I do when using maryen's - all the code I posted previously. Could this be simply because of the configuration tool type of interface you use? Could that be hiding all the same problems I see reported using maryen's python script?

Just checked /usr/local/bin and /usr/local/lib and couldn't see mfc42.dll in either directory. There's a wine folder in .../lib but no mfc42.dll there, and a number of wine files in .../bin. I'm currently working with a Ryzom installation managed by your script, blaah.

By the way, thank you all three for all your help with this

. One thing which is very obvious to me already, Ryzom launches under wine in about a third or a quarter of the time that it did under Windows

.

Posted: **Sun Mar 04, 2007 11:41 pm**

jamela wrote:Tried your update :

At which point I quit it.

Making a backup of my Ryzom folder now, then I'll move a ryzom installer into the "Rally v1.21" folder and try rally.py again.

Okay, I should have moved "Ryzom Installer" folder in too . Unpacking ...

InstallShield Wizard finds a previous installation and asks if I want to Modify, Repair or Remove. Selected Modify.

I seem to get all the same problem messages as previously, down to fixme:msi:MsiGetMode 3 6, then it diverges:
Code: Select all
fixme:msi:MsiGetMode 3 6
fixme:msi:ACTION_CustomAction msidbCustomActionTypeNoImpersonate not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeNoImpersonate not handled
err:msi:remove_tracked_tempfiles failed to delete L"C:\\windows\\temp\\msif946.tmp"
err:msi:msiobj_release Invalid handle!
err:ntdll:RtlpWaitForCriticalSection section 0x110020 "heap.c: main process heap section" wait timed out in thread 0030, blocked by 001d, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x110020 "heap.c: main process heap section" wait timed out in thread 0030, blocked by 001d, retrying (60 sec)
wine: Critical section 00110020 wait failed at address 0x7ef904e0 (thread 0030), starting debugger...
err:ntdll:RtlpWaitForCriticalSection section 0x110020 "heap.c: main process heap section" wait timed out in thread 0030, blocked by 001d, retrying (60 sec)
Cancelled it. I'll try blaah's now.

Selected scripts only, like you said, and default directory. Launched from the desktop icon and the fonts look fine, checking textures integrity now. Got a curious strip of corrupted graphic across the top of the load screen, and down left hand side, which looks rather like residue from the display last time I was in Yrkanis and crashed. Maybe due to difference in window size? No big deal and I'm sure it'll go away as I get things configured.

While graphically it all looked right, I crashed out after a few seconds as before. I'll Remove and retry from fresh. Maybe later .

I haven't made it check for the installed files till after it's checked for an installer. I'll move that up toward the beginning later, I just have to do some homework this week.

as for your mfc42.dll glitches, go into the data folder of the install script, and type 'regedit wine.reg'. that should fix the mfc42.dll problem.

Posted: **Mon Mar 05, 2007 12:22 am**

maryen wrote:...as for your mfc42.dll glitches, go into the data folder of the install script, and type 'regedit wine.reg'. that should fix the mfc42.dll problem.

Currently unwilling to try this, sorry - I just tried logging in to some of my alts, and two that happen to be in Umbra, rather than Yrkanis, seem to be absolutely stable. They dance with two left feet, admittedly, but I blame that on the fact that they don't have my remapped keys, hehe

.

Edit: Walked 50m with one character into Trench of Trials, and hung up. I'm not sure what you meant, but I found a wine.reg file in Rally v1.21 folder and issued the command you suggested.

Posted: **Mon Mar 05, 2007 3:13 am**

that's what I meant^

hopefully that fixes your problems with the game hanging.

Posted: **Mon Mar 05, 2007 7:23 pm**

jamela wrote:Blaah, I get none of the terminal feedback when using your installation script, that I do when using maryen's - all the code I posted previously.

my install script is redirecting wine mesages to log file and if setup is canceled / error (exit code not 0), it shows it. it destroys "user experience" if all that useless stuff is displayed on screen

now that you have ryzom installed and you want to see wine error messages, go to ryzom folder (~/.wine/drive_c most likely) and run "wine client_ryzom_rd.exe > /dev/null". only wine errors are showed and ryzom log is removed (ryzom specific is in log.log anyway)

The client.cfg files which both you and maryen supplied seem to have everything disabled or set to minimum levels, from what I can tell, and I have been using those.

minimum yes, but pixel/vertex shaders are still enabled (Display/Display advanced).
if ryzom_configuration_rd.exe does not run, then add/modify these to client.cfg
--
ForceDXTC = 0;
DisableVtxProgram = 1;
DisableVtxAGP = 1;
DisableTextureShdr = 1;
--

mfc42.dll (which is needed for ryzom configurator) is copied to ryzom directory by my script.
i only mentioned the /usr/local/bin, /usr/local/lib incase you compiled wine yourself and if you going back to distro package, then you should remove wine related items from there (wine stuff in there has similar creation date/time so easy to see them)

Posted: **Mon Mar 05, 2007 11:52 pm**

This looks interesting.

Posted: **Tue Mar 06, 2007 2:52 pm**

:O i was thinking about making something like that once I got better at programming!!! My dreams are crushed

Ryzom

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

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

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

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

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

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

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

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

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

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

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