-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Hi! Do you have glibc 2.35 or newer installed? Could you try running the game in windowed mode to see if it changes anything?
Hi I have glibc 2.39, and no running it in windowed mode does not change anything. It might be indicative of some sort of termination that the final line of the debug.log is cut short:
Code:
[01:39:57][pdx_json_settings.cpp:314]: [SPdxJsonSettingsIO] "pdI'll move the thread to our Tech Supp as the QA department can't assist much more with unsupported Linux distributions. Hopefully they'll be able to help you troubleshoot the issue!
What Distro is this please?
Did previous versions run on it okay?
I must say this looks pretty odd
Please attach here your Documents/Paradox Interactive/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/logs/ folder, attach here system.log , error.log
From your Documents/Paradox Interactive/Victoria3/crashes/ folder, attach here the latest (only!) exceptions.txt
Also in Steam please click on Steam-Help-System Info, and paste everything there into a text file and attach that here.
Did previous versions run on it okay?
I must say this looks pretty odd
No idea if that's related to your problem though.
Please attach here your Documents/Paradox Interactive/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/logs/ folder, attach here system.log , error.log
From your Documents/Paradox Interactive/Victoria3/crashes/ folder, attach here the latest (only!) exceptions.txt
Also in Steam please click on Steam-Help-System Info, and paste everything there into a text file and attach that here.
I am using Fedora 40 KDE Plasma 6.1.1 on Wayland. There is no crash and all the logs (that are populated) have been attached already, error.log is completely empty. 1.6.2 works perfectly fine as I have just tested by trying out the beta rollback. If it is of any help, I've also attached a gdb backtrace.
Was there really no system.log?
I see you have Vsync disabled; in our launcher's game settings menu also cap the refresh rate to 60.
I'm no developer (and as we are on an unsupported OS we can't get them involved) but without knowing which thread crashed, that backtrace is not a lot of use I don't think!
The Mesa version seems pretty up to date, but I don't see info on the actual GPU or its driver - what do you have in that area?
I see you have Vsync disabled; in our launcher's game settings menu also cap the refresh rate to 60.
I'm no developer (and as we are on an unsupported OS we can't get them involved) but without knowing which thread crashed, that backtrace is not a lot of use I don't think!
The Mesa version seems pretty up to date, but I don't see info on the actual GPU or its driver - what do you have in that area?
As I have stated, I attached system.log in the original post. I am using NVidia RTX 4070 Ti.
Again, I don't think it crashed. From the backtrace, it appears (to my untrained eye) to be some kind of deadlock situation.
Again, I don't think it crashed. From the backtrace, it appears (to my untrained eye) to be some kind of deadlock situation.
I was after a new one, but never mind.
I don't know why that screen shows only the Mesa version, which AFAIK is not used with Nvidia drivers. This is the latest driver for it
Is that what you have?
I don't know why that screen shows only the Mesa version, which AFAIK is not used with Nvidia drivers. This is the latest driver for it
Linux x64 (AMD64/EM64T) Display Driver | 550.90.07 | Linux 64-bit | NVIDIA
Download the English (US) Linux x64 (AMD64/EM64T) Display Driver for Linux 64-bit systems. Released 2024.6.4
www.nvidia.com
I am running Steam without hardware acceleration since it has artifacts with it out on wayland. I am on driver 555 which is the latest stable new feature branch.
I'm running out of ideas on this one, I am sorry! I haven't seen other such reports, as yet anyway.
Can you test with X.11 instead of Wayland?
I assume 1.7.2 didn't help?
Can you test with X.11 instead of Wayland?
I assume 1.7.2 didn't help?
I have just solved it thanks to some amazing people on the vic3 discord! Setting SDL_VIDEODRIVER=wayland environment variable fixed the issue and it now runs on wayland natively too. Thanks for your help!
- 3
