this post was submitted on 17 Aug 2023
7 points (100.0% liked)

Godot

5873 readers
16 users here now

Welcome to the programming.dev Godot community!

This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.

Make sure to follow the Godot CoC while chatting

We have a matrix room that can be used for chatting with other members of the community here

Links

Other Communities

Rules

We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent

Wormhole

!roguelikedev@programming.dev

Credits

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
Feyter@programming.dev
7
Vulkan on older intel CPUs (on manjaro) (lemmy.blahaj.zone)
submitted 1 year ago by Smorty@lemmy.blahaj.zone to c/godot@programming.dev
9 comments fedilink hide all child comments
 

I'm trying to run Godot 4 with the Forward+ Renderer on an older Thinkpad (T420 i5 2520M). So far I've installed vulkan-intel, lavapipe (vulkan-swrast) and vulkan-ultis for vulkaninfo. Now I don't get the "missing drivers" errors anymore, but now it just crashes. The console output is this:

handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.2.dev3.official (013e8e3afb982d4b230f0039b6dc248b48794ab9)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /usr/lib/libc.so.6(+0x3e710) [0x7f0529df1710] (??:0)
[2] llvm::CmpInst::getInversePredicate(llvm::CmpInst::Predicate) (??:0)
[3] [0x7f05140264c0] (??:0)
-- END OF BACKTRACE --

Is vulkan just not supported for older intel CPUs, or am I doing something wrong?

top 9 comments
sorted by: hot top controversial new old
[–] Redkey@programming.dev 4 points 1 year ago* (last edited 1 year ago) (1 children)

I once had problems getting an OpenGL program running under Windows on a 2nd gen i5 laptop, and discovered that the issue was that Intel had actually removed support for anything later than OpenGL 1.1 from the later versions of their drivers for those iGPUs.

After a little research, it looks like there's a "legacy" version of Mesa (mesa-amber) recommended for iGPUs on anything older than 3rd gen, and also that even the main Mesa drivers don't support Vulkan fully on 3rd and 4th gen Core iX processor iGPUs.

I think that you may just be out of luck trying to use Vulkan on a 2nd gen Core iX CPU iGPU, but I'd love to hear from someone who knows better.

[–] LinuxUserGD@feddit.de 2 points 1 year ago

lavapipe is a software renderer and should be compatible with any CPU afaik

[–] Schmeckinger@feddit.de 2 points 1 year ago

It uses a HD 3000 and I think the oldest intel GPU with vulxan support on linux is HD 4000. Not 100% sure tho.

[–] Feyter@programming.dev 1 points 1 year ago (1 children)

I'm a little bit confused? What would Vulkan have to do with the CPU? Isn't the GPU the important part here?

[–] Smorty@lemmy.blahaj.zone 5 points 1 year ago

It's the iGPU. So I'm using the built in GPU in the i5.

[–] TheTrueLinuxDev@programming.dev 1 points 1 year ago (1 children)

Maybe try installing swiftshader?

[–] Smorty@lemmy.blahaj.zone 3 points 1 year ago* (last edited 1 year ago) (1 children)

I actually did that before, but that ended up breaking a bunch of stuff. When running vulkaninfo for example, it gives me this output: /home/smorty/.cache/yay/swiftshader-git/src/SwiftShader/src/WSI/VkSurfaceKHR.cpp:246 WARNING: UNSUPPORTED: pSurfaceCapabilities->pNext sType = 1000111000 /home/smorty/.cache/yay/swiftshader-git/src/SwiftShader/src/WSI/VkSurfaceKHR.cpp:246 WARNING: UNSUPPORTED: pSurfaceCapabilities->pNext sType = 1000239000 Speicherzugriffsfehler (Speicherabzug geschrieben) (that's german for "save access denied, memory dump written") So yeah, that seems to not work unfortunately.

[–] TheTrueLinuxDev@programming.dev 2 points 1 year ago

Oof, sorry. :( I had hoped that they sorted it out by then...

[–] LinuxUserGD@feddit.de 1 points 1 year ago

"Please include this when reporting the bug to the project developer."

So just search if there is already an issue on GitHub (e. g. https://github.com/godotengine/godot/issues/70506#issuecomment-1368316996 ) and file a bug report otherwise.

Maybe try previous stable 4.1.1 release.