Jump to content



Photo
- - - - -

Pinup Popper Future Pinball table closes immediately after start


  • Please log in to reply
2 replies to this topic

#1 barny1100

barny1100

    Hobbyist

  • Members
  • PipPip
  • 35 posts

  • Flag: Austria

  • Favorite Pinball: All

Posted 01 March 2024 - 05:16 PM

After a long absence, greetings and another question in the round ;)

 

 

I installed Pinup Popper (it's awesome because you don't have to install all programs individually anymore) :love39:

with Visual Pinball all tables start perfectly 

..

 

Installed a few VPX and Future Pinball tables

So far so good ... :pinnochio:

 

Then I did an FP and BAM Essentials AIO update like in the great videos from Terry R   (to have FP and Bam up to date)

 

but after the update the DMD on the third monitor suddenly disappeared (only) on the FP tables ..?

 

 

After a sarch in the net  i find and I had to insert the following command line  in the FP script in Popper (marked with a green frame in the picture)

 

 

Then I had the DMD in the FuturePinball tables in the popper on the third display again  :dblthumb:  

 

But now  ithink? after the update

I noticed the problem at least now with one table in Future Pinball

(Aliens Legacy (Ultimate Edition) (v1.12) (p2.7) (DOFLinx) )

 

The table starts with the emu FPLoader exe in BAM (without popper) without problems.

 

But when I start the table with P.Popper frontend

the table opens and closes again immediately

and I have the Windows desktop on all three screens ?

 

But with ESC I return to the table selection menu in Popper...?

 

 

Other tables work fine (not only directly from Emu but also with Popper)...?

 

 

Does anyone have an idea what i do wrong so 

why the table  (only in the frontend popper)  closes immediately? :think:

 

Thank you

 

Skript Picture:

https://ibb.co/Gk3CJRG

 

Popper FP  Launch Skript:

rem Enable FP Backglass and Arcade Mode
REG ADD "HKCU\Software\Future Pinball\GamePlayer" /v "ArcadeMode" /t REG_DWORD /d 1 /f
REG ADD "HKCU\Software\Future Pinball\GamePlayer" /v "SecondMonitorEnable" /t REG_DWORD /d 1 /f
rem Disable FP Backglass and Arcade Mode if "Custom Launch Param" = PinEvent
if "[custom1]"=="PinEvent" (REG ADD "HKCU\Software\Future Pinball\GamePlayer" /v "ArcadeMode" /t REG_DWORD /d 0 /f)
if "[custom1]"=="PinEvent" (REG ADD "HKCU\Software\Future Pinball\GamePlayer" /v "SecondMonitorEnable" /t REG_DWORD /d 0 /f)
CD /d "[DIREMU]"
start /min "" "dmdext.exe" mirror --source=futurepinball -q --virtual-stay-on-top --fps 60 -g "[GAMENAME]" --use-ini="DmdDevice.ini"
 rem Run DMDExt from the FP folder only if "Custom Var #2" = FP_DMDExt
if "[custom2]"=="FP_DMDExt" (CD /d "[DIREMU]")
if "[custom2]"=="FP_DMDExt" (start /min "" "dmdext.exe" mirror --source=futurepinball -q --virtual-stay-on-top --fps 60 -g "[GAMENAME]" --use-ini="DmdDevice.ini")
if "[custom2]"=="FP_DMDExt" (timeout /t 1)
rem Launch Future Pinball
START "" "[STARTDIR]Launch\VPXSTARTER.exe" 10 5 60 "BSP Software*"
START "" "[DIREMU]\BAM\FPLoader.exe" /open "[GAMEFULLNAME]" /play /exit /arcaderender /STAYINRAM
 
---------------
 
Close Skript :
 
"[STARTDIR]LAUNCH\PUPCLOSER.EXE" WINTIT "Future Pinball" 2 1
REG ADD "HKCU\Software\Future Pinball\GamePlayer" /v "ArcadeMode" /t REG_DWORD /d 1 /f
REG ADD "HKCU\Software\Future Pinball\GamePlayer" /v "SecondMonitorEnable" /t REG_DWORD /d 1 /f
if "[custom2]"=="FP_DMDExt" (taskkill /f /im "dmdext.exe")

 

-----------

 

 

 

 

 

 

 

 

 

 

Ryzen 5 and 32GB DDR4

GTX 1060 with 6GB

 SSD ...

Three Screens  FHD

 

 

 

 

 

 

A few I have built

machines to play

(I always preferred screwing to programming​ :help:  )

​https://ibb.co/NCZWfz0


Edited by barny1100, 03 March 2024 - 03:21 PM.


#2 fhjui

fhjui

    Enthusiast

  • Members
  • PipPipPip
  • 375 posts
  • Location:Germany

  • Flag: Germany

  • Favorite Pinball: especially EM tables

Posted 04 March 2024 - 10:34 PM

ok, as no one has an idea I try to help you:

With adding your add. commandline it can be possible that  DMDext is called twice.

At first a short explanation what the launchscript does:

lines 2+3: reactivates the arcademode and the second monitor with backglass to be on the safe side, if a previously started PinEvent FP-table has not closed regulary, the closescript has not been executed.

lines 5+6: in case of a PinEvent table Arcademode and Backglass monitor are disabled. Therefore "custom launch param" in Gamemanager has to be set to "PinEvent"

lines 7+8: these lines are duplicated, they are the same as in lines 10-12

lines 10-12: here are the regular commands which you need to mirror the DMD to the DMD screen. Thats a feature of DMDext because FP can only handle 2 Screens and does not know what a DMD screen is.
         these commands are executed, if the value "FP_DMDExt" is set in "custom var #2" for this table in Gamemanager.

the penultimate line starts vpxstarter. Here the params  "10 5 60 "BSP Software*" means:

        if the program with window title "BSP Software" (i.e. Future Pinball) is found,  it hides Pinup Popper after 10 seconds and  keeps Future Pinball in focus for 5 seconds.

        if future Pinball (aks BSP Software in its title) cannot be found, Popper will go into timeout after 60 sec. and hide.

the last line runs Fploader which runs FP itself.

 

Because of popper doesn't recognize that FP is not running you get back to popper menu after pressing the game exit key.

To check what has popper done during launch and close, it saves its last executed scripts in the PinUpSystem\Launch dir. Look for the scripts curClose.bat and curLaunch.bat, that its content is ok and corresponds espec. with launch script.

 

from here I cannot exactly anaylze what goes wrong in your config. You have to try to isolate the error.

Do you have checked in taskmanager that FP is not running ?

There are two ways, which I would suggest:

  • you can create a new emulator only for test. You can name the new Emu "test-fp" , its up to you. Copy/paste the fields from the FP-Emu to the new test emu. Do the same with the launch /close script. The goal is to get a new emulator where the launch script can be changed and tested without destroying the regulat FP-Emu config.
  • run gamemanager , "add new game", and add this Alien Legacy table. The create a playlist on top and add this table for the new emulator.
  • now you can change the script to isolate the error. You can rem-out all lines except these ones:
    CD /d "[DIREMU]"
    start /min "" "dmdext.exe" mirror --source=futurepinball -q --virtual-stay-on-top --fps 60 -g "[GAMENAME]" --use-ini="DmdDevice.ini"
    timeout /t 1
    rem Launch Future Pinball
    START "" "[STARTDIR]Launch\VPXSTARTER.exe" 10 5 60 "BSP Software*"
    START "" "[DIREMU]\BAM\FPLoader.exe" /open "[GAMEFULLNAME]" /play /exit /arcaderender /STAYINRAM
  • then you can test it.
Second way is to create a batchfile for test:
 
CD /d "C:\vPinball\FuturePinball"
start /min "" "dmdext.exe" mirror --source=futurepinball -q --virtual-stay-on-top --fps 60 -g "C:\vPinball\FuturePinball\Tables\Aliens Legacy (Ultimate Edition) (v1.12) (p2.7) (DOFLinx).fpt" --use-ini="DmdDevice.ini")
timeout /t 1
rem Launch Future Pinball
START "" "C:\vPinball\FuturePinball\BAM\FPLoader.exe" /open "C:\vPinball\FuturePinball\Tables\Aliens Legacy (Ultimate Edition) (v1.12) (p2.7) (DOFLinx).fpt" /play /exit /arcaderender /STAYINRAM

 

perhaps you must change the dirs

To start DOLinX is unimportant for this test
 


Edited by fhjui, 04 March 2024 - 10:36 PM.

My documentation for installing vpin software with PinUpsystem (Baller installer): https://mega.nz/fold...wAXZlOEMQGbdutQ

Files and PDF-docu in the subdir "Installation vPin-Software with Baller-Installer"


#3 barny1100

barny1100

    Hobbyist

  • Members
  • PipPip
  • 35 posts

  • Flag: Austria

  • Favorite Pinball: All

Posted 07 March 2024 - 06:28 PM

ok, as no one has an idea I try to help you:

With adding your add. commandline it can be possible that  DMDext is called twice.

At first a short explanation what the launchscript does:

lines 2+3: reactivates the arcademode and the second monitor with backglass to be on the safe side, if a previously started PinEvent FP-table has not closed regulary, the closescript has not been executed.

lines 5+6: in case of a PinEvent table Arcademode and Backglass monitor are disabled. Therefore "custom launch param" in Gamemanager has to be set to "PinEvent"

lines 7+8: these lines are duplicated, they are the same as in lines 10-12

lines 10-12: here are the regular commands which you need to mirror the DMD to the DMD screen. Thats a feature of DMDext because FP can only handle 2 Screens and does not know what a DMD screen is.
         these commands are executed, if the value "FP_DMDExt" is set in "custom var #2" for this table in Gamemanager.

the penultimate line starts vpxstarter. Here the params  "10 5 60 "BSP Software*" means:

        if the program with window title "BSP Software" (i.e. Future Pinball) is found,  it hides Pinup Popper after 10 seconds and  keeps Future Pinball in focus for 5 seconds.

        if future Pinball (aks BSP Software in its title) cannot be found, Popper will go into timeout after 60 sec. and hide.

the last line runs Fploader which runs FP itself.

 

Because of popper doesn't recognize that FP is not running you get back to popper menu after pressing the game exit key.

To check what has popper done during launch and close, it saves its last executed scripts in the PinUpSystem\Launch dir. Look for the scripts curClose.bat and curLaunch.bat, that its content is ok and corresponds espec. with launch script.

 

from here I cannot exactly anaylze what goes wrong in your config. You have to try to isolate the error.

Do you have checked in taskmanager that FP is not running ?

There are two ways, which I would suggest:

  • you can create a new emulator only for test. You can name the new Emu "test-fp" , its up to you. Copy/paste the fields from the FP-Emu to the new test emu. Do the same with the launch /close script. The goal is to get a new emulator where the launch script can be changed and tested without destroying the regulat FP-Emu config.
  • run gamemanager , "add new game", and add this Alien Legacy table. The create a playlist on top and add this table for the new emulator.
  • now you can change the script to isolate the error. You can rem-out all lines except these ones:
    CD /d "[DIREMU]"
    start /min "" "dmdext.exe" mirror --source=futurepinball -q --virtual-stay-on-top --fps 60 -g "[GAMENAME]" --use-ini="DmdDevice.ini"
    timeout /t 1
    rem Launch Future Pinball
    START "" "[STARTDIR]Launch\VPXSTARTER.exe" 10 5 60 "BSP Software*"
    START "" "[DIREMU]\BAM\FPLoader.exe" /open "[GAMEFULLNAME]" /play /exit /arcaderender /STAYINRAM
  • then you can test it.
Second way is to create a batchfile for test:
 
CD /d "C:\vPinball\FuturePinball"
start /min "" "dmdext.exe" mirror --source=futurepinball -q --virtual-stay-on-top --fps 60 -g "C:\vPinball\FuturePinball\Tables\Aliens Legacy (Ultimate Edition) (v1.12) (p2.7) (DOFLinx).fpt" --use-ini="DmdDevice.ini")
timeout /t 1
rem Launch Future Pinball
START "" "C:\vPinball\FuturePinball\BAM\FPLoader.exe" /open "C:\vPinball\FuturePinball\Tables\Aliens Legacy (Ultimate Edition) (v1.12) (p2.7) (DOFLinx).fpt" /play /exit /arcaderender /STAYINRAM

 

perhaps you must change the dirs

To start DOLinX is unimportant for this test
 

 

 

Vielen Dank für Deine ausführliche Erklärung  :love39:

 

Das hilft mir sehr einige Zusammenhänge "etwas" zu verstehen 

und gibt mir  einige Ansätze was ich probieren kann...

 

Danke  :tup: