1353 replies to this topic

[TerryRed]

 

 

I'm running into a VPX full screen problem with b2s backglasses not showing / loading when launching from PBX. I've tried having B2S enabled in PBX / No backglass media, etc... and no change.

 

It works fine with VPX directly....even when using the delay function of 10.2....I only have this issue with PBX.

 

...ooops wrong thread.

 

 

Actually does anyone have any idea why this is?  I cannot get around this issue, so I guess this may be the right place to ask. This is only an issue with exclusive full screen VPX tables launched from PBX causing some DB2S files to not load (but DOF works fine). They load just fine from the editor. 

 

 

Also, it would be nice to have the option to enable exclusive full screen and the delay option to be configurable on a per table basis....since some DB2S files are much larger  and take longer to load, a much longer delay time is needed.

 

Great work so far on VPX!

[arngrim]

do you have the vpx and directb2s with the same name?

[TerryRed]

do you have the vpx and directb2s with the same name?

 

 

Absolutely, yes. Every one of them exactly the same. I don't have B2S enabled in PBX...just backglass videos. I tried using no BG videos, and no B2S, as well as no videos with B2S....all the same result. No error tone or anything...though I do have "ignore errors" enabled in B2S settings to allow all tables to load.

 

If VPX is in windowed full screen, they all load up normal from PBX

 

I would say about 50% of the 45 VPX tables I have are loading fine from PBX in exclusive full screen.

[gtxjoe]

Can you post an example of a working table/direcb2s and non-working table/directb2s.  I would like to give it a try on my cab

Edited by gtxjoe, 20 August 2016 - 08:29 PM.

[TerryRed]

Can you post an example of a working table/direcb2s and non-working table/directb2s.  I would like to give it a try on my cab

 

 

These were some that don't work...

 

Sopranos, Robocop, Bram Stoker Dracula, Cactus Canyon, Circus Voltaire, Demolition Man

 

These are some that do work...

 

Avatar, Iron Man, Pirates of Caribbean

 

Changing a table from a non working DB2S file to a "working" DB2S file (copying and renaming), doesn't make it work either...

Edited by TerryRed, 20 August 2016 - 09:49 PM.

[arngrim]

and if you give them a simple name like dracula.vpx/dracula.directb2s

[TerryRed]

and if you give them a simple name like dracula.vpx/dracula.directb2s

 

I think I know where you are going at with this.  Yes I tried renaming them with no brackets/year,etc...no change.

 

 

However, I did figure out something that fixes MOST of my issues.

 

By running VPX in a "custom" "other system" in PBX instead of the integrated Visual Pinball system, I was now able to get most of my VPX tables to load up their DB2S files, and be able to get the table into focus with the 10.2 "alt-tab" feature for full screen (set to 15 secs).

 

The only tables that didn't load their DB2S was :

 

Monster Bash, Walking Dead, Demolition Man.

 

 

I also tried Atarian's AHK script (without VPX's alt-tab switch) "bring_to_top.ahk".  

 

#SingleInstance force
DetectHiddenWindows, On

WinWaitActive, Form1,,10
WinWaitActive, Visual Pinball Player,,30
WinMaximize, Visual Pinball Player
ExitApp

 

 

Using that script, only these tables didn't load their DB2S (though I'm sure I could have tweaked it):

 

Walking Dead, America's Most Haunted, Demolition Man, Dirty Harry, Judge Dredd, King Pin, Monster Bash, South Park

 

 

 

Strange that Monster Bash, Walking Dead, and Demolition Man won't load no matter what (unless VPX is in windowed full screen)

 

 

It seems PBX's integrated VP handling is causing an issue. I also had to do the same thing with Pinball FX2 (custom system) in order to get dmdext to work with it (also having to use an AHK script).

[arngrim]

funny is that monster bash and dm are the only tables that i remember on my system, the bring to top is not working, i have to alt tab manually, but i have the backglass

 

so far i remember only one backglass it never showed on my system, was bassgeige highres cirqus voltaire, because too big i don't know, solution is to use another one and it launches

Edited by arngrim, 21 August 2016 - 05:08 AM.

[Pinball999]

I'm not sure if it can help or not, but I started having the same problem with Monster Bash DB2S not showing after I replaced my VP9 version with the latest VP10.

Before it was working just fine.

[doogie2301]

Do you guys have the "Error message without backglass" option enabled in the B2S settings?  I had the same problem with these tables when I was trying fullscreen and launching from PBX, and the error message box said that the b2s file couldn't be found.  The path of the file it said it couldn't fine though had an empty value for the file name, like "\.directb2s", so maybe when these tables take too long to load and they don't have focus it can't determine the filename? 

[Westworld]

>had an empty value for the file name, like "\.directb2s"

 

I had exactly the same problem. Also mainly the same tables as described above. New, modern, big tables.

All worked fine directly from VPX, failed from PinballX. All worked without fullscreen.

 

If I tried from VPX and THEN directly from PinballX it always works, but other tables fails. Always the last played table in VPX also worked in PinballX. So I thought it is something with Registry or so.

 

I renamed the tables and backglass, to simple names like "monster". Only lowercase, only characters, 8 char or less, good old DOS rules. Did not helped always.

I opened the direct2bs files (they are in fact XML) and entered there the same names. Helped with some, not with all.

I entered the ROM names. Helped with some more.

 

Sometimes I thought it was just that, then it failed with the next table again.

 

It was more trial&error mixed with magic as real fixing.

 

Because of Registry difference (comparing after launching directly from VPX and comparing with PinballX) I tried to launch PinballX as admin. That helped! But I always got that stupid admin dialog. So I removed the flag again - and it still worked. No idea why.

 

at least, at the end all tables worked except Lord of the Rings. I used an older, smaller backglass and now also that works. Currently all tables works for me... Happy again. Needed 4 weeks.

 

It is a combination of large tables and large backglass, launched from Pinballx and not directly.

btw, it is an i5 with 8 GB Ram, Windows 10, 2 screens + DMD.

 

So for all frustrated with the same issue: sorry, no clear help, but at least, you are not alone. And it seems to be solveable, don't give up.

Be careful, it could be several issues at the same time. Once i installed a new Elvira and that also failed, which always worked before. I needed a while to see I had a typo in the name, so table/backglass had different names and it was normal that this failed. But if you are already frustrated, you might miss that easy.

Every time when I thought I found the reason, the same trick failed with another table. But table by table, more and more worked, so don't give up.

 

I think it was worth the time. I had so much stutter before, was close to spend a fortune and purchase a 1080 card, just to be able to play without that stutter. Now (I have a 970) everything is fine, fast, super.

 

Fullscreen mode is great, thousand thanks to the developers!

[Carny_Priest]

Not saying that it is the fix because I don't run full screen. But I coded a custom VP launcher in ahk and I have PinballX launch the launcher, hence the process that it monitors is the ahk executable. Going that route should give you total control over delays and focus.


Sent from my iPhone using Tapatalk

[TerryRed]

Not saying that it is the fix because I don't run full screen. But I coded a custom VP launcher in ahk and I have PinballX launch the launcher, hence the process that it monitors is the ahk executable. Going that route should give you total control over delays and focus.


Sent from my iPhone using Tapatalk

 

By having VPX as a "custom" system instead of the integrated VP support... it seemed to bypass PBX doing any of the "delays" or any other handling it may try to do.

 

 

 

>had an empty value for the file name, like "\.directb2s"

 

I had exactly the same problem. Also mainly the same tables as described above. New, modern, big tables.

All worked fine directly from VPX, failed from PinballX. All worked without fullscreen.

 

If I tried from VPX and THEN directly from PinballX it always works, but other tables fails. Always the last played table in VPX also worked in PinballX. So I thought it is something with Registry or so.

 

I renamed the tables and backglass, to simple names like "monster". Only lowercase, only characters, 8 char or less, good old DOS rules. Did not helped always.

I opened the direct2bs files (they are in fact XML) and entered there the same names. Helped with some, not with all.

I entered the ROM names. Helped with some more.

 

Sometimes I thought it was just that, then it failed with the next table again.

 

It was more trial&error mixed with magic as real fixing.

 

Because of Registry difference (comparing after launching directly from VPX and comparing with PinballX) I tried to launch PinballX as admin. That helped! But I always got that stupid admin dialog. So I removed the flag again - and it still worked. No idea why.

 

at least, at the end all tables worked except Lord of the Rings. I used an older, smaller backglass and now also that works. Currently all tables works for me... Happy again. Needed 4 weeks.

 

It is a combination of large tables and large backglass, launched from Pinballx and not directly.

btw, it is an i5 with 8 GB Ram, Windows 10, 2 screens + DMD.

 

So for all frustrated with the same issue: sorry, no clear help, but at least, you are not alone. And it seems to be solveable, don't give up.

Be careful, it could be several issues at the same time. Once i installed a new Elvira and that also failed, which always worked before. I needed a while to see I had a typo in the name, so table/backglass had different names and it was normal that this failed. But if you are already frustrated, you might miss that easy.

Every time when I thought I found the reason, the same trick failed with another table. But table by table, more and more worked, so don't give up.

 

I think it was worth the time. I had so much stutter before, was close to spend a fortune and purchase a 1080 card, just to be able to play without that stutter. Now (I have a 970) everything is fine, fast, super.

 

Fullscreen mode is great, thousand thanks to the developers!

 

 

Geeze...a 1080 would be way overkill for VPX  lol!   I'm using a GTX 960  (My gaming PC has two gtx 970s) with an i5 2500K 8 gigs ram.....and with exclusive fullscreen and graphics all maxed out it runs buttery smooth like all other PC games do.  Just make sure that VSYNC in VPX is enabled (FPS limiter / Vsync=1) , and VSYNC in nvidia control panel is set to "application controlled". Also double check the table's options to make sure that vsync is enabled on there too.

 

 

I have tried alot of what you posted, but there are some other things there I may try. Thanks for the fantastic detail! I'm sure you have saved alot of people some nasty troubleshooting.

 

 

I will go back at it...luckily its only a few tables for now, one way or another...

Edited by TerryRed, 21 August 2016 - 03:35 PM.

[Carny_Priest]

I run my launcher in the usual PinballX Visual Pinball system slot. Bypass disclaimers check and Auto Configure not checked. The launcher runs a custom xml with its own version of an alternateexe tag. I have a lot of things going on in this launcher with those features not really being compatible with the delays that PinballX was using, but for your situation I mention this custom launcher because I too run a custom resolution for the third monitor to execute VPM with ddraw=0 and achieve a pixel perfect DMD display.

 

http://www.gameex.in...&comment=145260

 

Also, I patched my dB2S server executable. 

 

http://www.ntcore.com/4gb_patch.php

 

The patch seemed to at least get some of those huge bassgeige backglasses working on my system.

 

You are operating on the bleeding edge, so I'm not surprised that you are having to make extraordinary efforts to get this setup working the way you want. Sounds like you are enjoying the challenge though. Some people like to tinker more than play, and that's OK. I'm in the same boat.

Edited by Carny_Priest, 21 August 2016 - 04:31 PM.

[arngrim]

btw i found a bug in pbx, using alternateexe on a pinballx custom vp system, when exiting a table it doesn't close vp

[TerryRed]

I've never actually used the alternateexe feature.  

 

For me it was just easier to have a separate "other system" for VP9, PM5, and now VPX.   Then I just used "Manage Groups" to have them combine into one menu.

 

 

 

I run my launcher in the usual PinballX Visual Pinball system slot. Bypass disclaimers check and Auto Configure not checked. The launcher runs a custom xml with its own version of an alternateexe tag. I have a lot of things going on in this launcher with those features not really being compatible with the delays that PinballX was using, but for your situation I mention this custom launcher because I too run a custom resolution for the third monitor to execute VPM with ddraw=0 and achieve a pixel perfect DMD display.

 

http://www.gameex.in...&comment=145260

 

Also, I patched my dB2S server executable. 

 

http://www.ntcore.com/4gb_patch.php

 

The patch seemed to at least get some of those huge bassgeige backglasses working on my system.

 

You are operating on the bleeding edge, so I'm not surprised that you are having to make extraordinary efforts to get this setup working the way you want. Sounds like you are enjoying the challenge though. Some people like to tinker more than play, and that's OK. I'm in the same boat.

 

Thanks Carney.  

 

I actually use "Multi-Monitor Tool" for doing my resolution changes for my screens (including the VPX DMD screen resolution changes), and it works the best out of everything I have tried.

 

I just use the QuickLaunch plug-in to run multiple things for Launch Before, and it seems to work well (if you work around the few bugs it has). However I still have to learn how to use AHK more....

 

 

 

I do like to tinker, and get stubborn when trying to fix problems...

Edited by TerryRed, 21 August 2016 - 10:10 PM.

[DJRobX]

So I found the issue with the Boom balloon on Cirqus Voltaire.   Pretty simple.    There are two new options for pop bumpers (LBumper1) "Ring visible" and "Skirt visible".    These are defaulting to ON for old tables.      Just had to uncheck them to fix it. 

 

I suspect this is less dramatic of an issue on most other tables where the pop bumpers are always visible, but I wonder if the default should be changed to off (when loading files when it is not defined) to respect backwards compatibility?   There aren't that many tables for VPX yet so it probably doesn't matter too much though.   

Edited by DJRobX, 21 August 2016 - 09:07 PM.

[fuzzel]

So I found the issue with the Boom balloon on Cirqus Voltaire.   Pretty simple.    There are two new options for pop bumpers (LBumper1) "Ring visible" and "Skirt visible".    These are defaulting to ON for old tables.      Just had to uncheck them to fix it. 

 

I suspect this is less dramatic of an issue on most other tables where the pop bumpers are always visible, but I wonder if the default should be changed to off (when loading files when it is not defined) to respect backwards compatibility?   There aren't that many tables for VPX yet so it probably doesn't matter too much though.  

 

Ok I changed the code that as long as you don't load a 10.2 table the visibility setting of the bumper base is also set for the ring ans skirt. That should work for all pre10.2 tables or as long as you didn't save a pre10.2 table with the VP10.2

rev2765 is up:

 

- add compatibility with pre10.2 tables if only bumper base is set to be invisible.
- fix dynamic bulb mesh light not rendered issue
 

[arngrim]

thank you, the balloon bumper is now visible by default

 

about the core.vbs, could we change the default value of the pinmameinterval to 10 (or another bigger value that is harmless?), we discussed about it quite some time ago, 1 is quite low, benefit? and 10 improves the performance, that's what i remember from the discussions, at least after each release i change manually from 1 to 10

[hauntfreaks]

thank you, the balloon bumper is now visible by default

 

about the core.vbs, could we change the default value of the pinmameinterval to 10 (or another bigger value that is harmless?), we discussed about it quite some time ago, 1 is quite low, benefit? and 10 improves the performance, that's what i remember from the discussions, at least after each release i change manually from 1 to 10

 

I couldn't agree more... I was seeing this in scared stiff