scutters

Might need the log file of the crash too for PinballX, but try turning off the stats plugin (i know that has problems with .net core if xdmd/flexdmd output is selected). Don't know about game manager crashes.

Sorry to say, but i have no idea why the DMD only works in Win11 under compatibility mode for you. Screens look ok too. I'm afraid i'm out of suggestions

I don't know what to make of that . Something very strange going on somewhere. Mikes right, on your 2nd PinballX install ini file it shows you have auto position direct b2s set to True, which is why PinballX updated screenres.txt. But i don't know where it could get an x offset of 16000 either. How are your screens set up in windows? Did you reinstall lav codecs when you reinstalled? It looks like it. You're not running any other software as well that could throw things off are you (i'm thinking of stuff like RTSS frame limiter or afterburner), and you have Defender turned off (or exclusions set)?

Sorry, but i'm about out of ideas.. I run PinballX 5.37 x64 on Win11, with freezy 1.9.0, vpm 3.4, vpx10.7 without issues (and i also display 2 dmd displays, external and vpm). Can't see anything wrong in your log/ini files either. One last thing to try would be to run PinballX as admin just to see if that has any effect. Hope someone else chips in with some other ideas if not..

I was hoping the dmd was just hidden behind something else when launched from PinballX, looks like that's not the case then! Do you have anything set to run as admin or any compatibility modes on the new setup (and were they before the updates)? - i'm guessing the new setup is a brand new windows install, if so those settings will not have carried over abd might be messed up if you've now got VPX as admin or something. Other stuff to confirm - what version of freezy dmd device dll do you have, and does VPX launch ok with DMD if you manually use the same command as PinballX from a command window (e.g. C:\Visual Pinball\\VPinballX.exe /play -"C:\Visual Pinball\Tables2\Apollo 13 (Sega 1995) w VR Room v2.01.vpx")

That is a location on the Gameex FTP site, but basic members have upload only access - see https://forums.gameex.com/forums/explanation-of-member-groups/ Click the Store button at the top of the page for options.

Is the PinballX dmd window still open and appearing on top of the freezy dmd window after starting a game? It looks like you have (for the Elvis table anyway) selected not to hide the PinballX dmd when launching a game in game manager / pinballx database manager ('Not Hide DMD!' shown in log file). In \Visual Pinball\vpiname\dmddevice.ini for the Freezy display do you have this line set to true? ; virtual dmd stays on top of all other windows stayontop = true The vpiname window should stay appear on top of the apron instruction card display anyway by default (i think), but the instruction card apron display will always be on after launching a game. Please confirm what you see on the DMD display areas after launching a game from PinballX, and if with ALT+TAB you can bring the DMD windows to the front (or if they are not even open at all).

Ok.. so Screen 1 is Topper, DMD and Apron in PinballX and then in game is used for Topper and two dmd displays (freezy/external dmd and a vpinmame dmd?) Not sure i've got that right.. maybe pictures would help my if not. Which DMD display isn't working, and where (in PinballX or in game, or both?), and is it visible with ALT+TAB ?

I think you're reporting a different issue. This thread is for an issue using pinmame in the front end (where the actual rom is used on dmd rather than video or images), you have UsePinMAME=False in the ini file so i assume using videos. This should probably be raised in it's own thread. Can you also confirm some info on your settings, it looks like you're trying to use screen 1 as a split screen for DMD, Topper and Apron (instruction) screens?

Well, yes, and no! It's just more obvious now with the slower exit of VPX10.7. If i enable exit images (set as 5 secs) i then get 5 secs of black screen followed by 5secs of exit screen (basically just adds another 5secs before going back to the pinballx wheel) 09:57:29.03 30/01/2022: C:\Visual Pinball\VPinballX.exe -minimized /play -"C:\Visual Pinball\Tables\Attack from Mars (Bally 1995) MOD1.vpx" 09:57:29.05 30/01/2022: C:\PinballX32\vpauto.exe 09:57:56.32 30/01/2022: Found PinMAME ROM: afm_113 09:57:58.53 30/01/2022: Visual Pinball Player window foreground: 29 09:58:09.53 30/01/2022: Exit System Control Pressed 09:58:20.81 30/01/2022: Created DirectX BackGlass Window What i think should happen is the exit screen is shown immediately on 'Exit System Control Pressed', so in my example that would be shown for 5secs while VPX exits out rather than waiting for VPX to exit out showing a black screen and then the exit image being shown (which seems like a needless delay). It's probably always been like this, but like i say just more obvious now. Ideally, on 'Exit System Control Pressed' i'd like the wheel to appear immediately (with no exit image) and just let VPX close in the background, but i'd settle for the exit image being shown instead to cover the exit time if it's not possible to let VPX exit in the background. Hope that makes sense.. log.txt PinballX.ini

Hi Tom, VPX 10.7 process threads are a lot slower to close than in 10.6 on exit (in 10.6 the threads close almost instantly, in 10.7 on my desktop they take 5secs). This causes a longer black screen on table exit in PinballX than before, showing for the full 5 secs before the Exit Screen image (if enabled) is shown. I think this is because PinballX monitors the vpinballx.exe threads and waits for them to exit completely before doing anything else, as on my desktop where i have VP set up as an 'Other System' if i change the system type from visual pinball to custom the black screen time is a lot less (but i assume this comes at the cost of PinballX not retrieving high score data etc).. This time in the logs between Exit System Control Pressed and Created DirectX BackGlass Window, here for the other system using visual pinball as system type; 08:18:32.72 25/01/2022: C:\Visual Pinball\VPinballX.exe -minimized /play -"C:\Visual Pinball\Tables\Attack from Mars (Bally 1995) MOD1.vpx" 08:18:32.74 25/01/2022: C:\PinballX32\vpauto.exe 08:18:59.81 25/01/2022: Found PinMAME ROM: afm_113 08:19:01.94 25/01/2022: Visual Pinball Player window foreground: 29 08:19:10.08 25/01/2022: Exit System Control Pressed 08:19:15.86 25/01/2022: Created DirectX BackGlass Window and here using 'custom' as system type; 08:26:36.06 25/01/2022: C:\Visual Pinball\VPinballX.exe -minimized /play -"C:\Visual Pinball\Tables\Attack from Mars (Bally 1995) MOD1.vpx" 08:27:14.33 25/01/2022: Exit System Control Pressed 08:27:16.54 25/01/2022: Created DirectX BackGlass Window Is there anything you can do about the black screen time for VPX 10.7 exit from a PinballX point of view (e.g. showing exit screen as soon on Exit System Control Pressed event or if not enabled just show the playfield video straight away and then wait for the vpx threads to exit in the background)? Thanks for any help! log VP System.txt log Custom.txt PinballX.ini

Don't think i use PinballXStatus flag anywhere Mike. Maybe it's something to do with the 'online' initialisation status of PinballX for those two values, but that's just a guess. I'd be tempted to just change code to work for status 6 or 10 and see what happens!.

Think it's an FP thing. Maybe this workaround will work for you

A few quick answers; Normally you'd create another VP system (under Other Systems in settings). But if you don't think you'll have many VP9 tables in your final setup then you can use the 'alternateexe' flag in the xml to tell PinballX to override the normal executable used for a system, handy if you're dealing with a handful of tables. As you're starting out, setting up another system for either VP9 or VPX is probably easiest. For access to the FTP yes. But there is a vast amount of media freely available in the downloads section as well as in some media projects threads. You're talking about in game?. The options need changing in VP for that under the preferences menu 'Add missing tables' in settings (under general settings) should work to auto add them. Other stuff; Have a look at PinballX Database Manager as an alternative to Game Manager - i'm biased , but it has quite a few extra features (e.g. can auto add new tables and makes 'alternateexe' use a bit easier as well as lots of other stuff).

Loading media by table rather than in random needs the derandamomiser plugin (change the loading media mode in settings, copy the plugin dll file to the pinballx\plugins folder and and enable the plugin in plugin manager - see info on that page). Probably worth posting that in a new thread as a specific issue (don't forget to attach your log and ini files!) It's always worth recording your own playfield videos imo, that way the video you see will match the table/version you're using. Probably why you're not finding some on the FTP. I think there are some on a mega link somewhere though, might be a link buried in the database manager support thread (database manager can download media from mega links too once set up)

Enable Show System in Settings.exe (under general settings)? Agree with Mike though, once you start updating tables i suspect you'll have very few VP9 tables left enabled in PinbalX so might not be much of an issue when you get to that stage I did write up some stuff for setting up a vituapin controller a while back, but it's for V3 rather than V2 so not sure how much is relevant - https://forums.gameex.com/forums/topic/22391-virtuapin™-digital-plunger-kit-v3-nudge-and-tilt-setup-for-visual-pinball-10/

Gotcha.. that would be a problem with that solution (that i overlooked) Yep, the 'use playfield images' option working is internal to pinballx so would need Tom to look at for any possible improvement

Ok.. as you're using table images rather than videos i think using 'loading images' could work for you (if you have some spare disk space); Backup the contents of your media\loading images folder somewhere (can just be copied, no need to delete from the loading images folder) Copy table images from from the media\databasename\table images folder to the media\loading images folder Right click on the image files just copied in file explorer and select to rotate left (or right) twice (i'm going from memory that loading images need to be rotated 180deg from table images - but might be wrong). This will work for multiple image files if selected, so no need to do one at a time. In settings set to use 'loading folders' Copy the loading image derandomiser plugin to your plugins folder and enable it in pluginmanager Hopefully you should now have the table images used as loading images. Been a while since i've tested loading images with the plugin so sorry if here's any issues (or step 2 isn't needed)!. If they don't look any better then you can disable the plugin and remove the images in media\loading images and restore the files from backup, and change back to use playfield image in settings.

Not sure if you're using loading videos or letting pinballx take a screenshot and show that during table load. That setting is controlled in Settings.exe->General Settings->Table Loading Media mode, loading videos have generally a better result (for me anyway). Please attach your pinballx.ini and log.txt files!

Narrowed it down a bit more as it works ok on a test install to a clean directory. Turns out it's the usepinmame flag in the pinballx.ini file (?). Using this ini file with V5.33 32bit Game Manager crashes after a couple of seconds. Change the to UsePinMAME=False and Game Manager will work. PinballX.ini log.txt PinballX will launch ok whichever way the flag is set

Sorry, not tried using Game Manager in a while. Turns out i get the same issue if i try to open it with the 32bit version installed. I can open it ok using a 64bit install though. I'm guessing you're probably using a 32bit PinballX install? If so, try checking the 64 bit option during the install options to see if that fixes it.

I get the same with 5.32 (32 bit) Log and ini attached. log532.txtPinballX.ini (i'm upgrading hardware on the cab so they ini probably won't make much sense as it's from a test install on desktop) Error shown in log; 21:31:58.85 24/12/2021: Loading Game Statistics and Scores 21:31:58.91 24/12/2021: Loading Surfaces 21:31:58.92 24/12/2021: Error. Exiting 21:31:58.92 24/12/2021: 21:31:58.92 24/12/2021: Method not found: 'Void Direct2d.CFont..ctor(System.String, Direct2d.Device, System.Windows.Forms.Form, System.String, Single, Boolean, System.Drawing.FontStyle)'. 21:31:58.92 24/12/2021: at PinballX.FrmMain.am() 21:31:58.92 24/12/2021: 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) 21:31:58.92 24/12/2021: at PinballX.FrmMain..ctor() 21:31:58.92 24/12/2021: Disposing Plugins Last good version appears to be v5.28 Download that for now via the download page and click the See changleog at the bottom next to the What's New label, select 5.28 then download option from there EDIT - The X64 version of PinballX 5.32 appears to work ok (but i am using a different ini and media to test), so if you're on a 64bit windows version you could try selecting that in the install wizard options for 5.32 instead of rolling back to 5.28

@DBrown67 The backglass style wheel gifs i did will probably run a lot smoother than the apngs on your setup. An alternative animated wheel type with smaller files and less overhead (..though admittedly not much use if you like round wheel images)

I can't see the images either, but going by the description try adjusting this flag in settings; (think there's a tpyo in the description of that setting "Additional wait before showing desktop. Needed for bug tables on some systems", it's for big tables (slower to load on some systems) not bug tables ) That should add time before pinballx hides the loading screen. for the loading gif you could just create a small fully transparent image and then on ezgif.com make a one frame gif from it. That should work to hide it..

Can you attach these files?. Might be a clue in there..