1630 replies to this topic

[mjr]

Sorry if I was misleading, I mean in the FILENAME not the table name.

 

I'll give you a screen shot later this weekend if you still need it.

 

I definitely have table names with apostrophes, too - those shouldn't cause any problems. 

 

Let's see what the Windows error says.  That might have the explanation. 

 

The other thing you should do is turn on Table Launch logging in the options (Logging section) before running the test, then exit the program and look at the log file.  That will include the full Windows command line being generated for the launch.  Read the command line carefully and see if you can spot any syntax problems that would cause errors if you typed them into a DOS box.   It might just be some simple problem with your VP option settings (in the Systems > Visual Pinball section in the options) that you can fix by adjusting the way you're constructing the command parameters.

[BoltBait]

OK, not sure what the original error message was, but today I changed the name back to having ' in the name and it launched without problem.

 

False alarm, I guess.

[rlewis19]

I have DOF active for PinballY but don't know what it does.  So, finally I looked in the PinY log and saw this:

 

Sunday, January 19, 2020, 2:34:51 PM: Session started
PinballY 1.0.0 (Beta 18), build 9149 (x86, 20200101-2322)

DOF (DirectOutput): initializing DOF client

DOF: creating DOF COM object (a23bfdbc-9a8a-46c0-8672-60f23d54ffb6)
DOF: DOF COM object (a23bfdbc-9a8a-46c0-8672-60f23d54ffb6) is not registered on this system; DOF will not be used for this session

 

What should I do?

[mjr]

I have DOF active for PinballY but don't know what it does. 

 

DOF is a separate piece of software that you can install to control feedback devices on a dedicated pin cab, like solenoids and flashing lights.  Read "What is DOF?" here for more:

 

http://mjrnet.org/pi...ide.php?sid=DOF

 

 

What should I do?

 

If you don't have DOF installed, I'm guessing you're either running in a regular desktop setup, or you have a pin cab without any feedback devices, right?  In that case, the answer to "What should I do?" here is "nothing" - you don't need DOF, so you can just ignore this.

[rlewis19]

 

I have DOF active for PinballY but don't know what it does. 

 

DOF is a separate piece of software that you can install to control feedback devices on a dedicated pin cab, like solenoids and flashing lights.  Read "What is DOF?" here for more:

 

http://mjrnet.org/pi...ide.php?sid=DOF

 

 

What should I do?

 

If you don't have DOF installed, I'm guessing you're either running in a regular desktop setup, or you have a pin cab without any feedback devices, right?  In that case, the answer to "What should I do?" here is "nothing" - you don't need DOF, so you can just ignore this.

 

I'm sorry.  My post was totally lacking any real useful background information. That's what I get for being in a rush.  My cab has DOF active and working.  I have a sainsmart USB connected to 8 solenoids.  When playing games they work well.  I went into the DOF Config tool site and generated new config files as suggested in the documentation.  I then created the PinballY config file.    Is there anything else I should provide to help?

[mjr]

I'm sorry.  My post was totally lacking any real useful background information. That's what I get for being in a rush.  My cab has DOF active and working.  I have a sainsmart USB connected to 8 solenoids.  When playing games they work well.  I went into the DOF Config tool site and generated new config files as suggested in the documentation.  I then created the PinballY config file.    Is there anything else I should provide to help?

 

Ah, okay.  From the log excerpt you posted, PinballY isn't finding the "DOF COM object" installed.  If you installed DOF manually at some point in the past, that probably means you didn't go through the extra steps required to install the DOF COM object.  You can read about those steps in the DOF chapter I linked earlier, or in the DOF manual (linked from that chapter).  The easier solution might be to update to the latest DOF R3++ (also linked from the chapter) using the automatic Windows Setup (MSI) installer rather than attempting to do it manually.  The manual installation procedure tends to cause problems exactly like this because it has so many steps with so many things that can go wrong.

[rlewis19]

I installed the latest vpx 10.6 using the all in one installer.  I thought that install included DOF.  I did have DOF active long before that as well.  I'll take a look at the link and see about reinstalling just the DOF piece.

[mjr]

I installed the latest vpx 10.6 using the all in one installer.  I thought that install included DOF.  I did have DOF active long before that as well.  I'll take a look at the link and see about reinstalling just the DOF piece.

 

I'm almost sure that the VPX installer doesn't include DOF.

[rlewis19]

 

I installed the latest vpx 10.6 using the all in one installer.  I thought that install included DOF.  I did have DOF active long before that as well.  I'll take a look at the link and see about reinstalling just the DOF piece.

 

I'm almost sure that the VPX installer doesn't include DOF.

 

That did the trick.  Thank you!

[djlunchbox]

Ok strange issue.

Only on future pinball does the the topper video not stay on. Ive selected globally for the topper to remain on and even in some specific games as well. However once i launch a table it kills the attract Mode backglass video, topper and dmd. This only happens on Future Pinball. VPX and PBFX work fine.

I used to not have Process name: Future Pinball.exe filled in and when i didnt the backglass videos would continue to play and the topper video would stay on until the table fully launched or depending on how long the load of the table was it would go away before. Anyone else running Future pinball and have the topper video issue?

Any guidance?

Edited by djlunchbox, 21 January 2020 - 08:32 AM.

[mjr]

atarian - I made some further tweaks to the window/focus handling in Beta 19, which I'm hoping will make Pause/Resume behave better for you with the exclusive-mode setup using the 64-bit version.  So hopefully you won't be limited to the 32-bit version from now on. 

[mkl66]

Hi,

i hope that this is the right thread to address.

I came from pinballx as a frontend and changed to pinbally, because I love the all in one progamm approach.

Everything seems to be logical, and configurable, but one little issue is left unclear.

When I have a pinball game without a dedicated wheel art, nothing shows up in the wheel. I like the approach in pinballx, where you see at  least the name of the game.

Other than that it would be nice to configure a default wheel, when a specific one is missing.

Any help would be appreciated

 

best regards

Martin

[Thalamus]

@mkl66 : Tried latest version ? Was released only yesterday and contains this in the changelog :

* Fixed a bug that didn't display any text for a game title in the
wheel (for games without wheel images) when the "Wheel" font in the
options was set to a point size smaller than 40 points.  (Issue #109
on github.)

[atarian]

atarian - I made some further tweaks to the window/focus handling in Beta 19, which I'm hoping will make Pause/Resume behave better for you with the exclusive-mode setup using the 64-bit version.  So hopefully you won't be limited to the 32-bit version from now on.

Hi mjr. I installed the Beta 19 64-bit version under my Windows 7 64-bit cabinet setup and it works brilliantly.

1/ I can launch VPX which uses forced fullscreen mode, play, resume, terminate using your PinY menus. I can also use the 'exit directly' key.

That means it fixes the following:
- the issue where I couldn't even bring up the menus (I am not talking about the blank menus as that was fixed with font smoothing perf setting, but before with the 64-bit Beta 18 version I couldn't even activate any menus). I can bring up menus now with the 64-bit version.
- when the pause/resume menu comes up, it actually pauses the VPX player now in the background in that the ball stops where it is, and resumes where it left off. This wasn't working for me in Beta 18 even with the 32-bit version. All good now.
- as implied above resume now works, and terminate returns to PinballY. I can pause/resume as much as I like with no focus issues.

2/ I tested a 2-table batch capture and that worked too (I obviously flipped VPX temporarily to non forced fullscreen to overcome the way windows works).

3/ I have since added Pinball FX3 to PinballY and it also works great. I can use the exit key to exit directly. If I use the Pause/Resume menu I only see the Pinball FX3 resume menu and I resume from that. I don't see the PinballY menu but that is fine and probably is expected? If you don't expect this then it is possible it happens to me as I also run PFX3 in fullscreen too.

One minor observation. If I pause VPX, and instead of selecting resume or terminate, I press Exit then the menu disappears and nothing comes back to the front. I can just press the key again that brings up the resume menu again. Similarly if I view information or view high scores, etc, when I am finished I press exit, the info/high scores disappear and I get no menu. If you think these two cases need a tweak then it is probably a matter of just reshowing the menu when the user presses the exit key from either the resume menu itself, or from viewing information/high scores.

Thanks once again for this excellent software and the great support.

Edited by atarian, 22 January 2020 - 06:13 PM.

[mjr]

Atarian - glad to hear the new version is working better!  

 

It sounds like FX3 is probably intercepting the pause with its own handling.  I'm not sure how it's doing that - probably either intercepting the key press or intercepting the focus change.  But whatever it's doing must be preventing PBY from taking control.  There's probably a way to intercept the intercept and put PBY in front after all, but given that the behavior seems to be intentional on FX3's part, it might be better to leave well enough alone in this case rather than getting into a fight about which program is in charge.

 

I agree on the Exit menu behavior - it really should come up automatically any time the UI is idling in pause mode, since there's not much else to do in that mode.  I'll make a note about that.

[KPinball75]

Add me to the list of people having problems with batch captures.  I'm currently running Windows 7 Pro 64 bit.  I don't recall it happening it with beta 16.  It may have started in beta 17 but it's definitely happening with beta 18.  When it happens, there is no ffmpeg processes running.  Pinbally.exe is running as is the watchdog.  Sometimes, vpinballx will still be running.  When I move the mouse it shows the blue spinning cursor that you get when an app is hung.  Sometimes, the capture window will be visible but the time stops counting down and button presses don't do anything.  Sometimes, the capture window will be rotated sideways on the playfield and frozen and I can see another capture windows beneath it that's rotated the correct direction.  The capture window will sometimes go black when it hangs.

 

The only way to fix it is to kill pinbally.exe.  I can then start the capture again and it'll capture the same game it hung on with no issues.  Sometimes it'll capture another 20 games before hanging again.  Sometimes it'll capture just one before hanging again.

 

Another Issue I noticed with captures is when doing manual captures, occasionally, It'll start the capture then end the capture when I only pushed the buttons once to start the capture.  This happens pretty often.  I'm using standard pinball flipper buttons with a KLZ25 controller running pinscape.

[starwyvern]

Hi mjr,

 

I have the latest version installed. I really like it a lot. I have a couple of issues that started happening today.

 

1. I recently started with Pinball Y and have a few tables up and running correctly in it. I have a few with Table Audio when browsing on the Frontend, not playing a table yet. Just an MP3 of a song, named exactly how the other media files are etc. They all work except for one. It says unable to play table audio – rendering. Something slightly longer, but that is the gist. This was working earlier today and then it popped up with the rendering error. randr from VPinball pointed me to here.

 

2. In the Options Menu under startup, I clicked the Start in Admin Mode Automatically, thinking that would get rid of a couple errors I was having earlier. I would like to switch it back to Manually open Pinball Y and whenever I click it and hit Apply and close it, when I open it next, it is back at Automatic.

 

Any help would be greatly appreciated. Thanks!

[mjr]

Add me to the list of people having problems with batch captures.  [...]  I don't recall it happening it with beta 16.

 

If you're up for a little detective work, it would be helpful if you could go back to beta 16 and beta 17 to do some testing and see if you can determine for certain where exactly the problem started for you.  You can find old versions on the Web site - look for "Older Releases" in the Downloads section for a complete history of past release versions.

 

The problem seems to be sporadic for people who are running into it, so the way to check that it's *not* happening is to run enough successful tests in a row that you're satisfied that the odds that you merely got lucky are vanishingly small.  For example, if you're used to seeing the bug happen on every third or fourth attempt in Beta 18, it wouldn't be enough to run it three or four times without incident in Beta 16, since that could accidentally happen in Beta 18 as well, right?  In that case I'd want to see it work more like six or eight times in a row to be satisfied that it wasn't going to happen.

 

The reason I ask is that I can't seem to reproduce it myself, so I think the only way I'm going to track it down is to compare what changed between the last version where it *didn't* happen and the first version where it *does* happen.  If we can determine that for sure that Beta 16 / Beta 17 is the magic boundary, I can try backing out changes made across the update until we identify the one(s) that trigger it.

 

You might also want to check in here:

 

https://github.com/m...allY/issues/111

 

I'm not sure you're having exactly the same problem, but it sounds similar - maybe compare notes with the others on that thread and hopefully we can find the common element.

 

 

Another Issue I noticed with captures is when doing manual captures, occasionally, It'll start the capture then end the capture when I only pushed the buttons once to start the capture.  This happens pretty often.  I'm using standard pinball flipper buttons with a KLZ25 controller running pinscape.

 

I'll try to look into that - it sounds like I might need to insert an explicit check to make sure the buttons are released between Start and Stop.  Maybe your machine is a little faster than mine and it's checking in again too quickly.

It says unable to play table audio – rendering. Something slightly longer, but that is the gist. This was working earlier today and then it popped up with the rendering error. randr from VPinball pointed me to here.

 

If you can catch the exact message, that might be helpful.  I can't really guess without the details.  You might also want to check the log file (PinballY.log, in the main PinballY install folder) to see if there are any details there.

 

 

 

2. In the Options Menu under startup, I clicked the Start in Admin Mode Automatically, thinking that would get rid of a couple errors I was having earlier. I would like to switch it back to Manually open Pinball Y and whenever I click it and hit Apply and close it, when I open it next, it is back at Automatic.

 

I'm not sure why that's not working (it should), but you might try making the change manually.  Open Windows Task Scheduler.  Click on the "Task Scheduler Library" item in the left panel.  Find the PinballY launch task in the list in the middle.  Right click on it and select Properties.  On the General tab, un-check the box "Run with highest privileges".  Click OK, exit Task Scheduler.  Should be fixed.

[starwyvern]

mjr,

 

Thank you for the solution to the Auto Run in Admin mode. I followed those steps. As for the Table Audio issue. I believe I uploaded the picture into a gallery correctly on here and attached it below. Please let me know if you need any other information. It's strange because this was the first table I setup with audio and it worked perfectly. Anyway hopefully you know what's happening. Thanks again!

 

http://vpforums.org/.../8abohx1iiv.jpg

Edited by starwyvern, 29 January 2020 - 12:30 AM.

[mkl66]

@Thalamus : thanks for your info about the new version

@mjr; thanks for creating the new version

 

Now the wheel works as I expect it, so my issue is solved

 

Keep on providing such superior software ...

 

best regards

Martion