@ZyanKLee
Well for now you'll have to work around it like that or through some other means, I'm sorry but there's not much I can do right now:( Though the "correctly positioned, borderless window, on top" is still the best option imo, since it allows you to use the other monitor for e.g. IMs or
http://www.xdatabase.de ;p Most WMs that aren't deliberately primitive will allow you to do that.
Maquis196 wrote:We just need either primusrun/optirun passed to the executable. Like it has been mentioned earlier, Valve want it done through an environmental option (so the user can pick which bumblebee program to use), so as long as the game starts with;
optirun/optimus x3r_main (or whatever the executable is called) then we're gravy.
So maybe have the config main menu check to see if it was prefixed with anything when it started and then pass it on if so?
Until nvidia pull out some proper drivers this will be a nice workaround, and I'd hate to see you having to work around the issue beyond just checking the start flags.
OR...
thinking about it, can you do it like other games where you can right click the game in steam library and either start it or run the options? That way steam will pass the program to the executable as expected and we can set the options as normal anyway \o/.
my 2pence
The last one was actually part of my initial plan, originally the config and game were fused together and I split it for a few reasons, I'll try to do it now, though it might cause problems or not work (steam can be annoying sometimes).
Checking if the executable was prefixed by anything is actually harder than it sounds, because it actually isn't "prefixed", "optimus x3r_main" runs optimus that does magic and in turn runs x3r_main.
I was thinking along the lines of adding a combo box to the config dialog like "Run on default graphics card", "Run with optirun", "Run with primusrun", or just a textbox that allows you to run it however.
ezra-r wrote:I have played a few minutes and I can confirm the sticky keys bug occurs. In my case strafe right remained active and I found no way of disabling it, so I had to quit.
Hmm if it doesn't unstick after a few presses of the key that is stuck then it's very likely a slightly different issue from what I'm seeing, you'll have to give me a while to work out how to tackle this.
CodAv wrote:As long as the stick detects me holding it, the bug occurs. The moment I release the stick, it goes away. Hope this helps a bit to isolate the problem

Yeah that sensor is probably reported as just another button, and any button being held makes the game do that (it's the same on windows), I'll do something about it sooner or later. In the meantime you can probably check which button it is with evtest and try to disable it somehow (e.g. xorg.conf options like ButtonMapping) though I'm guessing sdl opens evdev directly so the only way would be some kinda evdev filtering kernel module (I don't know of any apart from my own, which I wouldn't recommend and you'd have to modify it either way).
bladerunner_92 wrote:With this update, though, when I launch from Steam, the config screen appears (I used to have X3R_config symlinked to X3R_main, but the update reverted it). When I then press Start X3, X3R_main is launched *with primusrun*! So it might have been magically fixed by itself

Actually they may have screwed something up, or at least whatever they did probably stops it from using the libs I packaged, which causes the other issues people started having:|
mathw wrote:
timon37 wrote:
2. Windowed or fullscreen, and with what mouse grabbing setting? It doesn't cause issues for me (at least with the current version).
Fullscreen. I haven't really found the mouse grab options so I'll just go with "default". Also, I don't know when the last patch was released, but I tried to reproduce it again today and it's more difficult. Sometimes it bugs right after a couple quick overlay shortcuts, sometimes it takes a lot of spamming.
I have yet to do more testing, but yesterday I was pestered with it during normal gameplay/usage of the overlay, without actually trying to trigger the bug.
Ok, the full option range (0-2) is in config.yaml, or you can change it in the input config dialog ("Always grab cursor") but it doesn't matter for fullscreen where it's always grabbed either way.
If it didn't happen when you tried and happened all the time when you didn't, it most likely is due to a minor difference in what you're doing. Try to notice what that is (e.g. holding a joystick button, while switching, or moving the mouse while switching), if you manage to find a reasonably repeatable method of triggering it then that's 50% of the fix;)
loggy wrote:So, this is xev output of pressing & releasing ^ on german dead keys keyboard. The key ist located directly left of "1 !" and with shift its supposed to produce the ° (degree) char.
Hmm there seems to be some xorg keymap tricks to this key, it doesn't behave like the rest, so yeah don't use it for now;p It might even be impossible to work around this (other than changing the keymap), so sorry but I'm gonna file this for much later.
loggy wrote:Another thing I got: Using a joystick (TM16000) I am not too much able to enable SETA - somewhat the joy sends keystrokes? Most of the time I cant get SETA in for more than a second. I even kicked in a 100% dead zone on the joy, and i can get SETA in just in some rare times.
Hmm might be a few things, first try to disable the throttle (in the sense that the actual joystick throttle axis isn't mapped to anything, and nothing is mapped to JoyThrottle (source -1)) and enable everything else like you would normally use it, report if that fixes it.
loggy wrote:
2nd The throttle of the joystick behaves somewhat strange, I have a range of about 3mm out of 30mm where I can set the speed from -10 to +100%. jstest-gtk shows X3 reacts on values between -16000 to +16000 (16384?

) but my joy works from -32767 to +32767.
Does the config dialog value bar go through the full range? Also there is some "Throttle Sensitivity" setting in the in-game-controll-settings where you have the deadzone, try fiddling with those and other options.
loggy wrote:
The Hat does not work at all, even though it acts as Axes 4 and 5, also from -32k to +32k, as I like it for strafing it would be nice to get it working.
If the hat reports as an axis (and the value bar changes when you assign and press it) then you should be able to map them to e.g. Joy2X/Y and set those in the in-game settings to strafing or anything else. Keep in mind it's very subtle (best to test at 0 speed near a station), also I'm not sure if strafing doesn't require some ship extension or is only on some ships.
@everyone
Regarding completely wrong portraits when running from steam, or the error terminal:
Looks like steam screwed with something and it launches the game in such a way that it can't find the included libs, it should work when you launch from the console. If the error
doesn't happen for someone when launching through steam please report asap.
If someone has an idea of what steam could be doing that screws with RPATH, also please tell me.
Either way I'm working on it.