scutters

I think the error is actually being raised from pinup for dmdext to spit out, but why it needs a rom name for FX3 i don't know, maybe something has changed in later versions of pup/dmdext since the Aliens pack was posted?. The only other thing i can suggest is to try adding -g ALIENS to the launch parameters to see if that helps (it shouldn't as it should be used to tell dmdext the gamename for FP not FX3), and make sure you're on the latest versions of dmdext & pinup. If you still have issues then i guess it's time to raise a bug on github https://github.com/freezy/dmd-extensions/issues and hope freezy has a clue.

It looks like you copied an extra '-' at the start of the launch parameters, don't think that's the issue as dmdext is (mainly) working - there's just that pinup output error.. I guess you've copied the pup stuff to an 'aliens' folder?.. if that's the case it might be worth hardcoding that to test rather then using the TABLEFILEWOEXT bit. E.g. mirror --source=pinballfx3 -q -d virtual --fx3-legacy --fps 60 --use-ini="C:\vPinball\VisualPinball\VPinMAME\DmdDevice.ini" --pinup "C:\vPinball\PinUPSystem\PUPVIDEOS\ALIENS" or mirror --source=pinballfx3 -q -d virtual --fx3-legacy --fps 60 --use-ini="C:\vPinball\VisualPinball\VPinMAME\DmdDevice.ini" --pinup PinUp\ALIENS

It'll fit on one line (copy and paste is easier though!).. it looks like the -q to quit on exit from Mikes tip is included already in the line so no need to worry about that.

Looking at the links i think you're correct. I still think the pup stuff can work from PinballX for FX3 without the pupdmdcontrol thingy. From [New PuP-Pack Alert]ALIENS (FX3 PuP-Pack) - Pinup-Popper & PuP-Pack Releases - Virtual Pinball Universe (vpuniverse.com) There's this launch info; c: cd /d "C:\Visual Pinball\VPinMAME" start /min "" "dmdext.exe" mirror --source=pinballfx3 -q -d virtual --fx3-legacy --fps 60 --use-ini="c:\Visual Pinball\VPinMAME\DmdDevice.ini" --pinup PinUp\[GAMENAME] Which would translate in PinballX as a 'Launch before' action (under settings for the system) Launch Before Executable - dmdext.exe Launch Before path - C:\Visual Pinball\VPinMAME (or whatever) Launch Before Parameters - mirror --source=pinballfx3 -q -d virtual --fx3-legacy --fps 60 --use-ini="c:\Visual Pinball\VPinMAME\DmdDevice.ini" --pinup PinUp\[TABLEFILEWOEXT] (i'm not sure in FX3 if the parameter would be TABLEFILEWOEXT, TABLEFILE or even DESCRIPTION) You might need a launch after as well to kill dmdext when you exit a table? (not sure about that either!) Hope that helps a bit...

Pretty sure that's just to mirror the dmd as an alternative to freezy dmdext.exe. So shouldn't be needed in PinballX. If it says otherwise somewhere then please post a link. I can't help much otherwise (don't use FX3), but maybe check this if you haven't already - [New PuP-Pack Alert]FX3 SSF (Surround Sound Feedback) PuP-Packs - Pinup-Popper & PuP-Pack Releases - Virtual Pinball Universe (vpuniverse.com) (from a quick glance i don't see anything 'popper' specific)

To use launching videos by table you need to use the plugin. See here for install and instructions;

Noticed a couple of wheel images appearing (on other forums) using the webp format. Can that format be added to PinballX at some stage? (only seen static webp images but there may also be some animated ones)

@Itchigo Are you using freezy for the DMD?, if you are make sure you have this line set in dmdevice.ini; ; virtual dmd stays on top of all other windows stayontop = true Not sure if it'll help, but worth a shot. Btw - noticed you're running a 2 screen setup but have the DMD enabled in PinballX on screen 2 (with backglass on screen 1); [DMD] Enabled=True monitor=2 x=0 y=0 width=900 height=300 Not sure if you used to have a 3rd screen or something but you may as well disable the DMD screen in PinballX

Not sure how the situation occurred with the duplicate file. My guess it was a bug in the old version of the plugin when you were running that and/or you somehow managed to copy a loading video into the loading videos folder while PinballX was running. You should be fine now.

It looks like somehow at least one duplicate file name and back up version has been created. Check your C:\PinballX\Media\Loading Videos\ folder; Are there files with a .mp4 and a .bump4 version for the same file name? (i think there's at least BALLY_Attack_from_Mars affected). Delete the .bump4 versions.

The new version works! Thanks @jrl

That makes sense, thanks Mike. I guess in its current format the starter app isn't useable in PinballX. Bit of a shame as it would be 'set and forget', the alternative is to use the alternateexe flag in PinballX but that does need more user maintenance. I'll reply on the vpu thread, not sure if Jarr3 / @jrl will see this here. Still doesn't quite explain the PinballX crash when the system using the starter app is set as Visual Pinball, if the starter app was set to stay open until vpx closes would pbx still crash?

I just had the same idea!. Changing the system type to custom instead of VP averts the crash of PinballX and the table launches ok, but sadly PinballX doesn't recognise the table as having launched and goes back to the wheel (so PinballX and VPX are active at the same time)

Hi, Finally getting round to updating the cab a bit and even loading on visual pinball 10.8 (beta). As part of the update process i thought i'd give the vpinballx.starter.exe app a go (as vpx 10.8 might not be totally backwards compatible i'd rather leave tables that were last saved in vpx 10.7 opening with vpx 10.7). The starter app when configured should look at the table launch parameters, open the table file in the background to work out which version it was saved with and then pass through the cmd to the correct vpinball exe version configured in it's ini file. But, after adding & configuring the starter app and renaming it to vpinballx.exe for PinballX to use, PinballX crashes on table launch. 12:46:15.38 28/11/2023: C:\Visual Pinball\VPinballX.exe /minimized /play "C:\Visual Pinball\Tables\The Walking Dead (Stern 2014)_x32.vpx" 12:46:16.01 28/11/2023: C:\PinballX\vpauto.exe 12:46:20.19 28/11/2023: Created DirectX BackGlass Window 12:46:20.39 28/11/2023: Created DirectX DMD Window 12:46:20.79 28/11/2023: Main display running full screen windowed. 12:46:20.85 28/11/2023: HRESULT: [0x88760868], Module: [Unknown], ApiCode: [Unknown/Unknown], Message: Unknown 12:46:20.91 28/11/2023: Error. Exiting 12:46:20.91 28/11/2023: Video 12:46:20.91 28/11/2023: HRESULT: [0x88760868], Module: [Unknown], ApiCode: [Unknown/Unknown], Message: Unknown 12:46:20.91 28/11/2023: at PinballX.FrmMain.a(Boolean A_0, Boolean A_1, Boolean A_2, Boolean A_3, Boolean A_4, Boolean A_5, Boolean A_6) 12:46:20.91 28/11/2023: at PinballX.FrmMain.a1() 12:46:20.91 28/11/2023: at PinballX.FrmMain.InternalNew() C:\Visual Pinball\VPinballX.exe /minimized /play "C:\Visual Pinball\Tables\The Walking Dead (Stern 2014)_x32.vpx" Will launch a table via the starter app correctly from a cmd prompt. I guess the crash has something to do with PinballX trying to monitor for the visual pinball player window when the process PinballX launches isn't actually visual pinball but a process that launches visual pinball and then closes?. log.txt PinballX.ini

Attachment in first post updated to V2.0.1, a small fix to 5min challenge mode if the challenge table was not found. Thanks @Mike_da_Spike

V2.0.0 of the plugin released and attachments updated in first post. This adds functionality for the Closest to the PIN Pinemhi Weekly Challenge and some bug fixes from Mike; check when PinballX closes if 5 min challenge is active, if so, stop it When no data return from Pinemhi, Filter to check table was empty which result that random a table was taken from all the tables. Now it will stop and doesn't run anything (as we have when no rom is found) Big thanks to @Dna Disturber & @Mike_da_Spike

PinballX is up to date but the plugin isn't, you need to update the plugin from V1.0.2 to V2.3.1 Loading videos were added to PinballX after V1.0.2 of the plugin was built. From the notes on the previous link; Install Extract the contents of the zip file into your PinballX\Plugins folder, unblock the dll file if required (https://www.limilabs.com/blog/unblock-dll-file) and then enable the Loading Image Changer plugin in plugin manager. If updating from the previous version you can also delete the now unused PBXLoadingImage.ini in the PinballX\Plugins folder. Make sure you overwrite the plugin dll file and confirm the version number of the selected plugin in plugin manager. If you still have problems after that please attach new copies of files you previously attached.

Please update to the latest version of the loading video / image changer plugin, see https://forums.gameex.com/forums/topic/23127-plugin-pinballx-loading-video-image-changer-de-randomiser-v2/ (unless you are using a version of PinballX older than V3.60, in which case update PinballX and then update the plugin) Then try again and if you still have problems please attach your Pinballx\Config\Pinballx,ini, PinballX\Log\Log.txt and PinballX\Plugins\PBXLoadingImage_log.txt files Make sure the files are copied after launching a table from PinballX, thanks.

@Fiery Phoenix File matching is disabled in your PinballX config, so we can rule that out. But, you do have UseB2S=True enabled. That means PinballX will attempt to start the backglass file if found in the front end rather than use any image or video media. Starting (and stopping) the B2S file for each table will take longer in PinballX than just showing media. Try turning that off; Settings.exe -> Display Settings -> Use DirectB2S in Front End -> set it to No

Just to clarify, are the images being created and saved or not?. First post seemed to indicate they were being created but then not used in PinballX, this now reads more like the images aren't being saved at all for some tables.

Also bear in mind that PinballX will prioritise backglass videos over backglass images if you have both present. Not sure if that's a factor for you when a screenshot is taken and saved in the correct folder but not shown in PinballX. What do you see in PinballX, is it the 'no backglass.mp4' video from the media\videos folder or something else? PinballX file matching if enabled might be a factor too. The pinballx.ini file will show us if that is enabled or not.

I can see the washed out effect in the Indiana Jones video. Not seen that effect before where the colours change while the video is dragged around the screen. Not a PinballX issue, think it's probably HDR or nvidia somewhere (maybe in combination with windows fullscreen optimisations) Make sure these two options in nvidia control panel are set and let us know if that helps;

The only other thing to try then is to do the recording in two steps. Make sure this box is not ticked in PbxRecorder; And the try to record just the playfield again. Hope that works, otherwise your hardware might not be up to recording audio and video simultaneously with the current version of PbxRecorder

In PinballX or in game? If in PinballX make sure you have the latest LAV codecs installed, and you could try using the YUV420P recording option in PbxRecorder. For in game issues with pup pack performance you probably need to contact the author via the packs download support thread, or down scale the videos.

The audio should be included in the playfield video file. From the pbx recorder log everything looks ok so i assume it worked Check the "C:\PinballX\Media\Visual Pinball\Table Videos\1 Doctor Strange Balutito Mod.mp4" file for sound. You may need to enable audio in videos in PinballX Settings -> Audio Settings -> Sound in Videos = Yes