UnknownUnknown
gamescope -w 640 -h 480 -W 1920 -H 1080 --force-grab-cursor -f -- %command%
Game is only on 640x480 so I use gamescope to maximize the game to my monitor resolution.
The game works great now, but it's only on 640x480 resolution, some people uses xrandr to make it work but I just use gamescope, the game works perfectly fine and save games works great, the game saves on the game directory so if you uninstall your game make sure to backup your save.
xrandr --output DP-1 --mode 640x480; %command%; xrandr --output DP-1 --mode 2560x1440
game has only one resolution with no options, so you have postal stamp size image in a left upper connor.
Look for Cy tinker report
- run
xrandrto find output name and resolution - adjust launch options accordingly
NOTE: solutuin changes systen resolution to 640x480, so if you happen to do ALT + TAB your other applications wil be unusable while game is running
SAVES ARE WORKING!
when I started to play with compatibility, Proton Hotfix was firts option, and sisnce i was able to save game to file and load from it - didn't try anything else
xrandr --output DP-1 --mode 640x480; %command%; xrandr --output DP-1 --mode 3840x2160
The game runs in a small 640x480 area of the screen.
Opening the save/load dialogue takes the game out of full-screen. I didn't find a way to focus it back. So even though the game loads the saved state properly, you cannot continue playing.
Unfortunately, BadMojo doesn't support modern resolutions - even though it claims to be "Redux". The only way to stretch it to full-screen is to match the system resolution. The above launch option does it automatically.
You might need to replace DP-1 with your output name. Check xrandr in terminal. Typical outputs are HDMI-0, DP-1, DisplayPort-2, etc.
If you prefer the game to run in a small area in the centre of your screen instead, you can achieve that by omitting launcher.exe and calling BADMOJO.EXE directly:
eval $(echo "%command%" | sed 's#launcher.exe#BADMOJO.EXE#')
The fact the game runs at all is a testament to Wine development. A year ago, it wouldn't even start - nowadays, it can be actually beaten. If you find a way to scale the game up instead of changing the system resolution, or to continue playing after loading a save, please, report back here.
Option 1: Proton 7.0-6. Game plays perfectly, sound works fine, but if you try and skip a cinematic the game crashes.
Option 2: Proton 8.0-5. Game plays perfect. No sound. No crash if you skip cinematics.
Options 1 works better imo, just remember to let the cinematics play and it's a good experience
Resolution manually set to 640x480. Framerate must be left uncapped.
Set display size to 640x400 in properties and set d-pad to keyboard arrows. Worked great full-screen and docked.
Changed d-pad to keyboard directional arrows
Tried this again with very simple settings and worked better than it ever has. This game shouldn't be bronze; it should be gold. Works fine with no audio or visual issues. I made a controller layout called Bad Mojo D-Pad so you don't have to manually set it. Enjoy.
Resolution needs to be set manually to 640x400 in the Steam Settings to display correctly.
The default Proton configurations each have a number of issues. Proton 7.x (default) has audio, but crashes if you try to skip any cutscenes. Proton 8.x/Experimental completely lack any audio for the game.
To play this title, you'll need to install and run the game under Proton TKG, which fixes both of these issues. This was tested with the 5638535607 build, which was the latest as of current testing.
Does Not Even Start
No matter what proton version I tried using, the game crashed immediately.
On startup, be patient. Blackscreen for 45 seconds before it starts, and between opening loads. Screen size/pos is annoying. Plays great.
Screen is locked to the upper right in game mode. Centers in desktop mode. Does not seem to be a way to force a true full screen
Long load times at the outset make it appear as though it's broken. You have to wait 45 seconds for first logo, then another 45 each for menu, opening cinematic, and game start. Be patient. Game plays fine.
Installs but doesn't start.
Some Black windows flicker, one with message "Troubles? Look at comments in launcher.bat", then crash. Comments in launcher2.bat are irrelevant. Error:
wine: Unhandled page fault on read access to 00000000 at address 00000000 (thread 0110), starting debugger...
That memory addres looks incorrect. I tried several versions of Proton: default, experimental and GE-7.33, as well as usual environment variables, nothing works.
Not working
The game works, but its play area is too small. It's probably no worse than on Windows, but I don't think I can play it like that
The window is 640x480, which on my 2K screen is the size of a postage stamp.
The game is in full-screen only
You need to set up the prefix and run wine cmd.exe /C gencfg.bat "%CD%" in game directory to generate the missing BADMOJO.INI file but even after that it crashes immediately after a split second of black screen and there's a segfault printed to STDERR when run from the terminal. Tried BADMOJO.EXE, launcher.exe and launcher2.bat - none start the game but STDERR outputs differ slightly.
Shows error message because of missing file (badmojo.ini).
UnknownComplains about missing badmojo.ini file and closes. I'm guessing this can be worked around but the ini file actually contains paths to game assets which I don't know how to set in relation to wine prefix.
Unknown
