[Solved] LowSpec Oolite

[drakeraider]

I'm having a lot of stutter right on the flight to Zaonce. Now I have alot of mods installed, and believe due to google searches it's OXP related, but I'm not sure how to diagnose which are the ones causing it, is there any way to do it?
I'm running ubuntu with an intel 4000, so I am pretty limited there, but unmodded Oolite runs fine.

[Cody]

Welcome aboard, Commander!

I'm not sure how to diagnose which are the ones causing it, is there any way to do it?

The binary method is often the fastest way to find the offending OXP:

Remove half the OXPs. If the problem goes away, change to the other half of the set and try again.
Continue removing half the remaining OXPs each time, eliminating the half that are trouble-free. Repeat until you have identified the culprit.
Even if you have hundreds of OXPs, this method will let you identify the source of the trouble in less than 10 iterations.

[drakeraider]

Is there a good file to find a list of all installed OXPs without going through each one in the menu? I found the folder where they're stored, but if I delete the game just redownloads them.

[Cody]

Try the Latest.log - found hereabouts in Linux:

Linux and other Unix-like systems: ~/.Oolite/Logs (that is, in the hidden folder .Oolite in your home folder). If you’re using Nautilus or Konqueror—if you’ve never heard of them, you probably are—select Show Hidden Files from the View menu.

[drakeraider]

Will that allow me to remove OXPs right from the document, or just it just list them?

[phkb]

The latest.log file will just list them. Removing them manually will mean navigating to the folder and moving files to some temporary location. You can remove managed OXP's from within Oolite itself, but this can only be done on a one-by-one basis, so it might not be the best way to debug performance issues if you have lots of OXP's to remove.

[dybal]

Will that allow me to remove OXPs right from the document, or just it just list them?

The oxz files should be in $HOME/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns

The game will use whatever is there when the game program is started.

I usually create a $HOME/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns.saved directory and move the oxz files back and forth.

You move them, start the game, see the results (perhaps look at $HOME/.Oolite/Logs/Latest.log too, depends on the actual problem), quit the game, move them again, etc..

The greatest hassle is dealing with the inter-OXP dependencies... if B requires A, to test for B you have to keep A there too.

[drakeraider]

Got everything working using your tricks! Thank you!

[phkb]

So what OXP was the culprit?

[Cody]

So what OXP was the culprit?

It was Colonel Mustard, in the Library, with the Revolver!

[GearsNSuch]

It was Colonel Mustard, in the Library, with the Revolver!

Or Clooedo, for all you brits.

[drakeraider]

I think it was a couple of the Ambience ones. I didn't get it specific, but i did get it down to a range of ones that all did stuff like add planetary systems or stuff like that. I also got rid of the Texture packs, and that seemed to help, but not as much as the other bunch.

Dumb question now that it's working, and may be worthy of another topic, but does anyone know if there's a way to get a mouse interface, ala Pioneer?
Obviously the content is further along in Oolite, but that would be a godsend for gameplay.

[Cody]

Clooedo, eh? Interesting! But what we really need is Moonopoly.
Xevera/Mayfair, Riedquat/Old Kent Road, Tionisla/Fleet Street