Yeah, this also seemed to happen in all of their games for me: Phantom Brave, Disgaea, and Disgaea 2 (all PC). I use DualShock 4 controllers, simple bluetooth connection or wired.

I'd suggest try finding a way to secure connections to your gamepad, if possible. There seems to be more of a problem with how the game engine runs.

And also, as the games note, be sure to save as frequently as possible to prevent any unsaved data loss.

Hey doods could I get specs please?

Originally posted by NISAAlex:

Hey doods could I get specs please?

computer specs?

Originally posted by Nern Guan:

Originally posted by NISAAlex:

Hey doods could I get specs please?

computer specs?

Yup. That'll help them see what any computers with this issue have in common.

For what it's worth, I do NOT have this issue with a wired PS4 controller; when I pull the plug it acts like I have the LEFT and UP D-pad buttons pressed instead. It does this for a second or two and then it corrects itself and allows me to use keyboard input.

If this matters any, here are my specs:
i7 3770, GTX1070, 16GB RAM, Windows 10 Home EN-US x64, wired PS4 controller (came with a Pro), no special drivers/input rewriters installed.

The same happened to me, when the battery of my X-BOX 360 controller was dead.

My specs:
i7-5820K 3.3GHz, GTX 970, 16GB RAM, Windows 10 Pro N x64, wireless X-BOX 360 controller

i7-3770 3.4GHz, 8GB RAM, AMD HD7800, Windows 7 SP1 64bit
Wireless XBox controller

Happened in D1 as well; did NOT happen in PB demo.

Edit: if the controller isn't turned on when starting the game, it seems it doesn't crash.
I think I read someone say to do this in D1, but I forgot.
Anyway, for those having this problem, try doing this to see if it works.

Originally posted by Anwonu:

Edit: if the controller isn't turned on when starting the game, it seems it doesn't crash.
I think I read someone say to do this in D1, but I forgot.
Anyway, for those having this problem, try doing this to see if it works.

Its work, thank you :)

If it helps I encountered this bug with an Xbox 360 controller on my old pc, on D1, and on my new PC, on D2 demo.

I always start games after I connect my controller since some games flat out do not detect a controller after booting, so it's not that. My old comp was W7 with a GTX770, new is W10 with a 1080. Same issue on two PCs on two different games? Its definately a game build issue.

Hope you guys fix it because I enjoy the games but I refunded D1 and cannot buy another of your ports whilst issue is there. Due to the nature of the games, crashing when you're most of the way through an item world run is so frustrating.

I totally misread that and had it the other way round - from the quick tests I did, this works. Start your game, THEN connect the controller.

It still could use fixing, bit of a silly bug..

Can anyone confirms if this works in Disgaea 1? I'm *THIS* close to pushing the button on a wired Xbone controller because of this issue. But if the "Turn on the controller AFTER turning on the game" trick works, and prevents Disgaea from CTD when the controller goes to sleep then I'll hold off.

I'm also experiencing this bug. Currently I am using a PS3 Controller and if the signal from the USB port breaks up for even a moment it will automatically trigger a crash. I've tried starting the game with the controller unplugged and then plugging it in but it doesn't work in my case for some reason. Hopefully this issue will be patched eventually since it seems that this game is still being updated. If there are any developers still looking at this here are my specs.

My specs: AMD FX(tm)-8320 Eight-Core Processor 4.00 GHZ, Nvidia GTX650ti video card, 8GB of RAM, Windows 7 64bit Professional operating system, wireless PlayStation 3 DS3 controller hooked up to USB port via cable (in conjunction with Better DS3 Tool)