SRSaunders
commented
3 days ago Your startup log looks completely normal. The unknown event is likely SDL_CLIPBOARDUPDATE = 0x900, which is not explicitly handled by the game's eventloop. However, one good thing is that it shows the event loop is running.
As an aside, the only unexpected thing is that your implementation does not seem to support VK_EXT_memory_budget. I don't think this will cause problems since it's only used for the overlay stats display. Once you get things working I would like to know if you can set com_showFPS 2 in the console. I don't want the game to crash if this Vulkan extension is not supported.
Back to the original problem, the only thing I can think of is SDL which provides windowing, events, and keyboard/mouse input handling. How did you install your SDL library and what version is it?
We know the game compiles and runs fine on arm64, but is officially tested on this arch using macOS not linux. It would be cool to get this working if possible.
nickbailuc
System
Vulkan (backstory)
Since the Asahi project recently added conformant Vulkan support, I decided to compile some Vulkan games. The system runs the
vkcubemodel as well as GZDoom and vkQuake perfectly, but I wanted something that actually has some nice visuals and thought of RBDOOM-3-BFG's move to Vulkan.How I installed Doom 3
Anyways, there's no aarch64-linux build of Vulkan SDK, so I first compiled Vulkan SDK, added the binaries to
$PATH, compiled RBDOOM-3-BFG, copied thebase/from the latest patched install ongog.com.The problem
Launching the executable opens a window, loads the screen where you select Doom 1, 3, or 2, plays the music, but I have no mouse cursor to move around nor does it respond to any keyboard input. Given this odd platform (aarch-64-linux) I have to compile most of my games. Thus far, I haven't had any issues with other 3D games utilizing SDL and Vulkan/OpenGL, so I think the system (Mesa, Vulkan, SDL) are functioning correctly. The
stdoutproduces some missing file errors, however not sure if that's causing the no input issue. I've tried the originalbase/from GOG, as well as applying the 1.3 or 1.5 patches from Moddb (one of them didn't launch the game at all, the other launched and same no input result).stdout
Here's the
stdout. I am determined to get this port working, so I am willing to do further tests and provide whatever info necessary.