For information and discussion about Oolite.
https://bb.oolite.space/
The build went okay, so please try downloading today's 1.79 build, and changing the parameter in your config file as above. (No in-game menu for it yet, but we can add one if it works)Mad Hollander wrote:To me oolite (like any game with joystick) requires features for calibrating the joystick or, at least, smoother change of sensitivity.
Hmm... when I put that into mycim wrote:For now to test it you need to putin your GNUStepDefaults file.Code: Select all
<key>JoystickNonlinear</key> <real>X</real>
GNUStepDefaults, it crashes Oolite every time. I've probably got something basic wrong... but what?GNUStepDefaults, as it doesn't launch in fullscreen as per normal.Okay, that's not supposed to happen...Cody wrote:Hmm... when I put that into mycim wrote:For now to test it you need to putin your GNUStepDefaults file.Code: Select all
<key>JoystickNonlinear</key> <real>X</real>GNUStepDefaults, it crashes Oolite every time. I've probably got something basic wrong... but what?
I don't think Oolite reads theGNUStepDefaults, as it doesn't launch in fullscreen as per normal.
.GNUstepDefaults in Windows is OpenStep format, while on Linux it seems to be XML. Put this line in your .GNUstepDefaults and it should be OK:Cody wrote:Hmm... when I put that into mycim wrote:For now to test it you need to putin your GNUStepDefaults file.Code: Select all
<key>JoystickNonlinear</key> <real>X</real>GNUStepDefaults, it crashes Oolite every time. I've probably got something basic wrong... but what?
I don't think Oolite reads theGNUStepDefaults, as it doesn't launch in fullscreen as per normal.
Code: Select all
JoystickNonlinear = X;I did and saw no difference, at least the same thing with the Adder.cim wrote:The build went okay, so please try downloading today's 1.79 build, and changing the parameter in your config file as above. (No in-game menu for it yet, but we can add one if it works)Mad Hollander wrote:To me oolite (like any game with joystick) requires features for calibrating the joystick or, at least, smoother change of sensitivity.
Cody wrote:There I was, having just scoffed a whole apple strudel with cream...
Checked old version, 1.77 - the same thing, it is very difficult to aim Adder at a target that more than 10km and after 20 km I barely can hit the targetMad Hollander wrote:I did and saw no difference, at least the same thing with the Adder.
Checked with Anaconda - all is ok, I can aim at distance even 30km.
Suppose the reason is high pitch value of the Adder and the same problem will be with any ship that has high pitch, 2 or more.
Damn, I had been playing with the value of JoystickNonlinear hell knows how many hours and the watermark was c2abd5canother_commander wrote:Just bringing to the attention of the Windows port users interested in testing joystick non-linearity, that the nightly build of this morning failed to get published in time for Windows. It got published just a few hours ago. If your nightly's hex id on the watermark reads c2abd5c, then the non-linearity feature is not yet in. The nightly version that contains it has hex tag 65f3e2e.
Try playing with the value of 'X'..Mad Hollander wrote:65f3e2e - looks like nonlinearity works a bit.
Probably, unless it turns out that regardless of ship turning it fully on gives best performance.Diziet Sma wrote:Just a thought here cim.. given that people will be playing with a variety of different ships, and given what a big difference the pitch-rate of a particular ship can make, it does sound as if a slider will be necessary to accommodate individual preferences.