kpo8 Posted September 24, 2018 So my case is a little unique. I am trying to run chocolate-doom on a custom board. The OS running the board is from buildroot, an open-source embedded OS designer. In the kernel, chocolate-doom can be installed as a package, easy right? Wrong. in user/share/games/doom/ Running chocolate-doom -iwad doom1.wad will give me the error Failed to initialize video: unable to open mouse. Running chocolate-doom-setup will give me the generic error, Failed to initialize GUI. Other notes: I cannot find my chocolate-doom.cfg, since this is on an board it does not have a home/.local/ so I do not know where it is saving it. 0 Quote Share this post Link to post
wesleyjohnson Posted October 12, 2018 (edited) I run Linux (but not Chocolate). If you do not have a directory where it is trying to save something, then it is safe to assume it did not save it. You will have to modify Chocolate doom to use a directory that you do have. Or you could make a soft link to make it look like the directory is there. There are probably other problems with your video and mouse hardware support. I think Chocolate doom uses SDL, so the problem is how well the SDL you have supports the video and mouse hardware on that "board". If you don't have SDL, then you might consider trying the DoomLegacy-X11 port, which only needs the X11 windowing system. It also will try to create a directory "/home/yourname/.doomlegacy", where it stores save files and config. For doomlegacy, you can try: >> doomlegacy --help >> doomlegacy -home /home/home_directory -config config_file.cfg -game doom1 Again, if you really need things more, then you have to change a header file and recompile, or even modify some code. Edited October 12, 2018 by wesleyjohnson 0 Quote Share this post Link to post
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.