Breath of Fire IV failing immediately

Support
1

lutris -d

JSON File

Sorry. Limited to two links here. Game log doesn’t say anything beyond the lutris -d output.

I am trying to run Breath of Fire IV (this is different than Breath of Fire 4 on your system).

The lutris installer simply runs the GoG installer which automates installing DirectX9 at the end. When I go to run the game I get:
Exit with return code 1280

It tries to run but quits immediately. I’ve tried several proton and wine runners. Tried adding WINEDLLOVERRIDES=“dinput8,dinput,ddraw=n,b” in the arguments field per a reddit comment about Steam Deck.

Tried playing around with different flags in Lutris to no avail. Should I be going to Wine forum for help?`

3

Running from terminal:

Terminal Output

4

I found this:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=5140

I have it running with lutris-GE-Proton7-26-x86_64. It also seems to work with the default versions for DXVK and DXVK NVAPI. It even works without the WINEDLLOVERRIDES=“dinput8,dinput,ddraw=n,b”

The setting that really seems to matter is dgvoodoo2 set to enabled. This stops the crashing on startup.

What doesn’t work is ALT-Tabbing out. When you come back in, it repeats the up or down arrow and all other input is locked.

Question: How would I enable DGVOODOO2 from command line?

5

Actually, what’s happening is that it will run properly after a reboot, but on subsequent launches, the keyboard inputs do not work. I have to run lutris with -d and then the keyboard seems to work.

lutris -d output when keyboard working

If I run:
WINEDLLOVERRIDES=dinput8,dinput,ddraw=n,b lutris the keyboard works every time. Therefore, I think having these parameters in the arguments field doesn’t work. It looks like they have to come in before wine is called. How do I do that? I don’t know how to translate dinput8,dinput,ddraw=n,b into the override fields in lutris.

What does the unspecified value mean for dinput8 and dinput? disabled?

6

I’ve since realized that it’s just a matter of running lutris from terminal that makes it work every time. No need for -d or WINEDLLOVERRIDES. Very strange. I’d still like to know how to properly enter this WINEDLLOVERRIDES parameter in the lutris interface.