protonscr

Disgaea PC

protonopen appid 405900Game compatibility - Unofficial
ValveSoftware/Proton#13 · opened 2018-08-22 by Bluexin · updated 2025-09-21 · 20 comments · github · game page · search this game
1 matching comments, n / p to jump
BBluexin 2018-08-22 github

I tested Disgaea PC and it worked perfectly fine for me, including sounds, controller input, effects, ... (or at least I didn't notice any difference compared to windows)

  • Fedora 28 (4.17.14-202.fc28.x86_64)
  • GTX770 (396.45)
  • R7 1700X
  • Proton 3.7 (default configuration)

System Information from Steam

Mmbfraga 2018-08-26 github

I need to point out that when setting fullscreen to ON, the game will stop working until game.cfg is removed from the game directory. The game is otherwise playable, but this may not be hard to fix.

I'm also running Fedora 28, with intel graphics and proton 3.7.

I can put my details here, but honestly I think this is affecting everyone, since it happened on multiple setups.

SscottAnselmo 2018-10-31 github

Both myself and at least two other Manjaro users are reporting this game as borked. The reoccuring theme seems to be it launching the game as a black window. My specs:

OS: Manjaro Linux
KERNEL: 4.19.0-3-MANJARO
CPU: Intel Core i7-6700K @ 4.00GHz
GPU: NVIDIA GeForce RTX 2080 Ti
GPU DRIVER: NVIDIA 410.73
RAM: 16 GB
Proton: 3.7-8

Kkisak-valve maintainer 2018-10-31 github

Hello @sanecito, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

SscottAnselmo 2018-10-31 github

@kisak-valve - Done:
steam-405900.log

Kkisak-valve maintainer 2018-10-31 github

These look like lines of interest from the log.

err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 3840x2160x0 @0! (NoRes)
err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 2560x1440x0 @0! (NoRes)
SscottAnselmo 2018-10-31 github

For context I have a 4K (XG2700) and 1080 (C422A) dual set of monitors. 4K is set to 1080 resolution because unfortunately Manjaro doesn't support independent scaling so I'm basically forced to use my 4K monitor at 1080 for the time being. Not sure if said context helps any.

Sshoober420 2020-01-27 github

Compatibility Report

System Information

LOG:
steam-405900.log

Symptoms

Black screen then it crashes to desktop

EElricleNecro 2020-04-14 github

With proton 3.7-8, a black window opens, then it hangs like that. With all other available version of >proton I have tried, the window does not even show up.

The game process is shown in the process list, but it does not do anything (no cpu usage, no disk >read or writing). I don't see it in nvtop (htop-like monitoring tools for nvidia GPU), so it seems it >hangs before actually being able to show anything.

steam-405900.log

Edit: Actually, this was due to the steam runtime (but I still don't know why). Now the game is working but with no sound at all, and when quitting it freeze.
steam-405900.log

My system info

RRipleyTom 2020-09-15 github

Just a note to say that Disgaea fullscreen bug is fixed in this wine commit.
Both current main branch and Proton 5.0-next use a wine fork a bit too old to have the fix though.

Hhasezoey 2022-02-19 github

Since updating to Proton 7.0 (Experimental), this game crashes on start-up

Proton Experimental Log (old prefix)

Proton Experimental Log (new prefix)

And the same happens when using gamescope

Proton Experimental with gamescope Log (old prefix)

(gamescope command: gamescope -w 2560 -h 1440 -r 60 -- %command%)

Note: the "old prefix" refers to upgrading a 6.x prefix into a 7.x prefix, and "new prefix" is a completely new prefix generated with 7.x

System:

Steam System Information 
Computer Information:
    Manufacturer:  MSI
    Model:  B150M MORTAR (MS-7972)
    Form Factor: Desktop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
    CPU Family:  0x6
    CPU Model:  0x9e
    CPU Stepping:  0x9
    CPU Type:  0x0
    Speed:  4500 Mhz
    8 logical processors
    4 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    AVX2:  Supported
    AVX512F:  Unsupported
    AVX512PF:  Unsupported
    AVX512ER:  Unsupported
    AVX512CD:  Unsupported
    AVX512VNNI:  Unsupported
    SHA:  Unsupported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    "Manjaro Linux" (64 bit)
    Kernel Name:  Linux
    Kernel Version:  5.16.7-1-MANJARO
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12101004
    X Window Manager:  KWin
    Steam Runtime Version:  steam-runtime_0.20220119.0

Video Card:
    Driver:  AMD AMD Radeon RX Vega (VEGA10, DRM 3.44.0, 5.16.7-1-MANJARO, LLVM 13.0.0)
    Driver Version:  4.6 (Compatibility Profile) Mesa 21.3.5
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 59 Hz
    VendorID:  0x1002
    DeviceID:  0x687f
    Revision Not Detected
    Number of Monitors:  3
    Number of Logical Video Cards:  1
    Primary Display Resolution:  2560 x 1440
    Desktop Resolution: 6400 x 1440
    Primary Display Size: 27.95" x 15.75" (32.05" diag)
                                            71.0cm x 40.0cm (81.4cm diag)
    Primary VRAM: 8192 MB

Sound card:
    Audio device: Realtek ALC892

Memory:
    RAM:  32047 MB

VR Hardware:
    VR Headset: None detected

Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Total Hard Disk Space Available:  143964 MB
    Largest Free Hard Disk Block:  93558 MB

Storage:
    Number of SSDs: 0
    Number of HDDs: 0
Aaeikum 2022-02-21 github

@hasezoey Thanks for reporting. I'm not able to see the problem on my machine, it's working well here. Do you have any gamepad devices plugged in?

Hhasezoey 2022-02-21 github

Do you have any gamepad devices plugged in?

yes i do, because i play Disgaea Games only with Controller (because the keyboard layout is super weird for me and is much easier to use a controller)

i dont know if i have Steam Input Enabled or Disabled for this game (will update tomorrow), but in Proton 6.x it worked just fine with controller

Note: my Controller (on that machine) is a XBox One Wireless (in this case wired) Controller

Update: Steam Input is Enabled

sidenote: i have also noticed that steam recently started crashing when trying to enter Big Picture Mode, or trying to open any interface related to it (like controller settings)

Hhasezoey 2022-08-14 github

i have just tried running Disgaea PC again, and the same issue still persists
steam-405900.log (completely new prefix)

with and without a XBOX controller plugged in

System:
Linux Manjaro 21.3.6
Kernel: Linux Meicoo-Manjaro 5.19.1-2-MANJARO #1 SMP PREEMPT_DYNAMIC Thu Aug 11 19:05:47 UTC 2022 x86_64 GNU/Linux
Display: KDE Plasma Wayland + Pipewire

PS: the same happens when not using experimental (1655148210 proton-7.0-3)

Iipr 2022-11-03 github

On Debian with PS4 controller this works fine.

On the Steam Deck, this does not recognize that there is gamepad and controls don't work. Setting control to mouse mode and going to settings -> key configure (from game main menu) you can see the gamepad config is greyed out.

So, the way Deck controls are reported to game is not recognized by the game as having gamepad available?

Lluni3359 2022-12-17 github

I'm not sure if this error is present in the base game, but the position of the mouse cursor is slightly off so you need to aim slightly offset to click where you want.

BBetaVersionBY 2023-07-02 github

Disgaea PC works fine with Proton 7.0-6, but crashes on startup with Proton 8.0-2 and Proton Experimental (and any 8.0 GE).
steam-405900.log

Kkisak-valve maintainer 2023-07-02 github

Hello @BetaVersionBY, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics), put it in a gist, then include a link to the gist in this issue report.

These look like the lines of interest from the log:

err:module:import_dll Library OpenAL32.dll (which is needed by L"Z:\\home\\beta\\.steam\\debian-installation\\steamapps\\common\\Disgaea PC\\alut.dll") not found
err:module:import_dll Library alut.dll (which is needed by L"Z:\\home\\beta\\.steam\\debian-installation\\steamapps\\common\\Disgaea PC\\dis1_st.exe") not found
[...]
err:module:LdrInitializeThunk Importing dlls for L"Z:\\home\\beta\\.steam\\debian-installation\\steamapps\\common\\Disgaea PC\\dis1_st.exe" failed, status c0000135

I looks like this should be handled by a first time setup installer. Can you move/remove the game's wineprefix and test what happens with a fresh run?

BBetaVersionBY 2023-07-02 github

Can you move/remove the game's wineprefix and test what happens with a fresh run?

Now it works with the newer Proton. Thank you.

Ppumpkinlink 2025-08-22 github

Some of the text and buttons prompts during the tutorial show question marks instead. The first one is supposed to be a green "A" button, and in the second screenshot they're supposed to be arrow right characters (→). I can confirm that this doesn't happen in Windows
Image
Image

Kkaincenteno 2025-09-21 github

Replying to https://github.com/ValveSoftware/Proton/issues/13#issuecomment-3212739307

This got fixed in the recent experimental release https://github.com/ValveSoftware/Proton/wiki/Changelog#available-in-proton-experimental-as-of-2025-09-19

would be nice if they changed the default to experimental or to 10.0-3 whenever it gets released

Proton versions

Launch options

Launch lines

DLLs