DJO Maverick

Would it be possible with the plugin to use the loading gifs over table video, as opposed to only stills? And at the same time, to specify an alternate table video folder? Thought would be, to have the normal table video continue to play, just with a loading animation overlay, seamlessly going into the game. This could have two advantages to doing it through plugin instead of the load video creator: 1) The load creator (as far as I can tell) can't go up to 4k quality; this would prevent jarring quality change during loading 2) Space saving, as one could use one pool of 4k table videos

Alright, continuing to research this. So yeah, getting a better handle on the ini file structure, the line entries are in the order of your own personal ports (which is why your line doesn't work for me). RGB sets of ports are one entry. So key section for me would be here: ...and those are (should be) controlled by this part of the line, that's propagating correctly from DOF Tool: The first blink there is the fire button (working), followed by exit (not), how to play (not), start (not)... Finally figured out what's going on. It appears to be a DOF Configtool bug. For whatever reason, on only the pinballx line (when it appears to be working right for everything else?), it is making only one entry for the RGB Fire Button, causing everything else to shift up two entries. Those first two 'plain' ONs are going to the green and blue channels of the fire button, and the start button assignment is then seen as the exit... apparently. After a little bit of jiggery-pokery, adding in two more entries freehand into the line solves the issue, like so (with a little bit of experimental rainbow phasing on the fire button for good measure): Which in turn leads to: (blinking start and launch not apparent, but working) Good news is, I guess it really wasn't on PBX end! Obscure DOF Configtool bug, apparently? Bad news is, I need to save that line and updating table definitions is now less trivial, until I find who to report that to... Thanks!

That is how DOF Configtool is generating it, every time. I'd noticed the game names before and was curious, but assumed it was being generated by the site. Do you have RGB flipper buttons? I'm just guessing that line is auto-generated to give the different color buttons for different games (which is functional) by the command @allrgb@. Deleting that section or turning it to 0 breaks the DOF that was working for PBX. Using your line also breaks it entirely for mine (likely because of our differing output maps). And yes, I use Notepad ++ for this stuff. PS: Those lines you pictured are entirely blank for mine as well.

It has never created a GlobalConfig either, actually. Current setup guidance on that side makes it sound like those are only necessary for Teensy or SainSmart, so I'm guessing that's why it never generated them...? You're increasing my curiosity as to whether the plugin has some dependency on those older files for output mapping! Log attached, but it also seems regretfully unilluminating. log.txt

Thanks! I was torn on how to theme it (and whether to have a full DMD or not) when the Futurama table came out, and that decided both for me. 😁 As to observations as I go... First, I'm upgraded to the latest unified x64/x86 install so it's using unified INIs No GlobalConfig_PinballX.xml existed at all. I did paste in yours to see if it altered anything other than the log complaining that it didn't find one... it did not. Mine is actually directoutputconfig51.ini, but it is updating the PinballX appropriately, and it does track what it shows in Config Tool, as updated (where Start should be blinking with the default command, etc). I have it with the default fu/fd timings. My working configuration has apparently likewise never had a bespoke cabinet configuration file, which the log points out (no cabinet.xml or the like). It's never been part of the config generation package since I built my cab. From cruising older forum posts, I gather it used to be a thing, but seems like it may have been deprecated for newer builds, with the possible exception if you're using addressable LEDs...? (I'm not) Made me wonder if the plugin is somehow still dependent on a separate, manual cabinet config file even though the framework otherwise isn't anymore? Wouldn't know why, just a brainstorm. Notwithstanding all that, and it being generated from the Config Tool, it is showing a few errors that haven't manifested as problems with any actual tables. This made me try parsing the config file LedControlFileTester and it is reporting the same errors... though I'm unclear on where the numbers are coming from (Line 301? Input 301? Error Code 301?) to try to follow back. Is it even referring to a global configuration error, or specific table configurations? No clue- I take that back, as I keep looking as I go, that whole section of errors is because whoever did the fouraces config has a raft of errors in that table. Managed to accidentally debug somebody's table config for a table I don't have and submit a fix, huzzah. Did something productive here! After fixing that, my log is utterly uneventful. Which is a stream-of-consciousness way of saying, I've got nothing, ha. My config package always includes only diredoutputconfig51, directoutputshapes (png and xml), and tablemappings.xml. directoutputconfig51.ini DirectOutput.log There's my current config and latest log from just turning on PBX and turning it off (deleted the globalconfig back out for that test). Maybe you'll catch something glaring I'm missing.

A delayed response for you sir... haven't had the time to go collate screen shots for you. Port mappings... Relevant table mappings (not much has been changed here)... Reality on the ground in PBX. Not obvious since it's a still, but the exit button is blinking, as opposed to just being lit. Start, How to Play, Launch, not responding to the mapping at all. RGB fire button does, flashers do, RGB flippers do... just the front buttons that don't, and it's only in PBX. I don't feel like taking a ton of extra screen shots right this second, so please take my word for it that they are all mapped to the correct ports (I know this because they work in real tables as intended, and as a sanity check, I retested those outputs in the Pinscape tool before drafting this post). And just in case there's something obscure in PBX config to blame, here's the ini... PinballX.ini Thoughts?

Was just referring to everything on face of cab (start, info, exit, launch). I follow that the behavior of the lamps is configured through the pinballx 'table' in DOF Config. That's what I was referring to editing. My question is how PBX is reporting the IDENTITY of buttons; I'm asking what is determining which button IS the Start or Exit (etc) button for PBX. In real tables that is assigned in the individual table scripts, but obviously that doesn't exist in that form here. To restate the example: the DOF Config Tool currently has Start set as a blinking light, and Exit as merely illuminated. In reality, Start is completely off and Exit is blinking. Basically, whatever layer is communicating to DOF which button is which (in PBX), is not accurate for some button lamps. I don't know if the plugin is supposed to be reading from the current key map (which makes sense), or if it is buried in a text file somewhere, or if it is hardcoded and ignores remaps... Etc. Does that make more sense?

So this was indirectly raised in another thread back in 2021 by someone else (re: strobes) and never seems to have been resolved... Where are DOF buttons identified/assigned in PBX? Using current PBX, DOF, and plugin. DOF works as intended in games, and the plugin is functional in PBX. Many things work fine in PBX, such as flipper SOLs, light bar, flipper buttons, and RGB fire button. However, face buttons are all being misidentified. Instead of a pulsing start button, I have a pulsing exit button, for example. Attempting to fix them in DOF Config doesn't work as intended. The Start button is assigned to blink, for example (not exit), however it stays dark. Same for info and launch buttons, setting them on has no effect. The key map for PBX appears to not jive with DOF Config's IDs/key map. So while I suspect I could just turn on random DOF devices one at a time in config until I figure out what output device PBX is treating these button lamps as... I thought maybe I should ask if there's some user-facing way to figure that out or remap them in PBX? Thanks-

I have not seen it happen yet in RC5, knock on wood.

Been a minute (was out of town), but here's a fresh example from first day back, this time with Chrono Trigger. This is a slight variation on the theme though, that I've seen a few times with FS Windowed; here PBX crashed while loading the table in the first place, and without ever bringing the player window into focus (VPX and everything launched, B2S and Freezy were up, but black window and doom-loop cursor of frozen PBX remained over the player window until I tabbed to it). PBX had to be alt-F4'd. log.txt PinballX.ini

I can create new ones next time it happens but I can tell you off the cuff when I glanced at it last time that the log ended in the same fashion. TZ is just the first one it's happened on since last post, though it always happened more frequently on newer VPW releases and the latest TAF (though it could happen on anything).

Update: Well, had a good run (inexplicably, apparently), but it cropped up again on Twilight Zone even in full screen windowed. So, that does not appear to be the solution. Whether it had some mitigating effect at least or I just had a run of good luck would take some more empirical testing...

Killed full screen exclusive on the VPX side; so far, so good. Will keep you posted if something changes. Thanks-

1. 3 screen cab w/ DOF 2. DMDExt and PUP Player (but not a PUP table in question) 3. VPX 10.8 RC4, all versions 4. Seemingly all tables at random, though seems more frequent on latest G5K Addams Family and VPW Twilight Zone (which could be just more frequent play) 5. Yes 6. See 3 I've seen a lot of older threads about what seems to be the same issue, and maybe I've missed the solution somewhere. I've got an ongoing problem that strikes seemingly at random, where PBX refuses to acknowledge a quit emulator command. I've got VPX menu bound purely to escape (which isn't mapped to an accessible cab button), and PBX quit emulator bound to Q, an exit button on the front of the cab, to ensure they no longer conflict... and sometimes it works, and sometimes it just... doesn't. When it doesn't, plugging in a keyboard and alt-tabbing to PBX, Windows indicates it has stopped responding. It never recovers and has to be force-closed. As far as I can tell, there's absolutely nothing in the log either, other than launching the last table. I did notice that some threads suggesting ensuring that VPX was running full-screen exclusive, which mine is. Thanks, log.txt PinballX.ini Visual Pinball.xml

Ok, video, as promised. Side note: it does continue to load right once in a great while. If it does at all, it will be the first attempt on a boot, then not again. Edit: Clarifying, it doesn't stay on the black mini HUD forever... I stopped the video before it rolled into high score display.

You have deepened the mystery, Good Sir. So I changed the table mode to 2 Screen (like your experiment). When set to 2 screen mode, PBX consistently launches it correctly. Launched repeatedly with no issues. Swapped back to 3-screen mode, and the issue remains. So to recap... I guess the table only has an issue launching from PBX, but ONLY in 3-screen mode, and then only with 10.8.

So I'm on the same versions of pup/vpinmame/b2s as you, but the major difference between our setups is that my table is set up to run in the 3 screen fullDMD mode. With that, the back glass remains just the back glass, and all the pup videos run on the third screen. They also all have overlay frames based on what's showing (ex: the credits appear as though on an old TV). I should be able to check at lunch if PBX launches it right for me in 2-screen mode like yours to try and isolate the issue.

I sure don't know the code either, but I was under the impression that the B2S server is still serving as an interpreter for both DOF and Pup, even without an actual B2S backglass, and that's why both require the server to be installed and running? No, that's not what is happening. The issue is the attract mode video (credits.mp4, I believe) does NOT play at all. It APPEARS that it might be trying to start at the right time for a split second (there's a bit of a momentary visual hitch on the DMD when it should start), but immediately stops and goes on to what would otherwise happen next (display of high scores). I would say there is a little bit of inconsistency with it. I'd say 1 time out of 20 tries, the audio DID play, but even then, the video was not visibly playing in any window that could be tabbed to. The other 19 times out of 20, there's no audio or anything other than the momentary glitch. There is no standalone B2S file in play; it's a 100% pup table and the backglass is coming from pup. Thus, nothing to rename. B2S is being called by the table script. Yep, LAV codecs installed and configured. Unless there's been some substantial update to that in the past year or so that would need reinstalled.

I think I was inarticulately wondering out loud if there was some sort of race condition that the existence of the pop up delay was defeating. But, the workaround does work; saving it in the old version and then forcing PBX to launch it with 7.4 still works, repeatably. It's just not desirable to have to leave the benefits of 10.8 on the table and roll back just for the frontend, when 10.8 otherwise works fine... Gave this a shot; no change in behavior. Opening video still refuses to play. Clearly this is some very edge case. Possible never reported before by people who have only ever launched it with PBX, because they wouldn't realize the one misbehavior. Just brainstorming, but is it possible that PBX's video player is not shutting down fast enough and 10.8 is causes B2S and the Pup plugin to load just incrementally faster, enough to conflict? Granted I don't use a lot of PUP tables, only ones that need it (Futurama, Blood Machines, Die Hard, Munsters, Harry Potter, think that's it)... but interesting that it seems to only affect this one. I don't understand PUP scripting well enough to recognize if there's some material difference in how the Batman credits video is called.

Confirmed no compatibility options are on. Will figure out how to capture DMD only; maybe can abuse Database Manager to accomplish it, if recording will start fast enough. One new experiment of note: went ahead and reacquired 7.4. When set to launch 7.4 64bit, PBX loading screen would give way to the error message complaining that the table was saved in 10.8. After clicking to launch anyway, PUP intro DID work normally, three times in a row. Obviously not desirable to roll back just for PBX purposes when it otherwise works fine in 10.8, but, there you go. It at least made me wonder if launching from PBX is in some way affecting the speed or order of add-ons like the pup player loading... and maybe the mere fact of VPX pausing for the nag confirmation was what made the difference?

PS - Now have also tried running through PBX with alternate exes... tried all editions of 10.8 with PBX, same result. Can reacquire a 7.4 later to try with it as necessary.

Update from retesting now... So for starters, PBX still demonstrating the same issue. I went back and started testing different exes at command line... With same command as yesterday, 32 bit GL worked... all 3 other flavors of 10.8 exe worked... and then retried 64 bit GL, and today IT worked, repeatably, from command line. Went back and retested same exe from PBX, and the glitch remained, every time. After that, went and tried command line 64 GL again to see if PBX was doing something that lingered and caused an issue... however, launched repeatedly from command line without issue today. No clue why command line launch caused issue last night but not today. At this point, command line launch is fine, PBX launch continues to have the same issue every time. As for what is different with Popper... I barely have it installed just to test it and haven't altered any of the default launch parameters, it's also set to use GL 64 version. So, whatever its default arguments are.

Eliminated the path for the executable in PBX settings; no change. And in a very interesting turn of events... running from the command line as requested gives the exact same problem as launching from PBX. I closed that instance, then relaunched VPX and selected the table from the menu to launch it... and it worked fine.

Give a brief description of you sytem setup (2/3 screen setup, feedback, addressable leds) 3 screen cabinet with FullDMD and standard suite of DOF devices Are you using any 3rd party add-ons (dmdext, doflinx, PUplayer) Freezy external DMD extensions, PUPlayer for tables that require it (like this one) Define which emulator you are having issues with (VPX, Future Pinball, FX3) VPX 10.8 RC4 Is the issue table specific or an issue for all tables? If so please state the table name. Unique to Batman '66 Does this issue occur only when launching the game via PBX? Only via PBX, no issues when launching directly from VPX or competing frontend What Version of PBX are you on? Current (6.07) Attach your Pinball X xml, ini, and log files, DO NOT COPY THE CONTENTS INTO YOUR QUESTION, attach the actual files. Attached. When launching Batman '66, it is supposed to trigger the credits.mp4 video for attract mode, with the theme song and such. When launching it via PBX, it acts like it is trying to start that video for a split second, then it disappears and goes back to the rest of the otherwise expected DMD activity. There do not appear to be any other issues with the pup videos and PBX; it appears to otherwise work normally, except for that initial video. This does not occur when launching from VPX directly, or Popper. This was not always an issue (as evidenced by me having successfully recorded a DMD video of it for PBX in the past), but I cannot seem to find a rollback that eliminates the issue. log.txt PinballX.ini