1630 replies to this topic

[freneticamnesic]

 

Any help setting up a game controller (xbox) for use in pinbally?

 

I made a video at youtube exactly with that. The only think... it is in spanish. But i think you can have a good idea seeing the video. Only one thing: as they say, don't download the v4 of x360ce, but the v3. 

 

Here is the video!

 

https://youtu.be/RTvlBtgtGtk

 

 

Thank you for this!

[Vercingetorix]

I'm thinking about starting a project where I go through my whole cabinet and capture all the tables' attract mode videos to cycle through on my DMD while PinballY is itself in attract mode. Obviously this would be a massively time-consuming ordeal so I want to think it all the way through before starting. 

 

I'm leaning towards switching PinballY's DMD screen from a 4:1 strip to the full 16:9 display before capturing the videos to accommodate tables that need more room (B2S 3rd screen DMDs that need to be "taller" than that, PUP-based tables, etc.). The only problem with that is that if the DMD is full-screen, then all the "DMD style" text in PinballY's integrated high score feature is stretched vertically. Alphanumeric style is unaffected, surprisingly, and I can always just use that for high scores on all tables, but switching text styles based on table eras is a clever idea and I'd rather keep that if possible. 

 

So, two questions for anyone who might have gotten down into the weeds on this before: 1) is there anywhere to mess around in settings.txt or the scripts to make the DMD-style high score text display "normally" in a non-4:1 window? And if not, then 2) is there anywhere I can just globally change the default style to alphanumeric so I don't have to go into every table individually and change it? 

 

Thanks! My apologies if it's already been covered somewhere in this thread and I somehow missed it. 

[Thalamus]

@vercingetorix : What you are looking for should be possible to do with Freezy. I advice you to read up on Flexdmd too.

[mjr]

Vercingetorix - there's not an option for that currently, but that should be easy to add, and seems like something at least a few people would find useful.  I'll see what I can do.

[Vercingetorix]

Vercingetorix - there's not an option for that currently, but that should be easy to add, and seems like something at least a few people would find useful.  I'll see what I can do.

 

Hey, thanks for considering it! I don't know how popular something like that would be -- admittedly, capturing and editing a whole cab's worth of attract videos will likely be very time-consuming. But I built a bar in my garage during quarantine and I'm thinking about moving the cab out there in the hope that it more people besides me and my kids will play on it, so enhancing the attract mode with some nice shiny videos seems like the thing to do. In the interim I'll just switch every table to alphanumeric style for high scores. Thanks again! 

[mjr]

1.1 Beta 5 is now available.  The main new feature is actually just a restoration of an old feature - SWF instruction cards should display again.  I don't know if anyone noticed, but Adobe killed Flash Player at the beginning of the year via a pushed update, so up-to-date systems have been unable to display SWF for a while now.  Beta 5 has an internal SWF renderer (no plug-ins required) that can display simple SWF files (no scripting, no video) without any external software, so your existing collection of instruction cards should work again and continue to work in the future.  Beta 4 also added support for Animated PNG (APNG), so that's available as well now.

[Vercingetorix]

Ok, I've found an odd single-table behavior in the betas that might be worth reporting. My daughter is a big fan of the Future Pinball table Jungle Girl (https://pinballnirva...fpx-v1-1.20242/), and that table (and only that table as far as I can tell) crashes when we launch it with any version of PinballY later than 1.1 Beta 1. 

 

Some specifics: 

 

1. I swapped around all the various PinballY.exes from 1.0 to the current 1.1b5. 1.0 and 1.1b1 both launch the table fine; once I swap in the beta 2 exe or anything later then the table crashes on launch. 

 

2. By "the table crashes," I mean that Future Pinball launches and begins to open up the correct table. Then there's kind of a "bleep-bloop" sound problem, the screen goes black, and it goes back to PinballY. 

 

3. If I look in the log file, then it appears PinballY is satisfied with the way the table launched and shut down. If I copy and paste the various launch parameters it used into the command line, I can launch the table fine that way. Whatever happens happens only from within the front end. 

 

4. I tried a couple of other FP tables and they all worked fine, although admittedly I don't use FP very often other than when my daughter wants to play this one table. 

 

5. I am using the current version of FP/BAM. 

 

Obviously one Future Pinball table is not a big deal! But I thought it might be worth reporting anyway, and obviously I'd be happy to provide any more information if you're interested. Cheers! 

Edited by Vercingetorix, 21 May 2021 - 05:20 PM.

[wiesshund]

I think beep bloop is your video driver crashing and restarting
or at least sounds like it, but i do not know why.

Especially since you can run it outside the front end.

[Vercingetorix]

Yes, very odd that I can launch it fine from a command line with the same parameters that the front end is passing to it, but if it has to make that transition with PinballY already running then it fails. I tried deleting the table's playfield & backglass videos so there would be none of that running as the table launched and that made no difference.

 

Video card is a 1660 Ti with recently updated reference drivers from NVIDIA, btw, so about as generic as it gets. 

[BPICKINPAUGH]

Just upgraded from a old version 1.0.0 Beta 21 to the current 1.1.0 Beta5 and it seems the high scores are not getting fuzzy matched through PINemHi for some what appears to be random tables, just wondering if anyone else is seeing this?  I did check the pinemhi.ini file and verified the rom names are still in there.

 

This is one that didn't work

 

NVRAM file search: determining NVRAM path for AC;DC (Pro Vault Edition)

+ Game is VP/VPX

+ No explicit NVRAM setting in game; using VPinMAME NVRAM path = D:\Visual Pinball\VPinMame\nvram

+ Still no match; trying a fuzzy match on the friendly ROM names

High score retrieval: looking for ad hoc scores file D:\Visual Pinball\Tables\ACDC (Stern 2012).pinballyHighScores

+ ad hoc scores file D:\Visual Pinball\Tables\ACDC (Stern 2012).pinballyHighScores doesn't exist

+ No high score source found for AC;DC (Pro Vault Edition)

 

This one worked

 

NVRAM file search: determining NVRAM path for World Poker Tour™

+ Game is VP/VPX

+ No explicit NVRAM setting in game; using VPinMAME NVRAM path = D:\Visual Pinball\VPinMame\nvram

+ Still no match; trying a fuzzy match on the friendly ROM names

++ Found a fuzzy match: wpt_140a.nv

++ Found exactly one match - using it (wpt_140a.nv)

+ NVRAM file wpt_140a.nv exists

Searching for Visual Pinball X in D:\PinballY\Media\System Underlays.*

Searching for Visual Pinball X in D:\PinballY\Assets\System Underlays.*

Searching for underlay in D:\PinballY\Media\Images.*

 

 

After some more testing is appears the tables that are not working only have [default] in the rom-name dropdown of the Game Details and the ones that work have [default - wpt_140a] for example.

Edited by BPICKINPAUGH, 28 May 2021 - 05:38 PM.

[topper2k]

Hey all! For those running FX3 in PinballY, today I noticed I can no longer launch FX3 tables from PBY.

 

 

When I try to launch a FX3 table from PBY, it launches FX3, but not the table. I'm taken to the main "Press A to continue" screen which then takes me to the main menu in FX3.

 

I've triple checked my launch params (-applaunch 442120 "-table_[TABLEFILEBASE]") and FX3 system settings per the PBY guide (http://mjrnet.org/.....temOptions.html).

 

I'm running the 1.1.0 Beta, but also still have an older version of PBY installed on my C drive. That older version has the same problem, but didn't when I was actively using it.

 

This all leads me to believe the issue is in Steam or FX3 somewhere, not PBY, but I can't for the life of me figure out what it is.

 

Any ideas what could cause this?

 

UPDATE: Solved. FX3 had somehow forgotten my cabinet code.

Edited by topper2k, 30 May 2021 - 04:25 PM.

[Csilk]

just FYI for everyone having video crashes and stuff perhaps you should go to Audio/Video and tick the box to lock frame rate to monitor refresh rate.

 

I was sitting here last night when I felt warmth on my leg upon investigation PinballY was running at 5802 fps and had the gpu pinned at full throttle 95 degree celcius, which can either kill a gpu that has bad cooling quicker over time or outright crash a sensitive system, I don't think I need the menu running with an image of a game going 5802 fps. I'm running PinballY on my Ryzen 3800X and Radeon 5700XT 8GB, not a cabinet.

[gunsofbrages]

Hi there!

 

I have been running PinballY for over 6 months without any problems. Yesterday I installed DOF to use a flasher board, using the automatic DOF setup. DOF works perfectly well with my PBY frontend (flashers go off when I switch tables), but whenever I try to launch a table, it immediately shuts down as soon as it finished loading. Here is what  the logfile says:

 

Table launch: Jokerz!, table file JP's Jokerz! v3.0, system Visual Pinball X

DOF: shutting down DOF client
+ launch: full table path C:\Visual Pinball\Tables\vpx-tables\JP's Jokerz! v3.0
+ table launch: table file C:\Visual Pinball\Tables\vpx-tables\JP's Jokerz! v3.0 doesn't exist; try adding extension -> C:\Visual Pinball\Tables\vpx-tables\JP's Jokerz! v3.0.vpx
+ table launch: file + extension (C:\Visual Pinball\Tables\vpx-tables\JP's Jokerz! v3.0.vpx) exists, using it
+ table launch: executable: C:\Visual Pinball\VPinballX.exe
+ table launch: applying command line variable substitutions:
+ Original> /minimized /play -"[TABLEPATH]\[TABLEFILE]"
+ Final   > /minimized /play -"C:\Visual Pinball\Tables\vpx-tables\JP's Jokerz! v3.0.vpx"

+ table launch: process launch succeeded
+ table launch: Close Game command received
+ table launch: trying to close the game process
+ table launch: game exited normally
+ table launch finished successfully

 

Can it be that DOF gives the Close Game command somehow?

[Thalamus]

I thought that DOF was called via the backglass ? Is backglass enabled ? Fairly recent updated dofconfig from configtool ? I should probably not answer this since my DOF has been dead in over a year now

Edited by Thalamus, 03 June 2021 - 10:22 AM.

[gunsofbrages]

Thank you Thalamus, I guess you are right about the backglass and DOF, I have my backglass enabled and the dofconfig was made at the same time I installed DOF, so I assume everything is fresh and updated. It seems as if when you start toying about with DOF, that's when the problems enter.   Until now, I've had a smooth ride ever since I built my cab last October.

[Outhere]

Run game without front end
Post DirectOutput.log

[gunsofbrages]

---------------------------------------------------------------------------------
DirectOutput Version 3.1.7776.42172, built 2021.04.16 23:25
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2021.06.03 13:20:05.307    DirectOutput Logger initialized
2021.06.03 13:20:05.257    Global config filename is "E:\DirectOutput\config\GlobalConfig_PinballY.xml"
2021.06.03 13:20:05.276    Global config file "E:\DirectOutput\config\GlobalConfig_PinballY.xml" does not exist; no global config loaded
2021.06.03 13:20:05.276    No global config file loaded
2021.06.03 13:20:05.307    Could not find or load the global config file E:\DirectOutput\config\GlobalConfig_PinballY.xml
2021.06.03 13:20:05.308    Loading Pinball parts
2021.06.03 13:20:05.308    Loading cabinet
2021.06.03 13:20:05.309    No cabinet config file loaded. Will use AutoConfig.
2021.06.03 13:20:05.315    Cabinet auto configuration started
2021.06.03 13:20:05.602    Detected and added Pinscape Controller Nr. 1 with name Pinscape Controller 01
2021.06.03 13:20:05.603    Added LedwizEquivalent Nr. 51 with name Pinscape Controller 01 Equivalent for Pinscape Controller Nr. 1, 36
2021.06.03 13:20:05.610    PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2021.06.03 13:20:05.619    LedWiz-like device at VID=64250, PID=247, product string=Pinscape Controller, manufacturer string=mjrnet
2021.06.03 13:20:05.620    HID caps: usage page=1, usage=4, number of link collection nodes=1, output report byte length=9
2021.06.03 13:20:05.624    LedWiz-like device at VID=1452, PID=524, product string=Apple Extended USB Keyboard, manufacturer string=Mitsumi Electric
2021.06.03 13:20:05.634    LedWiz-like device at VID=1452, PID=524, product string=Apple Extended USB Keyboard, manufacturer string=Mitsumi Electric
2021.06.03 13:20:05.650    Opening 32-bit LedWiz driver...
2021.06.03 13:20:05.681    Detected and added LedWiz Nr. 8 with name LedWiz 08
2021.06.03 13:20:05.682    Added LedwizEquivalent Nr. 8 with name LedWiz 08 Equivalent for Ledwiz Nr. 8
2021.06.03 13:20:05.686    Cabinet auto configuration finished
2021.06.03 13:20:05.686    Cabinet loaded
2021.06.03 13:20:05.686    Loading table config
2021.06.03 13:20:05.687    No TableFilename specified, will use empty tableconfig
2021.06.03 13:20:05.687    Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName PinballY
2021.06.03 13:20:05.702    Loading LedControl file E:\DirectOutput\directoutputconfig51.ini
2021.06.03 13:20:05.724    Min DOF Version is 0.8 for file directoutputconfig51.ini
2021.06.03 13:20:05.724    Resolving Tables Variables
2021.06.03 13:20:05.728    Resolving Global Variables
2021.06.03 13:20:06.218    1 directoutputconfig.ini or ledcontrol.ini files loaded.
2021.06.03 13:20:06.219    Config for RomName PinballY exists in LedControl data. Updating cabinet and config.
2021.06.03 13:20:06.265    Table config loading finished: romname=PinballY, tablename=PinballY
2021.06.03 13:20:06.266    Pinball parts loaded
2021.06.03 13:20:06.266    Starting processes
2021.06.03 13:20:06.267    Initializing cabinet
2021.06.03 13:20:06.267    Debug: Initializing output controllers
2021.06.03 13:20:06.269    Pinscape Pinscape Controller 01 intialized and updater thread started.
2021.06.03 13:20:06.269    Debug: Initializing LedWiz Nr. 08
2021.06.03 13:20:06.270    Pinscape Pinscape Controller 01 updater thread  started.
2021.06.03 13:20:06.270    Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2021.06.03 13:20:06.271    LedWiz Nr. 08 initialized and updater thread initialized.
2021.06.03 13:20:06.271    Debug: Output controllers initialized
2021.06.03 13:20:06.271    Updater thread for LedWiz 08 started.
2021.06.03 13:20:06.277    Cabinet initialized
2021.06.03 13:20:06.283    Loading shape definition file: E:\DirectOutput\DirectOutputShapes.xml
2021.06.03 13:20:06.660    Framework initialized.
2021.06.03 13:20:06.660    Have fun!
2021.06.03 13:20:17.782    Finishing framework
2021.06.03 13:20:17.784    Finishing cabinet
2021.06.03 13:20:17.785    Debug: Finishing output controllers
2021.06.03 13:20:17.789    Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2021.06.03 13:20:17.789    Pinscape Pinscape Controller 01 finished and updater thread stopped.
2021.06.03 13:20:17.789    Debug: Finishing LedWiz Nr. 08
2021.06.03 13:20:17.790    Updater thread for LedWiz 08 terminated.
2021.06.03 13:20:17.802    LedWiz Nr. 08 finished and updater thread stopped.
2021.06.03 13:20:17.802    Debug: Output controllers finished
2021.06.03 13:20:17.803    Cabinet finished
2021.06.03 13:20:17.803    DirectOutput framework finished.
2021.06.03 13:20:17.803    Bye and thanks for using!

[mjr]

I have been running PinballY for over 6 months without any problems. Yesterday I installed DOF to use a flasher board, using the automatic DOF setup. DOF works perfectly well with my PBY frontend (flashers go off when I switch tables), but whenever I try to launch a table, it immediately shuts down as soon as it finished loading. Here is what  the logfile says:

 

DOF is actually *supposed* to shut down on the PinballY side when you launch a table.  DOF doesn't deal well with multiple processes trying to access it, so when PinballY launches a game, it has to disconnect itself from DOF so that VP can take over instead.  So let's make sure we're talking about the same thing here.  If I'm reading this correctly, what you're posting here is the PinballY log file, which is saying, essentially, "okay, I'm launching this game now... the game has started... I'm going to disconnect from DOF so that the game can use DOF."  Am I parsing that correctly?  If so, that's all perfectly normal and exactly what should be happening.  So, my next question is: apart from these messages in the log file, is there something else going wrong?

[gunsofbrages]

Thank you, I see now that what I wrote in my post was ambiguous: What I mean is that the table will not launch. I chose "Play" in the menu,  the table starts loading, and then, just when it is about to start, it immediately goes to "exiting game" and back to PBY. I don't know if it has anything at all to do with DOF, but the issue began after I installed DOF.

[mjr]

What I mean is that the table will not launch. I chose "Play" in the menu,  the table starts loading, and then, just when it is about to start, it immediately goes to "exiting game" and back to PBY. I don't know if it has anything at all to do with DOF, but the issue began after I installed DOF.

 

I can't think of any reason it would be related to DOF, but maybe there's some weird interaction that's not coming to mind.  I notice this in the log listing you posted earlier:

 

+ table launch: Close Game command received

 

So it looks like you're explicitly exiting the game on the PinballY side.  There are three ways a Close Game command can happen:

 

1. You pressed the Exit button.

2. The game inactivity timer expired

3. Javascript generated it

 

I'm assuming you didn't manually press the Exit button, so let's rule out #1, but you might want to think it over briefly to make sure you didn't do something ELSE when you were setting up DOF that might be generating the button press - AHK scripts or something like that, say?  Anything at all that could be synthesizing a key press of any kind?  You'd be surprised at how many times people say "this started happening when I installed DOF", and it turned out they actually installed seven other pieces of software and did a bunch of other system reconfiguration at the same time they installed DOF, so they end up chasing DOF red herrings for quite a while before figuring it out.

 

If you're using any Javascript add-ins, try disabling those and see if it still happens.

 

Assuming you've ruled out the Exit button and you've ruled out Javascript, that leaves the inactivity timer.  That's in the options dialog under Game Launch.  Check that to make sure you don't didn't accidentally set it to 10 seconds at some point or something like that.

Edited by mjr, 03 June 2021 - 11:51 PM.