xrogaan wrote: ↑Wed, 7. May 25, 12:16
The AMD driver for both windows and linux are effectively using the same FOSS base. GPT is lying to you. Instead of asking a predictive algorithm what words would fit next, how about you do a proper search online? FSR 3 isn't tied to the driver anyway.
Fact of the matter is, FSR3 is not working properly on my machine, and also fact of the matter is that FSR1 runs better - as GPT is saying. I am doing my research. Not really sorry if I offended you by using ChatGPT and (god forbid) posting it here.
Maybe one of the developers can chime in on that. It is quite possible the necessary vector work for FSR3 is not fully implemented on Linux yet.
there is a lot of factors involved in the difference between fsr1 and fsr3. if you having issues with your system and the operating system i would contact the OS support team as they would be more capable with handling your system configuration issues.
and just as a general rule, chatgpt is a bad source of information. the recent chatgpt model was stated as going from a 15% to 30% chance of hallucinating, this is due in part of chatgpt consuming other llm produced content and as the saying goes, garbage in and garbage out.
i really dont want to be rude and i will try to not insult you or your intelligence. i'm not sure what your issue with fsr3 is ( maybe im a dummy and i cant read ) but i didnt see the issue being stated? is it the fps or frame time or system ram/ gpu ram consumption rate? i find that im very sensitive to the blurring effect of fsr/dlss and so i will turn them off. i know that some people enjoy this and a type of speed feeling/effect. if you can provide an example, i will do my best to reproduce it. i'm currently working on a very large project and i dont often have time to play x4 recently but i can mess with config files and ( hopefully ) find a quick solution.
GameBurrow wrote: ↑Fri, 2. May 25, 20:00
Howdy folks, just recently moved over to linux (at the beginning of the year) and there is something strange I've found with X4.
If I run the native version of X4 - the sounds tend to crack a lot (in video editing world we call this audio clipping, meaning audio hits the limiter), especially the ship engines when I start the travel drive (especially noticeble with Erlking). I can reduce the issue by lowering the game volume and using various easy effects effects to compress or limit the sound, but it only reduces the issue, it will still happen.
Didn't have this issue with the same hardware on windows. This week I've been temporarily running X4 through proton (to test X4 external app mod) and noticed if I run X4 using that, the audio is okay. So the issue seems to be specific to the linux build of the game. Additionally to note, haven't noticed this issue with any other game or program.
are you using pipewire with the pipewire-pulse as a replacement for pulse management tools? i had an issue with pipewire having an overactive power saving mode and so my devices were waking up and blasting and then immediately reducing power. it was this kind of blasting effect. i cant seem to find my solution in my bash history but something like `echo 0 > /sys/module/snd_hda_intel/parameters/power_save` might provide a temporary solution.
MarStrMind wrote: ↑Tue, 6. May 25, 07:16
Running openSUSE Leap 15.6 with KDE Plasma 5 LTS. X4 itself runs very well on my GPU... for a while. Then it starts to stutter.
i totally didnt read this whole thing, turn on the steam overlay. the stuttering will go away.
MarStrMind wrote: ↑Tue, 6. May 25, 07:16
Running openSUSE Leap 15.6 with KDE Plasma 5 LTS. X4 itself runs very well on my GPU... for a while. Then it starts to stutter.
i totally didnt read this whole thing, turn on the steam overlay. the stuttering will go away.
MarStrMind wrote: ↑Wed, 7. May 25, 13:50
For the record: I am fully aware what FSR1/3 is and that it is an open source component.
But just because it works on all platforms, does not mean it works equally well on all of them. I seem to have an issue with v3 of the tech.
Just to clear this one up: my initial conversation with ChatGPT still holds water. FSR-3 will only partially work with X4, even on Windows. The framegen-tech will not be available as it is dependent on DirectX 12 and fullscreen games. As X4 uses the Vulkan engine, it cannot avail of this tech in FSR-3. You can still use the upscaling though.
xAix1999 wrote: ↑Sat, 17. May 25, 20:00
yeah that's the same effect as enabling the steam overlay. enjoy your game!
Uhm... no. Specifying an empty LD Library Path defines that it should not look for shared libraries in system or other directories. Also, I cannot imagine that enabling overhead in Steam will improve performance. I never use that overlay anyways, but still - the logic completely eludes me.
MarStrMind wrote: ↑Sun, 18. May 25, 19:33
FSR-3 will only partially work with X4, even on Windows. The framegen-tech will not be available as it is dependent on DirectX 12 and fullscreen games. As X4 uses the Vulkan engine, it cannot avail of this tech in FSR-3.
Just to point out that, as of FSR 3.1, that is no longer true. With FSR 3.1, FrameGen is available under Vulkan, at least under Windows.
xAix1999 wrote: ↑Sat, 17. May 25, 20:00
yeah that's the same effect as enabling the steam overlay. enjoy your game!
Uhm... no. Specifying an empty LD Library Path defines that it should not look for shared libraries in system or other directories. Also, I cannot imagine that enabling overhead in Steam will improve performance. I never use that overlay anyways, but still - the logic completely eludes me.
LD_LIBRARY_PATH define the path where the linker should look for shared libraries. If that variable is empty (or not defined) then the linker defaults to the system's path (usually /lib and /usr/lib). In effect, defining LD_LIBRARY_PATH="" override anything defined by steam, forcing the software the use the system's libraries instead of whatever is being shipped by steam.
The stutter seems to be something linked to whatever valve ships with steam, as it also occurs for their own titles.
I'm using a Joystick and Throttle combo and it seems like the deadzone is applying to the middle of the throttle if bidirectional throttle is not enabled. Is this a linux specific issue?
MarStrMind wrote: ↑Wed, 7. May 25, 13:50
For the record: I am fully aware what FSR1/3 is and that it is an open source component.
But just because it works on all platforms, does not mean it works equally well on all of them. I seem to have an issue with v3 of the tech.
Just to clear this one up: my initial conversation with ChatGPT still holds water. FSR-3 will only partially work with X4, even on Windows. The framegen-tech will not be available as it is dependent on DirectX 12 and fullscreen games. As X4 uses the Vulkan engine, it cannot avail of this tech in FSR-3. You can still use the upscaling though.
xAix1999 wrote: ↑Sat, 17. May 25, 20:00
yeah that's the same effect as enabling the steam overlay. enjoy your game!
Uhm... no. Specifying an empty LD Library Path defines that it should not look for shared libraries in system or other directories. Also, I cannot imagine that enabling overhead in Steam will improve performance. I never use that overlay anyways, but still - the logic completely eludes me.
while the steam overlay is disabled the steam recording feature will start to have some trouble. i'm not sure when or why the steam recording starts to have troubles even though it should be turned off but the steam recording starts to want to sync the keyboard and mouse inputs to the games video. the syncing function will start to cause the frame time to elongate. when you enable the steam overlay and either have the steam recording on or off, the stuttering will not be present. if your hardware is not at the game requirements, fsr 3 and the frame gen ( which does work on 3.1 ) should help with you gaming experience. if your system meets or exceeds the game's requirements when i would suggest you turn fsr 3 off. also, using an nvidia 3060 and a monitor that has a refresh rate of 144hz or 240hz wont increase your game experience either. 60hz should be enough for your system and most peoples also. 60hz on your monitor and 60 fps on your game should allow you to turn off fsr 3. i would also consult a computer technician if you have any other questions instead of using chatgpt which continues to mislead you.
LazyDope wrote: ↑Sun, 18. May 25, 23:37
I'm using a Joystick and Throttle combo and it seems like the deadzone is applying to the middle of the throttle if bidirectional throttle is not enabled. Is this a linux specific issue?
have you used any calibration software to see if the sensitivity setting was reset or needs to be increased?
MarStrMind wrote: ↑Wed, 7. May 25, 13:50
For the record: I am fully aware what FSR1/3 is and that it is an open source component.
But just because it works on all platforms, does not mean it works equally well on all of them. I seem to have an issue with v3 of the tech.
Just to clear this one up: my initial conversation with ChatGPT still holds water. FSR-3 will only partially work with X4, even on Windows. The framegen-tech will not be available as it is dependent on DirectX 12 and fullscreen games. As X4 uses the Vulkan engine, it cannot avail of this tech in FSR-3. You can still use the upscaling though.
xAix1999 wrote: ↑Sat, 17. May 25, 20:00
yeah that's the same effect as enabling the steam overlay. enjoy your game!
Uhm... no. Specifying an empty LD Library Path defines that it should not look for shared libraries in system or other directories. Also, I cannot imagine that enabling overhead in Steam will improve performance. I never use that overlay anyways, but still - the logic completely eludes me.
while the steam overlay is disabled the steam recording feature will start to have some trouble. i'm not sure when or why the steam recording starts to have troubles even though it should be turned off but the steam recording starts to want to sync the keyboard and mouse inputs to the games video. the syncing function will start to cause the frame time to elongate. when you enable the steam overlay and either have the steam recording on or off, the stuttering will not be present. if your hardware is not at the game requirements, fsr 3 and the frame gen ( which does work on 3.1 ) should help with you gaming experience. if your system meets or exceeds the game's requirements when i would suggest you turn fsr 3 off. also, using an nvidia 3060 and a monitor that has a refresh rate of 144hz or 240hz wont increase your game experience either. 60hz should be enough for your system and most peoples also. 60hz on your monitor and 60 fps on your game should allow you to turn off fsr 3. i would also consult a computer technician if you have any other questions instead of using chatgpt which continues to mislead you.
I am 43, about 32 years or so of those experience with IT. I am in a software developer job and quite knowledgable on Linux systems. I am using ChatGPT and LMStudio whenever I see fit... privately and professionally - hmmkay?
And how many FPS are enough... well that is also my own decision.
Apart from that - not once have I used Steam Recording. OBS with access to the VA-API taxes my CPU with 0.5% at 1440p. And I highly recommend using that for recording.
PS: What GPT said is still correct for me. Framegen is not available on Linux systems, even at FSR 3.1.
LazyDope wrote: ↑Sun, 18. May 25, 23:37
I'm using a Joystick and Throttle combo and it seems like the deadzone is applying to the middle of the throttle if bidirectional throttle is not enabled. Is this a linux specific issue?
have you used any calibration software to see if the sensitivity setting was reset or needs to be increased?
Yes I've made sure everything is calibrated correctly, and everything works fine in bidirectional mode, since the deadzone should be in the middle in that case, however with bidirectional mode disabled, the deadzone is still in the same place on the thottle's position, except that now the middle is half way up the throttle instead of at the bottom. I've also tried changing the deadzone in evdev-joystick and even jscal (which I don't thing X4 uses) but neither have seemed to have an effect in game, only the in game, global deadzone setting seems to do anything.
would you happen to be using the windows version with proton? the reason i ask is, the proton/wine prefix could have different configurations settings which are isolated from your linux system.
xAix1999 wrote: ↑Tue, 20. May 25, 04:46
would you happen to be using the windows version with proton? the reason i ask is, the proton/wine prefix could have different configurations settings which are isolated from your linux system.
No, native linux version, however I am using the steam runtime.
i have a few peripherals that have no linux binaries and so i've had to use open software to configure them. which hardware are you talking about?
i have a controller that needed to be re-flashed every time i changed the controller style. (xbox to ps and back) i doubt that you will have this problem but are you running the calibration software as root? (sorry if that's a dumb question)
once i know the hardware i can do some research to help with a solution. i don't believe this is a linux issue but maybe a simple configuration issue.
xAix1999 wrote: ↑Wed, 21. May 25, 01:41
i have a few peripherals that have no linux binaries and so i've had to use open software to configure them. which hardware are you talking about?
i have a controller that needed to be re-flashed every time i changed the controller style. (xbox to ps and back) i doubt that you will have this problem but are you running the calibration software as root? (sorry if that's a dumb question)
once i know the hardware i can do some research to help with a solution. i don't believe this is a linux issue but maybe a simple configuration issue.
It is a Thrustmaster TWCS Throttle. It could be a configuration issue in regards to the evdev config not working, but the ingame deadzone not working as intended is still a game issue, no?