freezy / dmd-extensions

A toolbox for virtual pinball dot matrix displays.
GNU General Public License v2.0
128 stars 55 forks source link

Broken Functionality for Pinball FX3 PuP Packs #412

Open LunatechFringe opened 1 year ago

LunatechFringe commented 1 year ago

The latest DmdDevice.dll does not allow PuP Packs to trigger in Pinball FX3. I was able to restore functionality by temporarily replacing the current DmdDevice.dll file with the version from 1.8.2. Once I restore the latest file, PuP Packs for Pinball FX3 no longer work.

freezy commented 1 year ago

Logs please!

LunatechFringe commented 1 year ago

Here you go...sorry about that.

DmdDevice.log

LunatechFringe commented 1 year ago

I forgot to mention that I'm using the PuPDMD drivers in Pinball FX3. I have the latest PinUP Popper updates installed and configured for 64-bit support.

freezy commented 6 months ago

Sorry for the late response. Has this been resolved in v2.2.1?

LunatechFringe commented 6 months ago

No worries. I appreciate your time. I actually tested with 2.2.2 tonight, and it still won't work. I'm getting ready to do a fresh install using Baller Beta Bonanza. I'll test that first. I just ordered a new video card (going from AMD to nVidia), as I'm having some weird issues with AMD's drivers where my loading screens aren't transparent, anymore. There may be other issues I'm not aware of, but I'll let you know my results once I receive the card.

Thanks!

On Sun, Apr 21, 2024 at 11:56 AM freezy @.***> wrote:

Sorry for the late response. Has this been resolved in v2.2.1?

— Reply to this email directly, view it on GitHub https://github.com/freezy/dmd-extensions/issues/412#issuecomment-2068165566, or unsubscribe https://github.com/notifications/unsubscribe-auth/AU5I4DWO5ORF2IAWJ6SRS63Y6QDUBAVCNFSM6AAAAAA37IO3SCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE3DKNJWGY . You are receiving this because you authored the thread.Message ID: @.***>

freezy commented 6 months ago

Okay, thanks.

LunatechFringe commented 6 months ago

I removed my Radeon card's software using AMD's Cleanup Utility followed by DDU for both AMD and nVidia cards...all in safe mode. I had a smooth ASUS 4070 Ti Super installation afterwards. I'm also on the current Popper installation now and have updated all vpin components with it. Transparency is working as expected now.

However, FX3 PuP Pack events are still not getting triggered, although it initially loads with the table. Since it was working with an earlier version of Freezy DMD, I can only assume something broke with its color triggers. This could be reproduced.

Let me know if you need more information.

On Mon, Apr 22, 2024, 12:56 AM Stephen Salazar @.***> wrote:

No worries. I appreciate your time. I actually tested with 2.2.2 tonight, and it still won't work. I'm getting ready to do a fresh install using Baller Beta Bonanza. I'll test that first. I just ordered a new video card (going from AMD to nVidia), as I'm having some weird issues with AMD's drivers where my loading screens aren't transparent, anymore. There may be other issues I'm not aware of, but I'll let you know my results once I receive the card.

Thanks!

On Sun, Apr 21, 2024 at 11:56 AM freezy @.***> wrote:

Sorry for the late response. Has this been resolved in v2.2.1?

— Reply to this email directly, view it on GitHub https://github.com/freezy/dmd-extensions/issues/412#issuecomment-2068165566, or unsubscribe https://github.com/notifications/unsubscribe-auth/AU5I4DWO5ORF2IAWJ6SRS63Y6QDUBAVCNFSM6AAAAAA37IO3SCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE3DKNJWGY . You are receiving this because you authored the thread.Message ID: @.***>

coreduo0099 commented 3 months ago

I have the same issue. Tried 32 and 64 bit vpinmame/freezy 2.2.2. Also tried dmdext and PUPDMDControl method. Both Aliens 1.0 and the newer 1.1 puppacks.

Happy to gather whatever might be needed to debug.

coreduo0099 commented 3 months ago

well, found my solution from 2021 issue #223... This is the ONLY config that works for me with triggers working. I don't think there is a bug in the code necessarily. I went all the way back to 1.8.2 and this works with 2.2.2 as well. I Started with recommended config from nailbuster but changed the dmdext line... (local pathnames will vary based on install). Hopefully this will work for @LunatechFringe

@echo off

rem remove the next two rem lines to setup PUpDMD for FX3 rem cd /d "E:\Emulator\Pinball emu\VisualPinball\VPinMAME" rem start /min "" "PUPDMDControl.exe" FX3 PINUP[GAMENAME]

rem remove next two rem to use or setup DMDEXT for FX3 cd /d E:\Emulator\Pinball_emu\VisualPinball\VPinMAMEstart /min "" "dmdext.exe" mirror --source=pinballfx3 --fps 30 -q -d virtual --virtual-position=5889 321 1664 342 --pinup PINUP[GAMENAME] REM start /min "" "dmdext.exe" mirror --source=pinballfx3 --fps 60 -q -d virtual --virtual-position=5889 321 1664 342 --pinup PINUP[GAMENAME]

REM SET ALTPARAM=-class REM if "[ALTMODE]"=="arcade" (SET ALTPARAM=) REM If you prefer arcade Change the 1st 2 lines below to look like ones above REM Default is classic and arcade

SET ALTPARAM= if "[ALTMODE]"=="classic" (SET ALTPARAM=-class ) if "[ALTMODE]"=="hotseat2" (SET ALTPARAM=-hotseat_2 ) if "[ALTMODE]"=="hotseat3" (SET ALTPARAM=-hotseat_3 ) if "[ALTMODE]"=="hotseat4" (SET ALTPARAM=-hotseat_4 )

START "" "[STARTDIR]Launch\VPXSTARTER.exe" 5 5 20 "Pinball FX3"

cd /d "[DIREMU]" START "" "Pinball FX3.exe" -table_[GAMENAME]

timeout 6 START /min "" "[STARTDIR]Launch\SendFXNewGame.exe"

LunatechFringe commented 3 months ago

@coreduo0099

The only major differences between our launch scripts are as follows:

1) I use PUPDMDControl. There's a possibility of that being the cause of the problem. The file in use in the VPinMAME directory is timestamped as version 1.5.0.3 on 11/1/2023. SCRIPT ITEM: start /min "" "PUPDMDControl.exe" FX3 PINUP[GAMENAME]

2) I use steam.exe to applaunch the game:
SCRIPT ITEM: START "" "[DIREMU]\steam.exe" -applaunch 442120 %ALTPARAM% -table_[GAMENAME]

That's basically it. I wonder if that's the issue? Maybe we can have Nailbuster look into it.