Textures not displaying in Linux build of client

[TymTheEnchanter]

Hi,

I have recently downloaded the source and built everything, following the instructions in the svn/*checkout* page, seemingly OK. However I am having trouble with the client not displaying any textures.

This is a screen shot of the podium from laanx, the result is the same is I use the local server as well.

http://img.photobucket.com/albums/v253/tym_the_enchanter/psscreenshot.png

The effect in game is to display the shape and colour of everything but no textures, land is just green, rock just grey and so on.

I have modified the official client server.xml to include the localhost server and everything displays fine so there must be (not surprisingly) an issue with the version of the client that I have built.

I have been through all the output from the configure scripts in each component (cal3d, cs, cel & ps) and installed packages (normal and devel) to remove all but a couple (that look to be windows related or network related) of the no results from the checks. (I can post the results of the configure scripts (or the config.log files) if needed.

I have also replaced the art and data folders with the ones from the official client install to no effect.

Running either client (built version or official from the console gives no difference in output either.

One final test I did was to run walktest which worked perfectly as far as I can tell.

I assume that I am missing a library of two that I need but can't work out which ones?

Is any one able to help me please?

My system is:

opensuse 10.3 64bit
nvidia 169.09 drivers installed from nvidia repo
jam: Boost.Jam  Version 3.1.14. OS=LINUX.
gcc: (GCC) 4.2.1 (SUSE Linux)

[Caarrie]

looks like a driver issue, try updating your drives and make sure you have direct rendering enabled

[Vornne]

Hmm, also try downgrading your drivers, as 169.** caused a few problems for me, so I reverted - though not the problem you have there, which I have never seen.

gentoo linux amd64
nvidia-drivers 100.14.19
gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2)
nvidia-cg-toolkit 1.5.0

[TymTheEnchanter]

The drivers are the latest and

> glxinfo | grep direct
direct rendering: yes

so that shouldn't be a problem.

And as I mentioned, the official client works fine. Wouldn't a driver problem would cause both to have the same issue?

I'll try to rebuild everything again and play around with different versions of the nvidia drivers.

Cheers

[Caarrie]

are you sure the openGL libs are installed? and that they were found when you built?

[TymTheEnchanter]

Pretty sure, which configure check(s) would indicate this.

I have managed to reduce the number of no results for all four components to about the minimum I think and don't remember seeing any failures from the openGL output.

[Caarrie]

Pretty sure, which configure check(s) would indicate this.

they will only tell you if you read and look for them and it will not stop the build from completing.

[TymTheEnchanter]

they will only tell you if you read and look for them and it will not stop the build from completing.

I've already read through the configure output for each of the components (and the config.log as well) checking for failed options. I'll check again for any 'no' results in the configure output paying extra special attention to anything openGL related but was wondering which were the specific checks to look out for (although I guess they should be fairly obvious as they will usually contain GL somewhere ).

I'll try this evening (still at work) and post some results later.

Thanks

[pcrow]

I have the same problem, only using the ebuilds for Gentoo.  It worked when I first installed it, but I had other problems, so I reinstalled several times, and I've upgraded lots of other things.  Now I get no textures.  I have direct rendering turned on.  I'm using nvidia drivers, both 169.09 and 169.07.

[Vornne]

Could someone with 64 bit linux confirm if it works when building from source, using the art from the binary 020 release, and using nvidia drivers previous to 169.*, for example 100.14.19? I suspect there is a mistake in the art download for the ebuilds, or the newer drivers cause the problem.

[pcrow]

I downgraded to 100.14.23 drivers, and it didn't help.

I hadn't thought about the 64-bit issue.  I am running in 64-bit mode.

[TymTheEnchanter]

Well, I checked everything again last night and installed Blender as it was missing from the cal3d configure output. Then I cleaned each component (make/jam clean) and rebuilt each one. The PlaneShift source I downloaded clean from SVN and built.

And Lo! I have textures rendering fine.

I think my problem was that I had built a number of times before, without properly reading the configure output and didn't clean in between builds. DOH!

But... I have now lost all my gui elements. However as this is most likely a simple configuration issue, and the gui was fine when I had my original problem, I'm not too worried.

I'll poke around some more this evening and see if I can get everything to build and work as intended, but I feel I am basically there now.

If I get a bit of time I'll also look at which configure checks are real show stoppers for this (all the openGL, Cg and the like and as many others as I can track down) and try to modify the configure scripts to either exit if a dependency is missing (the way most others do) or to display some output at the end to inform the user they may have problems.

[Caarrie]

check in pssetup what skin you have, dont use cvs skin as it is not a working skin and imo should just be removed from svn.

[TymTheEnchanter]

I thought I had, Ive made that mistake before.

Changed it again and voila everything works fine, even able to run around the Hydlaa dungeon.

Thanks for the help, can now start the actual dev work

Haven't tested a build with the older nvidia drivers yet, will see about that this week, but Vornne, can now confirm that everything works with the following

opensuse 10.3 64bit
nvidia 169.09 drivers installed from nvidia repo
jam: Boost.Jam  Version 3.1.14.
gcc: (GCC) 4.2.1
cg 1.5

[Vornne]

Thanks

Don't worry about testing with the older nvidia drivers, it's obviously not that... just a hunch I had.