Moderators: timon37, Moderators for English X Forum
Try running Steam in a shell like this:loggy wrote:Since the last update, I have no more sound. Even when I run it via STEAM_RUNTIME=0 steam
Code: Select all
export SDL_AUDIODRIVER=alsa
steam
You are right, calling it directly gives me sound - even using pulseaudio.CodAv wrote:Alternatively, start Steam as usual, and run X³ from the shell.loggy wrote:Since the last update, I have no more sound. Even when I run it via STEAM_RUNTIME=0 steam
Code: Select all
AL lib: pulseaudio.c:612: Context did not connect: Access denied
AL lib: alsa.c:512: Could not open playback device 'default': No such file or directory
AL lib: oss.c:169: Could not open /dev/dsp: No such file or directory
^^ same hereandaag wrote:just popped in here to say I just bought the game (again) on steam to support the continued development of this. I used to play tons of X3 reunion, cant wait until the other ones get ported
Ctrl+C? That's not a bug, that's a feature for beta testing (instakill). Change hotkey for editor to something else.Hannes15 wrote:This Morning i start to use the script editor! I want change view lines of code
so i use the shortcut strg+c on my keyboard but instantly after i pressed the strg+c button X3:Reunion killed it self.
It reproducible. i try it ten times in a row the result was same! X3 was killed.
The keyboard has a german layout!
OS: Ubuntu 12.10
The way I do multitasking is I also use windowed mode and disable "Always grab cursor" in the input config dialog. That way when the cursor is visible it is not grabbed and you can freely move it out of the window, and when it's hidden (e.g. when steering, or during cutscenes) it's grabbed. Alternatively you can try ctrl+g, but that doesn't work very well in my experience.rothen wrote:Been playing it a lot, and fortunately all of the core gameplay is bug free.
However, there's been an issue that I haven't quite figured out how to fix. In Ubuntu 12.04 x86_64, in windowed mode (at full native resolution), when I change window focus and open another application or press alt (which is HUD control for Unity), the keyboard becomes significantly less responsive. I have to double tap a key to get it to respond, and holding a key down gets no response. A full restart of the game is required to fix the issue. This issue doesn't happen all the time, but I have to do it sometimes every 30 minutes or hour if I am constantly checking stuff on my other monitor.
Also I have had 3 Kha'aak destroyers wandering around in Home of Light for quite some time, and they won't freaking leave, but I don't think that is a bug with Linux
Sorry I'm not sure what the problem is exactly. You have "input device" in the first config window when you launch the game. There you can select which joystick you use and which axes are assigned to which internal controls (the bars on the right should change as you move the joystick), later in game (when flying or docked) you can setup what these do under options/controls/controls.Fantu wrote:Hi, thanks for improve the linux port for this good game.
I have a problem with joystick axes, on game are not working but on system with "joystick" package from ubuntu repository the axes are working correctly.
The game see the joystick and the buttons are working on game.
There are particular settings to do for have axes working?
I already tried to change axes settings in game but never working.
This is the joystick:
Bus 002 Device 004: ID 046d:c209 Logitech, Inc. WingMan Gamepad
Thanks for any reply and sorry for my bad english.
If you run the game from the console you'll get some output, give me the last 1000lines or so before the crash, it might help.sliznizy wrote:I have looked around the internet and have not found an answer, so I am making a post here. I have managed to get reunion cheat scripts, and mars control script loaded into X3 successfully (Sector Takeover i dont think loaded in but I havnt played much yet so I havnt been able to test if it did or not) Starting a new game works fine, game run exceptionally well, but when I dock and save, then try to load the save game, the game crashes to desktop every single time. It gets as far as the loading screen after you select your game to load. Sits on the loading screen a couple seconds, then crashes. Im not sure if its the scripts doing it or what. I suppose I can remove them and try again. But not sure if that would actually cause the game to CTD.
--EDIT--
I think i have found my answer myself. I had a hunch, because the crashing and when it does it reminds me of, say if you added a cockpit mod to your game, and tried to load a previous save, instead of starting a new game, it would crashing when loading. So I started a new game, and did not enable the script editer, and scripts, docked, and saved. Then I loaded the save file, and it loaded in just fine. So it would seem either the scripts, or the script editor is crashing my games when loading.
Probably no, it's too much trouble. Also while X3R doesn't integrate steam TC and AP on windows do, so they probably also will on linux (if/when I get to porting them).jug007 wrote:Will there be a nosteam version if the linux version is released?
Did you try e4defrag?Mellen wrote:I am not experiencing any noteworthy menu delays, apart from the docking problem which is apparently a known X3 issue - got stuck in docking for more than 30 minutes before I could continue.
2x NVIDIA GeForce GTX 670 (no sli), Ubuntu 12.10 x64, nvidia-313 from xorg-edgers.
if by got stuck in docking for more than 30 minutes you mean the ship goes in autopilot but never ends up fully docking even though it is in position, that's a known x3:r bug which can be worked-around by pressing SETA.Mellen wrote:I am not experiencing any noteworthy menu delays, apart from the docking problem which is apparently a known X3 issue - got stuck in docking for more than 30 minutes before I could continue.
2x NVIDIA GeForce GTX 670 (no sli), Ubuntu 12.10 x64, nvidia-313 from xorg-edgers.
It is often a freighter that "hangs" and almost always if I'm in the same system. The SETA "trick" only works if not docked. Otherwise save and reload save game also kicks the hanging ship(s).ezra-r wrote: if by got stuck in docking for more than 30 minutes you mean the ship goes in autopilot but never ends up fully docking even though it is in position, that's a known x3:r bug which can be worked-around by pressing SETA.
