Any way to slow down gameplay/speed

[DmitryDV]

Hi.

Nice game. I like it. But I cant follow its dynamics. Ships are too fast. Is there any way to slow NPC's and my ship down?

[another_commander]

Hi. You can either edit the ship stats in the game config files, which is very laborious, or you can use the Test Release version of the game, which has ability to slow down or speed up game tick time.

With the TR version running, just pause the game, use the left/right arrows to adjust game tick (use Shift+F to view this info shown as TAF) and then unpause the game. The left arrow reduces tick time in steps of 1/2 and the right arrows increases tick in steps of 2. There is also a way to set game tick to in-between values but this requires the use of scripting.

As a starting point, try setting game tick to half as described above. If that is good enough for you then that's all you will need to do.

[Cholmondely]

I like it.

Welcome to the wonderful world of Oolite!

Here's hoping that you enjoy it as much as we do!

[DmitryDV]

use the Test Release version of the game

Thank you for reply.

Finally I figured out how to do it - by converting deployment version to test. I tried 1.88 and 1.9 Both doesnt run. Deployment versions works just fine. Please advise.

[DmitryDV]

I like it.

Welcome to the wonderful world of Oolite!

Here's hoping that you enjoy it as much as we do!

Thank you for kind words. I used to play Elite back in late 80th and Elite Dangerous but it gets really boring. Oolite looks promising.

[another_commander]

Thank you for reply.

Finally I figured out how to do it - by converting deployment version to test. I tried 1.88 and 1.9 Both doesnt run. Deployment versions works just fine. Please advise.

What is the error message? Is there a Latest log in oolite app/Logs after a failure to run? If yes, please post it.

[DmitryDV]

Thank you for reply.

Finally I figured out how to do it - by converting deployment version to test. I tried 1.88 and 1.9 Both doesnt run. Deployment versions works just fine. Please advise.

What is the error message? Is there a Latest log in oolite app/Logs after a failure to run? If yes, please post it.

No errors on run just nothing. Here goes log

Spoiler

Opening log for Oolite version 1.90 (x86-64 test release) under Windows 10.0.19043.928 64-bit at 2024-11-15 16:50:51 +0300.
Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz 8 processors detected.
Build options: OpenAL, new planets, JavaScript console support, OXP verifier, localization tools, debug GraphViz support, JavaScript profiling.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

16:50:51.943 [display.mode.list.native]: Windows native resolution detected: 1366 x 768
16:50:51.988 [rendering.opengl.state]: Incorrect OpenGL state in -[MyOpenGLView initSplashScreen] (line 730)->OOSetOpenGLState
16:50:51.988 [rendering.opengl.state]: Expected previous state: <canonical initial state>
16:50:51.988 [rendering.opengl.state]: GL_ACTIVE_TEXTURE should be ENABLED but is ENABLED.
16:50:51.988 [rendering.opengl.state]: GL_CLIENT_ACTIVE_TEXTURE should be ENABLED but is ENABLED.
16:50:51.988 [rendering.opengl.badExtension]: ***** An uninitialized OpenGL extension function has been called, terminating. This is a serious error, please report it. *****

Closing log at 2024-11-15 16:50:51 +0300.

[another_commander]

Would it be possible to have a Latest.log from a normal run of the deployment version as well? Need to get the info about graphics card and driver.

[DmitryDV]

Would it be possible to have a Latest.log from a normal run of the deployment version as well? Need to get the info about graphics card and driver.

Sure

Normal

Spoiler

Opening log for Oolite version 1.90 (x86-64) under Windows 10.0.19043.928 64-bit at 2024-11-15 18:17:44 +0300.
Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz 8 processors detected.
Build options: OpenAL, new planets.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

18:17:44.882 [display.mode.list.native]: Windows native resolution detected: 1366 x 768
18:17:44.924 [joystick.init]: Number of joysticks detected: 0
18:17:44.924 [rendering.opengl.version]: OpenGL renderer version: 1.1.0 ("1.1.0"). Vendor: "Microsoft Corporation". Renderer: "GDI Generic".
18:17:44.924 [rendering.opengl.extensions]: OpenGL extensions (3):
GL_EXT_paletted_texture, GL_EXT_bgra, GL_WIN_swap_hint
18:17:44.930 [rendering.opengl.shader.support]: Shaders will not be used (OpenGL extension GL_ARB_shading_language_100 is not available).
18:17:44.955 [searchPaths.dumpAll]: Resource paths:
Resources
../AddOns
../AddOns/Basic-debug.oxp
18:17:45.212 [shipData.load.begin]: Loading ship data.
18:17:45.609 [startup.complete]: ========== Loading complete in 0.78 seconds. ==========
18:17:47.877 [exit.context]: Exiting: Exit Game selected on start screen.
18:17:47.880 [gameController.exitApp]: .GNUstepDefaults synchronized.

Closing log at 2024-11-15 18:17:47 +0300.

Test

Spoiler

Opening log for Oolite version 1.90 (x86-64 test release) under Windows 10.0.19043.928 64-bit at 2024-11-15 18:19:34 +0300.
Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz 8 processors detected.
Build options: OpenAL, new planets, JavaScript console support, OXP verifier, localization tools, debug GraphViz support, JavaScript profiling.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

18:19:34.203 [display.mode.list.native]: Windows native resolution detected: 1366 x 768
18:19:34.246 [rendering.opengl.state]: Incorrect OpenGL state in -[MyOpenGLView initSplashScreen] (line 730)->OOSetOpenGLState
18:19:34.246 [rendering.opengl.state]: Expected previous state: <canonical initial state>
18:19:34.246 [rendering.opengl.state]: GL_ACTIVE_TEXTURE should be ENABLED but is ENABLED.
18:19:34.246 [rendering.opengl.state]: GL_CLIENT_ACTIVE_TEXTURE should be ENABLED but is ENABLED.
18:19:34.246 [rendering.opengl.badExtension]: ***** An uninitialized OpenGL extension function has been called, terminating. This is a serious error, please report it. *****

Closing log at 2024-11-15 18:19:34 +0300.

[another_commander]

Right, I was suspecting it to be the case and the deployment log confirms it: Your graphics driver is the generic Microsoft one and is doing software rendering. Oolite requires hardware 3D acceleration in order to work correctly. I now know that the deployment version runs at extremely low framerates for you and the fact that it runs at all is purely a fortunate coincidence.

Unfortunately I cannot tell what graphics card you are running (dxdiag should be able to report that info, just go WindowsKey+R and type dxdiag), but my suggestion would be that you install the most recent available graphics driver for it. While at it, I would also recommend updating your Windows 10 to the latest version 22H2 (you are running 21H1).

[DmitryDV]

Right, I was suspecting it to be the case and the deployment log confirms it: Your graphics driver is the generic Microsoft one and is doing software rendering. Oolite requires hardware 3D acceleration in order to work correctly. I now know that the deployment version runs at extremely low framerates for you and the fact that it runs at all is purely a fortunate coincidence.

Unfortunately I cannot tell what graphics card you are running (dxdiag should be able to report that info, just go WindowsKey+R and type dxdiag), but my suggestion would be that you install the most recent available graphics driver for it. While at it, I would also recommend updating your Windows 10 to the latest version 22H2 (you are running 21H1).

Got back to desktop pc. Now test version runs just fine. 0.25 tick did exactly what I wanted to. Thanks a lot!

ps nope... after first laser hit tick settings resets to 1 and keeps resetting

[another_commander]

Try it without oxps. Does it still happen?

[DmitryDV]

Try it without oxps. Does it still happen?

Without oxps works fine. Is there any magic to make oxp and tick friends?

[another_commander]

Just need to find the one oxo that causes the problem and remove it. The binary division method should be the quickest way to achieve this.

[gilhad]

I think, I had read somewhere, that some OXP manipulates the ticks too, to make long ways faster. And restores it, when there is a fight or something.

Anyway the binary division method will find some culprit fast