Oolite Bulletins

Hi Commanders,

I am an absolute newbie to Oolite. I played for some days with no problem. During a docking station approaching, I paused the game. I know it is not advisable to pause an approaching protocol, but the docking protocol conflicted with a direct order from a Superior Commander, namely "Come to have dinner NOW!". I think it was when I came back (after dinner, no screen protector launched), something odd had happened to the world I was near to: it had no textures no it. I had the nerve to continue my approach, locating the bouy (which seemed ok to me), but the docking station had also no textures. I traded some items and went back to space (where all we Commanders belong) and hyperjumped to my next destination. To my surprise, this world had no textures, nor had the docking station next to it.

I saved and quited. I launched Oolite again. The Cobra Mk III in the main screen lacked its textures and so did the world I was launched to (PNG):
http://www.box.com/s/91ba89452f1800a3b751

I had installed some OXPs, I deleted them. Same problem.

I reinstalled Oolite 1.75.3 from Software Center. Same problem.

I updated NVIDIA propietary drivers from some 280 version to:
11:03:06.795 [rendering.opengl.version]: OpenGL renderer version: 3.3.0 ("3.3.0 NVIDIA 295.40"). Vendor: "NVIDIA Corporation". Renderer: "GeForce 9800 GT/PCIe/SSE2".
11:03:06.795 [rendering.opengl.extensions]: OpenGL extensions (236)
Same problem.

I uninstalled Oolite 1.75.3 and installed:
11:03:06.794 [dataCache.rebuild]: Data cache version (1.75.3) does not match Oolite version (1.76), rebuilding cache.
Same problem.

With Oolite 1.76 I get this at the end of the log:
11:03:08.571 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'NSPOSIXErrorDomain 111' (outStream status: 7, inStream status: 7)."
11:03:08.571 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'unknown error.' (outStream status: 0, inStream status: 0)."
11:03:08.571 [debugTCP.connect.failed]: Failed to connect to debug console at address 127.0.0.1:8563.
Which I don't think has anything to do with my problem.

These were extracts from my latest log:
11:03:06.492 [log.header]: Opening log for Oolite version 1.76 (x86-64 test release) under Linux at 2012-04-29 11:03:06 +0200.
4 processors detected.
Build options: spoken messages, mass/fuel pricing, JavaScript console support, OXP verifier, localization tools, debug GraphViz support, JavaScript profiling.

The rest of the log seems ok to me (considering that it is the first time I see an Oolite log).

I would appreciate an advice from a more experienced Commander

Thank you and greetings

(if something I wrote seems nonsense probably it is due to my limited english skills, ask whatever you don't understand, thanks!)

Hi and welcome.

From the screenshot you posted, it looks like Wireframe Graphics have accidentally been set to ON. Start the game, press F2 to go to the Options screen, then select Game Options and find the menu item titled Wireframe Graphics. If ON, change it back to OFF and you should be good to go.

hej, welcome !

Have you maybe accidentally switched the game to "wireframe graphics" ?
In the game options (F2, or in flight : pause, F2)you can see Wireframe graphics : On/ Off.

edit : oh, me too slow again.

fedegf wrote:

I updated NVIDIA propietary drivers

So some good came of it.

fedegf wrote:

I uninstalled Oolite 1.75.3 and installed:
11:03:06.794 [dataCache.rebuild]: Data cache version (1.75.3) does not match Oolite version (1.76), rebuilding cache.

Upgraded to v1.76. That's good too.

fedegf wrote:

With Oolite 1.76 I get this at the end of the log:
11:03:08.571 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'NSPOSIXErrorDomain 111' (outStream status: 7, inStream status: 7)."
11:03:08.571 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'unknown error.' (outStream status: 0, inStream status: 0)."
11:03:08.571 [debugTCP.connect.failed]: Failed to connect to debug console at address 127.0.0.1:8563.
Which I don't think has anything to do with my problem.

Correct. Failure to connect to the debug console is normal and correct. (It would be nice if the 'error messages' were less scary.)

fedegf wrote:

(if something I wrote seems nonsense probably it is due to my limited English skills, ask whatever you don't understand, thanks!)

(it's better than the English of many English university graduates!)

Suggestion to developers: do we need the "switch to wireframe" option? Is it for novelty? Debugging?

SandJ wrote:

do we need the "switch to wireframe" option? Is it for novelty?

On the contrary, it's for nostalgia. For all of us who have fond memories of the sensation that was hidden-line removal in 1983.

Hello again,

I feel very stupid now. Of course all of you were right. Probably I changed to wireframe graphics during flight with no object in front of me, that is the reason I realized only after dinner....errrr... strategy briefing.

Thank you very much, I love the game, I plan to download Famous Planets and other OXP and go on commanding, who knows, maybe one day I will become Elite hahaha

By the way, is there any chance for the game to go multiplayer?

Should I mark the topic [Solved] or is this an administrator task?

fedegf wrote:

Should I mark the topic [Solved] or is this an administrator task?

Just add [Solved] to your thread title... and hello!

fedegf wrote:

I feel very stupid now.

Never let a computer make you feel that way; if you can't work it out, it's probably bad design.

fedegf wrote:

is there any chance for the game to go multiplayer?

fedegf wrote:

Should I mark the topic [Solved]

Good idea; just edit your first post. Edit: ninja'd

fedegf wrote:

By the way, is there any chance for the game to go multiplayer?

Please read this thread for an answer.