Estas Aqui > Les forums > Your creations. > [Script] Perfect World International sv ru pl en fr

Foros

[Script] Perfect World International

Nuevo tema  - Responder
Autor Respuestas
Ir a la pagina 1 - 2
Ghostofkendo Sabado 6 Junio 2009 a las 23:19 - [Citar]
Membre

Membre
Hi,

Here's a script for the free to play MMORPG Perfect World International and here are the test conditions:
Wine version: 1.1.22
Distribution: Linux Mint
Distribution Version: 7 (Gloria, 32 bits)
Graphic card: NVIDIA GeForce 8600M GT
Driver of the graphic card: 180.44
Comments:
- Applying the update patches when running the game for the first time is very long (to my mind, it's because of the server being in asia).
- I didn't need to install DirectX 9 or to change registry keys to make it work, just to install the Microsoft fonts to make the texts readable.
- I didn't manage to change the key bindings (it could be problematic for non-qwerty keymaps).

Please test this script and tell me if it worked or not, I'll modify it if necessary.
When there will be positive test results, I'll be able to validate it and it will be officially available in POL.

EDIT: Since displaying the code of the script here was distorting the forum, I removed it. You can find it HERE instead. (the file's encoding is UTF-8)

Editado por: Ghostofkendo


Ghost of Kendo (GoK): You can't spell EVIL without vi
NSLW Domingo 7 Junio 2009 a las 12:43 - [Citar]
Membre

Membre
Hello,
i've got a question:
Do this work?
if [ "$APP_ANSWER" = "FALSE" ]; then
I mean: shouldn't there be double "=" so it would looks like
if [ "$APP_ANSWER" == "FALSE" ]; then
Ghostofkendo Domingo 7 Junio 2009 a las 19:48 - [Citar]
Membre

Membre

Citation de NSLW:

Do this work?
if [ "$APP_ANSWER" = "FALSE" ]; then
I mean: shouldn't there be double "=" so it would looks like
if [ "$APP_ANSWER" == "FALSE" ]; then
Yes, it also works with only one "=" character.
Moreover, using only one "=" seems to be the usual way of doing a test in Bash because all the Bash programming guides I found show examples of tests with one "=" (like this famous guide).

Bye

Ghost of Kendo (GoK): You can't spell EVIL without vi
NSLW Domingo 7 Junio 2009 a las 20:07 - [Citar]
Membre

Membre
Ok. Thanks for an answer, but i've got another question:
Would your script work on e.g. Jojonintendo's Linux? I mean this part of your script

POL_SetupWindow_make_shortcut "$GAME_PREFIX" "Program Files/Perfect World Entertainment/Perfect World International/patcher" "patcher.exe" "" "$GAME_NAME" "" ""

You assumed everyone on the world has got Program Files but it's not a fact. I suggest to look how i did it here

Editado por: NSLW

Ghostofkendo Domingo 7 Junio 2009 a las 20:44 - [Citar]
Membre

Membre

Citation de NSLW:

Ok. Thanks for an answer
Your welcome

Citation de NSLW:

Would your script work on e.g. Jojonintendo's Linux? I mean this part of your script

POL_SetupWindow_make_shortcut "$GAME_PREFIX" "Program Files/Perfect World Entertainment/Perfect World International/patcher" "patcher.exe" "" "$GAME_NAME" "" ""

You assumed everyone on the world has got Program Files but it's not a fact. I suggest to look how i did it here
My turn now to thank you for this very useful tip
However, before it edit the script to add this, I've got a question too:
The following line works great
PROGRAMFILES=`wine cmd /c echo "%ProgramFiles%"`
but the next one doesn't. For me, the PROGRAMFILES variable contains "e cmd /c echo "%ProgramFiles%"" instead of "Program Files" after running
PROGRAMFILES=${PROGRAMFILES:3}
Is it normal?

Bye

PS: By the way, I didn't notice until now that you've made a script for CATIA, I'm very impressed. Does it run well?

Ghost of Kendo (GoK): You can't spell EVIL without vi
NSLW Domingo 7 Junio 2009 a las 21:11 - [Citar]
Membre

Membre

Citation de Ghostofkendo:

My turn now to thank you for this very useful tip

You're also welcome

Citation de Ghostofkendo:


The following line works great
PROGRAMFILES=`wine cmd /c echo "%ProgramFiles%"`
So this line gives you
wine cmd /c echo "%ProgramFiles%"
and it should give you
C:/Program Files
(there should be backslash instead of slash)

Citation de Ghostofkendo:

For me, the PROGRAMFILES variable contains "e cmd /c echo "%ProgramFiles%"" instead of "Program Files" after running
PROGRAMFILES=${PROGRAMFILES:3}
Is it normal?

No it's not normal it should give you
Program Files

Are you sure you tested it carefully. It works for me you can see similar example here(10.5) They also using such quotes ' <- here is quote sign. Without them you would get such output as you posted

Maybe it's because of bash version. I use
GNU bash, version 3.2.39(1)-release

Citation de Ghostofkendo:

PS: By the way, I didn't notice until now that you've made a script for CATIA, I'm very impressed. Does it run well?


Yes it does run quite well. I didn't made any news because I think there aren't many peoples interested.
Ghostofkendo Lunes 8 Junio 2009 a las 11:45 - [Citar]
Membre

Membre

Citation de NSLW:

Are you sure you tested it carefully. It works for me you can see similar example here(10.5) They also using such quotes ' <- here is quote sign. Without them you would get such output as you posted
You are right, I didn't read carefully enough: I used simple quote characters ( ' ) instead of grave accent characters ( ` )

Now that it works, I updated the script

Ghost of Kendo (GoK): You can't spell EVIL without vi
Jojonintendo Lunes 8 Junio 2009 a las 14:16 - [Citar]
Membre

Membre
What happened with me ?
I do have the "Program File" directory , but sure it is useful to correct it for other users.

Thanks again for the srcipt, for now on it worked on my PC, but not on my laptop... I think my ATI GPU is the problem.
Ghostofkendo Lunes 8 Junio 2009 a las 14:21 - [Citar]
Membre

Membre
Thank you Jojonintendo for the report.

Citation de Jojonintendo:

Thanks again for the srcipt, for now on it worked on my PC, but not on my laptop... I think my ATI GPU is the problem.
Could you give more details about the issue with your laptop please?

Ghost of Kendo (GoK): You can't spell EVIL without vi
Jojonintendo Lunes 8 Junio 2009 a las 21:25 - [Citar]
Membre

Membre
Well, the update worked nice. The problem started when creating a character. It was displayed good, but with a strange bug that made the head of the character very long (out of the screen). And when I try to connect, it just doesn't work at all, it gets frozen and nothing more. I tried to use DirectX, but it is exactly the same.
Ghostofkendo Lunes 8 Junio 2009 a las 22:57 - [Citar]
Membre

Membre
Ok, so could you try to assign Wine 1.1.5 to PW to see if it solves your bug.

If not, assign back Wine 1.1.22 and do the registry changes indicated in this page, after the video.

Finally, if nothing above improved PW's behaviour, try to install DirectX 9 with winetricks (via NSLW's POL Helper).

Ghost of Kendo (GoK): You can't spell EVIL without vi
NSLW Martes 9 Junio 2009 a las 7:47 - [Citar]
Membre

Membre

Citation de Ghostofkendo:

try to install DirectX 9 with winetricks (via NSLW's POL Helper).

Thanks for advising my plugin but it's not required to do DirectX 9 installation.
I rewrote script for installing DirectX it's called DirectX End-User Runtimes and it is in Other section and i advise to use this, because you can choose which version of DirectX user wishes to install.
Jojonintendo Martes 9 Junio 2009 a las 14:03 - [Citar]
Membre

Membre
Hi again,

I tried to apply Wine 1.1.5, but I couldn't see the mouse, and the game got frozen just after. I tried with Wine 1.1.22 and the registry changes, but the problem is the same (i finally could take a shot):

Now NSLW I'll try your installation script of DirectX, and report back

Edit: I have a problem when installing DirectX, after the install is finished, I press the contunue button, and nothing happens... So I kill the process, and then POL gives me an error, and recommends me to retry the installation :-/

Editado por: Jojonintendo

NSLW Martes 9 Junio 2009 a las 15:45 - [Citar]
Membre

Membre

Citation de Jojonintendo:

POL gives me an error, and recommends me to retry the installation :-/

Your DirectX didn't download successfully and i didn't add force option for removal of this corrupted DirectX Anyhow delete anything that has directx in it in "~/.winetrickscache" directory and try again.
Jojonintendo Martes 9 Junio 2009 a las 16:20 - [Citar]
Membre

Membre
Actually, there is nothing in the ~/.winetrickscache directory. I'll try to install some other version of DirectX.
NSLW Martes 9 Junio 2009 a las 16:29 - [Citar]
Membre

Membre

Citation de Jojonintendo:

Edit: I have a problem when installing DirectX, after the install is finished


Citation de Jojonintendo:

there is nothing in the ~/.winetrickscache directory


These two sentences are contradiction. If you finished DirectX installation then DirectX was downloaded to "~/.winetrickscache" and started from there. Script doesn't delete this file so you don't have to download it twice. What message do you get exactly?
Jojonintendo Martes 9 Junio 2009 a las 17:49 - [Citar]
Membre

Membre
I think a shot is the best way to explain it well . I thought it was installed, but as you say, it's impossible... I get this and then the window won't quit:

So it seems to be installed, but as nothing happens, I kill the process, and then there is nothing in the directory (there is one directx thing only during the installation).

Editado por: Jojonintendo

NSLW Martes 9 Junio 2009 a las 17:56 - [Citar]
Membre

Membre
This script fired up DirectX installation. Now you have to click Suivant to continue directx installation.
Jojonintendo Martes 9 Junio 2009 a las 18:03 - [Citar]
Membre

Membre
That is just the problem ^^. I press Suivant and nothing happens at all.
NSLW Martes 9 Junio 2009 a las 18:17 - [Citar]
Membre

Membre

Citation de Jojonintendo:

That is just the problem ^^. I press Suivant and nothing happens at all.

I understand now
It's may be because your default Wine is 1.0.1 (installed in OS) and this version may have problems with DirectX installing. The solution would be to use earlier DirectX or to use newer Wine to do so set "1.1.23" value "Default Wine Version to run wine programs with PlayOnLinux" in Settings->Environment
Il n'y a rien à voir ici