Elite Wiki - User contributions [en]

https://wiki.alioth.net/api.php?action=feedcontributions&feedformat=atom&user=Hiran Elite Wiki - User contributions [en] 2026-06-23T13:20:49Z User contributions MediaWiki 1.31.12 https://wiki.alioth.net/index.php?title=Common_Testing&diff=89299 Common Testing 2026-06-06T09:49:33Z

<p>Hiran: </p> <hr /> <div>[[File:FPS report.png|right|400px]]<br /> Here are some tests that can be performed regardless of the operating system.<br /> <br /> == Audio output ==<br /> <br /> Run Oolite and check whether this output works as intended:<br /> * Background noise<br /> * Flying/shooting<br /> * Voice output<br /> <br /> == Performance Test ==<br /> <br /> The main functionality in Oolite is to process the "game loop". This reads user input, processes the world including running all your OXP/OXZs, and then renders out the world view. For meaningful tests you need to have a repeatable base. A good metric for performance is the number of [[Frame rate|frames per second]] (FPS) that Oolite can process.<br /> <br /> If you want to check performance, you must check with FPS uncapped, otherwise you are always getting v-sync FPS, which is usually a low number like 60 for a 60Hz monitor, 144 for a 144Hz one ''etc''. <br /> <br /> Add the '''"animation_timer_interval" = x;''' in your OoliteDefaults.plist, where x is 1.0/Maximum FPS You Want To Achieve. I usually set it to 0.001 which tells Oolite to "go for 1000 FPS if you can". Then you can compare actual performance between builds.<br /> <br /> Also, disable v-sync to have uncapped FPS. You do this by setting the OoliteDefaults.plist key '''"v-sync" = NO;'''.<br /> <br /> When comparing the performance of builds, always check with more or less the same number of entities in the system. If in one case you get 250 entities and in the other you get 70, then results may be biased (it takes much more processing power to manage the 250). Try to compare instances where the two system entity numbers are as close as possible. Shift+F shows you this info in the Oolite "Test Release" builds. Phkb wrote an expansion for that: [https://app.box.com/s/xrkkr5ylizshjng2dpc8uu9q6b39zt49 CustomPopulator.oxp.zip]. And as other OXP/OXZs may inhibit the build performance, make sure this is the only one you are running on top of a [[Vanilla game]].<br /> <br /> After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.<br /> <br /> === Example ===<br /> <br /> Here in ASCII Plist format:<br /> <br /> {<br /> "Jameson-humbletrash" = "-29624";<br /> "animation_timer_interval" = "0.001";<br /> "debug-settings-override" = {<br /> };<br /> "gamma-value" = 1;<br /> "v-sync" = no;<br /> "volume_control" = "0.5";<br /> "window_height" = 1043;<br /> "window_width" = 1920;<br /> }<br /> <br /> <br /> Or the same as XML:<br /> <br /> <?xml version="1.0" encoding="UTF-8"?><br /> <!DOCTYPE plist PUBLIC "-//GNUstep//DTD plist 0.9//EN" "http://www.gnustep.org/plist-0_9.xml"><br /> <plist version="0.9"><br /> <dict><br /> <key>NSGlobalDomain</key><br /> <dict><br /> </dict><br /> <key>oolite</key><br /> <dict><br /> <key>Jameson-humbletrash</key><br /> <integer>-29624</integer><br /> <key>animation_timer_interval</key><br /> <real>0.001</real><br /> <key>gamma-value</key><br /> <real>1</real><br /> <key>v-sync</key><br /> <false/><br /> <key>volume_control</key><br /> <real>0.5</real><br /> <key>window_height</key><br /> <integer>1043</integer><br /> <key>window_width</key><br /> <integer>1920</integer><br /> </dict><br /> </dict><br /> </plist><br /> <br /> === Note ===<br /> More of the configuration file's settings are documented on the [[Hidden Settings in Oolite]] wiki page.<br /> <br /> == Comparison ==<br /> <br /> Now we need to compare several such tests in order to see patterns. To facilitate this and also communicate to others, start filling in a table like this:<br /> <br /> {| class="wikitable" style="margin:auto"<br /> |+ Caption text<br /> |-<br /> ! Oolite Version/Build/package !! Installed expansions !! Amount of entities !! screen/window size !! perceived FPS<br /> |-<br /> | 1.90/debug/.run || CustomPopulator || 360 || 800x600 || 70<br /> |-<br /> | 1.92/test/appimage || CustomPopulator || 358 || 1024x768 || 35<br /> |-<br /> | 1.93/flatpak/release || CustomPopulator || 360 || 1233x700 || 40<br /> |}<br /> <br /> == Links ==<br /> *[[Frame rate]]<br /> *[[Developer's Corner]]<br /> *[[User:Hiran|Hiran]]</div>

Hiran https://wiki.alioth.net/index.php?title=Branding&diff=89126 Branding 2026-06-02T18:28:42Z

<p>Hiran: /* Others */</p> <hr /> <div>This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.<br /> Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].<br /> <br /> = Icon Change =<br /> <br /> Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.<br /> <br /> == Oolite ==<br /> <br /> * oolite\debian\oolite-logo1.xpm<br /> * oolite\Doc\OoliteRS.odt<br /> * oolite\Documentation\docs\assets\oolite-logo.png<br /> * oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp<br /> * oolite\installers\win32\Oolite.ico<br /> * oolite\installers\win32\Oolite-HDR.ico<br /> * oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp<br /> * oolite\Resources\Images\splash@2x.png<br /> * oolite\Resources\Images\WMicon.bmp<br /> * oolite\Resources\Images\splash.bmp<br /> * oolite\Resources\Images\splash.png<br /> <br /> == Debug Console ==<br /> <br /> * oolite-debug-console\images\OoJSC.icns<br /> * oolite-debug-console\images\OoJSC.ico<br /> * oolite-debug-console\images\OoJSC16x16.png<br /> * oolite-debug-console\images\OoJSC24x24.png<br /> * oolite-debug-console\images\OoJSC32x32.png<br /> * oolite-debug-console\images\OoJSC48x48.png<br /> * oolite-debug-console\images\OoJSC64x64.png<br /> * oolite-debug-console\images\OoJSC96x96.png<br /> * oolite-debug-console\images\OoJSC128x128.png<br /> * oolite-debug-console\images\OoJSC192x192.png<br /> * oolite-debug-console\images\OoJSC256x256.png<br /> <br /> == Oolite Starter ==<br /> <br /> * OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png<br /> * OoliteStarter/src/main/resources/icons/OoliteIcon24.png<br /> * OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png<br /> * OoliteStarter/src/main/resources/oolite_logo.ico<br /> * OoliteStarter/src/main/resources/oolite_logo.png<br /> <br /> == Wiki ==<br /> * the logo on the wiki (top left of every page)<br /> * the logo on the wiki (gray icon on the main page)<br /> * the logo on the wiki (colored icon on the main oolite page)<br /> * the favicon on the wiki<br /> <br /> == Others ==<br /> <br /> * the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)<br /> * the favicon on oolite.space<br /> * the logo on bb.oolite.space<br /> * the favicon on bb.oolite.space<br /> * the logo in the Microsoft Store<br /> * the logo in the FlatHub<br /> * Is there a central repository for AppImages? If so, there.<br /> * the logo on the GitHub site.OoliteStarter/<br /> <br /> = Related = <br /> <br /> See also [[Branding History]]</div>

Hiran https://wiki.alioth.net/index.php?title=Branding&diff=89061 Branding 2026-05-31T09:51:17Z

<p>Hiran: /* Oolite Starter */</p> <hr /> <div>This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.<br /> Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].<br /> <br /> = Icon Change =<br /> <br /> Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.<br /> <br /> == Oolite ==<br /> <br /> * oolite\debian\oolite-logo1.xpm<br /> * oolite\Doc\OoliteRS.odt<br /> * oolite\Documentation\docs\assets\oolite-logo.png<br /> * oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp<br /> * oolite\installers\win32\Oolite.ico<br /> * oolite\installers\win32\Oolite-HDR.ico<br /> * oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp<br /> * oolite\Resources\Images\splash@2x.png<br /> * oolite\Resources\Images\WMicon.bmp<br /> * oolite\Resources\Images\splash.bmp<br /> * oolite\Resources\Images\splash.png<br /> <br /> == Debug Console ==<br /> <br /> * oolite-debug-console\images\OoJSC.icns<br /> * oolite-debug-console\images\OoJSC.ico<br /> * oolite-debug-console\images\OoJSC16x16.png<br /> * oolite-debug-console\images\OoJSC24x24.png<br /> * oolite-debug-console\images\OoJSC32x32.png<br /> * oolite-debug-console\images\OoJSC48x48.png<br /> * oolite-debug-console\images\OoJSC64x64.png<br /> * oolite-debug-console\images\OoJSC96x96.png<br /> * oolite-debug-console\images\OoJSC128x128.png<br /> * oolite-debug-console\images\OoJSC192x192.png<br /> * oolite-debug-console\images\OoJSC256x256.png<br /> <br /> == Oolite Starter ==<br /> <br /> * OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png<br /> * OoliteStarter/src/main/resources/icons/OoliteIcon24.png<br /> * OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png<br /> * OoliteStarter/src/main/resources/oolite_logo.ico<br /> * OoliteStarter/src/main/resources/oolite_logo.png<br /> <br /> == Others ==<br /> <br /> * the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)<br /> * the favicon on oolite.space<br /> * the logo on bb.oolite.space<br /> * the favicon on bb.oolite.space<br /> * the logo in the Microsoft Store<br /> * the logo in the FlatHub<br /> * Is there a central repository for AppImages? If so, there.<br /> * the logo on the GitHub site.OoliteStarter/<br /> * the logo on the wiki <br /> * the favicon on the wiki<br /> <br /> = Related = <br /> <br /> See also [[Branding History]]</div>

Hiran https://wiki.alioth.net/index.php?title=Branding&diff=89060 Branding 2026-05-31T09:51:09Z

<p>Hiran: /* Debug Console */</p> <hr /> <div>This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.<br /> Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].<br /> <br /> = Icon Change =<br /> <br /> Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.<br /> <br /> == Oolite ==<br /> <br /> * oolite\debian\oolite-logo1.xpm<br /> * oolite\Doc\OoliteRS.odt<br /> * oolite\Documentation\docs\assets\oolite-logo.png<br /> * oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp<br /> * oolite\installers\win32\Oolite.ico<br /> * oolite\installers\win32\Oolite-HDR.ico<br /> * oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp<br /> * oolite\Resources\Images\splash@2x.png<br /> * oolite\Resources\Images\WMicon.bmp<br /> * oolite\Resources\Images\splash.bmp<br /> * oolite\Resources\Images\splash.png<br /> <br /> == Debug Console ==<br /> <br /> * oolite-debug-console\images\OoJSC.icns<br /> * oolite-debug-console\images\OoJSC.ico<br /> * oolite-debug-console\images\OoJSC16x16.png<br /> * oolite-debug-console\images\OoJSC24x24.png<br /> * oolite-debug-console\images\OoJSC32x32.png<br /> * oolite-debug-console\images\OoJSC48x48.png<br /> * oolite-debug-console\images\OoJSC64x64.png<br /> * oolite-debug-console\images\OoJSC96x96.png<br /> * oolite-debug-console\images\OoJSC128x128.png<br /> * oolite-debug-console\images\OoJSC192x192.png<br /> * oolite-debug-console\images\OoJSC256x256.png<br /> <br /> == Oolite Starter ==<br /> <br /> OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png<br /> OoliteStarter/src/main/resources/icons/OoliteIcon24.png<br /> OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png<br /> OoliteStarter/src/main/resources/oolite_logo.ico<br /> OoliteStarter/src/main/resources/oolite_logo.png<br /> <br /> == Others ==<br /> <br /> * the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)<br /> * the favicon on oolite.space<br /> * the logo on bb.oolite.space<br /> * the favicon on bb.oolite.space<br /> * the logo in the Microsoft Store<br /> * the logo in the FlatHub<br /> * Is there a central repository for AppImages? If so, there.<br /> * the logo on the GitHub site.OoliteStarter/<br /> * the logo on the wiki <br /> * the favicon on the wiki<br /> <br /> = Related = <br /> <br /> See also [[Branding History]]</div>

Hiran https://wiki.alioth.net/index.php?title=Branding&diff=89059 Branding 2026-05-31T09:50:56Z

<p>Hiran: /* Oolite */</p> <hr /> <div>This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.<br /> Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].<br /> <br /> = Icon Change =<br /> <br /> Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.<br /> <br /> == Oolite ==<br /> <br /> * oolite\debian\oolite-logo1.xpm<br /> * oolite\Doc\OoliteRS.odt<br /> * oolite\Documentation\docs\assets\oolite-logo.png<br /> * oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp<br /> * oolite\installers\win32\Oolite.ico<br /> * oolite\installers\win32\Oolite-HDR.ico<br /> * oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp<br /> * oolite\Resources\Images\splash@2x.png<br /> * oolite\Resources\Images\WMicon.bmp<br /> * oolite\Resources\Images\splash.bmp<br /> * oolite\Resources\Images\splash.png<br /> <br /> == Debug Console ==<br /> <br /> oolite-debug-console\images\OoJSC.icns<br /> oolite-debug-console\images\OoJSC.ico<br /> oolite-debug-console\images\OoJSC16x16.png<br /> oolite-debug-console\images\OoJSC24x24.png<br /> oolite-debug-console\images\OoJSC32x32.png<br /> oolite-debug-console\images\OoJSC48x48.png<br /> oolite-debug-console\images\OoJSC64x64.png<br /> oolite-debug-console\images\OoJSC96x96.png<br /> oolite-debug-console\images\OoJSC128x128.png<br /> oolite-debug-console\images\OoJSC192x192.png<br /> oolite-debug-console\images\OoJSC256x256.png<br /> <br /> == Oolite Starter ==<br /> <br /> OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png<br /> OoliteStarter/src/main/resources/icons/OoliteIcon24.png<br /> OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png<br /> OoliteStarter/src/main/resources/oolite_logo.ico<br /> OoliteStarter/src/main/resources/oolite_logo.png<br /> <br /> == Others ==<br /> <br /> * the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)<br /> * the favicon on oolite.space<br /> * the logo on bb.oolite.space<br /> * the favicon on bb.oolite.space<br /> * the logo in the Microsoft Store<br /> * the logo in the FlatHub<br /> * Is there a central repository for AppImages? If so, there.<br /> * the logo on the GitHub site.OoliteStarter/<br /> * the logo on the wiki <br /> * the favicon on the wiki<br /> <br /> = Related = <br /> <br /> See also [[Branding History]]</div>

Hiran https://wiki.alioth.net/index.php?title=Branding&diff=89058 Branding 2026-05-31T09:50:35Z

<p>Hiran: /* Others */</p> <hr /> <div>This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.<br /> Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].<br /> <br /> = Icon Change =<br /> <br /> Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.<br /> <br /> == Oolite ==<br /> <br /> oolite\debian\oolite-logo1.xpm<br /> oolite\Doc\OoliteRS.odt<br /> oolite\Documentation\docs\assets\oolite-logo.png<br /> oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp<br /> oolite\installers\win32\Oolite.ico<br /> oolite\installers\win32\Oolite-HDR.ico<br /> oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp<br /> oolite\Resources\Images\splash@2x.png<br /> oolite\Resources\Images\WMicon.bmp<br /> oolite\Resources\Images\splash.bmp<br /> oolite\Resources\Images\splash.png<br /> <br /> == Debug Console ==<br /> <br /> oolite-debug-console\images\OoJSC.icns<br /> oolite-debug-console\images\OoJSC.ico<br /> oolite-debug-console\images\OoJSC16x16.png<br /> oolite-debug-console\images\OoJSC24x24.png<br /> oolite-debug-console\images\OoJSC32x32.png<br /> oolite-debug-console\images\OoJSC48x48.png<br /> oolite-debug-console\images\OoJSC64x64.png<br /> oolite-debug-console\images\OoJSC96x96.png<br /> oolite-debug-console\images\OoJSC128x128.png<br /> oolite-debug-console\images\OoJSC192x192.png<br /> oolite-debug-console\images\OoJSC256x256.png<br /> <br /> == Oolite Starter ==<br /> <br /> OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png<br /> OoliteStarter/src/main/resources/icons/OoliteIcon24.png<br /> OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png<br /> OoliteStarter/src/main/resources/oolite_logo.ico<br /> OoliteStarter/src/main/resources/oolite_logo.png<br /> <br /> == Others ==<br /> <br /> * the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)<br /> * the favicon on oolite.space<br /> * the logo on bb.oolite.space<br /> * the favicon on bb.oolite.space<br /> * the logo in the Microsoft Store<br /> * the logo in the FlatHub<br /> * Is there a central repository for AppImages? If so, there.<br /> * the logo on the GitHub site.OoliteStarter/<br /> * the logo on the wiki <br /> * the favicon on the wiki<br /> <br /> = Related = <br /> <br /> See also [[Branding History]]</div>

Hiran https://wiki.alioth.net/index.php?title=Developer%27s_Corner&diff=89057 Developer's Corner 2026-05-31T09:49:06Z

<p>Hiran: </p> <hr /> <div>Here you will find information that helps understanding the Oolite source code, build and test the project.<br /> <br /> * [[Contributing to the project]]<br /> * [[Release Process]]<br /> * [[Branding]], [[Branding History]]<br /> * [https://ooliteproject.github.io/oolite/ Oolite API documentation]<br /> * [https://ooliteproject.github.io/oolite/ Doxygen Documentation]<br /> * [https://ooliteproject.github.io/oolite/coverage/index.html Code Coverage Report]<br /> * [[Cross Platform IDEs]]<br /> * [[Compiling with Clang instead of gcc]] (Windows/Linux)<br /> <br /> == OS Specific parts ==<br /> <br /> {| class="wikitable" style="margin:auto"<br /> |+ Operating System dependent stuff<br /> |-<br /> ! Procedure !! Apple Mac !! Linux !! Windows<br /> |-<br /> | Setting up a development environment || [[Development on Apple Mac]], [[Cross Platform IDEs]] || [[Development on Linux]], [[Cross Platform IDEs]] || [[Development on Windows]], [[Cross Platform IDEs]]<br /> |-<br /> | Compiling || [[Compiling on Apple Mac]] || [[Compiling on Linux]] || [[Developing Oolite#On_Windows_2 | Compiling on Windows]]<br /> |-<br /> | Testing || [[Testing on Apple Mac]], [[Common Testing]] || [[Testing on Linux]], [[Common Testing]] || [[Testing on Windows]], [[Common Testing]]<br /> |-<br /> | Packaging into Installer || [[Installer on Apple Mac]] || [[Installer on Linux]] || [[Installer on Windows]]<br /> |-<br /> | Running || [[Running Oolite-Mac]] || ||<br /> |}<br /> <br /> ==Releasing the code==<br /> <br /> Once you developed a while you might no longer be happy that all you have created is called 'nightly' or 'prerelease' or 'unstable'.<br /> <br /> If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]].<br /> <br /> [[Category:Oolite Development]]<br /> <br /> == Hints ==<br /> <br /> The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.<br /> <br /> If you need to update submodules you also need to tell people to update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&t=21470<br /> <br /> To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules</div>

Hiran https://wiki.alioth.net/index.php?title=Branding&diff=89056 Branding 2026-05-31T09:48:27Z

<p>Hiran: Removed redirect to Branding History</p> <hr /> <div>This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.<br /> Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].<br /> <br /> = Icon Change =<br /> <br /> Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.<br /> <br /> == Oolite ==<br /> <br /> oolite\debian\oolite-logo1.xpm<br /> oolite\Doc\OoliteRS.odt<br /> oolite\Documentation\docs\assets\oolite-logo.png<br /> oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp<br /> oolite\installers\win32\Oolite.ico<br /> oolite\installers\win32\Oolite-HDR.ico<br /> oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp<br /> oolite\Resources\Images\splash@2x.png<br /> oolite\Resources\Images\WMicon.bmp<br /> oolite\Resources\Images\splash.bmp<br /> oolite\Resources\Images\splash.png<br /> <br /> == Debug Console ==<br /> <br /> oolite-debug-console\images\OoJSC.icns<br /> oolite-debug-console\images\OoJSC.ico<br /> oolite-debug-console\images\OoJSC16x16.png<br /> oolite-debug-console\images\OoJSC24x24.png<br /> oolite-debug-console\images\OoJSC32x32.png<br /> oolite-debug-console\images\OoJSC48x48.png<br /> oolite-debug-console\images\OoJSC64x64.png<br /> oolite-debug-console\images\OoJSC96x96.png<br /> oolite-debug-console\images\OoJSC128x128.png<br /> oolite-debug-console\images\OoJSC192x192.png<br /> oolite-debug-console\images\OoJSC256x256.png<br /> <br /> == Oolite Starter ==<br /> <br /> OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png<br /> OoliteStarter/src/main/resources/icons/OoliteIcon24.png<br /> OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png<br /> OoliteStarter/src/main/resources/oolite_logo.ico<br /> OoliteStarter/src/main/resources/oolite_logo.png<br /> <br /> == Others ==<br /> <br /> - the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)<br /> - the favicon on oolite.space<br /> - the logo on bb.oolite.space<br /> - the favicon on bb.oolite.space<br /> - the logo in the Microsoft Store<br /> - the logo in the FlatHub<br /> - Is there a central repository for AppImages? If so, there.<br /> - the logo on the GitHub site.OoliteStarter/<br /> - the logo on the wiki <br /> - the favicon on the wiki <br /> <br /> <br /> = Related = <br /> <br /> See also [[Branding History]]</div>

Hiran https://wiki.alioth.net/index.php?title=Talk:Branding&diff=89055 Talk:Branding 2026-05-31T09:37:32Z

<p>Hiran: Hiran moved page Talk:Branding to Talk:Branding History: Name to better match the page's purpose</p> <hr /> <div>#REDIRECT [[Talk:Branding History]]</div>

Hiran https://wiki.alioth.net/index.php?title=Talk:Branding_History&diff=89054 Talk:Branding History 2026-05-31T09:37:32Z

<p>Hiran: Hiran moved page Talk:Branding to Talk:Branding History: Name to better match the page's purpose</p> <hr /> <div>Would it possible to attach all previous logos, icons, fonts ''etc''. to this page, or, at least, hyperlink on this page to repositories of all previous resource materials (with associated dates of having been in use, and record of first introduction/reveal) in this regard? Would it be possible to have this page be the dated, historical record of ''Oolite'' branding development and progression?<br /> <br /> Example: [https://www.livejournal.com/allpics.bml?user=oolite ''Oolite (progress)'' LiveJournal Userpic] 2004apr07tue - ??? ([https://oolite.livejournal.com/profile proof of start-date])<br /> <br /> My concern is that even on the initial 2006-01-03T18:26:46 post of the [https://wiki.alioth.net/index.php?title=Oolite&oldid=1294 ''Oolite''] wikipage, the original, blue logo (in use at the time of the initial posting of that page) has now been replaced by the new, red logo.<br /> <br /> Let not our origins be forgotten, as happens to the location of Old Earth in GalCop Space! ...nor as happened during the [https://wiki.alioth.net/index.php/Great_Deletion Great Deletion].<br /> <br /> Thanks for your consideration of this request.<br /> <br /> --[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 11:08, 4 January 2024 (UTC)<br /> <br /> <br><br><br /> <br /> Thy eminence,<br /> <br /> Phkb uploaded the new logo with the name of the old.<br /> <br /> But. If you ''look'' at the ''pages'' with the files on them (if that is the correct description) you will see that the original is still there, somehow: [[:File:Oolite-logo3.png]] & [[:File:Oolite-logo2.png]].<br /> <br /> Despite my supposed wizardly capabilities, I know not how to emblazon Seventh's original logo on another page here.<br /> <br /> I beg, sir, to remain yours ''etc''.,<br /> <br /> :''Cholmondeley 21:46, 4 January 2024 (UTC)''<br /> <br /> <br><br><br /> <br /> Woo-hoo! Yee-Haw! Yippee-hi-ho-kah-yay! :D I thought those files had been lost. Thank you, Commander Cholmondeley. I'm no wiki-wizard either, but I'll have a go at it.<br /> <br /> ...<br /> <br /> If I understand correctly, could the new, red-logo filenames perhaps be renamed differently, so that they do not clash with the original, blue-logo filenames, and, thus, hopefully, restore the blue logos on historical pages where they belong, and add the red ones to new pages? ...or am I not grasping the full complexity of the situation?<br /> <br /> Commander Cholmondeley, on the Branding wikipage, you refer to File:Oosat 1.png, File:Oosat 2.png, and http://s248731467.onlinehome.us/ ... I agree that Oosat 2.png seems to be logoless, but it also seems to me to be unclear whether the Oosat site/pages were ever supposed to have any official ''Oolite'' logos in the first place that might require preservation. Oosat 1.png has an Elite Wiki logo in the bottom, left-hand corner, but I don't think that's what we're looking for...?<br /> <br /> Also, on the Dizzy's ''Oolite'' Installers download page, that logo seems somewhat less "official", and might merely have been one that Dizzy designed for their own, personal purposes on their own, personal website; not necessarily to represent the ''Oolite'' comOonity as a whole. It does not seem as if it was ever a logo to be considered for display on any official ''Oolite'' website.<br /> <br /> What I have in mind, is the preservation of the original logo(s) that Aegidian designed, and used on his websites/pages, and which might be more-closely compared to the ''Elite'' insignia designed by Philip Castle ([https://www.frontierastro.co.uk/Files/elite_misc.html]). The new, red logo seems to follow this tradition rather nicely, and, since the commOonity was consulted on the ''Oolite'' bulletin boards, and the red logo was incorporated on the official ''Oolite''.space website, I would think that few would argue against the red logo's right to preservation.<br /> <br /> Attempting to preserve a file for every single ''Oolite'' logo out there, might not be practical and exhaustible/exhaustive; there will always be another one that we haven't included yet, and that is simply just more frustration than I am willing to sign up for. ...But ''official'' logos from original media... now those I'm willing to hunt down to the ends of the Earth. (...says I, not knowing what I'm getting myself into...)<br /> <br /> *<br /> <br /> I'll have to speak to my landlord regarding letting you be mine. He's not big on pets. Perhaps I can persuade him to let you stay in the basement. ''etc''. ;p (How am I ever to top such wonderfully-flowery language?)<br /> <br /> --[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 13:09, 7 January 2024 (UTC)<br /> <br /> <br><br><br /> <br /> I would recommend that the two resolutions of the new, red logo be renamed Oolite-logo4-128.png and Oolite-logo4-256.png respectively.<br /> <br /> How to get the Elite Wiki to display those, though, in stead of Oolite-logo3.png... I wouldn't know.<br /> <br /> Hiran, in your original post of the Branding wikipage, you mentioned fonts... Which fonts did you have in mind? Where can those be obtained?<br /> <br /> --[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 04:28, 8 January 2024 (UTC)<br /> <br /> <br /> ----<br /> <br /> Our past wiki-wizards were [[User:Winston|Winston]] (who set this up as the "Elite Wiki" back in the days before Oolite - hence our all-inclusive [[Main Page]] - and who still pays for it) and [[User:Maik|Maik]]. Both are programmers and both ''understand'' it. I merely have learned how to do a few things with it.<br /> <br /> Phkb (also a programmer) uploaded the new logo into the "name-space" (if that is what it is) of the old. So every use of the old was replaced automatically by the use of the new without needing to manually tweak each and every one of them.<br /> <br /> <br /> '''Use of dates on history-tab pages'''<br /> I ''presume'' that (on the logo's "file:" page) clicking on the ''old'' date gives you the ''old'' logo file which you can then download and re-upload with a new name.<br /> <br /> <br /> '''Notice the use of brackets in linking.'''<br /> <br /> '''Single brackets''' for website pages. Uses a ''space'' ( ) to rename<br /> '''Double brackets''' for wiki pages (avoids the little icon and avoids need for entire web address). Uses a ''pipe'' (|) to rename.<br /> <br /> And you can do other things with pipes (in linking to User: pages). And with colons (in linking to Category: pages).<br /> <br /> <br /> '''Dealing with "Category" pages can be complex.'''<br /> <br /> The [[:Category:Lore]] page has sub-categories. And a linked [[Lore]] wiki page which appears at the top of the page list, not in the alphabetical ordering. ''If you examine the "Category" tags on each of those linked pages you should be able to work out how all this was done.''<br /> <br /> Note that the addition of the colon to Category:Lore (-> :Category:Lore) immediately above. That prevents this talk page also being tagged with the Lore category and merely links to that page instead.<br /> <br /> You might find it helpful to browse the [[Special:Categories|list of categories]] and try and make sense of them.<br /> <br /> [[User:Debresser|Debresser]] seems to have spent quite some time pruning the categories to make more sense. I've not done so as I don't yet feel that I have the knowledge to do a decent job.<br /> <br /> The point of these pages seems to be "easy" indexing - where you include a page in an index by merely tagging it, rather than having to manually update an index each time the page changes (as would need to be done with my various manually collated lists of relevant OXPs dotted around this wiki).<br /> <br /> :''Cholmondeley 10:15, 8 January 2024 (UTC)''<br /> ----<br /> <br /> <br><br><br /> <br /> Proposal: I am willing to delete the new, red logo image-files from the ''Elite'' Wiki, rename the highest-resolution version to "''Oolite''-logo4.png", re-upload it, and then edit and replace every single last little hyperlink to ''Oolite''-logo2.png and ''Oolite''-logo3.png in the '''entire''' ''Elite'' Wiki -- on all of five ''other'' hyperlinking wikipages. ;) (Only the highest-resolution version is required, since the ''Elite'' Wiki apparently has the capability to scale images.)<br /> <br /> [https://wiki.alioth.net/index.php/Special:WhatLinksHere/File:Oolite-logo2.png Pages that link to ''Oolite''-logo2.png]<br /> <br /> [https://wiki.alioth.net/index.php/Special:WhatLinksHere/File:Oolite-logo3.png Pages that link to ''Oolite''-logo3.png]<br /> <br /> Howzat? Would this be acceptable to all? :)<br /> <br /> (Then we would be able show all the historical logo-images on this Branding page as well, in stead of merely hyperlinking to the source-file pages. :D )<br /> <br /> --[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 07:27, 10 January 2024 (UTC)<br /> <br /> <br><br><br /> <br /> The file-delete option that I thought I saw previously, apparently is not available to me (anymore?)... There goes my perfect plan in the pants! :/<br /> <br /> This was now discovered after uploading a new version of one of the logo-image files I had uploaded recently, and the new version of the image NOT being replaced into the location where the file is called... This is frustrating. ...when functionality apparently does not function as it is supposedly supposed to. Hm. :/<br /> <br /> --[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 06:29, 15 January 2024 (UTC)<br /> <br /> <br /> <br /> <br /> <br /> You need to speak with Maik (if he has any spare time) about deletion - he understands how it works, and understands rather more about how this wiki works than I do. I'm unhappy to delete something when I don't understand what the consequences are - and I don't. Look what happened when Hiran started deleting stuff on GitHub a couple of months ago - and he's a professional programmer! (https://bb.oolite.space/viewtopic.php?f=2&t=21457)<br /> <br /> ::''Cholmondeley 08:55, 15 January 2024 (UTC)''<br /> <br /> <br><br><br /> <br /> Nah. I don't think I'll bother Maik.<br /> <br /> The interface is less than what is optimal for all our spare times, at the moment.<br /> <br /> Been looking at fandom.com a bit... Not sure if their copyleft policy clashes with any ''Oolite'' licensing, though.<br /> <br /> On the other hand, (1) the ''Elite'' Wiki is here at alioth.net already (thanks to Dylan Smith); (2) migrating it... huge job, methinks; (3) not sure exactly why the grass seems greener on the other side, but it might be, as is usual, because of more plentiful manure... :/<br /> <br /> I guess what I'm saying, is: should the alioth.net ''Elite'' Wiki ''ever'' become borked beyond all practicality anymore, fandom.com might be an alternative that could be considered. In the meanwhile, let's keep what we know we've got.<br /> <br /> --[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 13:36, 19 January 2024 (UTC)</div>

Hiran https://wiki.alioth.net/index.php?title=Branding_History&diff=89052 Branding History 2026-05-31T09:37:31Z

<p>Hiran: Hiran moved page Branding to Branding History: Name to better match the page's purpose</p> <hr /> <div>[[File:Oolite-logo3.png|right]]<br /> = Introduction =<br /> This page attempts to record and preserve the historical heritage of ''Elite''/''Oolite'' branding, specifically in terms of logos, icons and fonts. [https://frontierastro.co.uk/ FrontierAstro] is very useful in this regard.<br /> <br /> Fonts came up from the OpenOffice documentation (Reference Sheet, etc.) that is distributed in PDF format. As soon as the PDFs were generated using open-source software only, it became apparent that the documents were based on fonts only available in Microsoft Windows operating systems. From that moment on, alternatives had to be found.<br /> <br /> This page focuses on ''Elite'' (and its descendant ''Oolite'') since (1) it is the origin of all the related brands, (2) and it has had a multitude of different versions, many of them introducing variations on the theme, while (3) the ''Frontier'' games do not seem to have had any significant brand-variations along the way. For completeness, though, the ''Frontier'' logos and icons will also be included, but [https://duckduckgo.com/?q=elite+dangerous+logos&va=p&atb=v355-1&iax=images&ia=images ''Elite: Dangerous''] has an impractically-large amount of branding for the purposes of the simple historical-record intended here.<br /> <br /> = ''Elite'' branding history =<br /> 1984... [[Classic_Elite|Elite]]... [[David Braben]], [[Ian Bell]], [[Robert Holdstock]], and... Philip Castle.<br /> <br /> The first three names were responsible for the programming and the documentation ([http://www.elitehomepage.org/playguide.htm ''Elite'' Players' Guide]; [https://archive.org/details/elite_acornsoft_manual/mode/1up?view=theater ''The Space Trader's Flight Training Manual''] and [https://openretro.org/file/ec43acc68931c84951a13b6285ed4ccd64b5b787 ''The Dark Wheel''], Stock Code Numbers for the latter: SBG38/B1 and SBG38/B3, respectively, etc.). However, the ''Elite'' simulator would probably not have had such a successful market-entrance had it not been for the fourth gentleman's eye-catching skills as an airbrush artist.<br /> <br /> On the [https://www.frontierastro.co.uk/Files/elite_misc.html "FrontierAstro ''Elite'' - Various Items"] page, approximately halfway down -- as if "quasi-[https://www.languagehumanities.org/what-is-a-chiastic-structure.htm chiastically]" in the central focal-point of the nine topic-sections -- he is briefly introduced... but his work is pretty much everywhere on that page.<br /> <br /> On [http://www.iancgbell.clara.net/elite/ Ian Bell's website], in the ''Elite'' Archives, in the file [http://www.elitehomepage.org/archive/a4120001.png a4120001.png], the "DECEMBER 1984" Acorn News report (scan), in the second column, third paragraph; and in [https://www.reddit.com/r/IAmA/comments/15od2s/comment/c7qdaj8/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button David Braben's 2013 reddit ''Elite: Dangerous'' AMA], [https://en.wikipedia.org/wiki/Philip_Castle Philip Castle] is authoritatively identified as the designer of the original ''Elite'' logo. (The [https://mythology.net/mythical-creatures/griffin/ "Griffin thing"], as mentioned by Braben, as a supposed element of the ''Elite'' logo, is debatable, though.)<br /> <br /> = ''Oolite'' branding history =<br /> > 7 April 2004, [[User:Aegidian|Aegidian]]'s [[Aegidian_devlog|''Oolite'' (progress)]] [https://oolite.livejournal.com/profile LiveJournal] introduced the [https://wiki.alioth.net/index.php/File:Oolite-logo1.png ''Oolite'' userpic], which can be downloaded from that [https://www.livejournal.com/allpics.bml?user=oolite page] (right-click > Save Image As...) as a 100 pixels x 100 pixels .png image.<br /> <br /> > 16:15, 3 January 2006, Rxke apparently uploaded to the ''Elite'' Wiki a 128 x 128 [https://wiki.alioth.net/index.php/File:Oolite-logo2.png ''Oolite'' logo] version of the userpic.<br /> <br /> > 12:57, 7 May 2011, Ahruman uploaded to the ''Elite'' Wiki the 256 x 256 [https://wiki.alioth.net/index.php/File:Oolite-logo3.png "New (2011) ''Oolite'' icon"] by Eugene Chernyakov (seventh).<br /> <br /> > Mon Oct 23, 2023 12:39 am, on the ''Oolite'' Bulletin Boards, in the Discussion forum, the [https://bb.oolite.space/viewtopic.php?f=2&t=21464 "New splash screen and icon"] thread was posted by phkb, in which was suggested that the ''Oolite'' splash screen and icon had been around for a while now, and it was proposed that they were about due for a refresh. This discussion led to the new, red versions of the [https://wiki.alioth.net/index.php/File:Oolite-logo2.png 128 x 128] and [https://wiki.alioth.net/index.php/File:Oolite-logo3.png 256 x 256] logo-images, and the new black-and-white version of the [https://wiki.alioth.net/index.php/File:Oolite-IconBW.png ''Oolite'' icon], all three uploaded to the ''Elite'' Wiki as new version of the old filenames six days later by Phkb. The new, red logo was also incorporated in the official [https://oolite.space/ oolite.space] website.<br /> <br /> = Caveat & HowTo =<br /> <br /> The ''Elite'' Wiki allows the uploading of new versions of old files. However, "new version" should be defined and understood as "improved version", rather than "different version", where "improved" could mean "increased resolution", or "more universally-applicable file format", or other more subtle edits, in order to establish the [https://wiki.alioth.net/index.php/File:Elite-logo1988-3_manual_front_cover_(rotated).jpg originally-intended, '''best'''] version of the file. Uploading a ''different'' version of an existing file causes that file to be replaced universally throughout the entire ''Elite'' Wiki -- even on old, "history" pages of ''Elite'' wikipages (e.g.: on the very first, 05:22, 14 February 2006 version of the [https://wiki.alioth.net/index.php?title=Oolite_Main_Page&oldid=3181 ''Oolite'' Main Page] the original, blue, 2006 logo had been replaced by the new, red, 2023 logo). This is not a black-and-white, easily-defined, well-behaved, simple and straight-forward issue, and there could, arguably, be many ambiguous scenarios and exceptions to whatever guidelines might have been imagined.<br /> <br /> Therefore -- ''if in doubt'' -- it is safer, in terms of the preservation of the historical integrity of the ''Elite'' Wiki (although it also requires more work), to upload a "new" version of an existing file under a correspondingly-new filename with the intention of replacing the old version on subsequent (and not previous, historical) wikipages. When a "new" version of an existing file is considered for upload, the following methodology is recommended. <br /> <br /> '''HowTo'''<br /> <br /> On an ordinary ''Elite'' wikipage, in the left-hand margin, under "tools" > "Special pages" > "Media reports and uploads" > "File list", in the "Search for media name" search box, enter a known portion of the filename (e.g.: "logo" or "icon"), click the "Include old versions of files" tick-box and then the "Go" button; then click the name-hyperlink that is associated with the desired thumbnail. Then, again, in the left-hand margin, under "tools" > "What links here", in order to determine where on which wikipages which hyperlinks or references would potentially need to be updated to a new filename, so that history pages will not unintentionally be [https://en.wikipedia.org/wiki/Ministries_in_Nineteen_Eighty-Four#Ministry_of_Truth Minitrue]-redacted.<br /> <br /> Therefore, in an attempt (1) to prevent a loss of the commOonity's heritage on ''Elite'' Wiki history pages, and (2) to facilitate easier searching for older logo-versions, it is recommended that future, new-logo designs be named according to, and uploaded under filenames conforming to the established naming-scheme of "''Oolite''-logo#", where # is the next number in the sequence, and that all of the hyperlinks throughout the ''Elite'' wiki be updated accordingly. It is recommended that only a single, highest-resolution logo-image be uploaded, since the ''Elite'' Wiki has the functionality to scale the logo images: <nowiki>[[File:oolite-logo#.png|196px]]</nowiki>. A similar, numbered naming-scheme, although not implemented as yet, is also recommended for icons.<br /> <br /> If an older logo (or icon) might be required for any purpose, the [https://wiki.alioth.net/index.php/Special:ListFiles?limit=1000&ilsearch=logo&user=&ilshowall=1 "logo" File list search-page] is recommended (substitute "icon" in stead of "logo", if required). Include old versions of files.<br /> <br /> = Original Logos and Icons =<br /> <br /> ''' ''Elite'' '''<br /> <br /> ''Elite'' logos have been sourced from box art, manual covers, half-title, title and other pages, and ''The Dark Wheel'''s front covers. It appears that other, minor media, included in any package, only have variations on the various themes in that package. The logos below are identified by, and arranged according to their dates and usage of first appearance. Hover over the images for descriptions. Consult [https://frontierastro.co.uk/ FrontierAstro] to see how some of these logos have been re-used for different elements of various versions.<br /> <br /> 1984<br /> [[File:Elite-logo1984-1 box art & The Dark Wheel front cover.jpg|128px|box art & The Dark Wheel front cover]]<br /> [[File:Elite-logo1984-2 manual front cover.png|128px|manual front-cover]]<br /> [[File:Elite-logo1984-3 manual half-title page.png|128px|manual half-title page]]<br /> <br /> 1985<br /> [[File:Elite-logo1985-1 box art & manual front cover.png|128px|box art & manual front-cover]]<br /> [[File:Elite-logo1985-2 Spectrum manual title page.png|128px|Spectrum manual title-page]]<br /> [[File:Elite-logo1985-4 The Dark Wheel front cover (rotated).jpg|128px|The Dark Wheel front cover]]<br /> <br /> 1988<br /> [[File:Elite-logo1988-1 box art.png|128px|box art]]<br /> [[File:Elite-logo1988-3 manual front cover (rotated).jpg|128px|manual front-cover]]<br /> <br /> 1991<br /> [[File:Elite-logo1991-1 ArcElite manual front cover.png|128px|ArcElite manual front-cover]]<br /> [[File:Elite-logo1991-2 ArcElite manual title page.png|128px|ArcElite manual title-page]]<br /> [[File:Elite-logo1991-3 Elite Plus UK box art & manual front cover.png|128px|Elite Plus UK box art & manual front-cover]]<br /> [[File:GalCop-logo1991-4 Elite Plus manual.png|128px|Elite Plus manual]]<br /> [[File:Tri-Alliance-logo1991-5 ArcElite manual.png|128px|ArcElite manual - Tri-Alliance logo]]<br /> <br /> Some logos were originally designed skew by a few degrees anticlockwise. The original, skew versions are available from the [https://wiki.alioth.net/index.php/Special:ListFiles?limit=1000&ilsearch=logo&user=&ilshowall=1 "logo" File list search-page]. For ease of comparison, and for streamlining this page's layout, only the upright-rotated logos are shown here.<br /> <br /> The 1991 ArcElite manual title-page and 1984 manual front-cover logos seem to be the cleanest, for the purposes of using them as potential templates for future designs.<br /> <br /> From time to time, among the logos, there does seem to be a subtle motif of "ascending to the next level" (3D), "accelerating", and then also "breaking out of the frame" and "transcending of boundaries", as it were; c.f.: 1984 box art & ''The Dark Wheel'' front cover (even extending off-page), 1985 ''The Dark Wheel'' front cover, and 1988 manual front-cover. The graphics for the [https://ia601304.us.archive.org/19/items/Elite_Plus_Manual/Elite_Plus_Manual_text.pdf 1991 ''Elite Plus'' manual's] title page, Cobra Mk III (p. 13), ''Observer's Guide to Ships in Service'' (pp. 67 - 86), and the ''Imprint'' novella's title page (p. "87"), all subtly communicate this repeated motif as well. In comparison with the other logos, and within itself, the 1991 ''Elite Plus'' simulator's logo also adds an extra, juxtaposed element of realism...<br /> <br /> <br /> <br /> ''' ''Oolite'' '''<br /> <br /> 2004<br /> [[File:Oolite-logo1.png|128px|Aegidian LiveJournal 100px x 100px userpic]]<br /> <br /> <br /> <br /> ''' ''Frontier'' ''' (for completeness)<br /> <br /> 1993<br /> [[File:Frontier- Elite II-logo1993 box art.png|128px|box art]]<br /> [[File:Frontier- Elite II-logo1993 manual front cover.png|128px|manual front-cover]]<br /> <br /> 1995<br /> [[File:Frontier- First Encounters-logo1995 box art.jpg|128px|box art]]<br /> [[File:Frontier- First Encounters-logo1995 manual front cover.jpg|128px|manual front-cover]]<br /> <br /> <br /> <br /> = Logos and Icons on the ''Elite'' Wiki =<br /> <br /> ''' ''Elite'' '''<br /> <br /> 2006<br /> <br /> Wiki functionality is broken for me. I did what I could, to the best of my abilities, but I am apparently not capable/allowed to do what needs to be done here further anymore. Thanks. It's been fun, while it lasted. I'll leave this in the capable hands of other, more powerful people now.<br /> <br /> ''' ''Oolite'' '''<br /> <br /> 2006<br /> <br /> <br /> 2011<br /> <br /> <br /> 2023<br /> <br /> <br /> <br /> ''' ''Frontier'' ''' (for completeness)<br /> <br /> 2006<br /> <br /> <br /> <br /> = Fonts =<br /> <br /> The font used in-game is a custom, mono-spaced font. ''Oolite'' does not work with Truetype or Freetype fonts.<br /> <br /> The fonts in the documentation are ...<br /> <br /> The fonts used in the website oolite.space are ...<br /> <br /> The fonts used in the wiki are ...<br /> <br /> The fonts used in the forum are ...<br /> <br /> [[Category:Classic]][[Category:Oolite]][[Category:Factual]]</div>

Hiran https://wiki.alioth.net/index.php?title=Branding&diff=89053 Branding 2026-05-31T09:37:31Z

<p>Hiran: Hiran moved page Branding to Branding History: Name to better match the page's purpose</p> <hr /> <div>#REDIRECT [[Branding History]]</div>

Hiran https://wiki.alioth.net/index.php?title=Oolite_Instruction_Manual&diff=88772 Oolite Instruction Manual 2026-05-14T21:33:59Z

<p>Hiran: /* Playing the game */</p> <hr /> <div>==Installing the game==<br /> * [[Running Oolite-Mac|Build, Install and run Oolite on Mac OS X]] (Oolite v.1.92 is not available for the AppleMac)<br /> * [[Running Oolite-Linux|Build, Install and run Oolite on Linux]]<br /> * [[Running Oolite-Windows|Build, Install and run Oolite on Windows]]<br /> * [[Running Oolite-Fedora Core 5|Build, Install and run Oolite on Fedora Core 5]]<br /> * [[Running Oolite-Unix|Build, Install and run Oolite on BSD and Irix]]<br /> <br /> Note that from release 1.77 onwards two different release configurations are available for download: "deployment" which includes full optimisation and is most suitable for those just wanting to play the game, and "test" which includes additional debugging and development tools, and is intended for OXP development. If you are unsure, we recommend the "deployment release" - it is easy to convert it into a "test release" later.<br /> <br /> === More general links ===<br /> * [https://bb.oolite.space/viewtopic.php?f=2&t=16255 Source Code and Ideas question] (2014: v.1.77.1) - handling GitHub, how to change maximum amount sellable, elite rankings, legal status<br /> <br /> ==A background to the game==<br /> * [[Alien Items]] - A series of short stories which set the scene.<br /> * [http://www.alioth.net/Fiction/oolitestory.pdf The Virtuous Misfortune] - A story that sets the scene (now included in "Alien Items")<br /> * [[Status Quo]] - Elite came with a Novella called 'The Dark Wheel', which set the scene for that game. 'Status Quo' aims to do the same thing for 'Oolite', introducing Commander Jamesons to the 'Ooniverse'... Status Quo is the first part of a five part series known as the [[Oolite Saga]].<br /> * [[Calliope|Calliope - a Captain Hesperus adventure]] - An episode from the unorthodox life of the commander of the ''Dubious Profit''<br /> * [[Powers and Organisations]] - Some histories of the various corporations and powers, both legal and illicit, that exist in the Oolite Galaxies.<br /> * [[Mr Gimlet]] - A wise Blue Frog aboard Lave Station has some tips for new Commanders.<br /> * The ''[[Rough Guide to the Ooniverse]]'' – A brief overview of the inhabitants, customs and cultures of Lave and other nearby worlds.<br /> <br /> ==Playing the game==<br /> * [https://github.com/OoliteProject/oolite/blob/master/Doc/OoliteRS.odt Download OoliteRS.odt] or access [https://oolite.readthedocs.io/en/latest/reference/ online] - Essential info reference sheet for a quick start<br /> * Ship's Manual - available through the [[Ship's Library OXP]]<br /> * [[Pilot's Reference Manual]]<br /> * [[Oolite Docking Clearance Protocol (v1.72 or later)|Docking Clearance Protocol]]<br /> * [[How to Dock|How to Dock]]<br /> * [[Oolite Equipment|Equipment]] (& [[Priming Equipment]] for OXPs)<br /> * [[Oolite Trading|Trading]]<br /> * [[Career Options]]<br /> * [[Oolite Tactics|General Combat Tactics]]<br /> :* [[Dealing with piracy (Oolite)|How to deal with pirates]]<br /> :* [[Dealing with Thargoids|How to deal with Thargoid ambushes]]<br /> :* [[Laser tactics]]<br /> :* [[Missile tactics]]<br /> :* [[Using weapons of mass destruction|WMD tactics]]<br /> * [[IFF system]]<br /> * [[Fuel Scoops|Scooping fuel and cargo]]<br /> * [[Contracts]]<br /> * [[Oolite Keyboard Controls|Keyboard Controls]]<br /> * [[Dizzy's guide to Setting up Joystick Axis Profiles|Setting up Joystick Axis Profiles]]<br /> * [[Oolite Voice Control|Voice Control]]<br /> * [[Oolite Missions|Missions]]<br /> <br /> ==Technical help and troubleshooting==<br /> * [[Location of Oolite saved settings]]<br /> * [[Hidden Settings in Oolite]]<br /> * [https://bb.oolite.space/ Oolite Bulletins Forum]<br /> * [[Oolite FAQ|Oolite Frequently Asked Questions (FAQ)]]<br /> * [[Joystick problems (Linux)]]<br /> <br /> [[Category:Oolite]][[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Oolite_Instruction_Manual&diff=88771 Oolite Instruction Manual 2026-05-14T21:33:21Z

<p>Hiran: /* Playing the game */</p> <hr /> <div>==Installing the game==<br /> * [[Running Oolite-Mac|Build, Install and run Oolite on Mac OS X]] (Oolite v.1.92 is not available for the AppleMac)<br /> * [[Running Oolite-Linux|Build, Install and run Oolite on Linux]]<br /> * [[Running Oolite-Windows|Build, Install and run Oolite on Windows]]<br /> * [[Running Oolite-Fedora Core 5|Build, Install and run Oolite on Fedora Core 5]]<br /> * [[Running Oolite-Unix|Build, Install and run Oolite on BSD and Irix]]<br /> <br /> Note that from release 1.77 onwards two different release configurations are available for download: "deployment" which includes full optimisation and is most suitable for those just wanting to play the game, and "test" which includes additional debugging and development tools, and is intended for OXP development. If you are unsure, we recommend the "deployment release" - it is easy to convert it into a "test release" later.<br /> <br /> === More general links ===<br /> * [https://bb.oolite.space/viewtopic.php?f=2&t=16255 Source Code and Ideas question] (2014: v.1.77.1) - handling GitHub, how to change maximum amount sellable, elite rankings, legal status<br /> <br /> ==A background to the game==<br /> * [[Alien Items]] - A series of short stories which set the scene.<br /> * [http://www.alioth.net/Fiction/oolitestory.pdf The Virtuous Misfortune] - A story that sets the scene (now included in "Alien Items")<br /> * [[Status Quo]] - Elite came with a Novella called 'The Dark Wheel', which set the scene for that game. 'Status Quo' aims to do the same thing for 'Oolite', introducing Commander Jamesons to the 'Ooniverse'... Status Quo is the first part of a five part series known as the [[Oolite Saga]].<br /> * [[Calliope|Calliope - a Captain Hesperus adventure]] - An episode from the unorthodox life of the commander of the ''Dubious Profit''<br /> * [[Powers and Organisations]] - Some histories of the various corporations and powers, both legal and illicit, that exist in the Oolite Galaxies.<br /> * [[Mr Gimlet]] - A wise Blue Frog aboard Lave Station has some tips for new Commanders.<br /> * The ''[[Rough Guide to the Ooniverse]]'' – A brief overview of the inhabitants, customs and cultures of Lave and other nearby worlds.<br /> <br /> ==Playing the game==<br /> * [https://github.com/OoliteProject/oolite/blob/master/Doc/OoliteRS.doc Download OoliteRS.doc] or access [https://oolite.readthedocs.io/en/latest/reference/ online] - Essential info reference sheet for a quick start<br /> * Ship's Manual - available through the [[Ship's Library OXP]]<br /> * [[Pilot's Reference Manual]]<br /> * [[Oolite Docking Clearance Protocol (v1.72 or later)|Docking Clearance Protocol]]<br /> * [[How to Dock|How to Dock]]<br /> * [[Oolite Equipment|Equipment]] (& [[Priming Equipment]] for OXPs)<br /> * [[Oolite Trading|Trading]]<br /> * [[Career Options]]<br /> * [[Oolite Tactics|General Combat Tactics]]<br /> :* [[Dealing with piracy (Oolite)|How to deal with pirates]]<br /> :* [[Dealing with Thargoids|How to deal with Thargoid ambushes]]<br /> :* [[Laser tactics]]<br /> :* [[Missile tactics]]<br /> :* [[Using weapons of mass destruction|WMD tactics]]<br /> * [[IFF system]]<br /> * [[Fuel Scoops|Scooping fuel and cargo]]<br /> * [[Contracts]]<br /> * [[Oolite Keyboard Controls|Keyboard Controls]]<br /> * [[Dizzy's guide to Setting up Joystick Axis Profiles|Setting up Joystick Axis Profiles]]<br /> * [[Oolite Voice Control|Voice Control]]<br /> * [[Oolite Missions|Missions]]<br /> <br /> ==Technical help and troubleshooting==<br /> * [[Location of Oolite saved settings]]<br /> * [[Hidden Settings in Oolite]]<br /> * [https://bb.oolite.space/ Oolite Bulletins Forum]<br /> * [[Oolite FAQ|Oolite Frequently Asked Questions (FAQ)]]<br /> * [[Joystick problems (Linux)]]<br /> <br /> [[Category:Oolite]][[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Common_Testing&diff=88528 Common Testing 2026-04-29T19:48:26Z

<p>Hiran: /* Comparison */</p> <hr /> <div>[[File:FPS report.png|right|400px]]<br /> Here are some tests that can be performed regardless of the operating system.<br /> <br /> == Performance Test ==<br /> <br /> The main functionality in Oolite is to process the "game loop". This reads user input, processes the world including running all your OXP/OXZs, and then renders out the world view. For meaningful tests you need to have a repeatable base. A good metric for performance is the number of [[Frame rate|frames per second]] (FPS) that Oolite can process.<br /> <br /> If you want to check performance, you must check with FPS uncapped, otherwise you are always getting v-sync FPS, which is usually a low number like 60 for a 60Hz monitor, 144 for a 144Hz one ''etc''. <br /> <br /> Add the '''"animation_timer_interval" = x;''' in your OoliteDefaults.plist, where x is 1.0/Maximum FPS You Want To Achieve. I usually set it to 0.001 which tells Oolite to "go for 1000 FPS if you can". Then you can compare actual performance between builds.<br /> <br /> Also, disable v-sync to have uncapped FPS. You do this by setting the OoliteDefaults.plist key '''"v-sync" = NO;'''.<br /> <br /> When comparing the performance of builds, always check with more or less the same number of entities in the system. If in one case you get 250 entities and in the other you get 70, then results may be biased (it takes much more processing power to manage the 250). Try to compare instances where the two system entity numbers are as close as possible. Shift+F shows you this info in the Oolite "Test Release" builds. Phkb wrote an expansion for that: [https://app.box.com/s/xrkkr5ylizshjng2dpc8uu9q6b39zt49 CustomPopulator.oxp.zip]. And as other OXP/OXZs may inhibit the build performance, make sure this is the only one you are running on top of a [[Vanilla game]].<br /> <br /> After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.<br /> <br /> === Example ===<br /> <br /> Here in ASCII Plist format:<br /> <br /> {<br /> "Jameson-humbletrash" = "-29624";<br /> "animation_timer_interval" = "0.001";<br /> "debug-settings-override" = {<br /> };<br /> "gamma-value" = 1;<br /> "v-sync" = no;<br /> "volume_control" = "0.5";<br /> "window_height" = 1043;<br /> "window_width" = 1920;<br /> }<br /> <br /> <br /> Or the same as XML:<br /> <br /> <?xml version="1.0" encoding="UTF-8"?><br /> <!DOCTYPE plist PUBLIC "-//GNUstep//DTD plist 0.9//EN" "http://www.gnustep.org/plist-0_9.xml"><br /> <plist version="0.9"><br /> <dict><br /> <key>NSGlobalDomain</key><br /> <dict><br /> </dict><br /> <key>oolite</key><br /> <dict><br /> <key>Jameson-humbletrash</key><br /> <integer>-29624</integer><br /> <key>animation_timer_interval</key><br /> <real>0.001</real><br /> <key>gamma-value</key><br /> <real>1</real><br /> <key>v-sync</key><br /> <false/><br /> <key>volume_control</key><br /> <real>0.5</real><br /> <key>window_height</key><br /> <integer>1043</integer><br /> <key>window_width</key><br /> <integer>1920</integer><br /> </dict><br /> </dict><br /> </plist><br /> <br /> === Note ===<br /> More of the configuration file's settings are documented on the [[Hidden Settings in Oolite]] wiki page.<br /> <br /> == Comparison ==<br /> <br /> Now we need to compare several such tests in order to see patterns. To facilitate this and also communicate to others, start filling in a table like this:<br /> <br /> {| class="wikitable" style="margin:auto"<br /> |+ Caption text<br /> |-<br /> ! Oolite Version/Build/package !! Installed expansions !! Amount of entities !! screen/window size !! perceived FPS<br /> |-<br /> | 1.90/debug/.run || CustomPopulator || 360 || 800x600 || 70<br /> |-<br /> | 1.92/test/appimage || CustomPopulator || 358 || 1024x768 || 35<br /> |-<br /> | 1.93/flatpak/release || CustomPopulator || 360 || 1233x700 || 40<br /> |}<br /> <br /> == Links ==<br /> *[[Frame rate]]<br /> *[[Developer's Corner]]<br /> *[[User:Hiran|Hiran]]</div>

Hiran https://wiki.alioth.net/index.php?title=Common_Testing&diff=88527 Common Testing 2026-04-29T19:46:52Z

<p>Hiran: /* Example */</p> <hr /> <div>[[File:FPS report.png|right|400px]]<br /> Here are some tests that can be performed regardless of the operating system.<br /> <br /> == Performance Test ==<br /> <br /> The main functionality in Oolite is to process the "game loop". This reads user input, processes the world including running all your OXP/OXZs, and then renders out the world view. For meaningful tests you need to have a repeatable base. A good metric for performance is the number of [[Frame rate|frames per second]] (FPS) that Oolite can process.<br /> <br /> If you want to check performance, you must check with FPS uncapped, otherwise you are always getting v-sync FPS, which is usually a low number like 60 for a 60Hz monitor, 144 for a 144Hz one ''etc''. <br /> <br /> Add the '''"animation_timer_interval" = x;''' in your OoliteDefaults.plist, where x is 1.0/Maximum FPS You Want To Achieve. I usually set it to 0.001 which tells Oolite to "go for 1000 FPS if you can". Then you can compare actual performance between builds.<br /> <br /> Also, disable v-sync to have uncapped FPS. You do this by setting the OoliteDefaults.plist key '''"v-sync" = NO;'''.<br /> <br /> When comparing the performance of builds, always check with more or less the same number of entities in the system. If in one case you get 250 entities and in the other you get 70, then results may be biased (it takes much more processing power to manage the 250). Try to compare instances where the two system entity numbers are as close as possible. Shift+F shows you this info in the Oolite "Test Release" builds. Phkb wrote an expansion for that: [https://app.box.com/s/xrkkr5ylizshjng2dpc8uu9q6b39zt49 CustomPopulator.oxp.zip]. And as other OXP/OXZs may inhibit the build performance, make sure this is the only one you are running on top of a [[Vanilla game]].<br /> <br /> After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.<br /> <br /> === Example ===<br /> <br /> Here in ASCII Plist format:<br /> <br /> {<br /> "Jameson-humbletrash" = "-29624";<br /> "animation_timer_interval" = "0.001";<br /> "debug-settings-override" = {<br /> };<br /> "gamma-value" = 1;<br /> "v-sync" = no;<br /> "volume_control" = "0.5";<br /> "window_height" = 1043;<br /> "window_width" = 1920;<br /> }<br /> <br /> <br /> Or the same as XML:<br /> <br /> <?xml version="1.0" encoding="UTF-8"?><br /> <!DOCTYPE plist PUBLIC "-//GNUstep//DTD plist 0.9//EN" "http://www.gnustep.org/plist-0_9.xml"><br /> <plist version="0.9"><br /> <dict><br /> <key>NSGlobalDomain</key><br /> <dict><br /> </dict><br /> <key>oolite</key><br /> <dict><br /> <key>Jameson-humbletrash</key><br /> <integer>-29624</integer><br /> <key>animation_timer_interval</key><br /> <real>0.001</real><br /> <key>gamma-value</key><br /> <real>1</real><br /> <key>v-sync</key><br /> <false/><br /> <key>volume_control</key><br /> <real>0.5</real><br /> <key>window_height</key><br /> <integer>1043</integer><br /> <key>window_width</key><br /> <integer>1920</integer><br /> </dict><br /> </dict><br /> </plist><br /> <br /> === Note ===<br /> More of the configuration file's settings are documented on the [[Hidden Settings in Oolite]] wiki page.<br /> <br /> == Comparison ==<br /> <br /> Now we need to compare several such tests in order to see patterns. To facilitate this and also communicate to others, start filling in a table like this:<br /> <br /> {| class="wikitable" style="margin:auto"<br /> |+ Caption text<br /> |-<br /> ! Oolite Version/Build/package !! Installed expansions !! Amount of entities !! screen/window size !! perceived FPS<br /> |-<br /> | 1.90/debug/.run || CustomPopulator || 360 || 800x600 || 70<br /> |-<br /> | 1.92/appimage/test || CustomPopulator || 358 || 1024x768 || 35<br /> |-<br /> | 1.93/flatpak/release || CustomPopulator || 360 || 1233x700 || 40<br /> |}<br /> <br /> == Links ==<br /> *[[Frame rate]]<br /> *[[Developer's Corner]]<br /> *[[User:Hiran|Hiran]]</div>

Hiran https://wiki.alioth.net/index.php?title=Common_Testing&diff=88526 Common Testing 2026-04-29T19:46:08Z

<p>Hiran: /* Performance Test */</p> <hr /> <div>[[File:FPS report.png|right|400px]]<br /> Here are some tests that can be performed regardless of the operating system.<br /> <br /> == Performance Test ==<br /> <br /> The main functionality in Oolite is to process the "game loop". This reads user input, processes the world including running all your OXP/OXZs, and then renders out the world view. For meaningful tests you need to have a repeatable base. A good metric for performance is the number of [[Frame rate|frames per second]] (FPS) that Oolite can process.<br /> <br /> If you want to check performance, you must check with FPS uncapped, otherwise you are always getting v-sync FPS, which is usually a low number like 60 for a 60Hz monitor, 144 for a 144Hz one ''etc''. <br /> <br /> Add the '''"animation_timer_interval" = x;''' in your OoliteDefaults.plist, where x is 1.0/Maximum FPS You Want To Achieve. I usually set it to 0.001 which tells Oolite to "go for 1000 FPS if you can". Then you can compare actual performance between builds.<br /> <br /> Also, disable v-sync to have uncapped FPS. You do this by setting the OoliteDefaults.plist key '''"v-sync" = NO;'''.<br /> <br /> When comparing the performance of builds, always check with more or less the same number of entities in the system. If in one case you get 250 entities and in the other you get 70, then results may be biased (it takes much more processing power to manage the 250). Try to compare instances where the two system entity numbers are as close as possible. Shift+F shows you this info in the Oolite "Test Release" builds. Phkb wrote an expansion for that: [https://app.box.com/s/xrkkr5ylizshjng2dpc8uu9q6b39zt49 CustomPopulator.oxp.zip]. And as other OXP/OXZs may inhibit the build performance, make sure this is the only one you are running on top of a [[Vanilla game]].<br /> <br /> After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.<br /> <br /> === Example ===<br /> <br /> Here in ASCII Plist format:<br /> <br /> {<br /> "Jameson-humbletrash" = "-29624";<br /> "animation_timer_interval" = "0.001";<br /> "debug-settings-override" = {<br /> };<br /> "gamma-value" = 1;<br /> "v-sync" = no;<br /> "volume_control" = "0.5";<br /> "window_height" = 1043;<br /> "window_width" = 1920;<br /> }<br /> <br /> <br /> Or the same as XML:<br /> <br /> <?xml version="1.0" encoding="UTF-8"?><br /> <!DOCTYPE plist PUBLIC "-//GNUstep//DTD plist 0.9//EN" "http://www.gnustep.org/plist-0_9.xml"><br /> <plist version="0.9"><br /> <dict><br /> <key>NSGlobalDomain</key><br /> <dict><br /> </dict><br /> <key>oolite</key><br /> <dict><br /> <key>Jameson-humbletrash</key><br /> <integer>-29624</integer><br /> <key>animation_timer_interval</key><br /> <real>0.001</real><br /> <key>gamma-value</key><br /> <real>1</real><br /> <key>v-sync</key><br /> <integer>0</integer><br /> <key>volume_control</key><br /> <real>0.5</real><br /> <key>window_height</key><br /> <integer>1043</integer><br /> <key>window_width</key><br /> <integer>1920</integer><br /> </dict><br /> </dict><br /> </plist><br /> <br /> === Note ===<br /> More of the configuration file's settings are documented on the [[Hidden Settings in Oolite]] wiki page.<br /> <br /> == Comparison ==<br /> <br /> Now we need to compare several such tests in order to see patterns. To facilitate this and also communicate to others, start filling in a table like this:<br /> <br /> {| class="wikitable" style="margin:auto"<br /> |+ Caption text<br /> |-<br /> ! Oolite Version/Build/package !! Installed expansions !! Amount of entities !! screen/window size !! perceived FPS<br /> |-<br /> | 1.90/debug/.run || CustomPopulator || 360 || 800x600 || 70<br /> |-<br /> | 1.92/appimage/test || CustomPopulator || 358 || 1024x768 || 35<br /> |-<br /> | 1.93/flatpak/release || CustomPopulator || 360 || 1233x700 || 40<br /> |}<br /> <br /> == Links ==<br /> *[[Frame rate]]<br /> *[[Developer's Corner]]<br /> *[[User:Hiran|Hiran]]</div>

Hiran https://wiki.alioth.net/index.php?title=Common_Testing&diff=88483 Common Testing 2026-04-23T19:16:06Z

<p>Hiran: </p> <hr /> <div>[[File:FPS report.png|right|400px]]<br /> Here are some tests that can be performed regardless of the operating system.<br /> <br /> == Performance Test ==<br /> <br /> The main functionality in Oolite is to process the "game loop". This reads user input, processes the world including running all your OXP/OXZs, and then renders out the world view. For meaningful tests you need to have a repeatable base. A good metric for performance is the number of [[Frame rate|frames per second]] (FPS) that Oolite can process.<br /> <br /> If you want to check performance, you must check with FPS uncapped, otherwise you are always getting v-sync FPS, which is usually a low number like 60 for a 60Hz monitor, 144 for a 144Hz one ''etc''. <br /> <br /> Add the '''"animation_timer_interval" = x;''' in your OoliteDefaults.plist, where x is 1.0/Maximum FPS You Want To Achieve. I usually set it to 0.001 which tells Oolite to "go for 1000 FPS if you can". Then you can compare actual performance between builds.<br /> <br /> Also, disable v-sync to have uncapped FPS. You do this by setting the OoliteDefaults.plist key '''"v-sync" = NO;'''.<br /> <br /> When comparing the performance of builds, always check with more or less the same number of entities in the system. If in one case you get 250 entities and in the other you get 70, then results may be biased (it takes much more processing power to manage the 250). Try to compare instances where the two system entity numbers are as close as possible. Shift+F shows you this info in the Oolite "Test Release" builds. Phkb wrote an expansion for that: [https://app.box.com/s/xrkkr5ylizshjng2dpc8uu9q6b39zt49 CustomPopulator.oxp.zip]. And as other OXP/OXZs may inhibit the build performance, make sure this is the only one you are running on top of a [[Vanilla game]].<br /> <br /> After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.<br /> <br /> === Note ===<br /> More of the configuration file's settings are documented on the [[Hidden Settings in Oolite]] wiki page.<br /> <br /> == Comparison ==<br /> <br /> Now we need to compare several such tests in order to see patterns. To facilitate this and also communicate to others, start filling in a table like this:<br /> <br /> {| class="wikitable" style="margin:auto"<br /> |+ Caption text<br /> |-<br /> ! Oolite Version/Build/package !! Installed expansions !! Amount of entities !! screen/window size !! perceived FPS<br /> |-<br /> | 1.90/debug/.run || CustomPopulator || 360 || 800x600 || 70<br /> |-<br /> | 1.92/appimage/test || CustomPopulator || 358 || 1024x768 || 35<br /> |-<br /> | 1.93/flatpak/release || CustomPopulator || 360 || 1233x700 || 40<br /> |}<br /> <br /> == Links ==<br /> *[[Frame rate]]<br /> *[[Developer's Corner]]<br /> *[[User:Hiran|Hiran]]</div>

Hiran https://wiki.alioth.net/index.php?title=Common_Testing&diff=88482 Common Testing 2026-04-23T19:15:17Z

<p>Hiran: /* Performance Test */</p> <hr /> <div>[[File:FPS report.png|right|400px]]<br /> Here are some tests that can be performed regardless of the operating system.<br /> <br /> == Performance Test ==<br /> <br /> The main functionality in Oolite is to process the "game loop". This reads user input, processes the world including running all your OXP/OXZs, and then renders out the world view. For meaningful tests you need to have a repeatable base. A good metric for performance is the number of [[Frame rate|frames per second]] (FPS) that Oolite can process.<br /> <br /> If you want to check performance, you must check with FPS uncapped, otherwise you are always getting v-sync FPS, which is usually a low number like 60 for a 60Hz monitor, 144 for a 144Hz one ''etc''. <br /> <br /> Add the '''"animation_timer_interval" = x;''' in your OoliteDefaults.plist, where x is 1.0/Maximum FPS You Want To Achieve. I usually set it to 0.001 which tells Oolite to "go for 1000 FPS if you can". Then you can compare actual performance between builds.<br /> <br /> Also, disable v-sync to have uncapped FPS. You do this by setting the OoliteDefaults.plist key '''"v-sync" = NO;'''.<br /> <br /> When comparing the performance of builds, always check with more or less the same number of entities in the system. If in one case you get 250 entities and in the other you get 70, then results may be biased (it takes much more processing power to manage the 250). Try to compare instances where the two system entity numbers are as close as possible. Shift+F shows you this info in the Oolite "Test Release" builds. Phkb wrote an expansion for that: [https://app.box.com/s/xrkkr5ylizshjng2dpc8uu9q6b39zt49 CustomPopulator.oxp.zip]. And as other OXP/OXZs may inhibit the build performance, make sure this is the only one you are running on top of a [[Vanilla game]].<br /> <br /> After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.<br /> <br /> == Comparison ==<br /> <br /> Now we need to compare several such tests in order to see patterns. To facilitate this and also communicate to others, start filling in a table like this:<br /> <br /> {| class="wikitable" style="margin:auto"<br /> |+ Caption text<br /> |-<br /> ! Oolite Version/Build/package !! Installed expansions !! Amount of entities !! screen/window size !! perceived FPS<br /> |-<br /> | 1.90/debug/.run || CustomPopulator || 360 || 800x600 || 70<br /> |-<br /> | 1.92/appimage/test || CustomPopulator || 358 || 1024x768 || 35<br /> |-<br /> | 1.93/flatpak/release || CustomPopulator || 360 || 1233x700 || 40<br /> |}<br /> === Note ===<br /> More of the configuration file's settings are documented on the [[Hidden Settings in Oolite]] wiki page.<br /> <br /> == Links ==<br /> *[[Frame rate]]<br /> *[[Developer's Corner]]<br /> *[[User:Hiran|Hiran]]</div>

Hiran https://wiki.alioth.net/index.php?title=Hidden_Settings_in_Oolite&diff=88481 Hidden Settings in Oolite 2026-04-22T19:20:13Z

<p>Hiran: /* Windows, Linux and other platforms */</p> <hr /> <div>[[Oolite]] has a number of settings that are potentially interesting for advanced users – mostly those working on [[OXP]]s – or for those who are experiencing graphical problems. This article focuses on settings stored on disk; for other tools that can be used while the game is running, see [[Debug_OXP]]. All changes described below should be made when the game is not running.<br /> <br /> All of these settings were introduced at some point after Oolite 1.65. Most of them will only apply to test releases at the moment.<br /> <br /> == Startup Parameters ==<br /> === Windows ===<br /> <br /> In Windows you can add a parameter to Oolite's shortcut (so that instead of pointing at C:\Oolite\oolite.app\oolite.exe it'll point at C:\Oolite\oolite.app\oolite.exe ''parameter''). [[:File:Oolite_Windows_Shortcut_Parameters.jpg|See here for an example.]]<br /> <br /> === Available parameters ===<br /> The parameters are:<br /> <br /> * -nosplash<br /> This removes the splash screen that appears when loading, and is useful to fix some graphical issues with certain graphics cards.<br /> * -splash<br /> This forces Oolite to always display the splash screen. If you try to use both -splash and -nosplash, -nosplash "wins".<br /> * -fullscreen<br /> This forces Oolite to start in fullscreen mode, not windowed.<br /> * -noshaders<br /> This forces shaders to be disabled when loading. This may be useful on some older graphics cards (e.g. the Intel GMA series) which report shader support to Oolite but don't do it particularly well.<br /> * -load path_to_savegame<br /> This forces Oolite to load the specified saved game. Use the full path, eg: -load c:\oolite\oolite.app\oolite-saves\Jameson.oolite-save<br /> * -verify-oxp path_to_oxp<br /> Rather than starting Oolite, perform some basic syntax checks on the OXP at the specified path. This is only available in the OXP developer builds of Oolite.<br /> * -message message_to_display<br /> Prints the argument that follows it as a message on the title game screen, e.g. -message "Hello World from Oolite".<br /> * -showversion<br /> Prints the version of the game on the title screen.<br /> * --compile-sysdesc, --export-sysdesc, --xml, --openstep<br /> These parameters are handling options to transform the system_description array for easier localization. The latter two are output format specifiers and are used only if either of the former two have been also set.<br /> <br /> == How to Change Settings ==<br /> === Mac OS X ===<br /> For Oolite under Mac OS X, there are several ways to modify these settings.<br /> * Most of them can be set with the [http://secrets.blacktree.com/ Secrets preference pane] for Mac OS X 10.5. (download the tool by selecting the "prefPane" option on the top right, click the downloaded prefPane to install it, choose Oolite in the list on the left)<br /> * If you have Xcode tools installed, they can be edited with Property List Editor. The preferences file can be found at ~/Library/Preferences/org.aegidian.oolite.plist. (This is human-readable in Mac OS X 10.3.9 and earlier, but binary in 10.4 and later.)<br /> * On all systems, the <code>defaults</code> command line tool can be used. To set a boolean value, use: <code>defaults write org.aegidian.oolite '''key''' -bool YES</code> (or <code>NO</code>). For numerical values, use <code>defaults write org.aegidian.oolite '''key''' 42</code>.<br /> <br /> *See Tips below for an example - altering memory - using '''Terminal''' (look in the ''Utilities'' folder in ''Launchpad'').<br /> <br /> === Windows, Linux and other platforms ===<br /> For platforms other than Mac OS X, you must edit a text file called <code>.GNUstepDefaults</code>. This file is created when you change a preference in Oolite, then quit. Depending on which version of GNUstep has been used to build Oolite, this file might be called <code>oolite.plist</code> or <code>OoliteDefaults.plist</code> instead.<br /> <br /> Under Windows, this file is found at <code><Oolite installation directory>\oolite.app\GNUstep\Defaults\.GNUstepDefaults</code>.<br /> <br /> Under Linux and other platforms, classic installations keep the file at <code>~/GNUstep/Defaults/.GNUstepDefaults</code>. Since its name starts with a full stop, it is hidden by default. If you’re using Gnome/Nautilus or KDE/Konqueror, you can show it by selecting Show Hidden Files from the View menu. In any event, it should be accessible from the command line.<br /> <br /> AppImage installations will create a GameData folder wherever the AppImage resides and then read GameData/OoliteDefaults.plist.<br /> <br /> FlatPak installations will access ~/.var/app/space.oolite.Oolite/OoliteDefaults.plist.<br /> <br /> <br /> The file content is a kind of [[property list]], but uses a slightly different syntax than usual; you may see values like <code><*I300></code>. However, when you edit it by hand it’s safe to write numbers in plain form, and booleans are written as <code>YES</code> or <code>NO</code>. All Oolite settings are in the dictionary named “oolite”.<br /> <br /> == Settings ==<br /> === Graphics ===<br /> '''Key:''' anti-aliasing<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> Turn on anti-aliasing. No effect if the hardware does not support it, like integrated Intel graphics cards.<br /> <br /> '''Key:''' max-texture-size<br /><br /> '''Type:''' integer<br /><br /> '''Default:''' Determined by graphics card and driver, typically 4096.<br /><br /> '''Minimum:''' 64<br /><br /> Limit the size (side length) of textures; textures larger than this size will be scaled down. The value should be a power of two; if it isn’t, it will be rounded '''up''' to the next power of two. '''Note:''' if reduced detail mode is enabled, textures with a side length larger than 512 pixels will be scaled down to half their size regardless of this setting. (This is done independently on each side; for instance, a 1024×2048 pixel texture will be scaled down to 512×1024 pixels, while a 512×1024 pixel texture will be scaled to 512×512 pixels.)<br /> <br /> '''Key:''' polygon-sprite-dump-svg<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.74<br /><br /> Test release 1.74 uses a more sophisticated mechanism for drawing missile and mine icons, which involves turning each one into two sets of triangles. This setting causes the generated triangle data to be written to SVG files in the logs folder.<br /> <br /> '''Key:''' sky-render-inset-coords<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> If set to <code>YES</code>, the outermost edges of stars and nebula parts will be cut off. This is intended to help with a rendering problem where boxes are drawn around stars and nebula parts on certain systems with defective graphics drivers.<br /> <br /> '''Key:''' splash-screen<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>YES</code><br /><br /> '''Introduced:''' 1.73.4<br /><br /> If set to <code>NO</code>, Oolite will not show the splash screen while loading. This works around a problem which causes some Windows systems with NVIDIA graphics accelerators to fall back to software rendering. No effect on Mac OS X.<br /> <br /> '''Key:''' texture-anisotropy-scale<br /><br /> '''Type:''' real<br /><br /> '''Default:''' 0.5<br /><br /> '''Range:''' 0–1<br /><br /> '''Introduced:''' 1.73/1.72.3 (implementation was previously broken)<br /><br /> Anisotropic filtering is a technique that improves the clarity of textures seen at a shallow angle, but has a significant performance cost. This setting changes the amount of anisotropic filtering applied, with 0 meaning none and 1 meaning as much as supported by your graphics hardware and drivers.<br /> <br /> '''Key:''' use-texture-lod-bias<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>YES</code><br /><br /> '''Introduced:''' 1.73<br /><br /> Texture LOD bias is an extension used to control the tradeoff between blurriness and graphical artefacts in textures. On certain ATi hardware under Windows, the use of texture LOD bias causes graphical problems, notably untextured stars and nebulae.<br /> <br /> '''Key:''' dump-synthesized-shaders<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.77<br /><br /> Dumps the synthesized shaders that will be introduced in 1.77 in a folder beside the normal log.<br /> <br /> === Logging ===<br /> '''Key:''' logging-echo-to-stderr<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> If set to <code>YES</code>, log messages are written to the standard error output as well as the log file.<br /> <br /> '''Key:''' logging-show-function<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> If set to <code>YES</code>, log messages will be prefixed with the function or method in which they occurred. This is of limited use.<br /> <br /> '''Key:''' logging-show-file-and-line<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> If set to <code>YES</code>, log messages will be prefixed with the source code location where they occurred. This is potentially convenient for developers.<br /> <br /> '''Key:''' logging-show-time<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>YES</code><br /><br /> If set to <code>YES</code>, log messages will be prefixed with the time on which they occurred. The time string is of the format hh:mm:ss.mil. This is potentially convenient for developers.<br /> <br /> '''Key:''' logging-show-class<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>YES</code> (but disabled when running the OXP verifier)<br /><br /> If set to <code>YES</code>, log messages will be prefixed with their log message class, an identifier that can be used to enable or disable messages by editing ''[[logcontrol.plist]]''.<br /> <br /> === OXP verifier ===<br /> All keys in this section are only relevant for the OXP Developer builds of Oolite.<br /> <br /> '''Key:''' enforce-oxp-standards<br /><br /> '''Type:''' integer<br /><br /> '''Default:''' <code>1</code><br /><br /> '''Available:''' Oolite 1.81 onwards<br /> This sets the level of run time checking of OXP standards.<br /> <br /> * '''0''': Off (always the case in standard builds, regardless of this setting)<br /> * '''1''': Warn (logs if deprecated or other common errors are found, default in OXP Developer builds)<br /> * '''2''': Enforce (as 1, and it where possible will disable deprecated content)<br /> * '''3''': Quit (as 1, and after reporting the error will immediately exit Oolite<br /> <br /> Setting a higher level than the default may be useful for some styles of OXP development, though is unlikely to be suitable for playing the game.<br /> <br /> '''Key:''' oxp-verifier-dump-debug-graphviz<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> If set to <code>YES</code>, a [http://www.graphviz.org/ Graphviz] dot file named ''OXPVerifierStageDependencies.dot'' will be generated (in the <code>../Oolite/Oolite.app/Logs/</code> folder) when the OXP verifier is run. This is used to analyze and debug the OXP verifier and is of little interest to end-users, unless they like technical-looking graphs. (If you do like technical-looking graphs, see '''[[#Miscellaneous|universe-dump-debug-graphviz]]''' below.)<br /> <br /> '''Key:''' oxp-verifier-open-log<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>YES</code><br /><br /> '''Platform:''' Mac OS X only.<br /><br /> If set to <code>YES</code>, the log file will be opened after the OXP verifier is run.<br /> <br /> '''Key:''' plist-schema-verifier-dump-structure<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> If set to <code>YES</code>, OXP verifier logs will be filled with meaningless gobbledegook. (The [[property list|plist]] schema verifier is a tool used to verify the structure of property lists, currently used only for ''[[shipdata.plist]]'' entries. This setting causes detailed information to be logged for every property list element inspected by the verifier. It is unlikely to be useful except for debugging the verifier.)<br /> <br /> === Miscellaneous ===<br /> '''Key:''' always-flush-cache<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.73<br /><br /> If set to <code>YES</code>, the data cache will be rebuilt each time Oolite runs. This is roughly equivalent to placing a brick on your shift key.<br /> <br /> In Linux, add a snippet like this to your <code>.GNUstepDefaults</code>:<br /> <br /> <key>always-flush-cache</key><br /> <string>YES</string><br /> <br /> <br /> '''Key:''' animation_timer_interval<br /><br /> '''Type:''' real<br /><br /> '''Default:''' <code>0.05</code><br /><br /> '''Introduced:''' 1.82<br /><br /> Sets the maximum desired frames per second. The number of FPS attempted to be achieved will be <code>1.0/animation_timer_interval</code>. So, a value of 0.0167 will result in 1.0/0.0167 = 60.0 FPS and a value of 0.03333 will result in a maximum of 30 FPS. This setting can be used for testing purposes to emulate low-end systems, or alternatively, to determine the maximum performance of a given system while running Oolite. A value of 0.001 will practically achieve this, as it will set the desired FPS to 1000. The default value is 0.05, which corresponds to a maximum of 200 frames per second.<br /> <br /> '''Key:''' debug-show-extra-menu-items<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> Mac-specific: if set to <code>YES</code>, a few extra menu items appear in the Debug menu when the [[Debug OXP]] is installed (specifically, ''Graphics Reset'', ''Clear Texture Cache'', ''Reset and Clear'' and ''Clear All Caches'').<br /> <br /> '''Key:''' disable-operation-queue-work-manager<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.74<br /><br /> Test release 1.74 introduces a new way of managing certain operations, primarily texture loading, under Mac OS X 10.5 and later, which should also automatically be used with GNUstep 0.20 and later. In the event that this causes problems, it can be disabled with this preference.<br /> <br /> '''Key:''' dump-stack-for-errors<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.75<br /><br /> (Test releases only) If this preference is set, additional debugging information is logged when a script encounters an error. If the [[Debug OXP]] is active, this is ignored in favour of the setting <code>debugConsole.dumpStackForErrors</code> (which defaults to <code>true</code>).<br /> <br /> '''Key:''' dump-stack-for-warnings<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.75<br /><br /> (Test releases only) If this preference is set, additional debugging information is logged when a script encounters an warning. If the [[Debug OXP]] is active, this is ignored in favour of the setting <code>debugConsole.dumpStackForWarnings</code> (which defaults to <code>true</code>).<br /> <br /> '''Key:''' jsruntime-size-mib<br /><br /> '''Type:''' integer<br /><br /> '''Default:''' <code>32</code><br /><br /> '''Introduced:''' 1.89<br /><br /> Adjusts the JavaScript runtime size. The value is expressed in MiB and in the absense of this key, the default value of 32 MiB is used.This can prove useful when too many script-heavy OXPs are in use.<br /> <br /> '''Key:''' escape-pod-activation-immediate<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.75<br /><br /> If true, the escape pod is activated by a single key press. If false, two key presses are needed (except in strict mode).<br /> <br /> '''Key:''' flight-arrow-key-precision-factor<br /><br /> '''Type:''' real<br /><br /> '''Default:''' 0.5<br /><br /> '''Range:''' 0–1<br /><br /> Set a slower precision movement with keyboard arrows when you hold control down. For more precise long-range aim you can set it to 0.1.<br /> <br /> '''Key:''' generate-ai-graphviz<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.74<br /><br /> When enabled, each time an AI is loaded (uncached), a [http://www.graphviz.org/ Graphviz] dot file is generated showing the AI’s states and the transitions between them. For an example, see [http://jens.ayton.se/oolite/ai-graphs/hardMissileAI.plist.pdf hardMissileAI.plist.pdf].<br /> <br /> '''Key:''' grab-mouse-on-mouse-control<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.82<br /><br /> This setting is currently Windows-only. When enabled and mouse control is also enabled, it will confine the mouse pointer within the game's window. This can be useful in cases where Oolite is run fullscreen on multi-monitor systems, where accidentally clicking the mouse button while the cursor has moved out of the gameplay area to another monitor, would result in the game losing focus. It can also be useful when mouse is active in windowed mode.<br /> <br /> '''Key:''' groolite-disable<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.74<br /><br /> Completely disables Growl integration (Mac OS X only).<br /> <br /> '''Key:''' mouse-control-in-windowed-mode<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> '''Introduced:''' 1.74<br /><br /> Enables the player to use mouse control in windowed Oolite.<br /> <br /> '''Key:''' show-ship-model-in-status-screen<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> Shows a model of the players current ship on the F5 Status screen.<br /> <br /> '''Key:''' universe-dump-debug-graphviz<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> If set to <code>YES</code>, various [http://www.graphviz.org/ Graphviz] dot files will be generated (in the <code>../Oolite/Oolite.app/Logs/</code> folder) when Oolite starts. At the moment, this means ''SystemDescription.dot'', which is used to analyze the '''system_description''' table in ''[[descriptions.plist]]''. This is primarily useful to those writing localization OXPs.<br /> <br /> '''Key:''' issue_136_fix<br /><br /> '''Type:''' boolean<br /><br /> '''Default:''' <code>NO</code><br /><br /> This is a workaround for a graphical glitch on Macs with a retina display which affects the short range chart - see the issue at [https://github.com/OoliteProject/oolite/issues/136 github]. Set to <code>YES</code> to enable.<br /> <br /> == Tips ==<br /> === Increase memory allotment (AppleMac/Linux) ===<br /> [https://bb.oolite.space/viewtopic.php?p=275919#p275919 From Commander_X (2021)] - reading your hidden settings, and increasing memory allotment for Oolite. How to do it on AppleMac & Linux:<br /> <br /> For further reference, from above:<br /> On all systems, the defaults command line tool can be used. To set a boolean value, use: defaults write org.aegidian.oolite key -bool YES (or NO). For numerical values, use defaults write org.aegidian.oolite key 42<br /> <br /> For the curious, entering in a terminal:<br /> <br /> defaults read org.aegidian.oolite<br /> <br /> will present a list of the settings Oolite saves without your knowledge!<br /> <br /> <br /> Applying this to what another_commander suggested (in the thread linked above), after you enter in a terminal:<br /> <br /> defaults write org.aegidian.oolite jsruntime-size-mib 64<br /> <br /> you should be all set (maybe use quotes, i.e. "jsruntime-size-mib"). AppleMac seems not to need the quotes.<br /> <br /> <br /> This works also on '''Linux''', when gnustep(-dev?) package is installed. Replace "org.aegidian.oolite" above with "oolite", though. I'd expect it to work with another_commander's dev environment, on '''Windows''', too, if one placed "<mountpoint>/Devlibs[32]/gnustep1201/Local/Tools" in their path variable.<br /> <br /> <br /> <br /> *More on this will be found [https://bb.oolite.space/viewtopic.php?p=297854#p297854 here] (several posts from 2024)<br /> <br /> === Change start-up picture from Cobra MkIII ===<br /> This is not strictly a hidden settings matter, and involves changing the Vanilla game code (back up first!):<br /> <br /> https://bb.oolite.space/viewtopic.php?f=2&t=18682 (2017)<br /> <br /> There is also an alternative in ZygoUgo's [https://bb.oolite.space/viewtopic.php?f=4&t=8541 collection] of oxp's.<br /> <br /> == Links ==<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=6158 Procedural skyboxes?] (2009)<br /> <br /> [[Category:Oolite]]</div>

Hiran https://wiki.alioth.net/index.php?title=Common_Testing&diff=88480 Common Testing 2026-04-22T19:15:33Z

<p>Hiran: /* Note */</p> <hr /> <div>[[File:FPS report.png|right|400px]]<br /> Here are some tests that can be performed regardless of the operating system.<br /> <br /> == Performance Test ==<br /> <br /> The main functionality in Oolite is to process the "game loop". This reads user input, processes the world including running all your OXP/OXZs, and then renders out the world view. For meaningful tests you need to have a repeatable base. A good metric for performance is the number of [[Frame rate|frames per second]] (FPS) that Oolite can process.<br /> <br /> If you want to check performance, you must check with FPS uncapped, otherwise you are always getting v-sync FPS, which is usually a low number like 60 for a 60Hz monitor, 144 for a 144Hz one ''etc''. <br /> <br /> Add the '''"animation_timer_interval" = x;''' in your OoliteDefaults.plist, where x is 1.0/Maximum FPS You Want To Achieve. I usually set it to 0.001 which tells Oolite to "go for 1000 FPS if you can". Then you can compare actual performance between builds.<br /> <br /> Also, disable v-sync to have uncapped FPS. You do this by setting the OoliteDefaults.plist key '''"v-sync" = NO;'''.<br /> <br /> When comparing the performance of builds, always check with more or less the same number of entities in the system. If in one case you get 250 entities and in the other you get 70, then results may be biased (it takes much more processing power to manage the 250). Try to compare instances where the two system entity numbers are as close as possible. Shift+F shows you this info in the Oolite "Test Release" builds. Phkb wrote an expansion for that: [https://app.box.com/s/xrkkr5ylizshjng2dpc8uu9q6b39zt49 CustomPopulator.oxp.zip]. And as other OXP/OXZs may inhibit the build performance, make sure this is the only one you are running on top of a [[Vanilla game]].<br /> <br /> After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.<br /> <br /> === Note ===<br /> More of the configuration file's settings are documented on the [[Hidden Settings in Oolite]] wiki page.<br /> <br /> == Links ==<br /> *[[Frame rate]]<br /> *[[Developer's Corner]]<br /> *[[User:Hiran|Hiran]]</div>

Hiran https://wiki.alioth.net/index.php?title=Common_Testing&diff=88465 Common Testing 2026-04-22T05:09:02Z

<p>Hiran: /* Performance Test */</p> <hr /> <div>Here are some tests that can be performed regardless of the operating system.<br /> <br /> = Performance Test =<br /> <br /> The main functionality in Oolite is to process the game loop. It reads user input, processes the world including running all expansions, then renders out the world view. For meaningful tests you need to have a repeatable base. A good metric for performance is the frames per second (FPS) that Oolite can process.<br /> <br /> If you want to check performance, you must check with fps uncapped, otherwise you are always getting v-sync fps, which is usually a low number like 60 for a 60Hz monitor, 144 for a 144Hz one etc. Add the '''"animation_timer_interval" = x;''' in OoliteDefaults.plist, where x is 1.0/MaximumFPSYouWantToAchieve. I usually set it to 0.001 which tells Oolite to "go for 1000 fps if you can". Then you can compare actual performance between builds.<br /> Also disable v-sync to have uncapped fps. You do this by setting the OoliteDefaults.plist key '''"v-sync" = NO;'''.<br /> <br /> When comparing builds performance check always with more or less the same amount of entities in the system. If in one case you get 250 entities and in the other you get 70 results may be biased. Try to compare instances where the two system entity numbers are as close as possible. Shift+F shows you this info in test release builds. phkb prepared an expansion for that: [https://app.box.com/s/xrkkr5ylizshjng2dpc8uu9q6b39zt49 CustomPopulator.oxp.zip]. And as other expansions may drag on performance, make sure this is the only one you are running on top of a vanilla Oolite.<br /> <br /> After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.</div>

Hiran https://wiki.alioth.net/index.php?title=Common_Testing&diff=88464 Common Testing 2026-04-22T05:03:53Z

<p>Hiran: Created page with "Here are some tests that can be performed regardless of the operating system. = Performance Test = The main functionality in Oolite is to process the game loop. It reads use..."</p> <hr /> <div>Here are some tests that can be performed regardless of the operating system.<br /> <br /> = Performance Test =<br /> <br /> The main functionality in Oolite is to process the game loop. It reads user input, processes the world including running all expansions, then renders out the world view. For meaningful tests you need to have a repeatable base. A good metric for performance is the frames per second (FPS) that Oolite can process.<br /> <br /> If you want to check performance, you must check with fps uncapped, otherwise you are always getting v-sync fps, which is usually a low number like 60 for a 60Hz monitor, 144 for a 144Hz one etc. Add the animation_timer_interval = x; in OoliteDefaults.plist, where x is 1.0/MaximumFPSYouWantToAchieve. I usually set it to 0.001 which tells Oolite to "go for 1000 fps if you can". Then you can compare actual performance between builds.<br /> Also disable v-sync to have uncapped fps. You do this by setting the OoliteDefaults.plist key "v-sync" = NO;.<br /> <br /> When comparing builds performance check always with more or less the same amount of entities in the system. If in one case you get 250 entities and in the other you get 70 results may be biased. Try to compare instances where the two system entity numbers are as close as possible. Shift+F shows you this info in test release builds. phkb prepared an expansion for that: [https://app.box.com/s/xrkkr5ylizshjng2dpc8uu9q6b39zt49 CustomPopulator.oxp.zip]. And as other expansions may drag on performance, make sure this is the only one you are running on top of a vanilla Oolite.<br /> <br /> After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.</div>

Hiran https://wiki.alioth.net/index.php?title=Developer%27s_Corner&diff=88463 Developer's Corner 2026-04-22T04:55:06Z

<p>Hiran: /* OS Specific parts */</p> <hr /> <div>Here you will find information that helps understanding the Oolite source code, build and test the project.<br /> <br /> * [[Contributing to the project]]<br /> * [[Release Process]]<br /> * [[Branding]]<br /> * [https://ooliteproject.github.io/oolite/ Oolite API documentation]<br /> * [https://ooliteproject.github.io/oolite/ Doxygen Documentation]<br /> * [https://ooliteproject.github.io/oolite/coverage/index.html Code Coverage Report]<br /> * [[Cross Platform IDEs]]<br /> * [[Compiling with Clang instead of gcc]] (Windows/Linux)<br /> <br /> == OS Specific parts ==<br /> <br /> {| class="wikitable" style="margin:auto"<br /> |+ Operating System dependent stuff<br /> |-<br /> ! Procedure !! Apple Mac !! Linux !! Windows<br /> |-<br /> | Setting up a development environment || [[Development on Apple Mac]] [[Cross Platform IDEs]] || [[Development on Linux]] [[Cross Platform IDEs]] || [[Development on Windows]] [[Cross Platform IDEs]]<br /> |-<br /> | Compiling || [[Compiling on Apple Mac]] || [[Compiling on Linux]] || [[Developing Oolite#On_Windows_2 | Compiling on Windows]]<br /> |-<br /> | Testing || [[Testing on Apple Mac]] [[Common Testing]] || [[Testing on Linux]] [[Common Testing]] || [[Testing on Windows]] [[Common Testing]]<br /> |-<br /> | Packaging into Installer || [[Installer on Apple Mac]] || [[Installer on Linux]] || [[Installer on Windows]]<br /> |-<br /> | Running || [[Running_Oolite-Mac]] || ||<br /> |}<br /> <br /> ==Releasing the code==<br /> <br /> Once you developed a while you are no longer happy that all you created is called 'nightly' or 'prerelease' or 'unstable'.<br /> If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]].<br /> <br /> [[Category:Oolite Development]]<br /> <br /> == Hints ==<br /> <br /> The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.<br /> If you need to update submodules you also need to tell update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&t=21470<br /> <br /> To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules</div>

Hiran https://wiki.alioth.net/index.php?title=Contextual_Jukebox_OXP&diff=88414 Contextual Jukebox OXP 2026-04-17T06:48:50Z

<p>Hiran: /* Overview */</p> <hr /> <div>[[File:IconLib.png|right]]<br /> Arquebus' Music OXP for Oolite<br /> <br /> == Overview ==<br /> <br /> Adds background music to Oolite. It is different than just listening to the radio while playing.<br /> Depending on your situation there are different tracks, and with that it vastly enhances the cinematic effect:<br /> <br /> You can hear anxiety when jumping into a new star system and being unsure what's waiting for you.<br /> <br /> You can hear danger coming.<br /> <br /> You can hear being home when getting to a safe harbour.<br /> <br /> == Dependencies ==<br /> <br /> This OXP needs [[Library OXP]] to function properly. It provides music for various different flight conditions in-game (Red Alert, Flight, arrival at [[Aegis]], ''etc''.)<br /> <br /> The music was composed by Eric Matyas (https://soundimage.org/), Professor in the Film department at Valencia College (Orlando, Florida).<br /> <br /> Used under royalty-free license as outlined here: https://soundimage.org/attribution-info/<br /> <br /> == Download ==<br /> *[[File:ContextualJukebox.oxz]] (OXZ: 110Mb)<br /> *[https://www.dropbox.com/sh/tphkcwqb7p1i9nc/AABjmkZBPtCAeHddJ22y9VkGa?dl=0 Contextual Jukebox OXP] (Original 2021 OXP from "box": 115Mb) <br /> <br /> == Links ==<br /> *Forum Thread [https://bb.oolite.space/viewtopic.php?f=4&t=21128 (WIP) Contextual Jukebox OXP] (2021-22)<br /> *Author: [[User:Arquebus|Arquebus]] <br /> *You-tube film with music playing: [https://www.youtube.com/watch?v=ZV5XLHPX8sk Let's Play Poorly - 3.01] - the music starts with the launch (6:24) <br /> *Music by Eric Matyas: https://soundimage.org/<br /> *[[Music]]<br /> <br /> {{ambience-OXP}} <br /> [[Category:Sound Sets OXPs]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88412 Find the culprit 2026-04-16T18:49:57Z

<p>Hiran: /* Check Partition (3) */</p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Algorithm =<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, [https://wiki.alioth.net/index.php/OXP#Locating_your_AddOns_folder find your directories] where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> = Example Scenarios =<br /> <br /> == Ben's problem in one expansion ==<br /> Ben loves playing Oolite, and over time he accumulated a couple of expansions. To stay simple we just call them with one letter each:<br /> A, B, C*, D, E, F, G<br /> <br /> One day Ben discovers a strange, annoying behaviour. His ship kills counter does not increase reliably when he blows up some ship. <br /> Ben has a problem in expansion C* (note the asterisk), but he does not know. With no better plan in mind he finds this wiki page and starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Ben finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. He makes a backup copy of these folders.<br /> Also he writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame fifteen<br /> - Switch to the F5 screen and check the kill count before<br /> - Launch from the station and kill the next trader ship in the star system<br /> - Switch to the F5 screen and check the kill count after<br /> - It is expected to see the kill count increased by one<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Ben removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> He restores the files from his backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Ben creates the list of his expansions: A, B, C*, D, E, F, G<br /> Then he deletes half of the expansions, so he is left with A, B, C*, D<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has more than one expansion installed, so he repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Ben creates the list of his expansions: A, B, C*, D<br /> Then he deletes half of the expansions, so he is left with A, B<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> With the two expansions installed the problem does not occur. He restores the expansions from the other half (C*, D) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Ben creates the list of his expansions: C*, D<br /> Then he deletes half of the expansions, so he is left with C*<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has only one expansion installed, so this one must be the culprit.<br /> <br /> Now Ben can go to the Oolite bulletin board and ask for help on expansion C. The author of that expansion is happy to hear his expansionn is getting used and fexes the bug in no time. Ben is happy, too.<br /> <br /> == Sarah's problem between two expansion ==<br /> Sarah is quite new to Oolite. Since she heard from Ben about the game she immediately installs several expansions, though not the exact same set as Ben. To stay simple we just call them with one letter each:<br /> A, B, C, D#, E, F, K#<br /> <br /> Sarah plays the game and gets frustrated. For some reason she cannot dock via the shuttle. When she presses the button the shuttle launches from her ship, but then she can see it going to various places, spending time, going elsewhere but just not to the station the way it works for Ben. She suffers an incompatibility between expansions D# and K# (mind the #) but nobody knows about it. With no better plan in mind Ben helps her find this wiki page and she starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Sarah finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. She makes a backup copy of these folders.<br /> Also she writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame blueberry<br /> - Launch from the station, fly a curve and stop.<br /> - Activate the shuttle to dock again<br /> - The shuttle is expected to dock at the station within 120 seconds.<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Sarah removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then she performs the test. Actually she tries to. But there is no shuttle in vanilla Oolite.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> She restores the files from her backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Sarah creates the list of his expansions: A, B, C, D#, E, F, K#<br /> Then she deletes half of the expansions, so she is left with A, B, C, D#<br /> Then she performs the test, as written down above. And can see the shuttle docking in good time.<br /> With the four expansions installed the problem does not occur. See restores the expansions from the other half (E, F, K#) and repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Sarah creates the list of his expansions: E, F, K#<br /> Then she deletes half of the expansions, so she is left with E, F<br /> Then she performs the test. Actually she tries to. But there is no shuttle any more.<br /> With the two expansions installed the problem does not occur. See restores the expansions from the other half (K#) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Sarah creates the list of his expansions: K#<br /> Then she deletes half of the expansions (give or take 1), so she is left with K#<br /> Then she performs the test, as written down above. And can see the shuttle docking in good time.<br /> All partitions were successful, the problem vanished?<br /> <br /> === The problem vanished ===<br /> <br /> Sarah installs the counterpart of step 1, which is expansions E, F, K# and verifies the problem is gone. What next?<br /> It takes her a while to understand mixing the halves, so she comes up with<br /> <br /> * the full list: A, B, C, D#, E, F, K#<br /> * Split 1: A, B, C, D# | E, F, K#<br /> * Split 2: A, B | C, D# || E, F | K#<br /> <br /> Then she swaps halves from split 2 and gets<br /> * Swap: A, B | K# || E, F | C, D#<br /> <br /> With that she goes back to the check partition step. But regardless whether she tests A, B, K# or the counterpart E, F, C, D# the problem does not occur.<br /> Sarah is desperate, so Ben takes over and changes the strategy. He removes expansions one by one to find the culprit.<br /> <br /> Test A, B, C, D#, E, F, K#: Problem occurs<br /> <br /> Test B, C, D#, E, F, K#: Problem occurs<br /> <br /> Test C, D#, E, F, K#: Problem occurs<br /> <br /> Test D#, E, F, K#: Problem occurs<br /> <br /> Test E, F, K#: Problem is gone<br /> <br /> Ben restores D# and deletes some other expansion<br /> <br /> Test D#, F, K#: Problem occurs<br /> <br /> Test D#, K#: Problem occurs<br /> <br /> Test D#: Problem is goneTest C, D#, E, F, K#: Problem occurs<br /> <br /> <br /> <br /> Just to be sure, Ben also tests the counterpart:<br /> <br /> Test K#: Problem is gone<br /> <br /> Now Ben is sure: There is something going on between expansion D and K. <br /> <br /> He goes to the Oolite bulletin board and asks for help. And learns that both expansions implement a shuttle - but in incompatible ways.<br /> So Ben tells Sarah to choose between D and K. Sarah is happy. The authors of expansions D and K add an entry to their manifest.plist files so any expansion manager knows about this incompatibility. This way future users will not go into the same pitfall.<br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88411 Find the culprit 2026-04-16T18:48:54Z

<p>Hiran: /* The problem vanished */</p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Algorithm =<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, [https://wiki.alioth.net/index.php/OXP#Locating_your_AddOns_folder find your directories] where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> = Example Scenarios =<br /> <br /> == Ben's problem in one expansion ==<br /> Ben loves playing Oolite, and over time he accumulated a couple of expansions. To stay simple we just call them with one letter each:<br /> A, B, C*, D, E, F, G<br /> <br /> One day Ben discovers a strange, annoying behaviour. His ship kills counter does not increase reliably when he blows up some ship. <br /> Ben has a problem in expansion C* (note the asterisk), but he does not know. With no better plan in mind he finds this wiki page and starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Ben finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. He makes a backup copy of these folders.<br /> Also he writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame fifteen<br /> - Switch to the F5 screen and check the kill count before<br /> - Launch from the station and kill the next trader ship in the star system<br /> - Switch to the F5 screen and check the kill count after<br /> - It is expected to see the kill count increased by one<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Ben removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> He restores the files from his backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Ben creates the list of his expansions: A, B, C*, D, E, F, G<br /> Then he deletes half of the expansions, so he is left with A, B, C*, D<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has more than one expansion installed, so he repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Ben creates the list of his expansions: A, B, C*, D<br /> Then he deletes half of the expansions, so he is left with A, B<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> With the two expansions installed the problem does not occur. He restores the expansions from the other half (C*, D) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Ben creates the list of his expansions: C*, D<br /> Then he deletes half of the expansions, so he is left with C*<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has only one expansion installed, so this one must be the culprit.<br /> <br /> Now Ben can go to the Oolite bulletin board and ask for help on expansion C.<br /> <br /> == Sarah's problem between two expansion ==<br /> Sarah is quite new to Oolite. Since she heard from Ben about the game she immediately installs several expansions, though not the exact same set as Ben. To stay simple we just call them with one letter each:<br /> A, B, C, D#, E, F, K#<br /> <br /> Sarah plays the game and gets frustrated. For some reason she cannot dock via the shuttle. When she presses the button the shuttle launches from her ship, but then she can see it going to various places, spending time, going elsewhere but just not to the station the way it works for Ben. She suffers an incompatibility between expansions D# and K# (mind the #) but nobody knows about it. With no better plan in mind Ben helps her find this wiki page and she starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Sarah finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. She makes a backup copy of these folders.<br /> Also she writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame blueberry<br /> - Launch from the station, fly a curve and stop.<br /> - Activate the shuttle to dock again<br /> - The shuttle is expected to dock at the station within 120 seconds.<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Sarah removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then she performs the test. Actually she tries to. But there is no shuttle in vanilla Oolite.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> She restores the files from her backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Sarah creates the list of his expansions: A, B, C, D#, E, F, K#<br /> Then she deletes half of the expansions, so she is left with A, B, C, D#<br /> Then she performs the test, as written down above. And can see the shuttle docking in good time.<br /> With the four expansions installed the problem does not occur. See restores the expansions from the other half (E, F, K#) and repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Sarah creates the list of his expansions: E, F, K#<br /> Then she deletes half of the expansions, so she is left with E, F<br /> Then she performs the test. Actually she tries to. But there is no shuttle any more.<br /> With the two expansions installed the problem does not occur. See restores the expansions from the other half (K#) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Sarah creates the list of his expansions: K#<br /> Then she deletes half of the expansions (give or take 1), so she is left with K#<br /> Then she performs the test, as written down above. And can see the shuttle docking in good time.<br /> All partitions were successful, the problem vanished?<br /> <br /> === The problem vanished ===<br /> <br /> Sarah installs the counterpart of step 1, which is expansions E, F, K# and verifies the problem is gone. What next?<br /> It takes her a while to understand mixing the halves, so she comes up with<br /> <br /> * the full list: A, B, C, D#, E, F, K#<br /> * Split 1: A, B, C, D# | E, F, K#<br /> * Split 2: A, B | C, D# || E, F | K#<br /> <br /> Then she swaps halves from split 2 and gets<br /> * Swap: A, B | K# || E, F | C, D#<br /> <br /> With that she goes back to the check partition step. But regardless whether she tests A, B, K# or the counterpart E, F, C, D# the problem does not occur.<br /> Sarah is desperate, so Ben takes over and changes the strategy. He removes expansions one by one to find the culprit.<br /> <br /> Test A, B, C, D#, E, F, K#: Problem occurs<br /> <br /> Test B, C, D#, E, F, K#: Problem occurs<br /> <br /> Test C, D#, E, F, K#: Problem occurs<br /> <br /> Test D#, E, F, K#: Problem occurs<br /> <br /> Test E, F, K#: Problem is gone<br /> <br /> Ben restores D# and deletes some other expansion<br /> <br /> Test D#, F, K#: Problem occurs<br /> <br /> Test D#, K#: Problem occurs<br /> <br /> Test D#: Problem is goneTest C, D#, E, F, K#: Problem occurs<br /> <br /> <br /> <br /> Just to be sure, Ben also tests the counterpart:<br /> <br /> Test K#: Problem is gone<br /> <br /> Now Ben is sure: There is something going on between expansion D and K. <br /> <br /> He goes to the Oolite bulletin board and asks for help. And learns that both expansions implement a shuttle - but in incompatible ways.<br /> So Ben tells Sarah to choose between D and K. Sarah is happy. The authors of expansions D and K add an entry to their manifest.plist files so any expansion manager knows about this incompatibility. This way future users will not go into the same pitfall.<br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88410 Find the culprit 2026-04-16T18:43:36Z

<p>Hiran: /* The problem vanished */</p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Algorithm =<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, [https://wiki.alioth.net/index.php/OXP#Locating_your_AddOns_folder find your directories] where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> = Example Scenarios =<br /> <br /> == Ben's problem in one expansion ==<br /> Ben loves playing Oolite, and over time he accumulated a couple of expansions. To stay simple we just call them with one letter each:<br /> A, B, C*, D, E, F, G<br /> <br /> One day Ben discovers a strange, annoying behaviour. His ship kills counter does not increase reliably when he blows up some ship. <br /> Ben has a problem in expansion C* (note the asterisk), but he does not know. With no better plan in mind he finds this wiki page and starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Ben finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. He makes a backup copy of these folders.<br /> Also he writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame fifteen<br /> - Switch to the F5 screen and check the kill count before<br /> - Launch from the station and kill the next trader ship in the star system<br /> - Switch to the F5 screen and check the kill count after<br /> - It is expected to see the kill count increased by one<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Ben removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> He restores the files from his backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Ben creates the list of his expansions: A, B, C*, D, E, F, G<br /> Then he deletes half of the expansions, so he is left with A, B, C*, D<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has more than one expansion installed, so he repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Ben creates the list of his expansions: A, B, C*, D<br /> Then he deletes half of the expansions, so he is left with A, B<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> With the two expansions installed the problem does not occur. He restores the expansions from the other half (C*, D) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Ben creates the list of his expansions: C*, D<br /> Then he deletes half of the expansions, so he is left with C*<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has only one expansion installed, so this one must be the culprit.<br /> <br /> Now Ben can go to the Oolite bulletin board and ask for help on expansion C.<br /> <br /> == Sarah's problem between two expansion ==<br /> Sarah is quite new to Oolite. Since she heard from Ben about the game she immediately installs several expansions, though not the exact same set as Ben. To stay simple we just call them with one letter each:<br /> A, B, C, D#, E, F, K#<br /> <br /> Sarah plays the game and gets frustrated. For some reason she cannot dock via the shuttle. When she presses the button the shuttle launches from her ship, but then she can see it going to various places, spending time, going elsewhere but just not to the station the way it works for Ben. She suffers an incompatibility between expansions D# and K# (mind the #) but nobody knows about it. With no better plan in mind Ben helps her find this wiki page and she starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Sarah finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. She makes a backup copy of these folders.<br /> Also she writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame blueberry<br /> - Launch from the station, fly a curve and stop.<br /> - Activate the shuttle to dock again<br /> - The shuttle is expected to dock at the station within 120 seconds.<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Sarah removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then she performs the test. Actually she tries to. But there is no shuttle in vanilla Oolite.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> She restores the files from her backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Sarah creates the list of his expansions: A, B, C, D#, E, F, K#<br /> Then she deletes half of the expansions, so she is left with A, B, C, D#<br /> Then she performs the test, as written down above. And can see the shuttle docking in good time.<br /> With the four expansions installed the problem does not occur. See restores the expansions from the other half (E, F, K#) and repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Sarah creates the list of his expansions: E, F, K#<br /> Then she deletes half of the expansions, so she is left with E, F<br /> Then she performs the test. Actually she tries to. But there is no shuttle any more.<br /> With the two expansions installed the problem does not occur. See restores the expansions from the other half (K#) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Sarah creates the list of his expansions: K#<br /> Then she deletes half of the expansions (give or take 1), so she is left with K#<br /> Then she performs the test, as written down above. And can see the shuttle docking in good time.<br /> All partitions were successful, the problem vanished?<br /> <br /> === The problem vanished ===<br /> <br /> Sarah installs the counterpart of step 1, which is expansions E, F, K# and verifies the problem is gone. What next?<br /> It takes her a while to understand mixing the halves, so she comes up with<br /> <br /> * the full list: A, B, C, D#, E, F, K#<br /> * Split 1: A, B, C, D# | E, F, K#<br /> * Split 2: A, B | C, D# || E, F | K#<br /> <br /> Then she swaps halves from split 2 and gets<br /> * Swap: A, B | K# || E, F | C, D#<br /> <br /> With that she goes back to the check partition step. But regardless whether she tests A, B, K# or the counterpart E, F, C, D# the problem does not occur.<br /> Sarah is desperate, so Ben takes over and changes the strategy. He removes expansions one by one to find the culprit.<br /> <br /> Test A, B, C, D#, E, F, K#: Problem occurs<br /> <br /> Test B, C, D#, E, F, K#: Problem occurs<br /> <br /> Test C, D#, E, F, K#: Problem occurs<br /> <br /> Test D#, E, F, K#: Problem occurs<br /> <br /> Test E, F, K#: Problem is gone<br /> <br /> Ben restores D# and deletes some other expansion<br /> <br /> Test D#, F, K#: Problem occurs<br /> <br /> Test D#, K#: Problem occurs<br /> <br /> Test D#: Problem is gone<br /> <br /> Just to be sure, Ben also tests the counterpart:<br /> <br /> Test K#: Problem is gone<br /> <br /> Now Ben is sure: There is something going on between expansion D and K. He goes to the Oolite bulletin board and asks for help. And learns that both expansions implement a shuttle - but in incompatible ways.<br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88407 Find the culprit 2026-04-15T19:32:23Z

<p>Hiran: /* Example Scenarios */</p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Algorithm =<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, [https://wiki.alioth.net/index.php/OXP#Locating_your_AddOns_folder find your directories] where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> = Example Scenarios =<br /> <br /> == Ben's problem in one expansion ==<br /> Ben loves playing Oolite, and over time he accumulated a couple of expansions. To stay simple we just call them with one letter each:<br /> A, B, C*, D, E, F, G<br /> <br /> One day Ben discovers a strange, annoying behaviour. His ship kills counter does not increase reliably when he blows up some ship. <br /> Ben has a problem in expansion C* (note the asterisk), but he does not know. With no better plan in mind he finds this wiki page and starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Ben finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. He makes a backup copy of these folders.<br /> Also he writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame fifteen<br /> - Switch to the F5 screen and check the kill count before<br /> - Launch from the station and kill the next trader ship in the star system<br /> - Switch to the F5 screen and check the kill count after<br /> - It is expected to see the kill count increased by one<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Ben removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> He restores the files from his backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Ben creates the list of his expansions: A, B, C*, D, E, F, G<br /> Then he deletes half of the expansions, so he is left with A, B, C*, D<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has more than one expansion installed, so he repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Ben creates the list of his expansions: A, B, C*, D<br /> Then he deletes half of the expansions, so he is left with A, B<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> With the two expansions installed the problem does not occur. He restores the expansions from the other half (C*, D) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Ben creates the list of his expansions: C*, D<br /> Then he deletes half of the expansions, so he is left with C*<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has only one expansion installed, so this one must be the culprit.<br /> <br /> Now Ben can go to the Oolite bulletin board and ask for help on expansion C.<br /> <br /> == Sarah's problem between two expansion ==<br /> Sarah is quite new to Oolite. Since she heard from Ben about the game she immediately installs several expansions, though not the exact same set as Ben. To stay simple we just call them with one letter each:<br /> A, B, C, D#, E, F, K#<br /> <br /> Sarah plays the game and gets frustrated. For some reason she cannot dock via the shuttle. When she presses the button the shuttle launches from her ship, but then she can see it going to various places, spending time, going elsewhere but just not to the station the way it works for Ben. She suffers an incompatibility between expansions D# and K# (mind the #) but nobody knows about it. With no better plan in mind Ben helps her find this wiki page and she starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Sarah finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. She makes a backup copy of these folders.<br /> Also she writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame blueberry<br /> - Launch from the station, fly a curve and stop.<br /> - Activate the shuttle to dock again<br /> - The shuttle is expected to dock at the station within 120 seconds.<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Sarah removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then she performs the test. Actually she tries to. But there is no shuttle in vanilla Oolite.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> She restores the files from her backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Sarah creates the list of his expansions: A, B, C, D#, E, F, K#<br /> Then she deletes half of the expansions, so she is left with A, B, C, D#<br /> Then she performs the test, as written down above. And can see the shuttle docking in good time.<br /> With the four expansions installed the problem does not occur. See restores the expansions from the other half (E, F, K#) and repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Sarah creates the list of his expansions: E, F, K#<br /> Then she deletes half of the expansions, so she is left with E, F<br /> Then she performs the test. Actually she tries to. But there is no shuttle any more.<br /> With the two expansions installed the problem does not occur. See restores the expansions from the other half (K#) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Sarah creates the list of his expansions: K#<br /> Then she deletes half of the expansions (give or take 1), so she is left with K#<br /> Then she performs the test, as written down above. And can see the shuttle docking in good time.<br /> All partitions were successful, the problem vanished?<br /> <br /> === The problem vanished ===<br /> <br /> Sarah installs the counterpart of step 1, which is expansions E, F, K# and verifies the problem is gone. What next?<br /> It takes her a while to understand mixing the halves, so she comes up with<br /> <br /> * the full list: A, B, C, D#, E, F, K#<br /> * Split 1: A, B, C, D# | E, F, K#<br /> * Split 2: A, B | C, D# || E, F | K#<br /> <br /> Then she swaps halves from split 2 and gets<br /> * Swap: A, B | K# || E, F | C, D#<br /> <br /> With that she goes back to the check partition step. But regardless whether she tests A, B, K# or the counterpart E, F, C, D# the problem does not occur.<br /> Sarah is desperate, so Ben takes over and changes the strategy. He removes expansions one by one to find the culprit.<br /> <br /> Test A, B, C, D#, E, F, K#: Problem occurs<br /> <br /> Test B, C, D#, E, F, K#: Problem occurs<br /> <br /> Test C, D#, E, F, K#: Problem occurs<br /> <br /> Test C, D#, E, F, K#: Problem occurs<br /> <br /> Test D#, E, F, K#: Problem occurs<br /> <br /> Test E, F, K#: Problem is gone<br /> <br /> Ben restores D# and deletes some other expansion<br /> <br /> Test D#, F, K#: Problem occurs<br /> <br /> Test D#, K#: Problem occurs<br /> <br /> Test D#: Problem is gone<br /> <br /> Just to be sure, Ben also tests the counterpart:<br /> <br /> Test K#: Problem is gone<br /> <br /> Now Ben is sure: There is something going on between expansion D and K. He goes to the Oolite bulletin board and asks for help. And learns that both expansions implement a shuttle - but in incompatible ways.<br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88406 Find the culprit 2026-04-15T19:13:19Z

<p>Hiran: /* Example Scenarios */</p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Algorithm =<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, [https://wiki.alioth.net/index.php/OXP#Locating_your_AddOns_folder find your directories] where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> = Example Scenarios =<br /> <br /> == Ben's problem in one expansion ==<br /> Ben loves playing Oolite, and over time he accumulated a couple of expansions. To stay simple we just call them with one letter each:<br /> A, B, C*, D, E, F, G<br /> <br /> One day Ben discovers a strange, annoying behaviour. His ship kills counter does not increase reliably when he blows up some ship. <br /> Ben has a problem in expansion C* (note the asterisk), but he does not know. With no better plan in mind he finds this wiki page and starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Ben finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. He makes a backup copy of these folders.<br /> Also he writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame fifteen<br /> - Switch to the F5 screen and check the kill count before<br /> - Launch from the station and kill the next trader ship in the star system<br /> - Switch to the F5 screen and check the kill count after<br /> - It is expected to see the kill count increased by one<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Ben removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> He restores the files from his backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Ben creates the list of his expansions: A, B, C*, D, E, F, G<br /> Then he deletes half of the expansions, so he is left with A, B, C*, D<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has more than one expansion installed, so he repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Ben creates the list of his expansions: A, B, C*, D<br /> Then he deletes half of the expansions, so he is left with A, B<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> With the two expansions installed the problem does not occur. He restores the expansions from the other half (C*, D) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Ben creates the list of his expansions: C*, D<br /> Then he deletes half of the expansions, so he is left with C*<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has only one expansion installed, so this one must be the culprit.<br /> <br /> Now Ben can go to the Oolite bulletin board and ask for help on expansion C.<br /> <br /> == Sarah's problem between two expansion ==<br /> Sarah is quite new to Oolite. Since she heard from Ben about the game she immediately installs several expansions, though not the exact same set as Ben. To stay simple we just call them with one letter each:<br /> A, B, C, D#, E, F, K#<br /> Sarah plays the game and gets frustrated. For some reason she cannot dock via the shuttle. When she presses the button the shuttle launches from her ship, but then she can see it going to various places, spending time, going elsewhere but just not to the station the way it works for Ben. She suffers an incompatibility between expansions D# and K# (mind the #) but nobody knows about it. With no better plan in mind Ben helps her find this wiki page and she starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Sarah finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. She makes a backup copy of these folders.<br /> Also she writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame blueberry<br /> - Launch from the station, fly a curve and stop.<br /> - Activate the shuttle to dock again<br /> - The shuttle is expected to dock at the station within 120 seconds.<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Sarah removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then she performs the test. Actually she tries to. But there is no shuttle in vanilla Oolite.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> She restores the files from her backup.<br /> <br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88405 Find the culprit 2026-04-15T19:00:35Z

<p>Hiran: /* Ben's problem in one expansion */</p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Algorithm =<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, [https://wiki.alioth.net/index.php/OXP#Locating_your_AddOns_folder find your directories] where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> = Example Scenarios =<br /> <br /> == Ben's problem in one expansion ==<br /> Ben loves playing Oolite, and over time he accumulated a couple of expansions. For stay simple we just call them with one letter each:<br /> A, B, C, D, E, F, G<br /> <br /> One day Ben discovers a strange, annoying behaviour. His ship kills counter does not increase reliably when he blows up some ship. <br /> Ben has a problem in expansion C (note the asterisk), but he does not know. With no better plan in mind he finds this wiki page and starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Ben finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. He makes a backup copy of these folders.<br /> Also he writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame fifteen<br /> - Switch to the F5 screen and check the kill count before<br /> - Launch from the station and kill the next trader ship in the star system<br /> - Switch to the F5 screen and check the kill count after<br /> - It is expected to see the kill count increased by one<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Ben removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> He restores the files from his backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Ben creates the list of his expansions: A, B, C, D, E, F, G<br /> Then he deletes half of the expansions, so he is left with A, B, C, D<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has more than one expansion installed, so he repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Ben creates the list of his expansions: A, B, C, D<br /> Then he deletes half of the expansions, so he is left with A, B<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> With the two expansions installed the problem does not occur. He restores the expansions from the other half (C, D) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Ben creates the list of his expansions: C, D<br /> Then he deletes half of the expansions, so he is left with C<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has only one expansion installed, so this one must be the culprit.<br /> <br /> Now Ben can go to the Oolite bulletin board and ask for help on expansion C.<br /> <br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88404 Find the culprit 2026-04-15T19:00:21Z

<p>Hiran: /* Ben's problem in one expansion */</p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Algorithm =<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, [https://wiki.alioth.net/index.php/OXP#Locating_your_AddOns_folder find your directories] where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> = Example Scenarios =<br /> <br /> == Ben's problem in one expansion ==<br /> https://cdn-0.plantuml.com/plantuml/png/SoWkIImgAStDuIfAJIv9p4lFILLmH68x8R6T5HAB5PISjPIGn5oGsAv8R3SajZkNGsfU2j0E0000<br /> Ben loves playing Oolite, and over time he accumulated a couple of expansions. For stay simple we just call them with one letter each:<br /> A, B, C, D, E, F, G<br /> <br /> One day Ben discovers a strange, annoying behaviour. His ship kills counter does not increase reliably when he blows up some ship. <br /> Ben has a problem in expansion C (note the asterisk), but he does not know. With no better plan in mind he finds this wiki page and starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Ben finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. He makes a backup copy of these folders.<br /> Also he writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame fifteen<br /> - Switch to the F5 screen and check the kill count before<br /> - Launch from the station and kill the next trader ship in the star system<br /> - Switch to the F5 screen and check the kill count after<br /> - It is expected to see the kill count increased by one<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Ben removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> He restores the files from his backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Ben creates the list of his expansions: A, B, C, D, E, F, G<br /> Then he deletes half of the expansions, so he is left with A, B, C, D<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has more than one expansion installed, so he repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Ben creates the list of his expansions: A, B, C, D<br /> Then he deletes half of the expansions, so he is left with A, B<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> With the two expansions installed the problem does not occur. He restores the expansions from the other half (C, D) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Ben creates the list of his expansions: C, D<br /> Then he deletes half of the expansions, so he is left with C<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has only one expansion installed, so this one must be the culprit.<br /> <br /> Now Ben can go to the Oolite bulletin board and ask for help on expansion C.<br /> <br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88403 Find the culprit 2026-04-15T18:59:22Z

<p>Hiran: /* Ben's problem in one expansion */</p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Algorithm =<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, [https://wiki.alioth.net/index.php/OXP#Locating_your_AddOns_folder find your directories] where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> = Example Scenarios =<br /> <br /> == Ben's problem in one expansion ==<br /> https://cdn-0.plantuml.com/plantuml/png/SoWkIImgAStDuIfAJIv9p4lFILLmH68x8R6T5HAB5PISjPIGn5oGsAv8R3SajZkNGsfU2j0E0000<br /> Ben loves playing Oolite, and over time he accumulated a couple of expansions. For brewity we just call them with one letter each.<br /> <br /> [[https://cdn-0.plantuml.com/plantuml/png/SoWkIImgAStDuIfAJIv9p4lFILLmH68x8R6T5HAB5PISjPIGn5oGsAv8R3SajZkNGsfU2j0E0000]]<br /> <br /> One day Ben discovers a strange, annoying behaviour. His ship kills counter does not increase reliably when he blows up some ship. <br /> Ben has a problem in expansion C (note the asterisk), but he does not know. With no better plan in mind he finds this wiki page and starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Ben finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. He makes a backup copy of these folders.<br /> Also he writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame fifteen<br /> - Switch to the F5 screen and check the kill count before<br /> - Launch from the station and kill the next trader ship in the star system<br /> - Switch to the F5 screen and check the kill count after<br /> - It is expected to see the kill count increased by one<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Ben removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> He restores the files from his backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Ben creates the list of his expansions: A, B, C, D, E, F, G<br /> Then he deletes half of the expansions, so he is left with A, B, C, D<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has more than one expansion installed, so he repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Ben creates the list of his expansions: A, B, C, D<br /> Then he deletes half of the expansions, so he is left with A, B<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> With the two expansions installed the problem does not occur. He restores the expansions from the other half (C, D) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Ben creates the list of his expansions: C, D<br /> Then he deletes half of the expansions, so he is left with C<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has only one expansion installed, so this one must be the culprit.<br /> <br /> Now Ben can go to the Oolite bulletin board and ask for help on expansion C.<br /> <br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88402 Find the culprit 2026-04-15T18:57:56Z

<p>Hiran: /* Ben's problem in one expansion */</p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Algorithm =<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, [https://wiki.alioth.net/index.php/OXP#Locating_your_AddOns_folder find your directories] where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> = Example Scenarios =<br /> <br /> == Ben's problem in one expansion ==<br /> https://cdn-0.plantuml.com/plantuml/png/SoWkIImgAStDuIfAJIv9p4lFILLmH68x8R6T5HAB5PISjPIGn5oGsAv8R3SajZkNGsfU2j0E0000<br /> Ben loves playing Oolite, and over time he accumulated a couple of expansions. For brewity we just call them with one letter each.<br /> <br /> [https://cdn-0.plantuml.com/plantuml/png/SoWkIImgAStDuIfAJIv9p4lFILLmH68x8R6T5HAB5PISjPIGn5oGsAv8R3SajZkNGsfU2j0E0000]<br /> <br /> One day Ben discovers a strange, annoying behaviour. His ship kills counter does not increase reliably when he blows up some ship. <br /> Ben has a problem in expansion C (note the asterisk), but he does not know. With no better plan in mind he finds this wiki page and starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Ben finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. He makes a backup copy of these folders.<br /> Also he writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame fifteen<br /> - Switch to the F5 screen and check the kill count before<br /> - Launch from the station and kill the next trader ship in the star system<br /> - Switch to the F5 screen and check the kill count after<br /> - It is expected to see the kill count increased by one<br /> <br /> === Validate Vanilla Oolite ===<br /> <br /> As a first step, Ben removes all expansions from the ~/Oolite/Addons and ~/Oolite/.ManagedAddons folders.<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> So Oolite itself is good, and the behaviour must have come from some expansion. But which one?<br /> He restores the files from his backup.<br /> <br /> === Check Partition (1) ===<br /> <br /> Ben creates the list of his expansions: A, B, C, D, E, F, G<br /> Then he deletes half of the expansions, so he is left with A, B, C, D<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has more than one expansion installed, so he repeats the Check Partition step.<br /> <br /> === Check Partition (2) ===<br /> <br /> Ben creates the list of his expansions: A, B, C, D<br /> Then he deletes half of the expansions, so he is left with A, B<br /> Then he performs the test, as written down above. And he can confirm that the kill count increases as expected.<br /> With the two expansions installed the problem does not occur. He restores the expansions from the other half (C, D) and repeats the Check Partition step.<br /> <br /> === Check Partition (3) ===<br /> <br /> Ben creates the list of his expansions: C, D<br /> Then he deletes half of the expansions, so he is left with C<br /> Then he performs the test, as written down above. And he can see the odd behaviour again.<br /> He has only one expansion installed, so this one must be the culprit.<br /> <br /> Now Ben can go to the Oolite bulletin board and ask for help on expansion C.<br /> <br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88401 Find the culprit 2026-04-15T18:48:11Z

<p>Hiran: </p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Algorithm =<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, [https://wiki.alioth.net/index.php/OXP#Locating_your_AddOns_folder find your directories] where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> = Example Scenarios =<br /> <br /> == Ben's problem in one expansion ==<br /> https://cdn-0.plantuml.com/plantuml/png/SoWkIImgAStDuIfAJIv9p4lFILLmH68x8R6T5HAB5PISjPIGn5oGsAv8R3SajZkNGsfU2j0E0000<br /> Ben loves playing Oolite, and over time he accumulated a couple of expansions. For brewity we just call them with one letter each.<br /> <br /> [https://cdn-0.plantuml.com/plantuml/png/SoWkIImgAStDuIfAJIv9p4lFILLmH68x8R6T5HAB5PISjPIGn5oGsAv8R3SajZkNGsfU2j0E0000]<br /> <br /> One day Ben discovers a strange, annoying behaviour. His ship kills counter does not increase reliably when he blows up some ship. <br /> Ben has a problem in expansion C (note the asterisk), but he does not know. With no better plan in mind he finds this wiki page and starts applying the algorithm to find the culprit.<br /> <br /> === Prerequisite ===<br /> <br /> Ben finds the folders for Addons in ~/Oolite/Addons and ~/Oolite/.ManagedAddons. He makes a backup copy of these folders.<br /> Also he writes down how to reproduce the bug:<br /> - Start Oolite<br /> - Load Savegame fifteen<br /> - Switch to the F5 screen and check the kill count before<br /> - Launch from the station and kill the next trader ship in the star system<br /> - Switch to the F5 screen and check the kill count after<br /> - It is expected to see the kill count increased by one<br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88400 Find the culprit 2026-04-15T18:20:56Z

<p>Hiran: /* Preparations */</p> <hr /> <div>[[File:Oolite-oxp-icon.png|right|300px]]<br /> Finding the one single OXP which is making your game go wrong!<br /> <br /> == Overview ==<br /> In case you experience a strange situation with Oolite - and in case you want to talk to someone about this - it definitely helps others to describe not just <br /> * the symptoms <br /> :but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions you have installed.<br /> <br /> But you can do even more. <br /> <br /> Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the eight hundred-odd expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> == Prerequisite ==<br /> <br /> * As you will be juggling a lot of expansions back and forth, find your directories where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> == Validate Vanilla Oolite ==<br /> <br /> First, find out if the problem occurs in the [[Vanilla game]] code. For this, remove all expansions, (for example, by ''restarting'' a new game in "Strict mode"). Perform your test.<br /> <br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> <br /> If it doesn't, the vanilla game code is clean. Restore your expansions.<br /> <br /> == Binary Search of OXPs/OXZs ==<br /> === Check Partition ===<br /> <br /> Create a list of all the installed expansions' names and versions - you will need this. Oolite Starter can do this easily for you.<br /> <br /> Delete half of them (if you have an odd number of them, then it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> <br /> Write down the list of those that are left.<br /> <br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> <br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> === The problem vanished ===<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halves. Cut each half into two pieces again (now you have quarters).<br /> <br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> <br /> Restore the smallest combination of expansions that produces the problem.<br /> <br /> Remove one and test again. <br /> <br /> If the problem persists, repeat the step.<br /> <br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> <br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!<br /> <br /> [[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88398 Find the culprit 2026-04-14T19:20:44Z

<p>Hiran: /* The problem vanished */</p> <hr /> <div>In case you experience a strange situation with Oolite and in case you want to talk to someone about this, it definitely helps others to describe not just <br /> * the symptoms but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions <br /> you have installed.<br /> <br /> But you can do even more. Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the 805 expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Prerequisite=<br /> <br /> * As you will be juggling a lot of expansions back and forth, find your directories where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> = Validate Vanilla Oolite =<br /> <br /> First, validate the problem does not occur in the core. For this, delete all expansions. Perform your test.<br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> If it doesn't, the core is clean. Restore your expansions.<br /> <br /> = Check Partition =<br /> <br /> Create a list of all the installed expansions' names and versions - you will need them.<br /> Delete half of them (in odd numbers it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> Write down the list of those that are left.<br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> = The problem vanished =<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> <br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halfvs. Cut each half into two pieces again (now you have quarters).<br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halves, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> Restore the smallest combination of expansions that produces the problem.<br /> Remove one and test again. <br /> If the problem persists, repeat the step.<br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88397 Find the culprit 2026-04-14T19:10:44Z

<p>Hiran: /* Prerequisite */</p> <hr /> <div>In case you experience a strange situation with Oolite and in case you want to talk to someone about this, it definitely helps others to describe not just <br /> * the symptoms but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions <br /> you have installed.<br /> <br /> But you can do even more. Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the 805 expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Prerequisite=<br /> <br /> * As you will be juggling a lot of expansions back and forth, find your directories where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate and then check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> = Validate Vanilla Oolite =<br /> <br /> First, validate the problem does not occur in the core. For this, delete all expansions. Perform your test.<br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> If it doesn't, the core is clean. Restore your expansions.<br /> <br /> = Check Partition =<br /> <br /> Create a list of all the installed expansions' names and versions - you will need them.<br /> Delete half of them (in odd numbers it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> Write down the list of those that are left.<br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> = The problem vanished =<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halfes. Like above, cut each half into quarters.<br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halfes, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> Restore the smalles combination of expansions that produces the problem.<br /> Remove one and test again. <br /> If the problem persists, repeat the step.<br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!</div>

Hiran https://wiki.alioth.net/index.php?title=Find_the_culprit&diff=88396 Find the culprit 2026-04-14T19:10:00Z

<p>Hiran: Created page with "In case you experience a strange situation with Oolite and in case you want to talk to someone about this, it definitely helps others to describe not just * the symptoms but..."</p> <hr /> <div>In case you experience a strange situation with Oolite and in case you want to talk to someone about this, it definitely helps others to describe not just <br /> * the symptoms but also<br /> * which Oolite version,<br /> * which distribution and especially<br /> * which expansions <br /> you have installed.<br /> <br /> But you can do even more. Here is a guide for troubleshooting, which should work if you track a problem in Oolite (core), in one expansion or in the incompatibility between several expansions. Basically it is a [https://en.wikipedia.org/wiki/Binary_search binary search] in the installed expansions. This allows with a minimum of test cycles to span a big number of expansions. Suppose you installed all the 805 expansions that currently are on the [https://github.com/OoliteProject/oolite-expansion-catalog expansion catalog]. Then only 10 tests should be sufficient to spot the one expansion causing a problem.<br /> <br /> = Prerequisite=<br /> <br /> * As you will be juggling a lot of expansions back and forth, find your directories where Addons and ManagedAddons are stored. <br /> * Create a backup of these directories.<br /> * Decide for a procedure to check for the bug. Write it down. This could be to load a savegame, fly to whatever star system, shoot a pirate. Check your cargo hold.<br /> <br /> Once you have that, you can start the troubleshooting loop.<br /> <br /> = Validate Vanilla Oolite =<br /> <br /> First, validate the problem does not occur in the core. For this, delete all expansions. Perform your test.<br /> If the problem occurs, it is in the core. Congratulations, you can [https://github.com/OoliteProject/oolite/issues file an issue in the oolite github repository].<br /> If it doesn't, the core is clean. Restore your expansions.<br /> <br /> = Check Partition =<br /> <br /> Create a list of all the installed expansions' names and versions - you will need them.<br /> Delete half of them (in odd numbers it does not matter whether you delete one more or less). If no expansion is left, and you still have not found the problem check the next section.<br /> Write down the list of those that are left.<br /> Run Oolite and perform your test.<br /> <br /> If the problem occurs, the installed expansions caused it. If that happened on the last one expansion, you found it! Go to the Oolite bulletin board and ask for help. Otherwise repeat the Check Partition step.<br /> If the problem does not occur, it stems from the other half. Restore the expansions from the other half and repeat the Check Partition step.<br /> <br /> = The problem vanished =<br /> <br /> While you were troubleshooting with partitions all of a sudden the problem no longer occurred. Neither in the first half nor in the second half.<br /> Then it is likely the problem is caused by a combination of expansions that now got split over the two halfes. Like above, cut each half into quarters.<br /> Now combine the first half's first half with the second half's first half. Combine the remaining two halfes, hoping the problem would show up with one of them. If it does, go back to the Check Partition step.<br /> <br /> If it still doesn't, we have to switch the strategy.<br /> Restore the smalles combination of expansions that produces the problem.<br /> Remove one and test again. <br /> If the problem persists, repeat the step.<br /> If the problem vanished, restore the deleted expansion and remove another one.<br /> This should bring you down to the least amount of expansions that - installed together - produce a problem. With that information go to the Oolite bulletin board and ask for help.<br /> <br /> Good luck, Commander!</div>

Hiran https://wiki.alioth.net/index.php?title=OXP&diff=88395 OXP 2026-04-14T18:23:38Z

<p>Hiran: /* Managing a stable of OXPs */</p> <hr /> <div>[[Image:oolite-oxp-icon.png|128px|right|OXP icon]]<br /> An '''OXP''' ('''O'''olite e'''X'''pansion '''P'''ack) is an enhancement to the game [[Oolite]]. An OXP could be a new game object (such as a ship, space station or a moon), a mission, or a combination of several elements. OXPs can use all of the facilities of Oolite, including some that are not used in the standard, unexpanded game. Please note that if you run Oolite in 'Strict Play' mode (set via pressing F2 when docked or paused and then selecting 'Reset to Strict play'), OXPs are not loaded.<br /> <br /> An '''OXZ''' is an OXP in a particular '''Z'''ipped format to make it easier for Oolite to process and for players to install - to find out what's inside one, use your unzipping tool of choice on it.<br /> <br /> == Finding OXPs ==<br /> === OXP's ===<br /> *The '''[[OXP List]]''' provides the most comprehensive list of Oolite OXP expansion packs.<br /> *[[Guide to Unlisted OXPs]] has 100 or so (which are not listed elsewhere).<br /> === OXZ's ===<br /> *The [http://www.oolite.space/oxps/#oxp '''OXZ List'''] provides the most comprehensive list of Oolite OXZ expansion packs (but only those uploaded to the in-game Expansions Manager).<br /> *Just for fun, the [[Index of artefacts]] provides the most comprehensive analysis of these Oolite OXZ expansion packs...<br /> *there are just a handful of oxz's (mostly experimental, but including some excellent ones by phkb) not listed on the Expansions Manager/OXZ List. They are mostly in the [[Guide to Unlisted OXPs]] mixed in with everything else.<br /> *Check out the [[Oolite Starter]] which makes management of the expansions in your Ooniverse refeshing like a sip of properly chilled gin and tonic.<br /> <br /> === Old versions ===<br /> For purely historical purposes (or a touch of nostalgia if you've been around Oolite for a long time) you might want to look at [http://oosat.alioth.net The Oolite Satellite Resource Site] ('''Oosat2''', quite broken but still accessible, 2006-11-04 until 2007-03-03) or the even older [http://capnhack.com/hosting/oolite/Oolite/OoSat.html Captain Hack OoSat Site] ('''Oosat1''', beginning until 2006-10-14). Oosat may have originally been hosted here on Alioth.net, as was '''Oldsat'''. They had a tendency to go off-line or to crash, losing all information. Search on the BB if you are curious!<br /> <br /> For your curiosity and maybe one or the other odd find there is also the [[OXP Attic]] which houses derelict OXPs from times long past. Also see [https://bb.oolite.space/viewtopic.php?f=2&t=20721 Recovering Lost Oxp's].<br /> <br /> == OXPs suitable for new players ==<br /> <br /> <br /> Everyone has their own idea of what OXPs should be in a starter pack, or which are just best. There are several threads on the Forum on this topic, perhaps the best-balanced and most useful for newcomers being [https://bb.oolite.space/viewtopic.php?f=2&t=11885 this one]. <br /> <br /> == Suitability for simpler or for more difficult/advanced gaming ==<br /> There exists a way of marking an OXP's difficulty level according to the author's belief. You can find the [[OXP_Levelindicators|level indicators]] on the wiki.<br /> <br /> Another system in progress is [[Template:IconOXP]].<br /> <br /> ==Player recommendations==<br /> These commanders have put together lists of their personal favourites:<br /> *[[User:Cpt|Cpt]] (2013)<br /> *[[User:JazHaz|JazHaz]] (2013)<br /> *[[User:Zireael|Zireael]] (2014)<br /> *[[User:Norby#Recommended_OXPs|Norby]] (2015-7): includes packages of recommended OXPs for new players, the more experienced ''etc''.<br /> *[[User:CaptSolo|CaptSolo]] (2020)<br /> <br /> == Help with OXPs ==<br /> <br /> Information on OXPs can also be found on the [https://bb.oolite.space/viewforum.php?f=4 Expansion Pack Forum], the Friendliest Board This Side of Riedquat. The helpful people there will be happy to assist you with any questions you have about OXPs.<br /> <br /> == Tweaking your OXPs ==<br /> Do you prefer a louder ''beep'' for audible docking clearance? Would you rather your Commander's Log also recorded purchases & repairs? Do you want your Laser Booster to activate automatically upon launch? <br /> <br /> You will find recipes for modifying some of the OXPs [https://bb.oolite.space/viewtopic.php?p=216177#p216177 here].<br /> <br /> == Installing an OXP ==<br /> <br /> OXPs are installed to the folder or directory ('folder' and 'directory' are synonyms) named '''AddOns'''. Read on, we will also tell you where to find that folder.<br /> <br /> === In OXZ format ===<br /> Download the OXZ file, and save it to your AddOns folder. <br /> <br /> Many OXZ format expansion packs can also be downloaded and installed for you from the [[Expansions Manager]] in Oolite. These will be placed in a separate folder which Oolite manages ('''ManagedAddOns''') - any you download yourself should go in the '''AddOns''' folder so that Oolite doesn't accidentally overwrite them.<br /> <br /> If you want to inspect an OXZ you've downloaded with the expansion pack manager, copy it out of the '''ManagedAddOns''' folder first, then open it with your unzipping program. Some versions of the Expansions Manager can do this for you when you press the ''x'' key.<br /> <br /> === In OXP format ===<br /> Typically, an OXP is downloaded as a ZIP file though occasionally other compression tools such as 7z or rar have been used. Unzip it to find a folder with a name ending .oxp<br /> <br /> After unzipping the file, make sure that it is ''only'' the OXP folder that put into the AddOns directory - some zipped OXPs can contain a top level folder with a readMe file, and the actual OXP folder is a level further down. If this is the case, move the folder with the '''.oxp''' extension into the AddOns folder.<br /> <br /> Sometimes the zipped files contain several folders, make sure you only copy the folder -or file for Macintoshes- ending with '''.oxp''' into the AddOns folder. This folder is found in different locations, depending on the platform.<br /> <br /> If you have followed these instructions and OXPs are not being recognised by the game make sure that your commander is a normal game. If you started your commander using the "Strict Mode" starting option, no OXPs will ever be used.<br /> <br /> == Locating your AddOns folder ==<br /> <br /> === Mac OS X ===<br /> Found in the folder that contains the Oolite application.<br><br /> <br /> Alternatively you can also have the '''AddOns''' folder in your user area at '''~/Library/Application&nbsp;Support/Oolite/AddOns/'''. When both places contain an '''AddOns''' folder, both contents are read with the content in the user libraries loading last.<br /> <br /> '''Troubleshooting:''' If you get an error saying "The item could not be moved because "AddOns" cannot be modified", that can happen if you weren't the user that installed Oolite.<br /> The solution is to put the OXPs of your choice in '''~/Library/Application&nbsp;Support/Oolite/AddOns/''' instead (you may need to create this folder).<br /> The error could also be triggered because you’re running from the disk image, you’ll need to copy the game somewhere else. Having done so, if you still get the error, use the Get Info command on the AddOns folder, open the Ownership & Permissions pane and check that it says You Can: Read & Write.<br /> <br /> === Linux ===<br /> The location of the AddOns folder will depend on whether you chose to install Oolite to 'Home' or 'System'.<br /> <br /> If you chose the 'Home' installation, the AddOns directory is located in '''~/GNUstep/Applications/Oolite/AddOns'''. The AddOns folder should be in the top level of the Oolite install directory (at the same level as the oolite.app folder) You may have to create it.<br /> <br /> If you chose the 'System' installation, the AddOns directory will be '''~/.Oolite/Add-ons'''. You may have to create it. Note that this is a 'hidden' directory, and so you may have to turn on 'Show hidden files' in your file manager before you can see it.<br /> <br /> An alternative location for a 'System' installation is the '''/opt/Oolite/AddOns''' directory, but most users find this less convenient than '''~/.Oolite/Add-ons'''.<br /> <br /> === Windows ===<br /> The AddOns folder should be in the top level of the Oolite install directory (at the same level as the oolite.app folder). Historical: if you are using the GNUStep dedicated versions (pre-Jan 2006), then the AddOns folder must be created inside the oolite.app folder.<br /> <br /> == Caveats ==<br /> If you purchase a ship that is an OXP ship and save the game, you will only be able to load that commander as long as this OXP is installed in AddOns. If it's not, Oolite will give you an error instead of trying to load the commander.<br /> <br /> == Managing a stable of OXPs ==<br /> Nowadays we download OXZs through the in-game Expansions Manager - and it manages them for us. But if we tweak one, it usually becomes an OXP and must then be kept in the AddOns folder. Some older oxps have yet to be turned into OXZs and some experimental OXPs are in a similar position.<br /> <br /> So, if you have large numbers of these oxps, see the following threads from the BB.<br /> *Issues with multiple expansions? [[Find the culprit]]<br /> *Issues with [https://bb.oolite.space/viewtopic.php?p=273473#p273473 single OXPs]<br /> *Issues with [https://bb.oolite.space/viewtopic.php?p=273490#p273490 multiple OXPs]<br /> *Issues with different copies of the game on the [https://bb.oolite.space/viewtopic.php?p=272073#p272073 same hard drive]<br /> *If you found a nice set of expansions and want to share that with others, consider using the [[Oolite Starter]]. It allows you to export and send expansion sets to other players, who then can activate it on their side.<br /> <br /> == Diagnostics ==<br /> With some OXPs installed, the directory structure will look something like this:<br><br /> :'''...\AddOns\Basic-debug.oxp'''<br><br /> :'''...\AddOns\Cabal_Common_Library1.5.1.oxp'''<br><br /> :'''...\AddOns\Explorers'_Club_1.3.1_2012-01-21.oxp'''<br><br /> :'''...\AddOns\halsis.oxp'''<br><br /> :'''...\AddOns\Material Test Suite v1.2.oxp'''<br><br /> with other directories and files under each of the .oxp directories. You should only find .oxp directories immediately under a \AddOns directory.<br /> <br /> If none of your OXPs are working, are you playing in Strict Mode? Try starting a new commander from the Normal Start and see if the OXPs work then.<br /> <br /> If you edit the contents of one of your OXPs and cannot see the change, restart Oolite holding down <Shift> to force Oolite to re-read all the OXP files.<br /> <br /> If an OXP you installed is not working or is misbehaving, check the [[Latest.log]] file - you should see a list of the OXPs you have installed. You should see a trend in the names which will tell you if you have installed an OXP within another OXP (move it) or two versions of an OXP (remove the older one) or it is absent suggesting you put it in the wrong place or did not get the .oxp directory extension correct (did you unzip the OXP?).<br /> <br /> If you know how, a system-wide search for any directory ending in ".oxp" should pull up the OXPs you have installed and they should only appear immediately beneath a '''\AddOns''' directory and never inside another .oxp directory (this is an easily-done error when extracting a zip file).<br /> <br /> Note that an OXP in the AddOns folder ''trumps'' an 'identical' OXZ in the ManagedAddOns folder. So if the OXP is an older version, it will [https://bb.oolite.space/viewtopic.php?p=218632#p218632 disable] the newer OXZ.<br /> <br /> === AppleMacs ===<br /> ... Strict semicolon parsing is a Mac thing. Windows and Linux use GNUstep to parse plists and that apparently is more relaxed syntax-wise than whatever it is that the Mac uses. <br /> ::[[User:Another_commander|Another_commander]] from [https://bb.oolite.space/viewtopic.php?p=262814#p262814 A possible solution?] (2018).<br /> <br /> ... the libraries in the Mac seems to be less tolerant of some things than the GNUStep libraries on Linux:<br /> :*lists are enclosed in '<font color="Red">'''('''</font>' '<font color="Red">''')'''</font>' with items separated by '<font color="Red">''','''</font>' and there must ''not'' be a comma after the last item in the list.<br /> :*objects are enclosed in '<font color="Red">'''{'''</font>' '<font color="Red">'''}'''</font>' and consist of pairs: <key> = <value>.<br /> :*Each key/value pair must have a '<font color="Red">''';'''</font>' at the end, even the last pair in the object<br /> :*''if'' the object is a value in a key/value pair in another object, it's closing '<font color="Red">'''}'''</font>' must be followed by a '<font color="Red">''';'''</font>'.<br /> ::lifted from a PM from [[User:Dybal|Dybal]] (2020)<br /> <br /> == Creating an OXP ==<br /> [[File:Plist-XML-ASCII-ill.png|thumb|right|702px|XML (left) & OpenStep (right)]]<br /> Legacy script comes in two versions: XML & OpenStep. And then there is the much more complex Javascript.<br /> <br /> It is intended to be easy to create expansion packs. OpenStep is relatively easy - XML and Javascript less so.<br /> <br /> === Start your own OXP ===<br /> <br /> There are two quite extreme ways to go, and a compromise:<br /> <br /> * OXZs are just renamed zipped OXPs. You can decompress any existing OXZ, look inside and start tweaking.<br /> * And you can start from scratch by creating everything yourself - this will take some advanced knowledge.<br /> * There also is the middle path - to follow our predefined paths and use a bunch of templates.<br /> <br /> We have provided three varieties which your OXP can be. Advanced OXP creators can also combine them into a single OXP, while even more advanced creators keep them separate and then link them using dependencies. We'll cover that later.<br /> <br /> So what style of OXP is on your mind? Take one of the guided tours:<br /> <br /> *[[Create_Ship_OXP|Ship]]<br /> *[[Create_Equipment_OXP|Equipment]]<br /> *[[Create_Mission_OXP|Mission]]<br /> <br /> Alternatively, or when curious take a look at the [[OXP howto|OXP Howto]] page for full background information.<br /> <br /> === OXP resources ===<br /> *Here is an [[index of artefacts]] already created in OXPs.<br /> *[[Documenting your artefacts]] (OXP, ships and equipment)<br /> *[[OXP howto]]<br /> *[[Publishing your OXP]]<br /> <br /> *[https://github.com/cim--/oxp-build-scripts OXP Packaging Scripts] Cim's collection for Linux (2015)<br /> *[https://bb.oolite.space/viewtopic.php?p=275434#p275434 What can OXP's ''not'' change?] (2021)<br /> <br /> Older OXPs (from [[User:Aegidian|Aegidian]]'s day were written in [[Legacy Scripting]]. Modern OXPs are written in JavaScript. Specifically oolite.jsVersion 185, an Oolite specific variant of '''ECMAv5'''. It is the same Spidermonkey version (1.8.5 - March 2011) that Firefox 4 shipped with many years ago, but it is a special build for Oolite. This is the version that we have almost always had and it has not changed between versions of the game. It is unlikely to change in the future (due to the [https://bb.oolite.space/viewtopic.php?p=256623#p256623 immense amount of work] involved in tampering with it!).<br /> <br /> == Loading Order of OXPs ==<br /> OXPs loaded after other OXPs will "trump" the earlier OXPs in terms of their effects on the game. It is a similar situation with the vanilla game code, where the OXPs trump or overwrite the relevant sections of the basic oolite game. <br><br /> The loading order under Macs and Windows is alphabetical, while Linux is unpredictable. There is no solution for Linux load ordering as yet ([https://bb.oolite.space/viewtopic.php?p=261821#p261821 Svengali 2018]).<br /> <br /> *[[Handling OXP Dependencies with JavaScript]] - how to determine the loading order<br /> *[https://bb.oolite.space/viewtopic.php?p=189416#p189416 Nested OXP's in AddOns folder] (2012)<br /> *[https://bb.oolite.space/viewtopic.php?p=231750#p231750 Cim on the subject] (2015)<br /> *[https://bb.oolite.space/viewtopic.php?f=4&t=8928 OXP loading order] discussion, including Ahruman on the subject (2011)<br /> <br /> == AddOns and Managed AddOns folders ==<br /> All versions of Oolite have an AddOns folder. Only versions 1.79 (2013) and onwards have the Managed AddOns folder.<br /> <br /> The contents of the '''AddOns folder''' must ''not'' be zipped if they are to be recognised by Oolite - so OXZs will not work if they are in there.<br /> <br /> The contents of the '''Managed AddOns''' folder must contain a [[Manifest.plist]] if they are to be recognised by your [[Expansions Manager]] (or by [[Oolite Starter]]). The Expansions Manager only checks ''this'' folder, not the AddOns folder.<br /> <br /> == OXP Lists ==<br /> *[http://www.oolite.org/oxps/ Expansion Manager OXZ list] - orderable<br /> *[[OXP List]] - orderable<br /> *[[Guide to Unlisted OXPs]] - with links at the bottom to older lists<br /> <br /> *[[Brilliant but broken...]] great oxp's that need updating/fixing... (do you have the skills?)<br /> <br /> [[Category:Oolite expansion packs]]<br /> [[Category:Factual]]</div>

Hiran https://wiki.alioth.net/index.php?title=Expansions_Manager&diff=88151 Expansions Manager 2026-03-15T14:13:57Z

<p>Hiran: </p> <hr /> <div>[[File:Expansions Manager.png|right|thumb|500px|In-game Expansions Manager (Surround is from [[XenonUI]])]]<br /> The Expansion Pack Manager was devised by [[User:Cim|Cim]] for Oolite v.1.80 (2014), and ushered in the move from [[OXP]]s to OXZs.<br /> <br /> == Expansion Packs and Catalog ==<br /> <br /> *Note that there are many Expansions (OXPs/OXZs) which are not listed in the Manager. See [[Guide to Unlisted OXPs]]<br /> *Note that the Expansions Manager depends on ''this'' wiki - if this wiki is down (and you are - for example - looking at a backup of this page), you will need a [https://bb.oolite.space/viewtopic.php?p=273722#p273722 workaround].<br /> <br /> Oolite allows to be extended via Addons and [[OXP]]s. Expansion packs that are registered to the [https://github.com/OoliteProject/oolite-expansion-catalog Expansions Catalog] and it's [https://ooliteproject.github.io/oolite-expansion-catalog/index.html browsable version]<br /> can be downloaded and installed automatically.<br /> <br /> == Using the builtin Expansion Pack Manager (EPM) ==<br /> <br /> This is about the expansion manager that is available within Oolite.<br /> <br /> '''The arrow keys <font color="Red">←</font> & <font color="Red">→</font> skip between pages - and the arrow keys <font color="Red">↓</font> & <font color="Red">↑</font> move up and down within a page.'''<br /> <br /> '''Press <font color="Red"> i </font> for more information on your chosen expansion pack''': The URL for even more information is copied to your clipboard automatically when you do this (unless your computer runs Unix and you are playing Oolite v.1.90 or older). <br /> <br /> '''Press <font color="Red"> f </font> to filter the selection of 700-odd listed expansion packs.''' (''eg'' Search for keyword, Search for author, list only uninstalled packs ''etc'')<br /> <br /> ----<br /> <br /> <br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #ffaaaa;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> Oolite.org is currently down. Try http://oolite.space/ instead. <br /> <br /> To rejig your in-game [[Expansions Manager]] to the new address, see [https://bb.oolite.space/viewtopic.php?f=2&t=21368 here] and a_c's following post.<br /> <br /> (''Cholmondeley 13:40, 29 March 2023 (BST)'')<br /> <br /> Or use Hiran's [[Oolite Starter]] instead<br /> |}<br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #aabbbb;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> The current Windows Pre-releases/"nightlies" now allow you to directly skip to the OXP category (''eg'' .Ambience, Ships, Weapons ''etc''.), rather than scroll through dozens of pages to get there! <br><br /> They can be downloaded from the very bottom of the [https://oolite.space/#download Downloads page] or directly from GitHub, [https://github.com/OoliteProject/oolite/releases here].<br /> |}<br /> <br /> [[File:XenonUI (Expansions Manager).png|thumb|right|500px|The [[XenonUI]] OXP now provides all this information on your screen!<br><br /> On the left (Sub-Commands): filter/information/extract contents<br><br /> On the right: guide to colours]]<br /> === Guide to Expansions Manager list colours ===<br /> :'''Yellow''' Ready to download and install.<br /> :'''White''' Installed and at the current version.<br /> <br /> :'''Cyan''' Installed; updated pack available for download.<br /> :'''Orange''' Ready to download, but Oolite will also download extra packs to make it work.<br /> :'''Brown''' Conflicts with an already installed pack.<br /> :'''Gray''' Incompatible with this version of Oolite.<br /> <br /> :'''Red''' Manually installed: cannot also be installed automatically (''eg''. a tweaked oxp in the AddOns folder)<br /> :'''Blue''' Installed but no longer available for download.<br /> <br /> ----<br /> === Downloading and Unzipping an Expansion for Tweaking ===<br /> <br /> ''or for extracting information - for example, [[User:Ramirez|Ramirez]]'s oxz's contain glorious .pdf's stashed full of information!''<br /> <br /> *Go to the '''Expansion Pack Manager''' in game.<br /> *Select '''List installed expansion packs''' (the ''second'' choice at the bottom of the screen).<br /> *It will now show you the list of OXZ files in your ManagedAddOns folder.<br /> *Highlight the one you want to fiddle with and press <font color="Red">'''x'''</font>.<br /> <br /> *Oolite will then extract the OZX to your AddOns folder and add .off to the end of the expanded (was .oxz but is now .oxp) folder.<br /> *Change this '''.off''' to '''.oxp''' or '''.txt''' and tweak away to your heart's delight!<br /> <br /> *Oolite will now ignore the original version and will run the newly-expanded OXP version in AddOns (with any changes you now make to it).<br /> ''If you make a mess of it, deleting the .oxp version (in the AddOns folder) will cause Oolite to go back to using the OXZ version (in the Managed AddOns folder).''<br /> <br /> == Out-game Expansions Manager ("Oolite Starter") ==<br /> <br /> [[File:Oolite Start v.0.1.7.png|right]]<br /> <br /> The [[Oolite Starter]] allows easy switching between bnuches of Oolite versions, OXPs and savegames. Mr. Gimlet guides novice users (and does not hold back advising experienced ones).<br /> See v0.1.35 (Mar '26) at [https://github.com/OoliteProject/OoliteStarter this Github repository]. There are installers for Linux, Mac and Windows.<br /> <br /> '''Reference''': Thread with posts starts [https://bb.oolite.space/viewtopic.php?p=289311#p289311 here] (May 2023)<br /> <br /> == Tweaking OXPs ==<br /> (''adapted from LittleBear's [https://bb.oolite.space/viewtopic.php?p=273769#p273769 BB post]'')<br /> *The Windows text editor sneaks in invisible bits of code which muck up the OXPs: '''Avoid it like the plague!'''<br /> *To edit I'd recommend Edit Pad Lite 8. It's free, won't mess up the file format and is colour coded (so will highlight code typos).<br /> *''Eg''. If you have missed a ''',''' or a '''"''' in a text string, it will show up as ''white'' rather than ''yellow'', so you can quickly see the mistake. ;-)<br /> <br /> *Been a bit of a blessing when I've been C&Ping long lists of procedurally generated text from my latest.log to my array file.<br /> <br /> *See discussion [https://bb.oolite.space/viewtopic.php?p=273782#p273782 here] for AppleMac suggestions.<br /> *See [[How to tweak OXZ's]] for more tweakish details.<br /> <br /> == Scenario OXP's ==<br /> These OXP's create a scenario and force all other oxp's out of the game (unless you tweak the scenario to let one or two back in!). The only examples so far are the SOTL oxp's. There is an issue with the Expansions Manager:<br /> But ... one reason I didn't put SOTL in the manager is that [[SOTL Exploration]] depends on Loader, so if you install Exploration, you get the Loader OXP too (ie: Song_of_the_Labyrinth_Startup_1.1). Loader can't depend on Exploration, because if it did, Exploration won't load in the core scenario, and then Loader won't load because Exploration isn't there, and then you can't actually start the scenario game. But that means when you're installing from the manager, if you install Loader it can't then auto-install Exploration ... and then if you try to run Loader it'll probably go wrong with an entirely unhelpful error message.<br /> <br /> The manager ideally needs a new relationship type adding to handle that sort of "install-time but not run-time" dependency, but I never got round to that. (Cim 2021).<br /> <br /> == Links ==<br /> *[https://bb.oolite.space/viewtopic.php?p=273236#p273236 Expansion Manager Pack] Suggestions for change (2020).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=18077 copy information_url to clipboard] (2016-21).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=16888 User tags for expansions] (2014)<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16790 Are OXZ's an improvement ...] over OXP's (2014).<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16610 OXZ and balance] What should go on the Expansions Manager? (2014)<br /> *[https://bb.oolite.space/viewtopic.php?p=210354#p210354 Cim's announcement] of the concept (2013)<br /> <br /> *[https://bb.oolite.space/viewtopic.php?f=4&t=20932 Oolite's interaction with Expansion Packs] (2021)<br /> <br /> === Download Counter for oxp's ===<br /> *[https://bb.oolite.space/viewtopic.php?p=287386#p287386 Suggestions for fixing it] (2022)<br /> <br /> [[Category:Oolite]][[Category:Factual]][[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Expansions_Manager&diff=88150 Expansions Manager 2026-03-15T14:13:32Z

<p>Hiran: </p> <hr /> <div>[[File:Expansions Manager.png|right|thumb|500px|In-game Expansions Manager (Surround is from [[XenonUI]])]]<br /> The Expansion Pack Manager was devised by [[User:Cim|Cim]] for Oolite v.1.80 (2014), and ushered in the move from [[OXP]]s to OXZs.<br /> <br /> == Expansion Packs and Catalog ==<br /> <br /> *Note that there are many Expansions (OXPs/OXZs) which are not listed in the Manager. See [[Guide to Unlisted OXPs]]<br /> *Note that the Expansions Manager depends on ''this'' wiki - if this wiki is down (and you are - for example - looking at a backup of this page), you will need a [https://bb.oolite.space/viewtopic.php?p=273722#p273722 workaround].<br /> <br /> Oolite allows to be extended via Addons and [[OXP]]s. Expansion packs that are registered to the [https://github.com/OoliteProject/oolite-expansion-catalog Expansions Catalog] and it's [https://ooliteproject.github.io/oolite-expansion-catalog/index.html browsable version]<br /> can be downloaded and installed automatically.<br /> <br /> == Using the builtin Expansion Pack Manager (EPM) ==<br /> <br /> This is about the expansion manager that is available within Oolite.<br /> <br /> '''The arrow keys <font color="Red">←</font> & <font color="Red">→</font> skip between pages - and the arrow keys <font color="Red">↓</font> & <font color="Red">↑</font> move up and down within a page.'''<br /> <br /> '''Press <font color="Red"> i </font> for more information on your chosen expansion pack''': The URL for even more information is copied to your clipboard automatically when you do this (unless your computer runs Unix and you are playing Oolite v.1.90 or older). <br /> <br /> '''Press <font color="Red"> f </font> to filter the selection of 700-odd listed expansion packs.''' (''eg'' Search for keyword, Search for author, list only uninstalled packs ''etc'')<br /> <br /> ----<br /> <br /> <br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #ffaaaa;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> Oolite.org is currently down. Try http://oolite.space/ instead. <br /> <br /> To rejig your in-game [[Expansions Manager]] to the new address, see [https://bb.oolite.space/viewtopic.php?f=2&t=21368 here] and a_c's following post.<br /> <br /> (''Cholmondeley 13:40, 29 March 2023 (BST)'')<br /> <br /> Or use Hiran's [[Oolite Starter]] instead<br /> |}<br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #aabbbb;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> The current Windows Pre-releases/"nightlies" now allow you to directly skip to the OXP category (''eg'' .Ambience, Ships, Weapons ''etc''.), rather than scroll through dozens of pages to get there! <br><br /> They can be downloaded from the very bottom of the [https://oolite.space/#download Downloads page] or directly from GitHub, [https://github.com/OoliteProject/oolite/releases here].<br /> |}<br /> <br /> [[File:XenonUI (Expansions Manager).png|thumb|right|500px|The [[XenonUI]] OXP now provides all this information on your screen!<br><br /> On the left (Sub-Commands): filter/information/extract contents<br><br /> On the right: guide to colours]]<br /> === Guide to Expansions Manager list colours ===<br /> :'''Yellow''' Ready to download and install.<br /> :'''White''' Installed and at the current version.<br /> <br /> :'''Cyan''' Installed; updated pack available for download.<br /> :'''Orange''' Ready to download, but Oolite will also download extra packs to make it work.<br /> :'''Brown''' Conflicts with an already installed pack.<br /> :'''Gray''' Incompatible with this version of Oolite.<br /> <br /> :'''Red''' Manually installed: cannot also be installed automatically (''eg''. a tweaked oxp in the AddOns folder)<br /> :'''Blue''' Installed but no longer available for download.<br /> <br /> ----<br /> === Downloading and Unzipping an Expansion for Tweaking ===<br /> <br /> ''or for extracting information - for example, [[User:Ramirez|Ramirez]]'s oxz's contain glorious .pdf's stashed full of information!''<br /> <br /> *Go to the '''Expansion Pack Manager''' in game.<br /> *Select '''List installed expansion packs''' (the ''second'' choice at the bottom of the screen).<br /> *It will now show you the list of OXZ files in your ManagedAddOns folder.<br /> *Highlight the one you want to fiddle with and press <font color="Red">'''x'''</font>.<br /> <br /> *Oolite will then extract the OZX to your AddOns folder and add .off to the end of the expanded (was .oxz but is now .oxp) folder.<br /> *Change this '''.off''' to '''.oxp''' or '''.txt''' and tweak away to your heart's delight!<br /> <br /> *Oolite will now ignore the original version and will run the newly-expanded OXP version in AddOns (with any changes you now make to it).<br /> ''If you make a mess of it, deleting the .oxp version (in the AddOns folder) will cause Oolite to go back to using the OXZ version (in the Managed AddOns folder).''<br /> <br /> == Out-game Expansions Manager ("Oolite Starter") ==<br /> ----<br /> [[File:Oolite Start v.0.1.7.png|right]]<br /> <br /> The [[Oolite Starter]] allows easy switching between bnuches of Oolite versions, OXPs and savegames. Mr. Gimlet guides novice users (and does not hold back advising experienced ones).<br /> See v0.1.35 (Mar '26) at [https://github.com/OoliteProject/OoliteStarter this Github repository]. There are installers for Linux, Mac and Windows.<br /> <br /> '''Reference''': Thread with posts starts [https://bb.oolite.space/viewtopic.php?p=289311#p289311 here] (May 2023)<br /> <br /> == Tweaking OXPs ==<br /> (''adapted from LittleBear's [https://bb.oolite.space/viewtopic.php?p=273769#p273769 BB post]'')<br /> *The Windows text editor sneaks in invisible bits of code which muck up the OXPs: '''Avoid it like the plague!'''<br /> *To edit I'd recommend Edit Pad Lite 8. It's free, won't mess up the file format and is colour coded (so will highlight code typos).<br /> *''Eg''. If you have missed a ''',''' or a '''"''' in a text string, it will show up as ''white'' rather than ''yellow'', so you can quickly see the mistake. ;-)<br /> <br /> *Been a bit of a blessing when I've been C&Ping long lists of procedurally generated text from my latest.log to my array file.<br /> <br /> *See discussion [https://bb.oolite.space/viewtopic.php?p=273782#p273782 here] for AppleMac suggestions.<br /> *See [[How to tweak OXZ's]] for more tweakish details.<br /> <br /> == Scenario OXP's ==<br /> These OXP's create a scenario and force all other oxp's out of the game (unless you tweak the scenario to let one or two back in!). The only examples so far are the SOTL oxp's. There is an issue with the Expansions Manager:<br /> But ... one reason I didn't put SOTL in the manager is that [[SOTL Exploration]] depends on Loader, so if you install Exploration, you get the Loader OXP too (ie: Song_of_the_Labyrinth_Startup_1.1). Loader can't depend on Exploration, because if it did, Exploration won't load in the core scenario, and then Loader won't load because Exploration isn't there, and then you can't actually start the scenario game. But that means when you're installing from the manager, if you install Loader it can't then auto-install Exploration ... and then if you try to run Loader it'll probably go wrong with an entirely unhelpful error message.<br /> <br /> The manager ideally needs a new relationship type adding to handle that sort of "install-time but not run-time" dependency, but I never got round to that. (Cim 2021).<br /> <br /> == Links ==<br /> *[https://bb.oolite.space/viewtopic.php?p=273236#p273236 Expansion Manager Pack] Suggestions for change (2020).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=18077 copy information_url to clipboard] (2016-21).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=16888 User tags for expansions] (2014)<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16790 Are OXZ's an improvement ...] over OXP's (2014).<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16610 OXZ and balance] What should go on the Expansions Manager? (2014)<br /> *[https://bb.oolite.space/viewtopic.php?p=210354#p210354 Cim's announcement] of the concept (2013)<br /> <br /> *[https://bb.oolite.space/viewtopic.php?f=4&t=20932 Oolite's interaction with Expansion Packs] (2021)<br /> <br /> === Download Counter for oxp's ===<br /> *[https://bb.oolite.space/viewtopic.php?p=287386#p287386 Suggestions for fixing it] (2022)<br /> <br /> [[Category:Oolite]][[Category:Factual]][[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Expansions_Manager&diff=88149 Expansions Manager 2026-03-15T14:12:38Z

<p>Hiran: </p> <hr /> <div>[[File:Expansions Manager.png|right|thumb|500px|In-game Expansions Manager (Surround is from [[XenonUI]])]]<br /> The Expansion Pack Manager was devised by [[User:Cim|Cim]] for Oolite v.1.80 (2014), and ushered in the move from [[OXP]]s to OXZs.<br /> <br /> == Expansion Packs and Catalog ==<br /> <br /> *Note that there are many Expansions (OXPs/OXZs) which are not listed in the Manager. See [[Guide to Unlisted OXPs]]<br /> *Note that the Expansions Manager depends on ''this'' wiki - if this wiki is down (and you are - for example - looking at a backup of this page), you will need a [https://bb.oolite.space/viewtopic.php?p=273722#p273722 workaround].<br /> <br /> Oolite allows to be extended via Addons and [[OXP]]s. Expansion packs that are registered to the [https://github.com/OoliteProject/oolite-expansion-catalog Expansions Catalog] and it's [https://ooliteproject.github.io/oolite-expansion-catalog/index.html browsable version]<br /> can be downloaded and installed automatically.<br /> <br /> == Using the builtin Expansion Pack Manager (EPM) ==<br /> <br /> This is about the expansion manager that is available within Oolite.<br /> <br /> '''The arrow keys <font color="Red">←</font> & <font color="Red">→</font> skip between pages - and the arrow keys <font color="Red">↓</font> & <font color="Red">↑</font> move up and down within a page.'''<br /> <br /> '''Press <font color="Red"> i </font> for more information on your chosen expansion pack''': The URL for even more information is copied to your clipboard automatically when you do this (unless your computer runs Unix and you are playing Oolite v.1.90 or older). <br /> <br /> '''Press <font color="Red"> f </font> to filter the selection of 700-odd listed expansion packs.''' (''eg'' Search for keyword, Search for author, list only uninstalled packs ''etc'')<br /> <br /> ----<br /> <br /> <br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #ffaaaa;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> Oolite.org is currently down. Try http://oolite.space/ instead. <br /> <br /> To rejig your in-game [[Expansions Manager]] to the new address, see [https://bb.oolite.space/viewtopic.php?f=2&t=21368 here] and a_c's following post.<br /> <br /> (''Cholmondeley 13:40, 29 March 2023 (BST)'')<br /> <br /> Or use Hiran's [[Oolite Starter]] instead<br /> |}<br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #aabbbb;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> The current Windows Pre-releases/"nightlies" now allow you to directly skip to the OXP category (''eg'' .Ambience, Ships, Weapons ''etc''.), rather than scroll through dozens of pages to get there! <br><br /> They can be downloaded from the very bottom of the [https://oolite.space/#download Downloads page] or directly from GitHub, [https://github.com/OoliteProject/oolite/releases here].<br /> |}<br /> <br /> [[File:XenonUI (Expansions Manager).png|thumb|right|500px|The [[XenonUI]] OXP now provides all this information on your screen!<br><br /> On the left (Sub-Commands): filter/information/extract contents<br><br /> On the right: guide to colours]]<br /> === Guide to Expansions Manager list colours ===<br /> :'''Yellow''' Ready to download and install.<br /> :'''White''' Installed and at the current version.<br /> <br /> :'''Cyan''' Installed; updated pack available for download.<br /> :'''Orange''' Ready to download, but Oolite will also download extra packs to make it work.<br /> :'''Brown''' Conflicts with an already installed pack.<br /> :'''Gray''' Incompatible with this version of Oolite.<br /> <br /> :'''Red''' Manually installed: cannot also be installed automatically (''eg''. a tweaked oxp in the AddOns folder)<br /> :'''Blue''' Installed but no longer available for download.<br /> <br /> ----<br /> === Downloading and Unzipping an Expansion for Tweaking ===<br /> <br /> ''or for extracting information - for example, [[User:Ramirez|Ramirez]]'s oxz's contain glorious .pdf's stashed full of information!''<br /> <br /> *Go to the '''Expansion Pack Manager''' in game.<br /> *Select '''List installed expansion packs''' (the ''second'' choice at the bottom of the screen).<br /> *It will now show you the list of OXZ files in your ManagedAddOns folder.<br /> *Highlight the one you want to fiddle with and press <font color="Red">'''x'''</font>.<br /> <br /> *Oolite will then extract the OZX to your AddOns folder and add .off to the end of the expanded (was .oxz but is now .oxp) folder.<br /> *Change this '''.off''' to '''.oxp''' or '''.txt''' and tweak away to your heart's delight!<br /> <br /> *Oolite will now ignore the original version and will run the newly-expanded OXP version in AddOns (with any changes you now make to it).<br /> ''If you make a mess of it, deleting the .oxp version (in the AddOns folder) will cause Oolite to go back to using the OXZ version (in the Managed AddOns folder).''<br /> <br /> == Out-game Expansions Manager ("Oolite Starter") ==<br /> The [[Oolite Starter]] allows easy switching between bnuches of Oolite versions, OXPs and savegames. Mr. Gimlet guides novice users (and does not hold back advising experienced ones).<br /> See v0.1.35 (Mar '26) at [https://github.com/OoliteProject/OoliteStarter this Github repository]. There are installers for Linux, Mac and Windows.<br /> <br /> '''Reference''': Thread with posts starts [https://bb.oolite.space/viewtopic.php?p=289311#p289311 here] (May 2023)<br /> <br /> ----<br /> [[File:Oolite Start v.0.1.7.png|right]]<br /> <br /> == Tweaking OXPs ==<br /> (''adapted from LittleBear's [https://bb.oolite.space/viewtopic.php?p=273769#p273769 BB post]'')<br /> *The Windows text editor sneaks in invisible bits of code which muck up the OXPs: '''Avoid it like the plague!'''<br /> *To edit I'd recommend Edit Pad Lite 8. It's free, won't mess up the file format and is colour coded (so will highlight code typos).<br /> *''Eg''. If you have missed a ''',''' or a '''"''' in a text string, it will show up as ''white'' rather than ''yellow'', so you can quickly see the mistake. ;-)<br /> <br /> *Been a bit of a blessing when I've been C&Ping long lists of procedurally generated text from my latest.log to my array file.<br /> <br /> *See discussion [https://bb.oolite.space/viewtopic.php?p=273782#p273782 here] for AppleMac suggestions.<br /> *See [[How to tweak OXZ's]] for more tweakish details.<br /> <br /> == Scenario OXP's ==<br /> These OXP's create a scenario and force all other oxp's out of the game (unless you tweak the scenario to let one or two back in!). The only examples so far are the SOTL oxp's. There is an issue with the Expansions Manager:<br /> But ... one reason I didn't put SOTL in the manager is that [[SOTL Exploration]] depends on Loader, so if you install Exploration, you get the Loader OXP too (ie: Song_of_the_Labyrinth_Startup_1.1). Loader can't depend on Exploration, because if it did, Exploration won't load in the core scenario, and then Loader won't load because Exploration isn't there, and then you can't actually start the scenario game. But that means when you're installing from the manager, if you install Loader it can't then auto-install Exploration ... and then if you try to run Loader it'll probably go wrong with an entirely unhelpful error message.<br /> <br /> The manager ideally needs a new relationship type adding to handle that sort of "install-time but not run-time" dependency, but I never got round to that. (Cim 2021).<br /> <br /> == Links ==<br /> *[https://bb.oolite.space/viewtopic.php?p=273236#p273236 Expansion Manager Pack] Suggestions for change (2020).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=18077 copy information_url to clipboard] (2016-21).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=16888 User tags for expansions] (2014)<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16790 Are OXZ's an improvement ...] over OXP's (2014).<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16610 OXZ and balance] What should go on the Expansions Manager? (2014)<br /> *[https://bb.oolite.space/viewtopic.php?p=210354#p210354 Cim's announcement] of the concept (2013)<br /> <br /> *[https://bb.oolite.space/viewtopic.php?f=4&t=20932 Oolite's interaction with Expansion Packs] (2021)<br /> <br /> === Download Counter for oxp's ===<br /> *[https://bb.oolite.space/viewtopic.php?p=287386#p287386 Suggestions for fixing it] (2022)<br /> <br /> [[Category:Oolite]][[Category:Factual]][[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Expansions_Manager&diff=88148 Expansions Manager 2026-03-15T14:11:11Z

<p>Hiran: </p> <hr /> <div>[[File:Expansions Manager.png|right|thumb|500px|In-game Expansions Manager (Surround is from [[XenonUI]])]]<br /> The Expansion Pack Manager was devised by [[User:Cim|Cim]] for Oolite v.1.80 (2014), and ushered in the move from [[OXP]]s to OXZs.<br /> <br /> == Expansion Packs and Catalog ==<br /> <br /> *Note that there are many Expansions (OXPs/OXZs) which are not listed in the Manager. See [[Guide to Unlisted OXPs]]<br /> *Note that the Expansions Manager depends on ''this'' wiki - if this wiki is down (and you are - for example - looking at a backup of this page), you will need a [https://bb.oolite.space/viewtopic.php?p=273722#p273722 workaround].<br /> <br /> Oolite allows to be extended via Addons and [[OXP]]s. Expansion packs that are registered to the [https://github.com/OoliteProject/oolite-expansion-catalog Expansions Catalog] and it's [https://ooliteproject.github.io/oolite-expansion-catalog/index.html browsable version]<br /> can be downloaded and installed automatically.<br /> <br /> == Using the builtin Expansion Pack Manager (EPM) ==<br /> <br /> This is about the expansion manager that is available within Oolite.<br /> <br /> '''The arrow keys <font color="Red">←</font> & <font color="Red">→</font> skip between pages - and the arrow keys <font color="Red">↓</font> & <font color="Red">↑</font> move up and down within a page.'''<br /> <br /> '''Press <font color="Red"> i </font> for more information on your chosen expansion pack''': The URL for even more information is copied to your clipboard automatically when you do this (unless your computer runs Unix and you are playing Oolite v.1.90 or older). <br /> <br /> '''Press <font color="Red"> f </font> to filter the selection of 700-odd listed expansion packs.''' (''eg'' Search for keyword, Search for author, list only uninstalled packs ''etc'')<br /> <br /> ----<br /> <br /> <br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #ffaaaa;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> Oolite.org is currently down. Try http://oolite.space/ instead. <br /> <br /> To rejig your in-game [[Expansions Manager]] to the new address, see [https://bb.oolite.space/viewtopic.php?f=2&t=21368 here] and a_c's following post.<br /> <br /> (''Cholmondeley 13:40, 29 March 2023 (BST)'')<br /> <br /> Or use Hiran's [[Oolite Starter]] instead<br /> |}<br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #aabbbb;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> The current Windows Pre-releases/"nightlies" now allow you to directly skip to the OXP category (''eg'' .Ambience, Ships, Weapons ''etc''.), rather than scroll through dozens of pages to get there! <br><br /> They can be downloaded from the very bottom of the [https://oolite.space/#download Downloads page] or directly from GitHub, [https://github.com/OoliteProject/oolite/releases here].<br /> |}<br /> <br /> [[File:XenonUI (Expansions Manager).png|thumb|right|500px|The [[XenonUI]] OXP now provides all this information on your screen!<br><br /> On the left (Sub-Commands): filter/information/extract contents<br><br /> On the right: guide to colours]]<br /> === Guide to Expansions Manager list colours ===<br /> :'''Yellow''' Ready to download and install.<br /> :'''White''' Installed and at the current version.<br /> <br /> :'''Cyan''' Installed; updated pack available for download.<br /> :'''Orange''' Ready to download, but Oolite will also download extra packs to make it work.<br /> :'''Brown''' Conflicts with an already installed pack.<br /> :'''Gray''' Incompatible with this version of Oolite.<br /> <br /> :'''Red''' Manually installed: cannot also be installed automatically (''eg''. a tweaked oxp in the AddOns folder)<br /> :'''Blue''' Installed but no longer available for download.<br /> <br /> ----<br /> === Downloading and Unzipping an Expansion for Tweaking ===<br /> <br /> ''or for extracting information - for example, [[User:Ramirez|Ramirez]]'s oxz's contain glorious .pdf's stashed full of information!''<br /> <br /> *Go to the '''Expansion Pack Manager''' in game.<br /> *Select '''List installed expansion packs''' (the ''second'' choice at the bottom of the screen).<br /> *It will now show you the list of OXZ files in your ManagedAddOns folder.<br /> *Highlight the one you want to fiddle with and press <font color="Red">'''x'''</font>.<br /> <br /> *Oolite will then extract the OZX to your AddOns folder and add .off to the end of the expanded (was .oxz but is now .oxp) folder.<br /> *Change this '''.off''' to '''.oxp''' or '''.txt''' and tweak away to your heart's delight!<br /> <br /> *Oolite will now ignore the original version and will run the newly-expanded OXP version in AddOns (with any changes you now make to it).<br /> ''If you make a mess of it, deleting the .oxp version (in the AddOns folder) will cause Oolite to go back to using the OXZ version (in the Managed AddOns folder).''<br /> <br /> == Out-game Expansions Manager ("Oolite Starter") ==<br /> The [[Oolite Starter]] allows easy switching between bnuches of Oolite versions, OXPs and savegames. Mr. Gimlet guides novice users (and does not hold back advising experienced ones).<br /> See v0.1.35 (Mar '26) at [https://github.com/OoliteProject/OoliteStarter this Github repository]. There are installers for Linux, Mac and Windows.<br /> <br /> '''Reference''': Thread with posts starts [https://bb.oolite.space/viewtopic.php?p=289311#p289311 here] (May 2023)<br /> <br /> The AppleMac version is not yet fully functional - one cannot start up the savegame of choice, but includes an automatically updated list of every OXZ on the oolite.space website as well as managing the OXPs in your AddOns folder. The fact that the AppleMac version of Oolite does not honor passed command line parameters is more a bug on Oolite than on the Oolite Starter.<br /> <br /> == Tweaking OXPs ==<br /> (''adapted from LittleBear's [https://bb.oolite.space/viewtopic.php?p=273769#p273769 BB post]'')<br /> *The Windows text editor sneaks in invisible bits of code which muck up the OXPs: '''Avoid it like the plague!'''<br /> *To edit I'd recommend Edit Pad Lite 8. It's free, won't mess up the file format and is colour coded (so will highlight code typos).<br /> *''Eg''. If you have missed a ''',''' or a '''"''' in a text string, it will show up as ''white'' rather than ''yellow'', so you can quickly see the mistake. ;-)<br /> <br /> *Been a bit of a blessing when I've been C&Ping long lists of procedurally generated text from my latest.log to my array file.<br /> <br /> *See discussion [https://bb.oolite.space/viewtopic.php?p=273782#p273782 here] for AppleMac suggestions.<br /> *See [[How to tweak OXZ's]] for more tweakish details.<br /> <br /> == Scenario OXP's ==<br /> These OXP's create a scenario and force all other oxp's out of the game (unless you tweak the scenario to let one or two back in!). The only examples so far are the SOTL oxp's. There is an issue with the Expansions Manager:<br /> But ... one reason I didn't put SOTL in the manager is that [[SOTL Exploration]] depends on Loader, so if you install Exploration, you get the Loader OXP too (ie: Song_of_the_Labyrinth_Startup_1.1). Loader can't depend on Exploration, because if it did, Exploration won't load in the core scenario, and then Loader won't load because Exploration isn't there, and then you can't actually start the scenario game. But that means when you're installing from the manager, if you install Loader it can't then auto-install Exploration ... and then if you try to run Loader it'll probably go wrong with an entirely unhelpful error message.<br /> <br /> The manager ideally needs a new relationship type adding to handle that sort of "install-time but not run-time" dependency, but I never got round to that. (Cim 2021).<br /> <br /> == Links ==<br /> *[https://bb.oolite.space/viewtopic.php?p=273236#p273236 Expansion Manager Pack] Suggestions for change (2020).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=18077 copy information_url to clipboard] (2016-21).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=16888 User tags for expansions] (2014)<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16790 Are OXZ's an improvement ...] over OXP's (2014).<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16610 OXZ and balance] What should go on the Expansions Manager? (2014)<br /> *[https://bb.oolite.space/viewtopic.php?p=210354#p210354 Cim's announcement] of the concept (2013)<br /> <br /> *[https://bb.oolite.space/viewtopic.php?f=4&t=20932 Oolite's interaction with Expansion Packs] (2021)<br /> <br /> === Download Counter for oxp's ===<br /> *[https://bb.oolite.space/viewtopic.php?p=287386#p287386 Suggestions for fixing it] (2022)<br /> <br /> <br /> ----<br /> [[File:Oolite Start v.0.1.7.png|right]]<br /> <br /> [[Category:Oolite]][[Category:Factual]][[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Expansions_Manager&diff=88147 Expansions Manager 2026-03-15T14:10:42Z

<p>Hiran: </p> <hr /> <div>[[File:Expansions Manager.png|right|thumb|500px|In-game Expansions Manager (Surround is from [[XenonUI]])]]<br /> The Expansion Pack Manager was devised by [[User:Cim|Cim]] for Oolite v.1.80 (2014), and ushered in the move from [[OXP]]s to OXZs.<br /> <br /> == Expansion Packs and Catalog ==<br /> <br /> *Note that there are many Expansions (OXPs/OXZs) which are not listed in the Manager. See [[Guide to Unlisted OXPs]]<br /> *Note that the Expansions Manager depends on ''this'' wiki - if this wiki is down (and you are - for example - looking at a backup of this page), you will need a [https://bb.oolite.space/viewtopic.php?p=273722#p273722 workaround].<br /> <br /> Oolite allows to be extended via Addons and [[OXP]]s. Expansion packs that are registered to the [https://github.com/OoliteProject/oolite-expansion-catalog Expansions Catalog] and it's [https://ooliteproject.github.io/oolite-expansion-catalog/index.html browsable version]<br /> can be downloaded and installed automatically.<br /> <br /> == Using the builtin Expansion Pack Manager (EPM) ==<br /> <br /> This is about the expansion manager that is available within Oolite.<br /> <br /> '''The arrow keys <font color="Red">←</font> & <font color="Red">→</font> skip between pages - and the arrow keys <font color="Red">↓</font> & <font color="Red">↑</font> move up and down within a page.'''<br /> <br /> '''Press <font color="Red"> i </font> for more information on your chosen expansion pack''': The URL for even more information is copied to your clipboard automatically when you do this (unless your computer runs Unix and you are playing Oolite v.1.90 or older). <br /> <br /> '''Press <font color="Red"> f </font> to filter the selection of 700-odd listed expansion packs.''' (''eg'' Search for keyword, Search for author, list only uninstalled packs ''etc'')<br /> <br /> ----<br /> <br /> <br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #ffaaaa;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> Oolite.org is currently down. Try http://oolite.space/ instead. <br /> <br /> To rejig your in-game [[Expansions Manager]] to the new address, see [https://bb.oolite.space/viewtopic.php?f=2&t=21368 here] and a_c's following post.<br /> <br /> (''Cholmondeley 13:40, 29 March 2023 (BST)'')<br /> <br /> Or use Hiran's [[Oolite Starter]] instead<br /> |}<br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #aabbbb;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> The current Windows Pre-releases/"nightlies" now allow you to directly skip to the OXP category (''eg'' .Ambience, Ships, Weapons ''etc''.), rather than scroll through dozens of pages to get there! <br><br /> They can be downloaded from the very bottom of the [https://oolite.space/#download Downloads page] or directly from GitHub, [https://github.com/OoliteProject/oolite/releases here].<br /> |}<br /> <br /> [[File:XenonUI (Expansions Manager).png|thumb|right|500px|The [[XenonUI]] OXP now provides all this information on your screen!<br><br /> On the left (Sub-Commands): filter/information/extract contents<br><br /> On the right: guide to colours]]<br /> === Guide to Expansions Manager list colours ===<br /> :'''Yellow''' Ready to download and install.<br /> :'''White''' Installed and at the current version.<br /> <br /> :'''Cyan''' Installed; updated pack available for download.<br /> :'''Orange''' Ready to download, but Oolite will also download extra packs to make it work.<br /> :'''Brown''' Conflicts with an already installed pack.<br /> :'''Gray''' Incompatible with this version of Oolite.<br /> <br /> :'''Red''' Manually installed: cannot also be installed automatically (''eg''. a tweaked oxp in the AddOns folder)<br /> :'''Blue''' Installed but no longer available for download.<br /> <br /> ----<br /> === Downloading and Unzipping an Expansion for Tweaking ===<br /> <br /> ''or for extracting information - for example, [[User:Ramirez|Ramirez]]'s oxz's contain glorious .pdf's stashed full of information!''<br /> <br /> *Go to the '''Expansion Pack Manager''' in game.<br /> *Select '''List installed expansion packs''' (the ''second'' choice at the bottom of the screen).<br /> *It will now show you the list of OXZ files in your ManagedAddOns folder.<br /> *Highlight the one you want to fiddle with and press <font color="Red">'''x'''</font>.<br /> <br /> *Oolite will then extract the OZX to your AddOns folder and add .off to the end of the expanded (was .oxz but is now .oxp) folder.<br /> *Change this '''.off''' to '''.oxp''' or '''.txt''' and tweak away to your heart's delight!<br /> <br /> *Oolite will now ignore the original version and will run the newly-expanded OXP version in AddOns (with any changes you now make to it).<br /> ''If you make a mess of it, deleting the .oxp version (in the AddOns folder) will cause Oolite to go back to using the OXZ version (in the Managed AddOns folder).''<br /> <br /> == Out-game Expansions Manager ("Oolite Starter") ==<br /> The [[Oolite Starter]] allows easy switching between bnuches of Oolite versions, OXPs and savegames. Mr. Gimlet guides novice users (and does not hold back advising experienced ones).<br /> See v0.1.35 (Mar '26) at [https://github.com/OoliteProject/OoliteStarter this Github repository]. There are installers for Linux, Mac and Windows.<br /> <br /> '''Reference''': Thread with posts starts [https://bb.oolite.space/viewtopic.php?p=289311#p289311 here] (May 2023)<br /> <br /> The AppleMac version is not yet fully functional - one cannot start up the savegame of choice, but includes an automatically updated list of every OXZ on the oolite.space website as well as managing the OXPs in your AddOns folder. The fact that the AppleMac version of Oolite does not honor passed command line parameters is more a bug on Oolite than on the Oolite Starter.<br /> <br /> === Tweaking OXPs ===<br /> (''adapted from LittleBear's [https://bb.oolite.space/viewtopic.php?p=273769#p273769 BB post]'')<br /> *The Windows text editor sneaks in invisible bits of code which muck up the OXPs: '''Avoid it like the plague!'''<br /> *To edit I'd recommend Edit Pad Lite 8. It's free, won't mess up the file format and is colour coded (so will highlight code typos).<br /> *''Eg''. If you have missed a ''',''' or a '''"''' in a text string, it will show up as ''white'' rather than ''yellow'', so you can quickly see the mistake. ;-)<br /> <br /> *Been a bit of a blessing when I've been C&Ping long lists of procedurally generated text from my latest.log to my array file.<br /> <br /> *See discussion [https://bb.oolite.space/viewtopic.php?p=273782#p273782 here] for AppleMac suggestions.<br /> *See [[How to tweak OXZ's]] for more tweakish details.<br /> <br /> == Scenario OXP's ==<br /> These OXP's create a scenario and force all other oxp's out of the game (unless you tweak the scenario to let one or two back in!). The only examples so far are the SOTL oxp's. There is an issue with the Expansions Manager:<br /> But ... one reason I didn't put SOTL in the manager is that [[SOTL Exploration]] depends on Loader, so if you install Exploration, you get the Loader OXP too (ie: Song_of_the_Labyrinth_Startup_1.1). Loader can't depend on Exploration, because if it did, Exploration won't load in the core scenario, and then Loader won't load because Exploration isn't there, and then you can't actually start the scenario game. But that means when you're installing from the manager, if you install Loader it can't then auto-install Exploration ... and then if you try to run Loader it'll probably go wrong with an entirely unhelpful error message.<br /> <br /> The manager ideally needs a new relationship type adding to handle that sort of "install-time but not run-time" dependency, but I never got round to that. (Cim 2021).<br /> <br /> == Links ==<br /> *[https://bb.oolite.space/viewtopic.php?p=273236#p273236 Expansion Manager Pack] Suggestions for change (2020).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=18077 copy information_url to clipboard] (2016-21).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=16888 User tags for expansions] (2014)<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16790 Are OXZ's an improvement ...] over OXP's (2014).<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16610 OXZ and balance] What should go on the Expansions Manager? (2014)<br /> *[https://bb.oolite.space/viewtopic.php?p=210354#p210354 Cim's announcement] of the concept (2013)<br /> <br /> *[https://bb.oolite.space/viewtopic.php?f=4&t=20932 Oolite's interaction with Expansion Packs] (2021)<br /> <br /> === Download Counter for oxp's ===<br /> *[https://bb.oolite.space/viewtopic.php?p=287386#p287386 Suggestions for fixing it] (2022)<br /> <br /> <br /> ----<br /> [[File:Oolite Start v.0.1.7.png|right]]<br /> <br /> [[Category:Oolite]][[Category:Factual]][[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Expansions_Manager&diff=88146 Expansions Manager 2026-03-15T14:08:17Z

<p>Hiran: </p> <hr /> <div>[[File:Expansions Manager.png|right|thumb|500px|In-game Expansions Manager (Surround is from [[XenonUI]])]]<br /> The Expansion Pack Manager was devised by [[User:Cim|Cim]] for Oolite v.1.80 (2014), and ushered in the move from [[OXP]]s to OXZs.<br /> <br /> == Expansion Packs and Catalog ==<br /> <br /> *Note that there are many Expansions (OXPs/OXZs) which are not listed in the Manager. See [[Guide to Unlisted OXPs]]<br /> *Note that the Expansions Manager depends on ''this'' wiki - if this wiki is down (and you are - for example - looking at a backup of this page), you will need a [https://bb.oolite.space/viewtopic.php?p=273722#p273722 workaround].<br /> <br /> Oolite allows to be extended via Addons and [[OXP]]s. Expansion packs that are registered to the [https://github.com/OoliteProject/oolite-expansion-catalog Expansions Catalog] and it's [https://ooliteproject.github.io/oolite-expansion-catalog/index.html browsable version]<br /> can be downloaded and installed automatically.<br /> <br /> == Using the builtin Expansion Pack Manager (EPM) ==<br /> <br /> This is about the expansion manager that is available within Oolite.<br /> <br /> '''The arrow keys <font color="Red">←</font> & <font color="Red">→</font> skip between pages - and the arrow keys <font color="Red">↓</font> & <font color="Red">↑</font> move up and down within a page.'''<br /> <br /> '''Press <font color="Red"> i </font> for more information on your chosen expansion pack''': The URL for even more information is copied to your clipboard automatically when you do this (unless your computer runs Unix and you are playing Oolite v.1.90 or older). <br /> <br /> '''Press <font color="Red"> f </font> to filter the selection of 700-odd listed expansion packs.''' (''eg'' Search for keyword, Search for author, list only uninstalled packs ''etc'')<br /> <br /> ----<br /> <br /> <br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #ffaaaa;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> Oolite.org is currently down. Try http://oolite.space/ instead. <br /> <br /> To rejig your in-game [[Expansions Manager]] to the new address, see [https://bb.oolite.space/viewtopic.php?f=2&t=21368 here] and a_c's following post.<br /> <br /> (''Cholmondeley 13:40, 29 March 2023 (BST)'')<br /> <br /> Or use Hiran's [[Oolite Starter]] instead<br /> |}<br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #aabbbb;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> The current Windows Pre-releases/"nightlies" now allow you to directly skip to the OXP category (''eg'' .Ambience, Ships, Weapons ''etc''.), rather than scroll through dozens of pages to get there! <br><br /> They can be downloaded from the very bottom of the [https://oolite.space/#download Downloads page] or directly from GitHub, [https://github.com/OoliteProject/oolite/releases here].<br /> |}<br /> <br /> [[File:XenonUI (Expansions Manager).png|thumb|right|500px|The [[XenonUI]] OXP now provides all this information on your screen!<br><br /> On the left (Sub-Commands): filter/information/extract contents<br><br /> On the right: guide to colours]]<br /> == Guide to Expansions Manager list colours ==<br /> :'''Yellow''' Ready to download and install.<br /> :'''White''' Installed and at the current version.<br /> <br /> :'''Cyan''' Installed; updated pack available for download.<br /> :'''Orange''' Ready to download, but Oolite will also download extra packs to make it work.<br /> :'''Brown''' Conflicts with an already installed pack.<br /> :'''Gray''' Incompatible with this version of Oolite.<br /> <br /> :'''Red''' Manually installed: cannot also be installed automatically (''eg''. a tweaked oxp in the AddOns folder)<br /> :'''Blue''' Installed but no longer available for download.<br /> <br /> ----<br /> == Downloading and Unzipping an Expansion for Tweaking ==<br /> <br /> ''or for extracting information - for example, [[User:Ramirez|Ramirez]]'s oxz's contain glorious .pdf's stashed full of information!''<br /> <br /> *Go to the '''Expansion Pack Manager''' in game.<br /> *Select '''List installed expansion packs''' (the ''second'' choice at the bottom of the screen).<br /> *It will now show you the list of OXZ files in your ManagedAddOns folder.<br /> *Highlight the one you want to fiddle with and press <font color="Red">'''x'''</font>.<br /> <br /> *Oolite will then extract the OZX to your AddOns folder and add .off to the end of the expanded (was .oxz but is now .oxp) folder.<br /> *Change this '''.off''' to '''.oxp''' or '''.txt''' and tweak away to your heart's delight!<br /> <br /> *Oolite will now ignore the original version and will run the newly-expanded OXP version in AddOns (with any changes you now make to it).<br /> ''If you make a mess of it, deleting the .oxp version (in the AddOns folder) will cause Oolite to go back to using the OXZ version (in the Managed AddOns folder).''<br /> <br /> === Tweaking OXPs ===<br /> (''adapted from LittleBear's [https://bb.oolite.space/viewtopic.php?p=273769#p273769 BB post]'')<br /> *The Windows text editor sneaks in invisible bits of code which muck up the OXPs: '''Avoid it like the plague!'''<br /> *To edit I'd recommend Edit Pad Lite 8. It's free, won't mess up the file format and is colour coded (so will highlight code typos).<br /> *''Eg''. If you have missed a ''',''' or a '''"''' in a text string, it will show up as ''white'' rather than ''yellow'', so you can quickly see the mistake. ;-)<br /> <br /> *Been a bit of a blessing when I've been C&Ping long lists of procedurally generated text from my latest.log to my array file.<br /> <br /> *See discussion [https://bb.oolite.space/viewtopic.php?p=273782#p273782 here] for AppleMac suggestions.<br /> *See [[How to tweak OXZ's]] for more tweakish details.<br /> <br /> == Scenario OXP's ==<br /> These OXP's create a scenario and force all other oxp's out of the game (unless you tweak the scenario to let one or two back in!). The only examples so far are the SOTL oxp's. There is an issue with the Expansions Manager:<br /> But ... one reason I didn't put SOTL in the manager is that [[SOTL Exploration]] depends on Loader, so if you install Exploration, you get the Loader OXP too (ie: Song_of_the_Labyrinth_Startup_1.1). Loader can't depend on Exploration, because if it did, Exploration won't load in the core scenario, and then Loader won't load because Exploration isn't there, and then you can't actually start the scenario game. But that means when you're installing from the manager, if you install Loader it can't then auto-install Exploration ... and then if you try to run Loader it'll probably go wrong with an entirely unhelpful error message.<br /> <br /> The manager ideally needs a new relationship type adding to handle that sort of "install-time but not run-time" dependency, but I never got round to that. (Cim 2021).<br /> <br /> == Links ==<br /> *[https://bb.oolite.space/viewtopic.php?p=273236#p273236 Expansion Manager Pack] Suggestions for change (2020).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=18077 copy information_url to clipboard] (2016-21).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=16888 User tags for expansions] (2014)<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16790 Are OXZ's an improvement ...] over OXP's (2014).<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16610 OXZ and balance] What should go on the Expansions Manager? (2014)<br /> *[https://bb.oolite.space/viewtopic.php?p=210354#p210354 Cim's announcement] of the concept (2013)<br /> <br /> *[https://bb.oolite.space/viewtopic.php?f=4&t=20932 Oolite's interaction with Expansion Packs] (2021)<br /> <br /> === Download Counter for oxp's ===<br /> *[https://bb.oolite.space/viewtopic.php?p=287386#p287386 Suggestions for fixing it] (2022)<br /> <br /> <br /> ----<br /> [[File:Oolite Start v.0.1.7.png|right]]<br /> == Out-game Expansions Manager ("Oolite Starter") ==<br /> The [[Oolite Starter]] allows easy switching between bnuches of Oolite versions, OXPs and savegames. Mr. Gimlet guides novice users (and does not hold back advising experienced ones).<br /> See v0.1.35 (Mar '26) at [https://github.com/OoliteProject/OoliteStarter this Github repository]. There are installers for Linux, Mac and Windows.<br /> <br /> '''Reference''': Thread with posts starts [https://bb.oolite.space/viewtopic.php?p=289311#p289311 here] (May 2023)<br /> <br /> The AppleMac version is not yet fully functional - one cannot start up the savegame of choice, but includes an automatically updated list of every OXZ on the oolite.space website as well as managing the OXPs in your AddOns folder. The fact that the AppleMac version of Oolite does not honor passed command line parameters is more a bug on Oolite than on the Oolite Starter.<br /> <br /> [[Category:Oolite]][[Category:Factual]][[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Expansions_Manager&diff=88145 Expansions Manager 2026-03-15T14:08:00Z

<p>Hiran: </p> <hr /> <div>[[File:Expansions Manager.png|right|thumb|500px|In-game Expansions Manager (Surround is from [[XenonUI]])]]<br /> The Expansion Pack Manager was devised by [[User:Cim|Cim]] for Oolite v.1.80 (2014), and ushered in the move from [[OXP]]s to OXZs.<br /> <br /> == Expansion Packs and Catalog<br /> <br /> *Note that there are many Expansions (OXPs/OXZs) which are not listed in the Manager. See [[Guide to Unlisted OXPs]]<br /> *Note that the Expansions Manager depends on ''this'' wiki - if this wiki is down (and you are - for example - looking at a backup of this page), you will need a [https://bb.oolite.space/viewtopic.php?p=273722#p273722 workaround].<br /> <br /> Oolite allows to be extended via Addons and [[OXP]]s. Expansion packs that are registered to the [https://github.com/OoliteProject/oolite-expansion-catalog Expansions Catalog] and it's [https://ooliteproject.github.io/oolite-expansion-catalog/index.html browsable version]<br /> can be downloaded and installed automatically.<br /> <br /> == Using the builtin Expansion Pack Manager (EPM) ==<br /> <br /> This is about the expansion manager that is available within Oolite.<br /> <br /> '''The arrow keys <font color="Red">←</font> & <font color="Red">→</font> skip between pages - and the arrow keys <font color="Red">↓</font> & <font color="Red">↑</font> move up and down within a page.'''<br /> <br /> '''Press <font color="Red"> i </font> for more information on your chosen expansion pack''': The URL for even more information is copied to your clipboard automatically when you do this (unless your computer runs Unix and you are playing Oolite v.1.90 or older). <br /> <br /> '''Press <font color="Red"> f </font> to filter the selection of 700-odd listed expansion packs.''' (''eg'' Search for keyword, Search for author, list only uninstalled packs ''etc'')<br /> <br /> ----<br /> <br /> <br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #ffaaaa;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> Oolite.org is currently down. Try http://oolite.space/ instead. <br /> <br /> To rejig your in-game [[Expansions Manager]] to the new address, see [https://bb.oolite.space/viewtopic.php?f=2&t=21368 here] and a_c's following post.<br /> <br /> (''Cholmondeley 13:40, 29 March 2023 (BST)'')<br /> <br /> Or use Hiran's [[Oolite Starter]] instead<br /> |}<br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #aabbbb;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> The current Windows Pre-releases/"nightlies" now allow you to directly skip to the OXP category (''eg'' .Ambience, Ships, Weapons ''etc''.), rather than scroll through dozens of pages to get there! <br><br /> They can be downloaded from the very bottom of the [https://oolite.space/#download Downloads page] or directly from GitHub, [https://github.com/OoliteProject/oolite/releases here].<br /> |}<br /> <br /> [[File:XenonUI (Expansions Manager).png|thumb|right|500px|The [[XenonUI]] OXP now provides all this information on your screen!<br><br /> On the left (Sub-Commands): filter/information/extract contents<br><br /> On the right: guide to colours]]<br /> == Guide to Expansions Manager list colours ==<br /> :'''Yellow''' Ready to download and install.<br /> :'''White''' Installed and at the current version.<br /> <br /> :'''Cyan''' Installed; updated pack available for download.<br /> :'''Orange''' Ready to download, but Oolite will also download extra packs to make it work.<br /> :'''Brown''' Conflicts with an already installed pack.<br /> :'''Gray''' Incompatible with this version of Oolite.<br /> <br /> :'''Red''' Manually installed: cannot also be installed automatically (''eg''. a tweaked oxp in the AddOns folder)<br /> :'''Blue''' Installed but no longer available for download.<br /> <br /> ----<br /> == Downloading and Unzipping an Expansion for Tweaking ==<br /> <br /> ''or for extracting information - for example, [[User:Ramirez|Ramirez]]'s oxz's contain glorious .pdf's stashed full of information!''<br /> <br /> *Go to the '''Expansion Pack Manager''' in game.<br /> *Select '''List installed expansion packs''' (the ''second'' choice at the bottom of the screen).<br /> *It will now show you the list of OXZ files in your ManagedAddOns folder.<br /> *Highlight the one you want to fiddle with and press <font color="Red">'''x'''</font>.<br /> <br /> *Oolite will then extract the OZX to your AddOns folder and add .off to the end of the expanded (was .oxz but is now .oxp) folder.<br /> *Change this '''.off''' to '''.oxp''' or '''.txt''' and tweak away to your heart's delight!<br /> <br /> *Oolite will now ignore the original version and will run the newly-expanded OXP version in AddOns (with any changes you now make to it).<br /> ''If you make a mess of it, deleting the .oxp version (in the AddOns folder) will cause Oolite to go back to using the OXZ version (in the Managed AddOns folder).''<br /> <br /> === Tweaking OXPs ===<br /> (''adapted from LittleBear's [https://bb.oolite.space/viewtopic.php?p=273769#p273769 BB post]'')<br /> *The Windows text editor sneaks in invisible bits of code which muck up the OXPs: '''Avoid it like the plague!'''<br /> *To edit I'd recommend Edit Pad Lite 8. It's free, won't mess up the file format and is colour coded (so will highlight code typos).<br /> *''Eg''. If you have missed a ''',''' or a '''"''' in a text string, it will show up as ''white'' rather than ''yellow'', so you can quickly see the mistake. ;-)<br /> <br /> *Been a bit of a blessing when I've been C&Ping long lists of procedurally generated text from my latest.log to my array file.<br /> <br /> *See discussion [https://bb.oolite.space/viewtopic.php?p=273782#p273782 here] for AppleMac suggestions.<br /> *See [[How to tweak OXZ's]] for more tweakish details.<br /> <br /> == Scenario OXP's ==<br /> These OXP's create a scenario and force all other oxp's out of the game (unless you tweak the scenario to let one or two back in!). The only examples so far are the SOTL oxp's. There is an issue with the Expansions Manager:<br /> But ... one reason I didn't put SOTL in the manager is that [[SOTL Exploration]] depends on Loader, so if you install Exploration, you get the Loader OXP too (ie: Song_of_the_Labyrinth_Startup_1.1). Loader can't depend on Exploration, because if it did, Exploration won't load in the core scenario, and then Loader won't load because Exploration isn't there, and then you can't actually start the scenario game. But that means when you're installing from the manager, if you install Loader it can't then auto-install Exploration ... and then if you try to run Loader it'll probably go wrong with an entirely unhelpful error message.<br /> <br /> The manager ideally needs a new relationship type adding to handle that sort of "install-time but not run-time" dependency, but I never got round to that. (Cim 2021).<br /> <br /> == Links ==<br /> *[https://bb.oolite.space/viewtopic.php?p=273236#p273236 Expansion Manager Pack] Suggestions for change (2020).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=18077 copy information_url to clipboard] (2016-21).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=16888 User tags for expansions] (2014)<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16790 Are OXZ's an improvement ...] over OXP's (2014).<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16610 OXZ and balance] What should go on the Expansions Manager? (2014)<br /> *[https://bb.oolite.space/viewtopic.php?p=210354#p210354 Cim's announcement] of the concept (2013)<br /> <br /> *[https://bb.oolite.space/viewtopic.php?f=4&t=20932 Oolite's interaction with Expansion Packs] (2021)<br /> <br /> === Download Counter for oxp's ===<br /> *[https://bb.oolite.space/viewtopic.php?p=287386#p287386 Suggestions for fixing it] (2022)<br /> <br /> <br /> ----<br /> [[File:Oolite Start v.0.1.7.png|right]]<br /> == Out-game Expansions Manager ("Oolite Starter") ==<br /> The [[Oolite Starter]] allows easy switching between bnuches of Oolite versions, OXPs and savegames. Mr. Gimlet guides novice users (and does not hold back advising experienced ones).<br /> See v0.1.35 (Mar '26) at [https://github.com/OoliteProject/OoliteStarter this Github repository]. There are installers for Linux, Mac and Windows.<br /> <br /> '''Reference''': Thread with posts starts [https://bb.oolite.space/viewtopic.php?p=289311#p289311 here] (May 2023)<br /> <br /> The AppleMac version is not yet fully functional - one cannot start up the savegame of choice, but includes an automatically updated list of every OXZ on the oolite.space website as well as managing the OXPs in your AddOns folder. The fact that the AppleMac version of Oolite does not honor passed command line parameters is more a bug on Oolite than on the Oolite Starter.<br /> <br /> [[Category:Oolite]][[Category:Factual]][[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Expansions_Manager&diff=88144 Expansions Manager 2026-03-15T14:06:56Z

<p>Hiran: </p> <hr /> <div>[[File:Expansions Manager.png|right|thumb|500px|In-game Expansions Manager (Surround is from [[XenonUI]])]]<br /> The Expansion Pack Manager was devised by [[User:Cim|Cim]] for Oolite v.1.80 (2014), and ushered in the move from [[OXP]]s to OXZs.<br /> <br /> == Expansion Pack Manager<br /> <br /> *Note that there are many Expansions (OXPs/OXZs) which are not listed in the Manager. See [[Guide to Unlisted OXPs]]<br /> *Note that the Expansions Manager depends on ''this'' wiki - if this wiki is down (and you are - for example - looking at a backup of this page), you will need a [https://bb.oolite.space/viewtopic.php?p=273722#p273722 workaround].<br /> <br /> Oolite allows to be extended via Addons and [[OXP]]s. Expansion packs that are registered to the [https://github.com/OoliteProject/oolite-expansion-catalog Expansions Catalog] and it's [https://ooliteproject.github.io/oolite-expansion-catalog/index.html browsable version]<br /> can be downloaded and installed automatically.<br /> <br /> == Using the builtin Expansion Pack Manager (EPM) ==<br /> <br /> This is about the expansion manager that is available within Oolite.<br /> <br /> '''The arrow keys <font color="Red">←</font> & <font color="Red">→</font> skip between pages - and the arrow keys <font color="Red">↓</font> & <font color="Red">↑</font> move up and down within a page.'''<br /> <br /> '''Press <font color="Red"> i </font> for more information on your chosen expansion pack''': The URL for even more information is copied to your clipboard automatically when you do this (unless your computer runs Unix and you are playing Oolite v.1.90 or older). <br /> <br /> '''Press <font color="Red"> f </font> to filter the selection of 700-odd listed expansion packs.''' (''eg'' Search for keyword, Search for author, list only uninstalled packs ''etc'')<br /> <br /> ----<br /> <br /> <br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #ffaaaa;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> Oolite.org is currently down. Try http://oolite.space/ instead. <br /> <br /> To rejig your in-game [[Expansions Manager]] to the new address, see [https://bb.oolite.space/viewtopic.php?f=2&t=21368 here] and a_c's following post.<br /> <br /> (''Cholmondeley 13:40, 29 March 2023 (BST)'')<br /> <br /> Or use Hiran's [[Oolite Starter]] instead<br /> |}<br /> <br /> {| border="2" style="margin: 1em auto 1em auto;"<br /> |style="background-color: #aabbbb;padding: .6em 3em 1em;"|<br /> <center>'''Important Note'''</center><br /> The current Windows Pre-releases/"nightlies" now allow you to directly skip to the OXP category (''eg'' .Ambience, Ships, Weapons ''etc''.), rather than scroll through dozens of pages to get there! <br><br /> They can be downloaded from the very bottom of the [https://oolite.space/#download Downloads page] or directly from GitHub, [https://github.com/OoliteProject/oolite/releases here].<br /> |}<br /> <br /> [[File:XenonUI (Expansions Manager).png|thumb|right|500px|The [[XenonUI]] OXP now provides all this information on your screen!<br><br /> On the left (Sub-Commands): filter/information/extract contents<br><br /> On the right: guide to colours]]<br /> == Guide to Expansions Manager list colours ==<br /> :'''Yellow''' Ready to download and install.<br /> :'''White''' Installed and at the current version.<br /> <br /> :'''Cyan''' Installed; updated pack available for download.<br /> :'''Orange''' Ready to download, but Oolite will also download extra packs to make it work.<br /> :'''Brown''' Conflicts with an already installed pack.<br /> :'''Gray''' Incompatible with this version of Oolite.<br /> <br /> :'''Red''' Manually installed: cannot also be installed automatically (''eg''. a tweaked oxp in the AddOns folder)<br /> :'''Blue''' Installed but no longer available for download.<br /> <br /> ----<br /> == Downloading and Unzipping an Expansion for Tweaking ==<br /> <br /> ''or for extracting information - for example, [[User:Ramirez|Ramirez]]'s oxz's contain glorious .pdf's stashed full of information!''<br /> <br /> *Go to the '''Expansion Pack Manager''' in game.<br /> *Select '''List installed expansion packs''' (the ''second'' choice at the bottom of the screen).<br /> *It will now show you the list of OXZ files in your ManagedAddOns folder.<br /> *Highlight the one you want to fiddle with and press <font color="Red">'''x'''</font>.<br /> <br /> *Oolite will then extract the OZX to your AddOns folder and add .off to the end of the expanded (was .oxz but is now .oxp) folder.<br /> *Change this '''.off''' to '''.oxp''' or '''.txt''' and tweak away to your heart's delight!<br /> <br /> *Oolite will now ignore the original version and will run the newly-expanded OXP version in AddOns (with any changes you now make to it).<br /> ''If you make a mess of it, deleting the .oxp version (in the AddOns folder) will cause Oolite to go back to using the OXZ version (in the Managed AddOns folder).''<br /> <br /> === Tweaking OXPs ===<br /> (''adapted from LittleBear's [https://bb.oolite.space/viewtopic.php?p=273769#p273769 BB post]'')<br /> *The Windows text editor sneaks in invisible bits of code which muck up the OXPs: '''Avoid it like the plague!'''<br /> *To edit I'd recommend Edit Pad Lite 8. It's free, won't mess up the file format and is colour coded (so will highlight code typos).<br /> *''Eg''. If you have missed a ''',''' or a '''"''' in a text string, it will show up as ''white'' rather than ''yellow'', so you can quickly see the mistake. ;-)<br /> <br /> *Been a bit of a blessing when I've been C&Ping long lists of procedurally generated text from my latest.log to my array file.<br /> <br /> *See discussion [https://bb.oolite.space/viewtopic.php?p=273782#p273782 here] for AppleMac suggestions.<br /> *See [[How to tweak OXZ's]] for more tweakish details.<br /> <br /> == Scenario OXP's ==<br /> These OXP's create a scenario and force all other oxp's out of the game (unless you tweak the scenario to let one or two back in!). The only examples so far are the SOTL oxp's. There is an issue with the Expansions Manager:<br /> But ... one reason I didn't put SOTL in the manager is that [[SOTL Exploration]] depends on Loader, so if you install Exploration, you get the Loader OXP too (ie: Song_of_the_Labyrinth_Startup_1.1). Loader can't depend on Exploration, because if it did, Exploration won't load in the core scenario, and then Loader won't load because Exploration isn't there, and then you can't actually start the scenario game. But that means when you're installing from the manager, if you install Loader it can't then auto-install Exploration ... and then if you try to run Loader it'll probably go wrong with an entirely unhelpful error message.<br /> <br /> The manager ideally needs a new relationship type adding to handle that sort of "install-time but not run-time" dependency, but I never got round to that. (Cim 2021).<br /> <br /> == Links ==<br /> *[https://bb.oolite.space/viewtopic.php?p=273236#p273236 Expansion Manager Pack] Suggestions for change (2020).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=18077 copy information_url to clipboard] (2016-21).<br /> *[https://bb.oolite.space/viewtopic.php?f=6&t=16888 User tags for expansions] (2014)<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16790 Are OXZ's an improvement ...] over OXP's (2014).<br /> *[https://bb.oolite.space/viewtopic.php?f=2&t=16610 OXZ and balance] What should go on the Expansions Manager? (2014)<br /> *[https://bb.oolite.space/viewtopic.php?p=210354#p210354 Cim's announcement] of the concept (2013)<br /> <br /> *[https://bb.oolite.space/viewtopic.php?f=4&t=20932 Oolite's interaction with Expansion Packs] (2021)<br /> <br /> === Download Counter for oxp's ===<br /> *[https://bb.oolite.space/viewtopic.php?p=287386#p287386 Suggestions for fixing it] (2022)<br /> <br /> <br /> ----<br /> [[File:Oolite Start v.0.1.7.png|right]]<br /> == Out-game Expansions Manager ("Oolite Starter") ==<br /> The [[Oolite Starter]] allows easy switching between bnuches of Oolite versions, OXPs and savegames. Mr. Gimlet guides novice users (and does not hold back advising experienced ones).<br /> See v0.1.35 (Mar '26) at [https://github.com/OoliteProject/OoliteStarter this Github repository]. There are installers for Linux, Mac and Windows.<br /> <br /> '''Reference''': Thread with posts starts [https://bb.oolite.space/viewtopic.php?p=289311#p289311 here] (May 2023)<br /> <br /> The AppleMac version is not yet fully functional - one cannot start up the savegame of choice, but includes an automatically updated list of every OXZ on the oolite.space website as well as managing the OXPs in your AddOns folder. The fact that the AppleMac version of Oolite does not honor passed command line parameters is more a bug on Oolite than on the Oolite Starter.<br /> <br /> [[Category:Oolite]][[Category:Factual]][[Category:Help pages]]</div>

Hiran https://wiki.alioth.net/index.php?title=Logfile&diff=87107 Logfile 2025-08-29T19:16:15Z

<p>Hiran: Redirected page to Latest.log</p> <hr /> <div>#redirect [[Latest.log]]</div>

Hiran https://wiki.alioth.net/index.php?title=Developer%27s_Corner&diff=86422 Developer's Corner 2025-07-18T15:22:03Z

<p>Hiran: </p> <hr /> <div>Here you will find information that helps understanding the Oolite source code, build and test the project.<br /> <br /> * [[Contributing to the project]]<br /> * [[Release Process]]<br /> * [[Branding]]<br /> * [https://ooliteproject.github.io/oolite/ Oolite API documentation]<br /> * [https://ooliteproject.github.io/oolite/ Doxygen Documentation]<br /> * [https://ooliteproject.github.io/oolite/coverage/index.html Code Coverage Report]<br /> * [[Cross Platform IDEs]]<br /> <br /> == OS Specific parts ==<br /> <br /> {| class="wikitable" style="margin:auto"<br /> |+ Operating System dependent stuff<br /> |-<br /> ! Procedure !! Apple Mac !! Linux !! Windows<br /> |-<br /> | Setting up a development environment || [[Development on Apple Mac]] [[Cross Platform IDEs]] || [[Development on Linux]] [[Cross Platform IDEs]] || [[Development on Windows]] [[Cross Platform IDEs]]<br /> |-<br /> | Compiling || [[Compiling on Apple Mac]] || [[Compiling on Linux]] || [[Developing Oolite#On_Windows_2 | Compiling on Windows]]<br /> |-<br /> | Testing || [[Testing on Apple Mac]] || [[Testing on Linux]] || [[Testing on Windows]]<br /> |-<br /> | Packaging into Installer || [[Installer on Apple Mac]] || [[Installer on Linux]] || [[Installer on Windows]]<br /> |-<br /> | Running || [[Running_Oolite-Mac]] || ||<br /> |}<br /> <br /> ==Releasing the code==<br /> <br /> Once you developed a while you are no longer happy that all you created is called 'nightly' or 'prerelease' or 'unstable'.<br /> If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]].<br /> <br /> [[Category:Oolite Development]]<br /> <br /> == Hints ==<br /> <br /> The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.<br /> If you need to update submodules you also need to tell update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&t=21470<br /> <br /> To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules</div>

Hiran