I noticed this behaviour when I tried to fix my 4870x2 problem with OpenGL by adding an OpenGL wrapper.
I had to turn off the shader code in that wrapper in order to make that problem go away. The wrapper wasn't good for playing, though, as it crashed after a short time. So I'm back with a 4870x2 which performs far worse than the X800XTPE on my much slower computer.
Screet who was banned on the AMD/ATI forum for reporting that the 4870x2 apparantly has an OpenGL bug as it's performing worse than the X800XTPE.
@govert: Can you please post the contents of the game log, found in oolite.app\Logs\Latest.log? It looks like Oolite cannot see resources (note the version number on the window title reads 'nil').
Also the exe reads the wrong date for 1.72.2. I recommend a full reinstall of the latest version.
[log.header]: Opening log for Oolite version 1.72.2 (x86-32 test release) under Windows at 2009-02-25 13:44:32 +0100.
2 processors detected.
Note that the contents of the log file can be adjusted by editing logcontrol.plist.
[joystickHandler.init]: Number of joysticks detected: 0
[display.mode.list.native]: Windows native resolution detected: 1440 x 900
[rendering.opengl.version]: OpenGL renderer version: 1.1.0 ("1.1.0")
Vendor: Microsoft Corporation
Renderer: GDI Generic
[rendering.opengl.extensions]: OpenGL extensions (3):
GL_WIN_swap_hint GL_EXT_bgra GL_EXT_paletted_texture
[rendering.opengl.shader.support]: Shaders will not be used (OpenGL extension GL_ARB_shading_language_100 is not available).
[dataCache.notFound]: No data cache found, starting from scratch.
[searchPaths.dumpAll]: ---> OXP search paths:
(oolite.app/Resources, AddOns)
[shipData.load.begin]: Loading ship data...
[script.load.world.listAll]: Loaded 5 world scripts: "oolite-cloaking-device" 1.72.2, "oolite-constrictor-hunt" 1.72.2, "oolite-nova" 1.72.2, "oolite-thargoid-plans" 1.72.2, "oolite-trumbles" 1.72.2
[dataCache.willWrite]: About to write data cache.
[dataCache.write.success]: Wrote data cache.
[gnustep]: 2009-02-25 13:46:34.437 oolite[6092] Defaults path 'C:\Program Files/Oolite/oolite.app/GNUstep/Defaults' did not exist - created it
[gameController.exitApp]: .GNUstepDefaults synchronized.
Closing log at 2009-02-25 13:46:34 +0100.
@govert: Can you please post the contents of the game log, found in oolite.app\Logs\Latest.log? It looks like Oolite cannot see resources (note the version number on the window title reads 'nil').
The log file is in a different place if he uses windows vista and installed to the default directory in program files instead of a folder like "C:\Oolite". The problem is caused by windows vista virtualization.
For me, that resulted in an oolite folder being created by vista in the following directory:
C:\Users\Screet\AppData\Local\VirtualStore\Program Files
There it did have the log in an oolite.app\logs\ subfolder.
With vista, it's a good idea not to insteall to C:\program files for this reason. There are also other programs suffering from this, for example my razer mouse drivers
Screet
Edit: ARGH. Took too long to reply seeing that the log has already been found, well, maybe it helps other users who read this topic
You don't have your graphics card's drivers installed correctly. Oolite is trying to use software rendering.
Deja vu, I'm sure we had this happening just a few days ago...
I beleive that the problem is that I have the latest, but buggy driver:
1) New laptop received by IT department 3 weeks ago
2) Driver Detective tells me I have the latest drivers installed
3) Downloading & running the latest drivers from ATI i get the reply
Setup did not find a driver compatible with your current hardware or operating system
I beleive that the problem is that I have the latest, but buggy driver:
1) New laptop received by IT department 3 weeks ago
2) Driver Detective tells me I have the latest drivers installed
3) Downloading & running the latest drivers from ATI i get the reply
Setup did not find a driver compatible with your current hardware or operating system
Maybe it helps to give the HIS drivers for comparable hardware sold by them a try.
I tried the outdated HIS drivers on my Asus 4870x2 and they fixed a lot of problems which also exist with ATI original drivers of the same time. Seems they found a bug in ATI drivers and fixed it only for themselves, but might also just have been luck.
)
