Jump to content

PS:T problem

Guest Baum

Recommended Posts

Guest Baum

I can start a new PS:T game, but all I get is the game screen without any controls. Dialogs don't work either.


I've found this in the message output:


[GUIScript]: Loading Script MessageWindow...Traceback (most recent call last):

  File "./GUIScripts/pst\MessageWindow.py", line 36, in ?

    from GUIINV import *

  File "./GUIScripts/pst\GUIINV.py", line 26, in ?

    import string

ImportError: No module named string


Maybe the directory separators of Linux and Windows got mixed up?

Link to comment

This is a symptom of an incorrectly installed python environment.

string is a standard python module which isn't found.


Hmm, maybe the windows binary i released isn't enough?

Sucks :) You probably can fix it if you download and install the python development environment.




Go for the windows installer.


I'll try to make a better release next time which doesn't require any additional package.

Link to comment

Now that really sucks :)

Well, i guess quite few people will be able to run it.

(It runs for me, of course, but i have the development environment).

Now i have to find a clean machine and see what's wrong.

Unless someone can tell me.

Link to comment

I've just installed IWD2 and tried that, but that didn't work better:

When I try to start a new game, GemRB crashes and when I try to load a savegame it hangs after loading.

Link to comment

All games will hang sooner or later without the string library.

This is because string.py isn't on the search path.

You could try to copy the python lib contents (a bunch of .py files in C:/Python24/Lib for me.) to the gemrb guiscript root. (gemrb/guiscripts)

Link to comment

wow, thats interesting, and definitely something internal :D

I have a sre.py in the original python lib.


Ok, i think i know what's the problem. In my distribution, there is a python23.dll in the gemrb dir.

Maybe replace it with yours (which should be a python24.dll).


Yeah, i know this gets tedious :)



Aaand... that copy must be named python23.dll too...

ok, this was the last try, hehe.

Link to comment

Ok, then the problem was twofold:



1. we have to publish the python standard libraries (a bunch of py files)

2. the binary works only with python 2.3 (2.2 and 2.4 requires some handiwork).


If you installed 2.3 in the first place we could have skipped 2 extra steps :) But well, who knew that.

Link to comment


This topic is now archived and is closed to further replies.

  • Create New...