Problem with fragmented text on forward view

[Kaks]

Really? acmesediver, I've no idea how you manage to uninstall it by shutting down, you must have a very special system.

Have you got linux actually installed on your system, or are you running it off an install CD?

Or is it a college/work computer that you're using in your free time?

[acmesediver]

It is my personal laptop, installed Ubuntu Lucid Lynx last month off install CD, running fine. I am just going to go back to the original Oolite via the software directory and muddle through without the com logs I guess.

[Micha]

Didn't someone else complain that their Oolite was 'uninstalled' after they rebooted? Hmm, can't find the thread now.

As far as I recall it was an issue with the menu - the actual oolite installation was still there. Try opening a Terminal and running "oolite" from a shell prompt.

Using Oolite from the Lucid repository will yield no ends of problems - firstly it is 1.65 which is hideously outdated, and secondly it will use your system gnustep-base library, which is at version 1.19.3 and broken. You will encounter issues with this, such as not being able to load your savegame.

Also, you might want to run through the compatibility test suite for graphics cards (linked in the test-release announcement for Oolite 1.74), if you haven't already, and report the results back to us. It may assist further.

[Getafix]

@acmesediver
It would be useful to do the following:

Could you post the output of the following?

Code: Select all

$ which oolite
$ which oolite-trunk

and

Code: Select all

$ cd /
$ find . -name [Oo]olite* -print 2>> /dev/null

[acmesediver]

So, I was able to run oolite from the terminal, and it loaded 1.73.4.- Yea.
Far better game than 1.65. Yea!
No flashing graphics- Yea.
Fragmented Text problem still exists- Boo!!
I am looking for the graphic card stuff yet.

Terminal response below. Thanks to all for your help: May your thargoids be slow and poor shots.

mace@mace-laptop:/$ which oolite
/usr/bin/oolite
mace@mace-laptop:/$ which oolite-trunk
mace@mace-laptop:/$ cd /
mace@mace-laptop:/$ find . -name [Oo]olite* -print 2>> /dev/null
./usr/share/linda/overrides/oolite-data
./usr/share/pixmaps/oolite-icon.png
./usr/share/doc/oolite-data
./usr/share/icons/oolite-icon.png
./usr/share/lintian/overrides/oolite-data
./usr/share/app-install/desktop/oolite.desktop
./usr/bin/oolite
./usr/bin/oolite-update
./usr/lib/GNUstep/System/Applications/oolite.app
./usr/lib/GNUstep/System/Applications/oolite.app/Contents/Resources/Music/OoliteTheme.ogg
./usr/lib/GNUstep/System/Applications/oolite.app/Contents/Resources/oolite-icon.icns
./usr/lib/GNUstep/System/Applications/oolite.app/Contents/Resources/Textures/oolite-expansion-document.png
./usr/lib/GNUstep/System/Applications/oolite.app/Contents/Resources/Textures/oolite-document.png
./usr/lib/GNUstep/System/Applications/oolite.app/Contents/Resources/Textures/oolite-logo1.png
./usr/lib/GNUstep/System/Applications/oolite.app/Contents/Resources/Textures/oolite-logo.png
./usr/lib/GNUstep/System/Applications/oolite.app/Contents/Resources/oolite-expansion-document.icns
./usr/lib/GNUstep/System/Applications/oolite.app/Contents/Resources/oolite-document.icns
./usr/lib/Oolite
./usr/lib/Oolite/doc/OoliteReadMe.pdf
./usr/lib/Oolite/doc/OoliteRS.pdf
./usr/lib/Oolite/oolite.app
./usr/lib/Oolite/oolite.app/oolite
./usr/lib/Oolite/oolite.app/Resources/Music/OoliteTheme.ogg
./usr/lib/Oolite/oolite.app/Resources/AIs/oolite-constrictor-AI.plist
./usr/lib/Oolite/oolite.app/Resources/Shaders/oolite-default-shader.fragment
./usr/lib/Oolite/oolite.app/Resources/Shaders/oolite-standard-vertex.vertex
./usr/lib/Oolite/oolite.app/Resources/Shaders/oolite-tangent-space-vertex.vertex
./usr/lib/Oolite/oolite.app/Resources/Config/oolite-javascript-errors.plist
./usr/lib/Oolite/oolite.app/Resources/Config/oolite-font.plist
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-cloaking-device-pod.js
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-global-prefix.js
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-constrictor-hunt-mission.js
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-cloaking-device-mission.js
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-default-ship-script.js
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-nova-mission.js
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-thargoid-warship.js
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-cloaking-device-target-ship.js
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-constrictor.js
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-trumbles-mission.js
./usr/lib/Oolite/oolite.app/Resources/Scripts/oolite-thargoid-plans-mission.js
./usr/lib/Oolite/oolite.app/Resources/oolite-icon.icns
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-font.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-nebula-3.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-barrel-specular.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-ball-turret.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-scarred-metal-specular.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-star-1.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-nebula-2.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-expansion-document.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-nebula-1.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-document.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-logo1.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-logo.png
./usr/lib/Oolite/oolite.app/Resources/Textures/oolite-nebula-4.png
./usr/lib/Oolite/oolite.app/Resources/oolite-expansion-document.icns
./usr/lib/Oolite/oolite.app/Resources/oolite-document.icns
./usr/lib/Oolite/oolite.app/Resources/Models/oolite-ball-turret.dat
./usr/lib/Oolite/oolite.app/Resources/Models/oolite-unknown-ship.dat
./usr/lib/Oolite/oolite-deps
./home/mace/oolite-saves
./home/mace/Downloads/oolite-1.73.4-test.x86.package
./home/mace/GNUstep/Library/Caches/Oolite-cache.plist
./home/mace/oolite-1.73.4-test.x86(2).package
./home/mace/.local/share/Trash/files/oolite-1.73.4-test.x86.package
./home/mace/.local/share/Trash/info/oolite-1.73.4-test.x86.package.trashinfo
./home/mace/Documents/OoliteRS.pdf
./home/mace/Documents/Oolite 1.65 ReadMe.pdf
./var/packages/oolite-1.73.4-test
./var/packages/oolite
./var/packages/@oolite-linux.berlios.de/oolite:1.73.4-test
./var/packages/@oolite-linux.berlios.de/oolite:1.73.4-test/backup/usr/lib/Oolite
./var/packages/@oolite-linux.berlios.de/oolite:1.73.4-test/backup/usr/lib/Oolite/oolite.app
./var/packages/@oolite-linux.berlios.de/oolite:1.73.4-test/backup/usr/lib/Oolite/oolite.app/oolite
./var/cache/apt/archives/oolite-data_1.65-2_all.deb
./var/cache/apt/archives/oolite_1.65-6build2_i386.deb
./var/lib/dpkg/info/oolite-data.md5sums
./var/lib/dpkg/info/oolite-data.list

[Micha]

Ok, it looks like you have both an autopackaged version of Oolite installed as well as an Ubuntu packaged one.

In a Terminal:

Code: Select all

sudo apt-get remove oolite oolite-data
sudo apt-get autoremove
sudo apt-get autoclean

Also, 1.74 has been released.. 1.73.4 is now an out-of-date test release, so you might want to grab the new autopackage and upgrade to that.

[Getafix]

@acmesediver
It still seems that the main issue is grafix drivers, though.

[Getafix]

@acmesediver
Please, try the following:
Backup the .GNUstepDefaults file

Code: Select all

$ cd ~/GNUstep/Defaults
$ cp -p .GNUstepDefaults .GNUstepDefaults.original

then, with your favorite editor alter .GNUstepDefaults where

Code: Select all

	"shader-mode" = <*I3>;

(the value can be I2 instead of I3) to display

Code: Select all

	"shader-mode" = <*I1>;

Save the changes and exit the editor. This should disable shaders for oolite.
Execute, oolite again and tell us if that changes, by any means, the behavior.

[acmesediver]

Micha- I did what you recommended, but have not upgraded to 1.74 yet- still getting used to this linux thing.

Getafix- What do you mean by "My favorite editor"? I backed up the GNUstepDefaults file, (Whatever the heck that is... ) and did a file search for GNUstepDefaults, found a file named that, which contained two folders- Library and defaults. Defaults was empty, Library held a Cache folder, which only had Oolite-cache.plist. I could only open with a word processor, and had 1500 some odd pages.

[Getafix]

@acmesediver
The .GNUstepDefaults file starts with a ".", which is part of the filename and must not be omitted.
Files, whose filenames start with ".", are displayed by "ls -a".
In your case:

Code: Select all

mace@mace-laptop:<path>$ cd ~/GNUstep/Defaults/
mace@mace-laptop:~/GNUstep/Defaults$ ls -a
.  ..  .GNUstepDefaults  .GNUstepDefaults.original
mace@mace-laptop:~/GNUstep/Defaults$ 

The ".GNUstepDefaults.original" should be there if you performed the previous instructions correctly.

Now do the following:

Code: Select all

mace@mace-laptop:~/GNUstep/Defaults$ gedit .GNUstepDefaults

This will open the "gedit" text editor and load ".GNUstepDefaults" file.

Then change the line where "shader-mode" is set, to display the following:

Code: Select all

   "shader-mode" = <*I1>;

Save the changes and exit the editor.

Execute, oolite again and tell us if that changes, by any means, the behavior.

[acmesediver]

I was able to follow your great directions Getafix, and changed the shader. The results were mixed: No defragmented Text, but Far, far slower and jumpy gameplay, as if I were driving a v-8 with with 2 missing cylinders. Not worth the addition of the full text, which was nice to see though! Going to try the graphics test next.

[acmesediver]

and the defrag text issue is still gone, but the slow gameplay/response/graphics remain.

[acmesediver]

So I looked at my system monitor on a hunch, and oolite is using nearly all my CPU capacity- Running at 100% whenever game is on.

[Getafix]

@acmesediver
You could also try the simple shader effects:

Code: Select all

   "shader-mode" = <*I2>;

[Svengali]

Higher CPU usage on my machine too (Laptop Core2Duo XP Pro x86, GeForce Go 7950 GTX, 179.48) compared to v1.73.x.
But there are a few things you could try:

1. Oolites Vsync seems to collide with the drivers Vsync on my machine.
- If your Mesa driver has options for Vsync and tripple buffering try to toggle tripple buffering.
- If it doesn't help try to disable Vsync to see what happens then (this will probably cause tearing though), but reduces CPU load on my machine (and FPS = 63/64 instead of 60).

2. Please check if using injectors and torus drive reduces CPU load and keep an eye on CPU/GPU loads and temperatures.

3. Strange enough, but disabling dithering for DXT1 has made VSync a lot more stable on my machine. Could be that the driver does some 'optimizations' internally, but I don't know if this is possible with Mesa drivers.

4. Could be interesting to know what kind of CPU-states (C,P,S,D) are set via BIOS.
short explanation -> http://en.wikipedia.org/wiki/Advanced_C ... _Interface
deeper stuff, Intel related -> http://software.intel.com/en-us/blogs/a ... ylor-kidd/