Crash on initialization [Linux]

[(Kat)]

Hello everybody,
A friend of mine recently bought me Victoria 3. While I am grateful for them doing so, it's now caused the problem that I really need to get this thing to work, or I would feel terrible. The problem, as I'm sure you've gathered, is that I can't do that. My pc is far from a supercomputer, but it absolutely goes above the minimum specs required. I've categorized all the relevant information I could think of in bold, for ease of reading.
THE SPECS
1tbb ssd, 16gb ram intel i-7 cpu, no dedicated gpu (so maybe that's the issue?). There shouldn't be an issue here, judging by the requirements page. The only thing I can think of is maybe it's because I run it on linux, but then again Vic3 has native linux support so I don't know why that's an issue. Also, since I know someone will bring this up, the pinned thread does not help here. I don't have a 12th generation processor, mine is older than that.
THE PROBLEM
When running the game, I can't get past the initialization screen. It just crashes after loading for a little while, before getting to any menu screen. I don't know if this means anything, but there's also no music and the hands on the stopwatch loading cursor don't move. The cursor does, it just doesn't "change the time" if that makes sense (though, this may be the case in vic 3 normally).
"Did you check the crash log?"
Yes, it says this: "[gfx_vk_master_context.cpp:1455]: Failed creating pixel buffer" over and over and over again.
"Did you update your drivers?"
From what I can tell, all that is up to date. I could be wrong, but I'm pretty sure they're up to date.
FIXES I TRIED
I assume these recommendations will be brought up, so i'll list these things i've tried here:
Running normally (duh), running with proton, forcing to run with dx11 (didn't even work, but I mean what could I have expected really), forcing to run with open gl (This is actually the closest I got to it running! I didn't get to the menu but the instant before it crashed, the cursor changed to a brass looking arrow. It did introduce some new errors in the crashlog, though), verifying file integrity, running in windowed mode, lowering resolution while running windowed mode, restarting my computer, running steam in offline mode, running in debug mode, and finally, asking here for help. Also probably some other stuff I forgot. I run the game with nothing else running, except steam. also this isn't a "fix", as such, but I have sent the crash report.
SOME LEADS I HAVE INTO THE PROBLEM THAT ARE PROBABLY NOTHING BUT I FELT LIKE PUTTING HERE ANYWAY
I have had some new launcher issues before, but eu4 and ck2 still work, so I doubt that's the issue. Plus, that was ages ago and I'm pretty sure I just needed to reinstall the game or something. I've heard ck3 has similar issues relating to graphical stuff, but I don't own ck3, so I can't say for sure if that's true.
"gfx_vk_master_context" implies it's a graphical renderer issue, but beyond that I have no clue. My guess is that maybe victoria 3 requires a dedicated gpu? Vic 3 doesnt seem that demanding graphically though, and even if it did again I doubt that that would include the menu, of all things. I assume either I or the program have something set it should have or isnt should that should be, but I have no clue what. I know that's not very helpful, but I don't really know what else to say.
thank you etc etc
I really appreciate any advice. If the problem is just that my pc sucks, I'll accept that as a solution if it's geniunely what's solving the problem, but given what the specs sheet says the game requires, i should be more than able to at least get to the menu.
Thanks for the time!

 

[AndrewT]

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.

 

[(Kat)]

Sure, it should be in here.

 

[(Kat)]

I just noticed from reading these logs again that one of my ram sticks was unseated, so the information is technically inaccurate. the same bug happened in the same fashion, so I doubt it should be really important, but im attaching updated versions just in case (although the only differences in the files should be the time and the ram/memory)
Again, for all intents and purposes, this should be effectively the same information. However, since there is technically a difference, I uploaded it here, just to be safe. Double checked and all the other hardware is in place properly (though to be fair, all the other hardware would be VERY noticeable if they were malfunctioning.
Sorry about that. I don't have any explanation other than me sometimes being an idiot, but like i said the error happened in the same fashion, so i doubt that was the issue, or related.

 

[AndrewT]

I'm afraid the Intel(R) HD Graphics 4600 is well below the minimum requirement for the game, the Intel® HD Graphics 630

UserBenchmark: Intel HD 4600 (Desktop 1.25 GHz) vs 630 Kaby Lake)

And the Intel(R) Core(TM) i7-4600M is slightly below the minimum, the Intel® Core™ i3-3250

UserBenchmark: Intel Core i3-3250 vs i7-4600M

So I don't think this game will ever run on this PC, I'm sorry!

See if your friend can get a refund for their purchase, unless you have access to hardware that meets the requirements, which under Linux are:

• OS: Ubuntu 22.04 LTS
• Processor: Intel® Core™ i3-3250 or AMD® FX 8370 (AVX support required)
• Memory: 8 GB RAM
• Graphics: Nvidia® GeForce™ GTX 660 (2GB) or AMD® R7 370 (2GB) or Intel® HD Graphics 630 or AMD Radeon™ Vega 8

Sorry for the bad news!

 

[(Kat)]

The graphics makes sense, but Im not sure about the cpu. Maybe im insanely wrong but I fail to see how any i7 could be worse than an i3, much less ones released so closely to one another. Again i'll fully admit to ignorance on that subject, though. I'm not as well-versed on intel cpu formats, and only really use it on my setup now since the laptop is old and seems to require it.
But it's good to know it's a hardware issue, at least. If it's a hardware issue it sucks but It's not something I have to worry about "fixing" if that makes sense. I had a suspicion that it was a graphics issue. I still don't know why that would explain the error log specifically, though. Failing to create a pixel buffer is a pretty specific issue. If it was a hardware problem you'd think it'd give an error related to a lack of memory or power or space or whatever. Maybe vic is just programmed differently from all the games i've bugfixed though.

 

[AndrewT]

Maybe im insanely wrong but I fail to see how any i7 could be worse than an i3,

The key there is the M, which means Mobile and so much less processing power than the non-M model with the same model number.

 

[(Kat)]

The key there is the M, which means Mobile and so much less processing power than the non-M model with the same model number.

Ahh, I see. well, that is frustrating, but i'd prefer to know it's a hardware issue than me having to bugfix more. I appreciate the help.