Demul padDemul error: IDirectInputDevice8 CreateEffect FAILED

[BadMouth]

Got a couple NAOMI driving games up and running on my main pc (Vista) and wrote an autohotkey script to make them go fullscreen and play nice with my front-end.
Once everything was sorted and working right, I copied it to my driving cab, which runs XP.
On it, I get the following error when a game is launched:

I click OK, and the game plays perfectly fine.

From what I gathered googling the error, HRESULT = 80070057 is an invalid argument and
IDirectInputDevice8 CreateEffect FAILED has something to do with force feedback (which I didn't think Demul supported).

I reset all the gamepad mappings to NONE - same result.
I deleted the padDemul cfg file - same result.
I made sure all the P1 controls were mapped to something for Dreamcast, Naomi & Atomiswave - same result.
I turned off force feedback in windows control panel>gamepads - same result.
The only thing that gets rid of the error is changing to xinput, but then of course my controls don't work.

I was using a logitech gamepad (no rumble) on my main pc and I'm using a logitech momo wheel on my driving cab.

Anyone have any insight?

[BadMouth]

 
Messed with it a while this morning, then gave up.
I disabled the windows error sound and added to the autohotkey script to have it press enter for "OK".
It all takes place behind a black window, so the game appears to load fine when you launch it from the front end.
So problem not fixed, but covered up. 
I'd still like to correct the issue if possible, just don't want to sink anymore time into it right now.

[headkaze]

Try the "Pad Plugin" from http://demul.emulation64.com/downloads/

By numerous requests we have added support of old gamepads, which don't support Event Notification, to the PAD plugin. We hope that all PADs can now be used with our emulator. Of course, not a big change for "long-awaited" new build, but this is better than nothing.
To install, just replace default padDemul with new one.

If that fails try this Google Search as there are others who have had this problem with this emu.

[ant2]

any one find a fix to this ? Im experiencing the same issue

[dorito213]

For those that feel this issue was a lost cause because it plagued alot of people. Just install this.  http://www.microsoft.com/en-us/download/confirmation.aspx?id=35

[delt31]

I have this same error - what was the resolution?  I can't configure ANY keys?  Seems to default to joystick 1 button 1 when I try to change anything

[BadMouth]

I never did get it resolved.  Ended up making an autohotkey script that just covers the screen with a black box and presses enter to skip the error message.
Also disabled the error sound in windows.

This issue never interfered with my ability to map keys though and was only present when using a force feedback steering wheel.
I haven't tested the latest version of Demul.

[jw2000uk]

I never did get it resolved.  Ended up making an autohotkey script that just covers the screen with a black box and presses enter to skip the error message.
Also disabled the error sound in windows.

This issue never interfered with my ability to map keys though and was only present when using a force feedback steering wheel.
I haven't tested the latest version of Demul.

Hi Badmouth, In desperation ive had to drag a oldish thread up..

After months of configuring, Gameex and All the emu's + G25 are working..

Jut cant sort out how to fix this problem with AHK to resolve this issue,Tried reading, but its not clicking in my brain lol.

Gameex does have a add CMD line option per Emu, maybe something i can add to that to close the error screen,instead of the AHK route.



Could you give me steps on how to close it please mate.

[jw2000uk]

Well, Ive cheated lol.

Sorted it with a APP called Clickoff. Small, Freeware App.

Basically point it at  box you want it to shut, ctrl-alt-d

And it will close it from now on. Works 100%

Now i cant get the bleady mouse cursor to go  .. Tried nomousy cmd. it hides the cursor, But stops demul opening..

Tried start nomousy.exe /hide demul.exe -run=dc -image="[ROMPATH]\[ROMFILE]"

any ideas?

[xbrunox]

I never did get it resolved.  Ended up making an autohotkey script that just covers the screen with a black box and presses enter to skip the error message.
Also disabled the error sound in windows.

This issue never interfered with my ability to map keys though and was only present when using a force feedback steering wheel.
I haven't tested the latest version of Demul.

HI I know is a very old topic. But Pls can u share your script code. Thanks

[gstav]

I never did get it resolved.  Ended up making an autohotkey script that just covers the screen with a black box and presses enter to skip the error message.
Also disabled the error sound in windows.

This issue never interfered with my ability to map keys though and was only present when using a force feedback steering wheel.
I haven't tested the latest version of Demul.

HI I know is a very old topic. But Pls can u share your script code. Thanks

Hi guys!

I also ran intro this old bug which still is an annoying thing.
I did modify my rocketlauncher module for demul.7 on line 460 (the black lines is the new code)
Remeber you will get invalid CRC reading so RL will falg this module now, bute works perfect


RLLog.Info("Module - Waiting for Demul to finish loading game.")
winTextSplit := []
;----------------------- mute speakers and kill error message box when steering wheel is connected ------------------------
Send {Volume_Mute}
Winwait, padDemul,,3
IfWinExist, padDemul
{
   IfWinNotActive, padDemul
   {
      WinActivate, padDemul
   }
   WinWaitActive, padDemul
   IfWinActive, padDemul
   {
      Sleep, 500
      Send, {ENTER}
   }
}
Send {Volume_Mute}
;-------------------------------------------------------------------------------------------------------------------------

Hope this help! Please write here if it worked 

[Killa7977]

I dont use rocket Launcher, Just plain big box. Got this error today while moving my Dreamcast bunch of racing games to the cab with steering wheel. Any help about what to do? Thanks

[gstav]

This really is as simple as:

MUTE speakers, wait for the paddemul error window 3 sec. If it comes, press enter on the error message and finally reset the mute again

This is a bug which occurs when you have the steering wheel connected and this kinda fixes this behind the fade of the load of a game.

I guess you want something similar to be hooked in LB/BB when launching demul.

[MotownC]

gstav,
code works great - many thanks!

[Gimpy]

Sorry to up this again, but I just had the exact same problem - what fixed it for me was uninstalling VJoy from my system. Obviously not an ideal solution if you actually rely on Vjoy at all, but for anybody who might have ended up with it installed but doesnt actually use it like me, this immediately resolved the problem. Just figured it was worth adding just in case anybody is on a mad google hunt like I was!

[johey]

Also I have been crying over this for hours, but finally found a somewhat proper solution hidden in a thread at the launchbox-app forum. Just in case the link will not work, here is the content copy-pasted:

Code: (ruby) [Select]

file = File.open("padDemul.dll", "r+b")
file.pos = 0x27E23
buffer = [0xE9, 0x95, 0x00].pack("c*")
file.write(buffer)
Just install ruby (https://rubyinstaller.org/) create a file called "patch.rb" in the Demul plugins folder, copy the above code into the file and save it, and then run the "patch.rb" file. That should also fix the issue.

Also should mention the patch applies specifically to Demul build 111117, which you can find here: http://demul.emulation64.com/files/demul07_111117.7z

I can confirm this patch is working. It prevents the popup from happening and just proceeds starting the game. My force feedback wheel still works with the FFBArcadePlugin.

[sushko]

I can confirm that the patch works but it stopped DumulShooter from working so I cant use it. anyone make a script for LB BB yet.