1624 replies to this topic

[wiesshund]

Ouch... This hurts :-) I cant remember what tables we talked about, but I am sure nobody had that in mind.

Guess this covers a large percentage of tables.

 

Thank you wiesshund.

LOL

 

It's what i do, it's the lazy way

 

Pick table, if backglass only shows 1 score block guess we skip and move on LOL

 

Most though will be 2 or 4

 

2 for a lot of early EM tables

4 for later ones and SS ones
as a general rule, there are exceptions.

 

Originals are hit and miss, totally depends on the author.

 

I know you can put things in categories in pinball Y pinball X and Popper but, im just too lazy to bother

i just rather have them all in one wheel.
 

So, i just look at the backglass

[Jewer76]

Perhaps someone can help me on this one:

 

I have at some point made a category in PinballY, but now I want to delete it. I have tried picking it and press Delete, and it is deleted. But perhaps a day or two later, it pops up again.

 

I have checked if any tables are part of the category, but it is empty.

 

So my question is: is there some file where category names are stored, that I can edit, since it reverts back within PinballY?

[htamas]

I started a separate thread about a problem I have, but then I realized it would rather belong here.

 

This weird issue is affecting only a few tables. This is on my 3-screen cabinet. I'm running the latest PinballY 64-bit version.

When I launch the table directly from VPX, everything is fine, backglass shows up and works es expected.

When I start the exact same table from PinballY, then the table starts but the backglass remains blank. If it's a table with a DMD, then DMD shows up OK.

One would think that if the table activates the backglass when running directly from VPX, the same should be the case when running the table via a frontend as well. I see nothing wrong in the database XML or anything else obvious.

 

There seems to be no rhyme or reason why would this happen, and I wasn't able to find any pattern why is this the case with some tables but not with the majority of them. Did anyone else experience this, and if yes, how to fix it? 

[digitalarts]

Maybe check at the "Game Details" menu of the problematic table, if you have any check marks set at the bottom
Be sure there is no checkmark in 'Backglass'

[htamas]

Maybe check at the "Game Details" menu of the problematic table, if you have any check marks set at the bottom
Be sure there is no checkmark in 'Backglass'

 

Do you mean "Game Launch" under the PinballY Options menu?

All checkboxes are unchecked there.

 

I'm not aware of specific settings for individual tables.

[digitalarts]

Of course there are specific settings for individual tables.
It's the menu where you can set the table name, manufacturer,year, type, Rom,... at the bottom of this menu you can set individual if for this table PinballY take care for backglass or DMD (viewing picture or video while gameplay)

[htamas]

OK, found that - but since I never used it to set individual values for specific games, there is nothing that would cause the problem.

Still stumped what could be the reason for this issue...

[htamas]

In the meantime, I figured out that the backglass for the problematic tables does get started, but it is in the background. I can alt+tab to them and they work fine after that, so I suppose I need to find out why the (latest, 2.1.0) B2S server is not bringing them forward like it happens with direct start from VPX. Also, what causes the difference? Strange...

Edited by htamas, 07 February 2024 - 05:55 AM.

[csdf28]

If the backglass is in the background, and yet you can't see it, that means something else is in the foreground covering it.  Are you sure that that "something else" isn't PinballY's backglass window?  

[htamas]

I found the solution.

For the problematic backglasses, the fix was to set "Bring Forms:" to "Standard" or "Form to Top". My default was "Form to Back", to avoid the DMD being covered (invisible) by the B2S DMD image when that is set to "Visible".

This still doesn't explain why the previous setting was affecting only certain tables and not all of them, but at least now I know how to fix the issue on an individual table level.

[MisterCoffee]

It's probably quite simple, but I can't figure it out right now.

Is it possible to always start Pinbally with a specific filter and table selected in the wheel?

 

The default setting is that the last table played is displayed. I have set various filters via "Wheel Actions" and would like to always have Pinbally start with my "menu" filter so that I can start my selection from the beginning every time.

Pretty sure this is possible using the main.js or an extra js.file, but I need a hint.

 

Thanks.

[Carny_Priest]

I guess if you are happy with everything else with the setup then you could simply set the settings file to read-only.

[MisterCoffee]

Really a good idea.
However, this results in an error message when I close Pinbally.
Meaning: "Cannot write the settings file"

 

Is it possible to hide that window?

Or maybe it is easier to go another way.

 

Another idea that comes to my mind would be the at startup command in the pinbally options. You could possibly start a “wheel action filter.js” here. but I do not know how :-) my js.files work pretty fine, but the command only allows .exe.

 

 

So we have got:

1. set settings to read only --> the error message needs to disapear

2. some code in the main.js

3. a command in the start up line in the pinbally options

Edited by MisterCoffee, 18 March 2024 - 05:06 PM.

[licwip]

I'm loving PinballY for 64-bit. Thanks for updating it! I was unable to get DOF working with the prior version, so I had to stay at 32-bit. Now it's great.

 

However, I'm unable to capture playfield video during my Media Capture. Keep getting a message: "FFmpeg exited with error code -2." Can anyone help? (Not sure where to find the log file either.)

[mjr]

> However, I'm unable to capture playfield video during my Media Capture. Keep getting a message: "FFmpeg exited with error code -2."

 

I broke the command-line builder for some captures when I updated to the newer ffmpeg.  I've already fixed it (as far as the known problem, at least), but I haven't posted the update yet - I'll try to put that together soon.

[licwip]

Great, thank you!

[leprinco]

I have some issue with pinballY and DOF.

My installation is very up to date. But when pinballY starts, here is the sequence I observe :

 

- I have the temporary black screen of pinballY,

- In log : 

samedi 16 novembre 2024, 17:48:41: Session startedPinballY 1.1.0 (Beta 10), build 10086 (x64, 20241103-1939)
DOF (DirectOutput): initializing DOF client
DOF: creating DOF COM object (a23bfdbc-9a8a-46c0-8672-60f23d54ffb6)

- It takes some time.. then I can see the RGB test sequence of my leds blinking

- Then still black screen and wait again and in log I can see a new DOF initialisation :

DOF (DirectOutput): initializing DOF 
clientDOF: creating DOF COM object (a23bfdbc-9a8a-46c0-8672-60f23d54ffb6)

Checking for Javascript main script file C:\PinballY\scripts\main.js
High score retrieval (init): VPinMAME NVRAM path is C:\Visual Pinball\VPinMame\nvram
...

So as if DOF was started twice. and in DOF log, I can see the same. Two complete sequences, one successfull, the second one that ends with exception : access refused

2024.11.16 17:59:31.099	EXCEPTION: WemosD1MPStripController "Wemos" updater thread could not connect to the controller. Thread will quit.
2024.11.16 17:59:31.099	EXCEPTION: Thread: WemosD1MPStripController "Wemos" updater thread
2024.11.16 17:59:31.099	EXCEPTION: Message: Exception --> A exception occurred while trying to open the Com-port 'COM3'. Found the following Com-Ports: COM3.  Will not send data to the controller.
2024.11.16 17:59:31.108	EXCEPTION: Stack trace:    à DirectOutput.Cab.Out.AdressableLedStrip.TeensyStripController.ConnectToController()
2024.11.16 17:59:31.108	EXCEPTION: Stack trace:    à DirectOutput.Cab.Out.OutputControllerCompleteBase.UpdaterThreadDoIt()
2024.11.16 17:59:31.109	EXCEPTION: Target site: Void ConnectToController()
2024.11.16 17:59:31.109	EXCEPTION: InnerException 1: UnauthorizedAccessException --> L'accès au port 'COM3' est refusé.

So what can be the cause of that  ?

What is missing so that pinballY to consider DOF is well initialized after first sequence ? 

 

Thanks a lot

Edited by leprinco, 16 November 2024 - 05:05 PM.

[TehLurv]

I've recently gone through the work of setting up PinballY as my new frontend. The only issue I'm having with it that I haven't been able to resolve is PinballY is unable to close PinballFX/PinballM using the Exit button and PinballY gets stuck if I exit either program through it's own menu. So far I've tried setting both programs to run as borderless windows, checking that my assigned Exit button isn't also mapped to another function in Steam or those programs, and setting PinballY to terminate the process. No success so far.

[mjr]

leprinco - I haven't heard of DOF double connections like that before.  If anyone else is running into the same thing, it would be good to know, maybe you can compare notes and see if there's something in common between your systems. 

 

There is one odd little detail in the log you posted that I'd like to confirm isn't just a cut-and-paste artifact:

 

DOF (DirectOutput): initializing DOF
clientDOF: creating DOF COM object (a23bfdbc-9a8a-46c0-8672-60f23d54ffb6)

 

See how that "initializing DOF / client" is split across two lines?  Is that actually what it looks like in your log file, or is that just the way it got rendered after pasting into the forum post?  If you're actually seeing the extra newline inserted there, it makes me wonder if you've got something weird going on with multiple PinballY processes running at the same time, both trying to write to the log file at once.

[mjr]

TehLurv - can you describe in more detail the state the system is in after the game exits and PinballY is "stuck"?  E.g., what's on the screen, which process is in the foreground, anything else that might be going on.  I assume you've already tried the various Close Window possibilities in the settings, not just Kill Process - and even if you have, it might be worth looking closely to see if there's any noticeable difference in the behavior with the different settings, again in terms of the screen display left over and which process has control.  Any differences might point the way to a solution.  Since you mentioned that Steam is involved, it might be worth going through your launch setup for the game again, since Steam adds its own complications by having its own launcher involved, adding a third process to the mix.  It might be that PinballY is targeting the wrong process for the Kill Process/Close Window operation (targeting Steam instead of the actual game process, or vice versa), or that the Steam process is the element that's refusing to exit when asked, or something like that.  These things are obnoxious enough when only two processes are involved...