Fora

Hmmm sorry, I didn't see that I was on the english forum, I found this thread via google ^^

I searched a little and found the LoL-Linux-Tools-master directory.
I then launched the lol_linux.py script manually in a terminal, and it worked.
All items in the shop now have an icon.

So it seems that your script failed to launch lol_linux.py by itself.

Do you have xterm installed?

Yes.

Then I don't know.

Ok, it seems xterm and x-terminal-emulator can only be used interchangeably (like $POL_TERM would like you to believe) in specific cases.
Namely, xterm -e runs the remaining of the command line inside the terminal, whereas x-terminal-emulator -e runs the next argument with a shell in the terminal. To get the same thing as xterm -e you must use x-terminal-emulator -x...
So I decided not to depend on such differences, and create a temporary shell script that I just start in the terminal...
I hope this will fix those discrepancies between PoL 4.1.x, PoL 4.2.x, and probably between distros too...

I understand that this should fix in-game icons, but it's also said that this fixes icons in the shop. I'm curious as to how you guys are even able to get into the shop. If I click the shop icon, all I see is a black page with nothing.

Any suggestions on purchasing items in game (ie Runes)?

It only refers to the in-game shop. The IP/RP shop doesn't need this as the icons all work. Though getting to it is another problem (black screen like you experienced). Though the only solution for that is to install ie, but that's only brought me more problems.

Derp. In-game; to be taken as literally as possible.

Whats the glt ????that has to be install

Edytowane przez lilshorty

It works without problem for me, thank you :)

hey i have a question whats glt ,that has to be installed

hi i have an other question what wine version of lol do i use theres lots of them on playonlinux ?

hi its me again sorry for being a bother but am really egar to use the in-shop to change server ..i have tryed doing the inshop fix in playonlinux but doesnt complete the procedure it just disapears i want to try the old way u used in the confi.py i have to change the "lol_path" to your League of Legends directory ,but how it looks like this,# Path to League of Legends Directory
lol_path = './'

what do i delete ,do i delete the lol_path only and put the lol directory and leave = './' alone , or do i delete lol_path = './' and then put the lol directory

My shop icons are very large, and it is therefore very difficult to buy items in the shop. The red icons I can deal with, but this really makes it hard to play.

The icons show up as a sort of ghost image superimposed over the top of the regular shop. I can't click on the giant ghost image... I have to click in the regular spot for the items, but I can't see where to click because of the giant ghost image over the top.

This DOES NOT happen in custom games, only in regular games.

@ElysMustache: got the same problem, I was wondering if that was a driver issue of something (I'm using nVidia driver 325.15 that's experimental on Debian...)

Edytowane przez petch

@ElysMustache: got the same problem, I was wondering if that was a driver issue of something (I'm using nVidia driver 325.15 that's experimental on Debian...)
[img]http://ks369561.kimsufi.com/~petchema/wine/lol/LoL%20shop%20large%20icons.jpg[/img]

I only have the huge shop icons on Howling Abyss luckily. Using Nvidia 325.08 Linux MInt 15.

I'm on Ubuntu 13.04 using the latest Nvidia 325.xx and an Nvidia GTX 570HD inside. I experience no bugs, but I ran the script manually, using 'python3.3' rather than python. I could swear I read somewhere on the dev's page that he designed his script for python3.3 but only said it "should" work on python2.x.

Petch, when you automated the script, did you set it to use python 2.x? That might be why people are running into trouble.

remember, you need to specify python3.3, or else the command 'python' will default to python 2.x

Yeah. I'm 95% sure you're ALL having this glitch cause you use python 2.7 by default.

Try again with the same script executed manually, but use "python3.3" instead of "python". It should be installed by default on most distros. It is on Ubuntu.

In the script I just used chmod +x on the Python script and ran it, so I relied on the #! line