Compressed textures do not work correctly with Intel driver (i945G card) on Linux. Mesa 6.5 is blacklisted but mesa 7.0 (in recent Xorg like 1.4) is not. So you will see the white rectangles instead of inventory items.

You can blacklist it:

--- data/config-plugins/gldrivers.xml   (revision 31585)
+++ data/config-plugins/gldrivers.xml   (working copy)
@@ -693,11 +693,15 @@
       * 2006-11-24: S3TC support in Intel DRI (at least in Mesa 6.5.1) is
                     broken. Since S3TC may also be used through generic
           compression formats, disable TC completely.
+      * 2008-11-18: Still broken on 7.0.4
       -->
     <rule description="Intel DRI: Disable texture compression">
       <conditions>
         <regexp string="renderer" pattern="Mesa.*Intel" />
-        <regexp string="glversion" pattern="Mesa 6\.5\.." />
+        <conditions fulfill="one">
+          <regexp string="glversion" pattern="Mesa 6\.5\.." />
+          <regexp string="glversion" pattern="Mesa 7\.0\.." />
+        </conditions>
       </conditions>
       <applicable>
         <usecfg>disableTC</usecfg>


 ARB_fragment_program is also broken on Intel, and correctly blacklisted in CS. The CS walktest is broken when it is enabled.

However, when it is disabled much stuff in PS is very black - insides of buildings, the landscape outside of cities, building shadows. In contrast, removable objects and characters remain very bright. Reenabling  ARB_fragment_program causes PS to run very slow but you can see in the outside lansdcape and in dark places.

--- data/config-plugins/gldrivers.xml   (revision 31585)
+++ data/config-plugins/gldrivers.xml   (working copy)
@@ -730,7 +734,7 @@
         <regexp string="renderer" pattern="Mesa.*Intel" />
         <conditions fulfill="one">
           <regexp string="glversion" pattern="Mesa 6\.5\.." />
-          <regexp string="glversion" pattern="Mesa 7\.0\.." />
+          <!--regexp string="glversion" pattern="Mesa 7\.0\.." /-->
         </conditions>
       </conditions>
       <applicable>


You can speed up PS by downsampling textures.

1/1  - unusable, uncompressed textures do not fit into memory
1/2 - slow
1/16 - very ugly. Reasonably fast outside and in simple non-crowded parts of cities. Complex areas are somewhat slower  - like if you see too much of DR at once.

You could possibly also gain speed by decreasing rendered distance pref somewhere or disabling shadows but I did not see any difference wrt shadows when I tried.

It looks PS would really benefit from distant object simplification like OGRE has but it's based on CS so I guess it's not gonna happen.

Intel does not do multisampling so no point in trying to turn it on.

Newer cards like GMA3000 (G33 and such) and higher should perform faster but i have no idea if the functionality problems are resolved. They might be hardware limitations (the multisampling likely is) or driver problem (most likely the textures).

Originally posted by Alos

Do you guys have any OS altering haxies?

let\'s see what cruft has accumulated here (the Others line in System Preferences):

Application Enhancer
Environment Variables
Norton Auto-Protect (not running, probably too annoying when installing software)
Norton QuickMenu
Remote Desktop
ShapeShifter (unregistered-defunct)
uControl

Perhaps I could try and install another system on an external disk to see if the errors go away.
I am sometimes quite surprised by this one

Computer type : Powerbook G4
Mac OS Version :  10.3.9
Processor : 867 GHz G4 (3.3)
RAM: 640MB DDR
Video Card : GeForce4 MX (10de:0179:00a5) 32MB

Planeshift runs (y/n): 0.3.10 yes, 0.3.11 no
Average FPS: stops when I look at Plaza
Platform-specific bugs encountered:  0.3.11 crashes on startup

one suggestion: search.
Both issues have been discussed here in a recent thread already.

How do you get a video card driver for OS X?

I have not seen one so far (except the drivers shipped with the system).

no, the pip\'s thread is about client crash, while this one is about server complaining that the client version is wrong.

This probably means that the client was not updated correctly.

It looks like nobody else is experiencing the same issue. Unless you post some more information (ie the updater log) we will probably not figure out what the problem is.

Posting several threads about the same problem will not help resolving it, nor will writing the topic in allcaps, it\'s just annoying.

However, a topic that does describe your problem may be a good start

Just check out from cvs.

There is a build guide for GNU/Linux which should work on OS X as well.

EDIT: it still crashes for me with PS from today and CS and CEL from 2005-08-12 (the Tag says it\'s actually 2005.08.11.22).

I would try to roll it forward a bit but the SF CVS currently does not work for me. It is quite unreliable lately. Perhaps next time.

Looks like the CS is still quite fragile.

*sneaks away on his tiptoes in the fear of being buried by a collapsing CrystalSpace*

Hmm, and I do not understand jam. I always thought it is good for putting on bread, not for building things with. I never know what it rebuilds and why. Is there some clear-jam jam-clean or jelly or whatever? It thinks --help is a target ..

There are many people asking about the same problem: they click the psclient application (or pssetup or anything else),and it does not start.

The application appears in dock only briefly or the dock makes space for it but the icon does not appear at all. The application does not crash, no window appears.

This usually means that the permissions on the application are wrong - it is not executable. This is related to the unix base of Mac OS X, not the shiny Aqua interface most people know.

For information how to fix the permissions see the Chaos\' thread about running PlaneShift on OS X.