Gaming Spaceway project call for testing

I've got an ageing Intel Mobile card and I'm pulling about 1-3 FPS while textures load, and about a just-about playable 10 FPS normally.

Looking pretty cool! I like the river thing.

I get the controls OK, but how do you change the warp speed of the vessel?
 
"High end computer required" is unfortunately the only feedback I can provide.

My
AMD Athlon 3000+
GeForce 6600GT
1.75 GB RAM
just can't handle it. It runs on 6 FPS for about 20 seconds, then crashes and gives an error message to contact developer.


"Critical error in OGLA.dll, terminating. See ogla.log for details for developer."
Whole bunch of nonsense...
"Error in smobs_render (i=0)".

But there is no ogla.log. I'm posting shader.log and spaceway.log below:

shader.log
Code: 
Vessel program 0:
Vessel program 1:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 2:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 3:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 4:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 5:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 6:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 7:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Planet program 0:
Planet program 1:
Planet program 2:
Planet program 3:
Planet program 4:
Planet program 5:
Planet program 6:
Planet program 7:
Planet program 8:
Planet program 9:
Planet program 10:
Planet program 11:
Planet program 12:
Planet program 13:
Planet program 14:
Planet program 15:
Haze program 0:
Ring program:
Post program:
Nebular program:
prog[0]:
prog[1]:
Vessel program 0:
Vessel program 1:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 2:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 3:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 4:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 5:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 6:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 7:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Planet program 0:
Planet program 1:
Planet program 2:
Planet program 3:
Planet program 4:
Planet program 5:
Planet program 6:
Planet program 7:
Planet program 8:
Planet program 9:
Planet program 10:
Planet program 11:
Planet program 12:
Planet program 13:
Planet program 14:
Planet program 15:
Haze program 0:
Ring program:
Post program:
Nebular program:
prog[0]:
Fragment info
-------------
0(360) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(360) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(462) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(361) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(361) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(361) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(462) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(360) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(387) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(387) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(462) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(388) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(388) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(388) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(462) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(387) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(414) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(414) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(462) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(415) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(415) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(415) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(462) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(414) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(453) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(453) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(462) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(454) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(454) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(454) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(462) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(453) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable

Vessel program 0:
Vessel program 1:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 2:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 3:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 4:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 5:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 6:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Vessel program 7:
Fragment info
-------------
0(6) : error C5041: cannot locate suitable resource to bind parameter "tsp"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"
0(6) : error C5041: cannot locate suitable resource to bind parameter "<null atom>"

Planet program 0:
Planet program 1:
Planet program 2:
Planet program 3:
Planet program 4:
Planet program 5:
Planet program 6:
Planet program 7:
Planet program 8:
Planet program 9:
Planet program 10:
Planet program 11:
Planet program 12:
Planet program 13:
Planet program 14:
Planet program 15:
Haze program 0:
Ring program:
Post program:
Nebular program:
prog[0]:
0(302) : warning C7011: implicit cast from "int" to "float"
0(303) : warning C7011: implicit cast from "int" to "float"
0(304) : warning C7011: implicit cast from "int" to "float"

Fragment info
-------------
0(302) : warning C7011: implicit cast from "int" to "float"
0(303) : warning C7011: implicit cast from "int" to "float"
0(304) : warning C7011: implicit cast from "int" to "float"
0(339) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(339) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(420) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(340) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(340) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(340) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(420) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(339) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(368) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(368) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(420) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(369) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(369) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(369) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(420) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(368) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(415) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(415) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(420) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(416) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(416) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(416) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(420) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(415) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable

shader.log
Code: 
14.9.2011-12:50:07:[SWAY      ]:-----------------Started-----------------------
14.9.2011-12:50:07:[DBG       ]:Spaceway engine v110913 started.
14.9.2011-12:50:07:[DBG       ]:Loading settings
14.9.2011-12:50:07:[DBG       ]:Loading gui colors
14.9.2011-12:50:07:[DBG       ]:Rendering
14.9.2011-12:50:09:[DBG       ]:Loading language
14.9.2011-12:50:09:[DBG       ]:Reading vessel cfgs
14.9.2011-12:50:09:[DBG       ]:Reading log
14.9.2011-12:50:09:[DBG       ]:Setting scripts
14.9.2011-12:50:09:[DBG       ]:Reading bases cfgs
14.9.2011-12:50:09:[DBG       ]:Navigation and vessels
14.9.2011-12:50:12:[DBG       ]:Registering MFDs
14.9.2011-12:50:12:[DBG       ]:Making GUI
14.9.2011-12:50:35:[DBG       ]:System graphics
14.9.2011-12:50:35:[OGLADBG   ]:OGLA 110913 Debug.
14.9.2011-12:50:43:[script    ]:Sayo base module for "Sayo"
14.9.2011-12:51:03:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:04:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:04:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:04:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:04:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:04:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:05:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:05:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:06:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:07:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:07:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:07:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:08:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:09:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:09:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:10:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:10:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:10:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:11:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:11:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:51:11:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:52:47:[SWAY      ]:-----------------Started-----------------------
14.9.2011-12:52:47:[DBG       ]:Spaceway engine v110913 started.
14.9.2011-12:52:47:[DBG       ]:Loading settings
14.9.2011-12:52:47:[DBG       ]:Loading gui colors
14.9.2011-12:52:47:[DBG       ]:Rendering
14.9.2011-12:52:48:[DBG       ]:Loading language
14.9.2011-12:52:48:[DBG       ]:Reading vessel cfgs
14.9.2011-12:52:48:[DBG       ]:Reading log
14.9.2011-12:52:48:[DBG       ]:Setting scripts
14.9.2011-12:52:48:[DBG       ]:Reading bases cfgs
14.9.2011-12:52:48:[DBG       ]:Navigation and vessels
14.9.2011-12:52:51:[DBG       ]:Registering MFDs
14.9.2011-12:52:51:[DBG       ]:Making GUI
14.9.2011-12:52:57:[DBG       ]:System graphics
14.9.2011-12:52:57:[OGLADBG   ]:OGLA 110913 Debug.
14.9.2011-12:53:02:[DBG       ]:Genesis
14.9.2011-12:53:02:[DBG       ]:Loading current
14.9.2011-12:53:05:[script    ]:Sayo base module for "Sayo"
14.9.2011-12:53:05:[DBG       ]:Running
14.9.2011-12:53:09:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:09:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:09:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:09:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:10:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:10:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:11:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:11:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:12:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:12:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:12:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:12:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:12:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:12:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:12:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:13:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:13:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:13:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:13:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:14:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:53:14:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:13:[SWAY      ]:-----------------Started-----------------------
14.9.2011-12:55:13:[DBG       ]:Spaceway engine v110913 started.
14.9.2011-12:55:13:[DBG       ]:Loading settings
14.9.2011-12:55:13:[DBG       ]:Loading gui colors
14.9.2011-12:55:13:[DBG       ]:Rendering
14.9.2011-12:55:15:[DBG       ]:Loading language
14.9.2011-12:55:15:[DBG       ]:Reading vessel cfgs
14.9.2011-12:55:15:[DBG       ]:Reading log
14.9.2011-12:55:15:[DBG       ]:Setting scripts
14.9.2011-12:55:15:[DBG       ]:Reading bases cfgs
14.9.2011-12:55:15:[DBG       ]:Navigation and vessels
14.9.2011-12:55:18:[DBG       ]:Registering MFDs
14.9.2011-12:55:18:[DBG       ]:Making GUI
14.9.2011-12:55:25:[DBG       ]:System graphics
14.9.2011-12:55:25:[OGLADBG   ]:OGLA 110913 Debug.
14.9.2011-12:55:32:[script    ]:Sayo base module for "Sayo"
14.9.2011-12:55:37:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:37:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:37:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:37:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:37:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:37:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:38:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:38:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:38:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:39:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:39:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:39:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:39:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:40:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:40:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:40:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:40:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:40:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:41:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:41:[Graph     ]:Error: Error in smobs_render (i=0)
14.9.2011-12:55:41:[Graph     ]:Error: Error in smobs_render (i=0)
 
Spacethingy said:
I get the controls OK, but how do you change the warp speed of the vessel?
Click to expand...
Like in WarpDriveMFD - Shift++ or -.

RisingFury said:
It runs on 6 FPS for about 20 seconds, then crashes and gives an error message to contact developer.
Click to expand...
Try unsetting these in data/options/ogla.cfg:
Multilight_Terrain=0
Advanced_Graphics=0

If it does not help, try disabling use GPU in Options menu.
 
This is looking like a great thing you've got going, how long have you been working on it? This is the first I've heard of it.
 
Oh my God, it's full of stars
Click to expand...

This version got me hooked. OGLA has been evidently de-bugged, and with GPU off, and an NVIDIA GeForce 8600M GS and a dual-core CPU, I get decent 28-30 FPS during takeoff and low atmospheric flight (68 FPS in space). Cannot comment on docs, since having orbiter controls makes use intuitive. All in all, looking forward to further breakthroughs.
 
Note to everyone who tried it:
If you had problems with defaults, but succeeded in getting it playable by tweaking the settings, it would be helpful if you posted the tweaks and your hardware description.

I don't have a clear idea on real system requirements, besides them being quite high, so a set of data points would help a lot.

Wishbone said:
with GPU off, and an NVIDIA GeForce 8600M GS
Click to expand...
You can also try tweaking GPU generation options - reduce resolution, reduce amount of slices, etc.
It's a good card, may be able to handle it.

Pyromaniac605 said:
how long have you been working on it?
Click to expand...
Started as some gravity sim and star gen toys long ago.
Turned 3D by impressions of Orbiter around 2003.
Revived with OGLA engine around 2008.
And it's current procedural-generation-of-all shape goes from about 2009.

...It's been eight years since i found Orbiter.
Time surely flies.
 
Artlav said:
Try unsetting these in data/options/ogla.cfg:
Multilight_Terrain=0
Advanced_Graphics=0
Click to expand...


This prevented crashing on my machine (AMD Athlon 3000+, GeForce 6600 GT, 1.75 GB RAM) and surprisingly enough, achieved playable FPS. When I say playable...

~60 in gateship scenario
~10-20 in Ice moon and Watch a gas giant scenario. Even up to 25 if I turned around and flew over the part of terrain that was generated. But both of these scenarios needed some 10 to 20 seconds to generate terrain around the starting point of the vehicle and that resulted in the first moments being laggy.

KSP doesn't run much better then this...
 
RisingFury said:
~10-20 in Ice moon and Watch a gas giant scenario. Even up to 25 if I turned around and flew over the part of terrain that was generated. But both of these scenarios needed some 10 to 20 seconds to generate terrain around the starting point of the vehicle and that resulted in the first moments being laggy.
Click to expand...
More things to try would be reducing the texture size in options menu, maybe reduce the slice or timings.

Also, try CPU generation - less terrain, but may work faster summarily (certainly on 4 cores, not sure about 2).

What happens on planet approach?
Try dialing @1 in gateships scenario (F opens the menu, G opens the gate), that'll put you on natural approach.
 
Artlav said:
Not really.
System specs?
Does it happen in each and every scenario?
Does it happen in "glittering stars" scenario, which is interstellar?
Click to expand...

Specs: Intel(R) Core(TM)2 CPU, T5500 @ 1,66GHz, 981 MHz, 2 GB of RAM. It happens in all scenarios, including "glittering stars".
 
diogom said:
Specs: Intel(R) Core(TM)2 CPU, T5500 @ 1,66GHz, 981 MHz, 2 GB of RAM. It happens in all scenarios, including "glittering stars".
Click to expand...
And the video card?

Please try the suggestions i gave RisingFury - disable advanced graphics and multilight_terrain in the cfg, etc.
 
Artlav said:
And the video card?

Please try the suggestions i gave RisingFury - disable advanced graphics and multilight_terrain in the cfg, etc.
Click to expand...

Video card, is a NVIDIA GeForce Go 7400. And it works after I disabled these option, thanks!
 
Works great on my Toshiba L650D-15F. But I'm having a problem with the MFDs. Is it normal that there aren't any other buttons than Sel? If yes, is there a way to display all those MFD buttons?
 
astrosammy said:
Works great on my Toshiba L650D-15F. But I'm having a problem with the MFDs. Is it normal that there aren't any other buttons than Sel? If yes, is there a way to display all those MFD buttons?
Click to expand...
You've got to resort to keyboard Shift shortcuts (Lshift for left MFD, Rshift for right), just like in the good old days of Orbiter 2005.
 
astrosammy said:
Is it normal that there aren't any other buttons than Sel? If yes, is there a way to display all those MFD buttons?
Click to expand...
No, no buttons implemented. Possibly, not yet.
 
It still works pretty nicely on my machine, although at a lower average framerate than previous versions.

Also, every once in a while it freezes for 10 or so seconds, then continues to function normally. Could not reproduce circumstances relyably, but it happens more often when other large programs are running (doing nothing) in the background.

All in all, this gets better and better. Now we need an orbiteresque API interface for modders, and this baby might take off beyond recognition. Might not even need Orbiter galaxy anymore...

For future priorites, though, I would suggest to concentrate on establishing solid airodynamics and driving physics. Nothing too over the top, just to give a feeling like you're flying or driving.
 
Last edited:
Although I have hit a bug with the base, You can't dial in to it. (or at least, there is no obvious way) When I placed a gate ship to deal with this, I ended up dialing 2 gates at once any time I wanted to dial out. I can only think what that's doing to the memory structures.
 
jedidia said:
Now we need an orbiteresque API interface for modders, and this baby might take off beyond recognition.
Click to expand...
Some of it is already here - look at the cfg files for the base and warp ship.

It comes with it's own compilers, so no DLLs or pseudo-free IDEs are needed.
API needs work and documentation, however.

jedidia said:
For future priorites, though, I would suggest to concentrate on establishing solid airodynamics and driving physics. Nothing too over the top, just to give a feeling like you're flying or driving.
Click to expand...
Certainly, that is high on priority list.

jangofett287 said:
Although I have hit a bug with the base, You can't dial in to it. (or at least, there is no obvious way)
Click to expand...
Bug confirmed, can only dial from the same solar system.

jangofett287 said:
When I placed a gate ship to deal with this, I ended up dialing 2 gates at once any time I wanted to dial out. I can only think what that's doing to the memory structures.
Click to expand...
That's normal.
There is no way to dial a particular gate, so all gates in the vicinity are opened.
The gate's horizon is a sensor, which triggers an instantaneous transfer on contact, not a wormhole like in the movie.
 
I just loaded this in and started playing, so no real feedback yet, except for noticing some landing strip Z-buffer fighting while zooming in and out. Also, terrain generation is so slow that I often fly completely by the landscape before it is much more than jagged pixels (but that I blame mostly on my anemic computer -- I really need an upgrade).

AMD Athlon 64 3800+, 2.4 GHz, 64bit Win 7, 2 Gigs Dual Channel Ram, GeForce 8800 GT

But so far it is quite playable, no sudden crashes or CTDs, and completely amazing for a floppy sized zip file.

This might belong in a separate thread, but what is the chance of splitting out the procedural planet generator as a stand alone? And making it export to Orbiter? And giving the user multiple customization options?

:)
 
Mandella said:
This might belong in a separate thread, but what is the chance of splitting out the procedural planet generator as a stand alone? And making it export to Orbiter? And giving the user multiple customization options?
Click to expand...
Was done before, being done now.
Many pieces of Spaceway are reused in Orbiter in one way or another.

Older incarnation, Spaceway stripped of vessels:
http://www.orbiter-forum.com/showthread.php?t=7205

Recent incarnation, a separate solar system generator by jedidia, with textures from Spaceway:
http://www.orbiter-forum.com/showthread.php?t=9428&page=39
 
You must log in or register to reply here.

Similar threads

dgatsoulis
Project TrajectoryOptimizerMFD open for testing
Replies
16
Views
5K
drgullen
D
B
General Question Enjoying Orbiter as a Totally Blind User
Replies
9
Views
3K
N_Molson
N_Molson
HarvesteR
Gaming Kitten Space Agency - Now live on Ahwoo
Replies
3
Views
5K
Jeb
Jeb
dgatsoulis
Project VideoPlayerMFD -- Test thread [CLOSED]
Replies
7
Views
4K
misha.physics
misha.physics
pi314
KSP degen returning after a decade or so
Replies
0
Views
650
pi314
pi314
Back
Top