BrandonLaw

Am I to understand using Animated backglasses past PBX is working in FX3? Someone share their .ini so I can see what's up. I'd like to have blinkies when I tapping some FX3 ballies.

Can we edit the brightness of the b2s backglass preview that PBX is pulling from VP/Tables? I have a couple that are pretty dim. It's an OCD thing, but I assume I'm in good company for that

A member...

SO! I have the answer. I've been battling it for a while prior to that and want to share my findings. You CANNOT call Steam.exe as it's ALREADY RUNNING. If it doesn't quit, how can it ever 'start' to initiate the call So...you have to call your Pinball FX3.exe! Just change Steam.exe to the Pinball FX3.exe and of course it's relative path. Also, don't forget to delete the app id from the parameters and you're golden. Now you have a program that starts...and stops...and calls...and quits. Boom!

YEP! DLL's call .ini's. Worked like a charm. Here's the .ini. Change the port as needed. pinDMD.ini

Something interesting as I've seen there is debate on what uses what .dll. I see here that PINDMD created a log this morning, meaning it was trying to use that particular .dll. Maybe if I place an .ini into the dir stating 'com3' I might get somewhere? Just seems it can't find it.

It's about to do the same here today. Also, PBX doesn't mirror anything, correct? So DMDEXT wouldn't be a part of this equation unless I've missed something...probably have:)

Yessir!

Hey All! New DMD arrived Thursday. All is well with the games, but dag if I can't get PBX to see it. Doesn't even try according to the log. Someone want to point me in the right direction? It's a PinDMDv3 and I haven't moved any .dll's around or anything as I've read it should naively work. I've tried every monitor in the .ini and I can see the virtual DMD show up, but nothing ever populates on the actual dmd. I might state that i'm using win10 and it's recognized as a serial/com device. Log and Ini attached. log.txt PinballX.ini

Thumbs up, brother! That would be great as I am comfortable doing either. Did you just go the 'Ctrl+C' route as a 'run after' bat? Let's sort this out as it's driving me nutty. It's funny as GitHub I believe states that the software updates to the FX series could break it at any time....looks like that time is now.

Here's the deal. I have the DMD bat file firing up with PFX3 no problem. Frames are grabbed...I beat the ball around a little and figure it's time to hit another table. Esc out to front-end and choose another table. NADA. What is happening is it seems the --quit-when-done parameter for the command line isn't recognized. I assume when that parameter is recognized, the window shuts down? As in goes away? Basically, I need it to shut down to begin the process again and take advantage of the 'start before' feature of PBX. Might be a CMD thing I'm missing? I can hit ctrl+c or of course close the window, but that does me no good for automation. To clarify, this isn't a PBX issue, just a feeler for why the parameter may not be working correctly.

Didn't see y'all respond so thanks!@ I can get it to 'launch,' but it seems as if the commanding only sees for 1 monitor and slams the backglass to the playfield and stretches it to hell. I think it may only be a couple of command lines away from being at least launchable with success.

Every once in a while we find something that was like "wow, why did I struggle so much" and this is one of those times, so I thought I'd share. If you're unaware, VPx has split sounds that require 2 sound cards. Mechanical sounds from inside the machine (bumpers, lifts, servos, and really just a lot of clanking and banging that adds to the realism by 100%) and game sounds for the backglass speakers. I have my on-board sound card for the backglass stuff and just picked up this bad boy as I've struggled for a while now trying to get it to work. Windows 10 haaaaaaaaaaaaaaaaaaaaaaaaaaaaaaates old sound cards. This puppy was at Bitch-buy and pricematched for 13 bucks!! Do yourself a favor. Hook it up, go into your sound control panel and revert your on-board sound back to default, fire up VP, go to Preferences/Audio and get those sounds. I'm not even sure I would hear them without doing this. The mechanical sounds are fantastic and wildly add to the overall experience. The USB SOUND CARD mentioned.

Thanks!!

VirtuaPin bros? Also, you have quite the list!! You know what they say: “90% of the time customizing and 10% playing.”

Yep! The MAME cab was built by me and houses a core i7/1050ti4gb system with around 130 emulators including daily up-to-date tittles such as injustice 2 being the newest, but I try to stay current especially with fighters. Front end is Hyperspin (sorry! Lol) (And before anyone asks those silver things are fold out cup holders for boats.) PInCab is fresh new Widebody from VirtuaPin. With 2 new kiddos and how in depth these can get I wanted a pro to do it right. Paul has been a delight to work with and the cab is just premium in every way. I opted to source the components myself and went with a Ryzen5/gtx970 system running PBX of course. VPx, Arcooda, Zaccaria, and FX3 run on her. Massive overkill but my cabs will run forever. Any other questions feel free to ask away. Edit: You asked of the rig too. 7700k @ a safe and cool 4600mhz with 1080tiROG/OC GPU. Edit#2: Tittles was accidentally said. Tittles was left in place for obvious reasons.

My DMD is being repaired....so don't mind that lil' guy.

Starting super fresh and clean here with the spanking new pincab. Did we figure out how to successfully at least launch Arcooda from within PBX? I understand launching specific tables isn't a thing as of current release, but just to simply get into the software without exiting PBX and somewhat a clean and easier setup to do so? TIA, Gents!

I have also run into this. You may want to post your .ini and log as I'm sure you'll be asked to do so:)

That was just for testing to show myself what was happening. Notice the backglass jammed up in the corner. Not sure what about the 64bit ver. was keeping it from working correctly...maybe directX related. 32bit is working fine:)

Thanks for that Draco! Gave me some insight as to what 'could' have been going on, but being one step away from re-installing windows, I uninstalled PBX for the third time and decided to try forcing 32bit mode. Fixed. Ugh.

Morning! Odd quandry.... I was playing with my 'make this my main display' in windows and all of a sudden my backglass is stuck being tiny and at 0px of the main display. It's like PBX doesn't recognize a 2nd display at all now. I've tried removing the display cables to reassert that the display is there. I've tried totally deleting the pinballX.ini, editing it of course to no avail. If I put coordinates and sizing into the backglass, nothing is recognized. Backglass just doesn't seem to be an option for PBX now. Totally strange. Any assistance would be much appreciated! PinballX.ini and log attached along with screenshot of backglass issue. (Keep in mind all the options showing are from testing.) PinballX.ini log.txt

Good output, sir. Looking forward to it!

Same. Download happened, but .exe didn't make it and validating doesn't recognize it as a missing file. Guess we are back to waiting. Quick edit: Uninstalled/Reinstalled to save y'all some time trying. No dice.

Samesies. Even re-verified steam files..jusssssst to be sure Farsight wasn't going to maybe overpromise? Bah. Such is life.