psclient (linux) and the crystal space engine

[ralph-hogaboom]

hi everybody,

this is a help request. i\'m using red hat linux 8.0 (2.4.18-14) on an AMD 1700+, 512 mb ddr ram, geforce 2 64mb ddr video card.

time of test: 7:00 am PST, saturday march 8th
psclient version 0.2.6
opengl or safe: opengl


although this is my first post, i\'ve been a lurker here on the forums for awhile. when i read that  the mb release was out, i rushed over to the sourceforge page and downloaded the linux tar.gz, unzipped it and tried to run both the psclient and the pssetup.

i type this:

[ralph@vancouver planeshift]$ ./psclient

and it gives me this:

Warning: Failed to load \'xwin\'; use \'-verbose\' argument for details.
Warning: Failed to load \'xwin\'; use \'-verbose\' argument for details.
aws-debug: Couldn\'t find iGraphics2d plugin!!
./psclient: line 43: 28584 Segmentation fault       bin/psclient $@

now, when I installed the Crystal Space 3d engine, it installed to /usr/local/crystal but i couldn\'t get any of the demo apps to work. so I also have the crystal linux executable files downloaded and installed to /usr/bin/CS. all the demo apps in there work fine.

it doesn\'t seem like planeshift is seeing my crystal space files, since it can\'t run.

what do i need to do to get psclient to see my crystal space installation? should i make a symlink to some crystal space file (and which file)?

thanks,

ralph hogaboom

[acraig]

Do you have a CRYSTAL var set? It should point to the dir that you have CS installed.

[patrickg]

I had the same problem. I had to edit the psclient and pssetup scripts that start the binaries for the client and setup, so that the CRYSTAL enviromental variable pointed to my crystal installation. I did this with a bit of doubt, becausse comments in the scripts said to make sure that I didn\'t \"collider\" with a installed crystal. And in the script whatever CRYSTAL was set to was unset, and then set to be inside the game\'s working directory. And in the lib/ subdir of the game, there ARE crystal-libraries, amongst others, xwin.so. However, changing the CRYSTAL variable to point to my systems crystal installation made the xwin error go away. And I was able to run  \"pssetup\" without problem.. \"psclient\" also seemed to work nice. I was able to create a new character, and was getting excited and ready to play.
But then it crashed. This is the error I get:
-- cut --

PreloadModels: Preloading complete
Constructing psdWarning: 0xa9cb4e8
Destructing Warning: 0xa9cb4e8
        loading definitions file /planeshift/data/custom.def...
        load successful (1 windows, 0 skins loaded.)
./psclient: line 44: 27743 Segmentation fault      bin/psclient $@

-- /cut --

I asume that this is when the first 3d graphics are to be loaded.  So probably this is becausse I altered the script to use  my systems crystal libraries instead of those which come within the planeshit-package. (I use RH80 aswell, but with selfcompiled crystal)

When I instead of creating a new character choose to \"connect\" and use the standard connect-prefs that are entered, the game seems to load. I get a loading screen and in the terminal where I started psclient I see lots of (almost) nice messages about loading. But this also crashes.. probably, this time, aswell, when it is about to show it\'s first 3d graphics..
-- cut --

Switch to FASTMESH \'(null)\'!
LOTS OF LOTS OF THESE...
Switch to FASTMESH \'(null)\'!
crystalspace.engine.warning: Couldn\'t load cached lighting for 131 object(s):
crystalspace.engine.warning:     _s_stairsides_01
crystalspace.engine.warning:     _g_barrel01c_01
crystalspace.engine.warning:     _g_barrel01c_02
crystalspace.engine.warning:     _g_barrel01c_03
crystalspace.engine.warning:     ...
crystalspace.engine.warning: Use -relight cmd option to refresh lighting.
Region hydlaa loaded successfully.
Requesting Actorslist!
HandleMessage: Received world

HandleMessage: Persist Message: CELPERSISTCMD_SEND_ENTITY

cel.persist.classic:   Reading entity 35 (\'Enigma\')...

cel.persist.classic: Adding PC \'pcmesh\' to Entity \'Enigma\'
./psclient: line 44: 28226 Segmentation fault      bin/psclient $@

-- /cut --

So using my own Crystal seems to be a bad idea as far as I can see. But how do I get ps to use the provided crystal-libraries? Or does it use them, but has some kind of problem with the xwin.so that is provided?

[ralph-hogaboom]

Andrew,

I\'ve tried setting the CRYSTAL var. I installed crystal space to /usr/local/crystal. According to the crystal space online docs, it should be as simple as typing a few lines in your terminal. but i couldn\'t get that to work, either. their example:

\"... if Crystal Space is installed in `/usr/local/CS\' the correct commands would be:

CRYSTAL=\"/usr/local/CS\"
export CRYSTAL

..\"

I also tried adding this to my .bashrc file, hoping that this would set the CRYSTAL variable when I rebooted. no such luck.

Patrick,

I might try your method of editing the psclient /pssetup files. If i do, i\'ll report back on what happened.

i\'m going to try more googling on registering the crystal environment variable, as well as look for some solid crystal space rpm\'s (yeah, yeah, but they might correctly install everything, where it seems i can\'t get planeshift to see the crystal space installation).

ralph hogaboom

[ralph-hogaboom]

patrickg,

you might be able to install the crystal entity layer (CEL) and get your modified psclient to work. to install cel, you need a working cs-config file from the crystal space source. since i\'m using the precompiled binaries, i can\'t install cel. but you could ...
 
download it from http://cel.sourceforge.net. you have to do something with remaking the cs-config file from your original crystal space source, and then copying that file and using it for making cel, but it\'s all in the readme.

good luck.

[patrickg]

Originally posted by ralph-hogaboom

CRYSTAL=\"/usr/local/CS\"
export CRYSTAL

..\"

I also tried adding this to my .bashrc file, hoping that this would set the CRYSTAL variable when I rebooted. no such luck.

Patrick,

I might try your method of editing the psclient /pssetup files. If i do, i\'ll report back on what happened.

This will never work.. becausse the script you run to start psclient does this:
-- cut --

#Make sure we don\'t collider with an installed CS or CEL
unset CEL
unset CRYSTAL

cd $MYPATH
export CEL=`pwd`
export CRYSTAL=`pwd`

-- /cut --

so whatever you have set the CRYSTAL variable to gets unset, and then set to `pwd` (which is the dir where the games resides). This is what I mentioned in my previous post, so you probably have figured this out by your own now:)

I downloaded the cel-package that you mentioned, I will try to install it now.

[ralph-hogaboom]

actually, i missed that funny, it\'s quite obvious to me now ...

i see it now. let me know how the CEL thing goes, and i\'m going to try to get crystal space working by compiling it, then try CEL. i\'ll report back on how that goes.

ralph hogaboom