Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hey, thanks for the reply. Took me a few days to validate. Found another cause for potential error message, which might look like this:

$ Downloads/SternlyWordedAdventuresV47Demo.AppImage 
Error: Could not initialize SDL video subsystem (wayland not available)
stack traceback:
    [love "boot.lua"]:352: in function <[love "boot.lua"]:348>
    [C]: at 0x7f68a4d725a0
    [C]: in function 'require'
    [love "boot.lua"]:251: in function <[love "boot.lua"]:126>
    [C]: in function 'xpcall'
    [love "boot.lua"]:362: in function <[love "boot.lua"]:355>
    [C]: in function 'xpcall'

I don't understand where it's coming from, but some googling reminded me of a quirks I set some time ago for other applications: SDL_VIDEODRIVER=wayland - after I unset it, the game started. 

Glad you got it working! I thought it might have been because my launch script loaded the window module early if the config has no values for resolution set. I already changed V48 so that it delays the window module and user config loading until after the other core modules, I'd be interested to know if that would interact with that setting, or if it would have still crashed anyway.