scutters

.. or maybe you have vpx set to run as admin? Glad it's sorted anyway Just as a note you probably don't need to create videos and images, the front end will use videos if found first then look for images.

More info from the thread on vpf (https://www.vpforums.org/index.php?showtopic=54204&p=540217) the vpinmame error code is "c0000005" which is a memory access violation. @Itchigo Not sure if that error is on the win7 or win10 (or both?), or if vpinmame is the only app affected. It does hint at deeper trouble which could be software or hardware related. Lots of suggestions in google to try but i'd start with a system file check (sfc /scannow see Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support) and a memory diagnostic check (Diagnose memory problems on your PC (microsoft.com)) as well as running dxdiag. Does that problem relate to the PinballX issue, or even the DP problem?... sorry no idea

Please attach the PBXrecorder.log file (should be in the same location as the pbxrecorder executable). Can you also advise if you've used previous versions of pbxrecorder before without issue (so we know if this is something new introduced with v2.1), it should definitely close each table after recording it.

If you are having vpinmame issues as well that could be related as you are using vpinmame in PinballX. Also try changing the 'Use Pinmame in front end' setting to No in Display Settings. Then attach the new log and ini files. (not sure if you tried the installing the current framework version of PinballX or not, but you did try v2.06 which was probably framework only at that time so probably achieved the same thing anyway [and didn't work ]) Edit - there was one actual error in one of the log files posted previously; HRESULT: [0x8876086C], Module: [Unknown], ApiCode: [Unknown/Unknown], Message: Unknown Which hints at a direct x problem so please also run dxdiag and check for any problems reported on any of the tabs. It'd be a bit strange if you have the same directx problem on both a win7 and a win10 install.. but worth a check.

I meant install the PinballX .net framework version (not the actual .net 4 runtime). The PinballX installer includes .net core and .net framework versions, the default install is .net core but if you change the compatibility mode of the PinballX installer it can install the framework version of PinballX instead (which has the same version number and updates as the core version). The PinballX log file will indicate on the first line which flavour is installed.

Think he still has the black screen in PinballX issue with just the 1050 (but no black screen in Windows) The log file is showing the same old loop ... 18:24:34.99 10/1/2024: Main display running full screen windowed. 18:24:35.21 10/1/2024: Created DirectX BackGlass Window 18:24:35.48 10/1/2024: Main display running full screen windowed. 18:24:35.71 10/1/2024: Created DirectX BackGlass Window ... and then finishes with an error. Not sure how old your PinballX install was before the upgrade so please try with the legacy .net 4 version of the latest PinballX instead (doesn't use .net core) As https://forums.gameex.com/forums/topic/28684-news-pinballx-590/ "To force the .net 4 install on 64 bit Windows 7 or newer set the compatibility to Windows XP or Vista." (i.e. change the compatibility mode of the installer exe before running it)

@Itchigo This is about the best i can find for black screen issues, see first post here and links - https://forums.evga.com/Comprehensive-Windows-10-Black-Screen-Trouble-shooting-Guide-m3131813.aspx Lists a lot more than i could suggest anyway!... Hopefully something on there is the answer. Like @Draco1962 i'm pretty sure once the BG DP issue is resolved on the 3060ti PinballX will just work.

I assume this one? https://nvidia.custhelp.com/app/answers/detail/a_id/5233/?linkId=100000076816300 @Itchigo please confirm Edit - just saw your post above, not that one then! - might be worth a shot with this one. And yes, agree sort out the issue with the 3060 first. And a few more question for @Itchigo.. On the win 10 OS with just the 3060 ti ; Are Windows and Nvidia drivers updated (think 561.09 for Nvidia - GeForce Game Ready Driver | 561.09 | Windows 11 | NVIDIA) In Device Manager -> Display Adapters is the 3060ti shown or some form of generic adapter name When the 1050 ti was used on its own was the BG connected via HDMI or DP? (asking mainly because I have had an issue before where I actually had to enable DP 1.2 in monitor settings for DP to work correctly at higher resolutions - but I guess if the monitor worked ok with DP on the 1050 then that's probably not it)

Plenty of factors at play with this issue @Itchigo! Searching on the term "GPU 2:" in this forum shows plenty of matches which suggests it does (but whether the 2nd GPU was in use for anything i don't know - but i suspect 2 GPU's in itself is not the issue in PinballX) The underlying issue is probably linked to the DP issue you have and if that is resolved then the 2nd GPU can be removed from the equation so i don't want to muddy the waters of @Draco1962 questions too much but a a couple of extra things to confirm; Windows 7 SP1 - does your install include the post SP1 updates? (How to obtain and install Windows 7 SP2 - Microsoft Community) Can you try running PinballX with the option in settings -> display settings -> 'use directb2s in front end' set to No. There's a chance that an issue running the B2S in pinballx is creating the backglass <-> playfield loop seen in the log file.

Just to re-cap, is the remaining issue that some system(s?) don't appear in the Lists menu (but they do appear ok in the Systems wheel)? If so, can you disable a couple of the currently visible systems in the Lists menu as a test and take a screenshot of what you see in the menu after that. This will confirm if it is the too many items to show in that menu problem.

Pbx Recorder V2.1 Changes V2.0 Skip comment (#) lines in screenres.txt If screenres.txt not found in Visual Pinball\Tables folder attempt to locate using B2S registry entries Added a taskkill catch all (useful if using vpx starter app - https://vpuniverse.com/files/file/17134-vpinballxstarter/ where the actual vpinball exe is a child process) Changed DMD_X location to also include backglass offset value Playfield screen videos captured via ddagrab instead of gdigrab should now capture VPX OpenGL fullscreen (requires updated ffmpeg.exe) Added link to forum post re audio capture Kill pinemhi rom monitor at startup and restart on exit (avoid potential for leaderboard popups in captured videos) Changes V2.1 (thanks @Mike_da_Spike) Add option for ‘-INI’ Check: Added a check for the ‘-INI’ parameter on the launch line to facilitate launching VPX. Correction custom XML handling . Fixed an issue where custom XML files were creating new systems in the media directory with the name of the XML file. Bug Fix: Progress Window: Replaced internal function progress with newly created myprogress to avoid flickering during rapid updates to the Progress window. Pause Progressbar: Fixed the progress window behaviour after return of pause Note - this version uses a newer version of ffmpeg to enable ddagrab for VPX OpenGL capture (gdigrab results in a static image capture only), this is included in the zip, an older ffmpegold.exe version is included as well which after renaming to ffmpeg.exe can be used with V1.9 if you have any problems with V2.1. PBXRecorder_x64_v2.1.zip

I think you probably have too many List items to show in that menu (see https://forums.gameex.com/forums/topic/22259-pinballx-enhancementsfeatures-requests/?do=findComment&comment=206928Does it appear under Systems? Note - you may need to enable system list in settings, these two options;

Try renaming removing the '-' character.

Quick one for Ltek's Fallout VE table using @hauntfreaks backglass, just a simple on off..

I know what you mean.. MS!!! Most of the 'play' functions are self contained, just telling WMP what to play and when, so hopefully it should be fairly simple to change to another library if/when it's needed.

Yeah, but as WMP is still included with Win11 there's less dependencies required in the plugin just to use that (for now)

Internet Radio The media player plugin is compatible with internet radio stations. You can create a playlist with favourite stations and skip through them using the navigation buttons. Track data will not appear in the player though, just the station name. For the stations to play correctly you must enter the source of the stream playing the tracks though and not all stations show this. Laut.fm is a good example of easy to use stream URL's. http://fmstream.org/index.php?c=FT is a useful site to use, select the station you want and it will display the correct URL to use. To test a stream URL you can open Windows Media Player (legacy) right click on it and select 'Open URL', if the stream opens you can add it to your playlist. If it errors with "Windows Media Player encountered a problem while playing the file" then the address is not valid.

For anyone having issues building larger apng files with the image to spinball app, replace the apngasm.exe file in the apps Resources folder with this version; apngasm64.zip (Note - this is probably only needed if you are using a 4k underlay image and with a lot of animation frames, which in turn uses a lot of memory) Thanks @Mike_da_Spike I'll update the copy in the main download in the next app update

As the brightness is ok most of the time also check the monitor for some sort of adapative / dynamic contrast setting (if there is one disable it)

Yep.. all ok in 6.11. Thanks!

Hi Tom, For info, i get this error running the installer for V6.10 I click OK and continue and the install completes and PinballX launches V6.10 ok. Not sure if it's something my end or not (i have plenty of space on C:\). Not too worried as Pbx launches ok.

Can i put that on my CV? 🤣

I think you missed my edit.. Can you try that too

Please try with the VPX 'Force exclusive fullscreen mode' checked Please attach new copies of the log.txt & poinballx.ini files if the problem persists after that Edit - one further thing to try, in PinballX\Settings.exe under General Settings -> Table Loading Media Mode try changing to 'Use Loading Folders' (this will prevent PinballX from trying to take a screenshot of the playfield video to use as a loading image if that is the cause of the delay)

Looks like the main delay is before VPX is launched, after Set Plugin data; 22:04:19.50 03/09/2024: Launch System 22:04:19.50 03/09/2024: Hide Backglass 22:04:19.50 03/09/2024: Waiting for threads 22:04:19.60 03/09/2024: Disposing display 22:04:19.68 03/09/2024: Set Plugin data 22:05:20.36 03/09/2024: Writing ScreenRes.txt 22:05:20.37 03/09/2024: C:\Visual Pinball\VPinballX.exe /play -"C:\Visual Pinball\Tables\Spider_man.vpx" 22:05:20.42 03/09/2024: C:\PinballX\vpauto.exe 22:05:28.74 03/09/2024: Visual Pinball Player window foreground: 8 22:05:29.47 03/09/2024: Found PinMAME ROM: sman_261 As no plugins are enabled it could be loading media or playfield image creation related with some sort of timeout in PinballX(?) Make sure LAV codecs are installed as a first step - https://forums.gameex.com/forums/files/file/2451-lav-video-codecs/ Let us know if that helps.