373 replies to this topic

[arngrim]

i tried to use that initially but i have plenty of tables having an image instead of a vid and recorder tries to record vids when missing, this will take a hell of a time, i'm happy with the images for static playfield or backglass.

also i have +150 that are not on my pbx xml, and recorder shows me them at some point, that's why i "manually" record, but delete old vids or drag and drop new table, i don't see a big difference in operation, it's even quicker to drag and drop one file than delete 2 or 3 files per table

using drag and drop or auto search wouldn't make a difference anyway, because both are calling vp the same way hat handles true fullscreen in a certain way that when you record or take simple screenshot, it is blank, i had that also before pbx recorder, with camtasia

 

what is your gfx? and driver?

can you share the reg djrobx

[gStAv]

Cool Arngrim.

I have to test the drag'n drop tactics.
If it works I shure would fint this method more handy as you usually know which table/tables who needs an update.

I report back when I've tried.

I'm using the latest driver for my GTX970. Cant remeber, but the driver is like a week old tops.

[DJRobX]

 

can you share the reg djrobx

 

All I'm doing is setting VP to windowed fullscreen, going into regedit, and exporting the whole 

 

HKEY_CURRENT_USER\Software\Visual Pinball\VP10\Player

 

to VP10-WindowedFullScreen.Reg

 

Then setting it back to true fullscreen and doing it again:

 

to VP10-TrueFullScreen.reg

 

Then I have a little .bat file:

 

reg import VP10-WindowedFullScreen.reg
start /wait PBXRecorder.exe
reg import VP10-TrueFullScreen.reg

[chokeee]

What about black frame on DMD in True Full Screen mode? I have latest Vpinmame and that frame still is there. Any ideas?

[MrKnister]

Is anyone using PinballX successfully with true full screen?  I'm having issues with true fullscreen mode where when I start a table through PinballX the backglass won't load and I'll get an error saying that <tables directory>/.directb2s couldn't be found, as if it loses the name of the table during the load.  I've seen mention of this in the past but am wondering if anyone has gotten around this issue.

if i remember right ... the trick to get pbx running with vpx in true fullscreen, is that the vpx system you defined via game manager has to be a "custom" one .. if the vpx true fullscreen setup is set to "visual pinball" (which is the default if you pick the first list entry in pbx setup) the b2s errors came for me also.

 

long story short ... fire up the pbx setup .. jump to the "system lists" .. make a new entry and set this system to "custom" .. then copy your xml (from the "normal" vpx folder) to the new created custom system folder in your filesystem where the databases are. im not sure if youll have to name the xml the way your system folder is since i guess pbx reads all xml's the hard way.

 

startup pbx and test ... you will then most likely see two entries for every table ... if after a test all works fine, cut the xml from your regular database folder and save it somewhere for later usage maybe. only the systems were a xml is will be listed i guess.

 

give it a try

 

(im not at my cab but at work .. so sorry for the vague description, maybe someone else can chime in here with better details .. and remember what dj robx said .. in some cases just opening up a taskmanager and let it stay in the background while using pbx can do wonders) 

Edited by MrKnister, 23 November 2016 - 11:09 AM.

[GInsonic]

I recently opened up a thread regarding PBX and full screen issues in PBX forum. Tom did not answer yet, but Carny_Priest convinced me to wait, until the current beta versions of VPM, VPX and BTS will become stable. Meanwhile you should do, like MrKnister suggests above. I also "moved" VP into a custom system using system type "custom" instead of "Visual Pinball". Since I had troubles terminating fullscreen VPX correctly then (process remained active in the background while PBX reappeared), I wrote a little AHK script (VP_Starter), which starts and terminates all VP versions correctly after it examines the database xml and reads corresponding exe from an xml tag similar to <alternateexe>. If everything works right out of the box, you do not need such a script, only move VP to a custom system then !

For now everything works for me like a charm !

Edited by GInsonic, 23 November 2016 - 10:57 AM.

[Seraph74]

Im doing a similar thing to djrobx 's reg entry solution for pbx recorder,

but having the batch files set as launch before / after options in pinballx

That way can use the editor in windowed mode , and play fs in pbx

[Ark Malmeida]

 

Is anyone using PinballX successfully with true full screen?  I'm having issues with true fullscreen mode where when I start a table through PinballX the backglass won't load and I'll get an error saying that <tables directory>/.directb2s couldn't be found, as if it loses the name of the table during the load.  I've seen mention of this in the past but am wondering if anyone has gotten around this issue.

if i remember right ... the trick to get pbx running with vpx in true fullscreen, is that the vpx system you defined via game manager has to be a "custom" one .. if the vpx true fullscreen setup is set to "visual pinball" (which is the default if you pick the first list entry in pbx setup) the b2s errors came for me also.

 

long story short ... fire up the pbx setup .. jump to the "system lists" .. make a new entry and set this system to "custom" .. then copy your xml (from the "normal" vpx folder) to the new created custom system folder in your filesystem where the databases are. im not sure if youll have to name the xml the way your system folder is since i guess pbx reads all xml's the hard way.

 

startup pbx and test ... you will then most likely see two entries for every table ... if after a test all works fine, cut the xml from your regular database folder and save it somewhere for later usage maybe. only the systems were a xml is will be listed i guess.

 

give it a try

 

(im not at my cab but at work .. so sorry for the vague description, maybe someone else can chime in here with better details .. and remember what dj robx said .. in some cases just opening up a taskmanager and let it stay in the background while using pbx can do wonders) 

 

 

 

I recently opened up a thread regarding PBX and full screen issues in PBX forum. Tom did not answer yet, but Carny_Priest convinced me to wait, until the current beta versions of VPM, VPX and BTS will become stable. Meanwhile you should do, like MrKnister suggests above. I also "moved" VP into a custom system using system type "custom" instead of "Visual Pinball". Since I had troubles terminating fullscreen VPX correctly then (process remained active in the background while PBX reappeared), I wrote a little AHK script (VP_Starter), which starts and terminates all VP versions correctly after it examines the database xml and reads corresponding exe from an xml tag similar to <alternateexe>. If everything works right out of the box, you do not need such a script, only move VP to a custom system then !

For now everything works for me like a charm !

 

Thanks the suggestions guys!  I'll give the custom system thing a shot.  I did try having a task manager open in the background in the past but had no luck there.

[DJRobX]

What about black frame on DMD in True Full Screen mode? I have latest Vpinmame and that frame still is there. Any ideas?

 

See carny's post above.  http://www.vpforums....=34672&p=362326.  You probably do not have the latest beta where I removed the black bars, and Toxie improved the appearance. 

[arngrim]

thanks rob, i forgot that was so easy to create a reg file..

[chokeee]

forgive me that question... which one should I install pindmd3, 2, 1 or maybe PinMame (two screens cab)?

[Ark Malmeida]

I recently opened up a thread regarding PBX and full screen issues in PBX forum. Tom did not answer yet, but Carny_Priest convinced me to wait, until the current beta versions of VPM, VPX and BTS will become stable. Meanwhile you should do, like MrKnister suggests above. I also "moved" VP into a custom system using system type "custom" instead of "Visual Pinball". Since I had troubles terminating fullscreen VPX correctly then (process remained active in the background while PBX reappeared), I wrote a little AHK script (VP_Starter), which starts and terminates all VP versions correctly after it examines the database xml and reads corresponding exe from an xml tag similar to <alternateexe>. If everything works right out of the box, you do not need such a script, only move VP to a custom system then !

For now everything works for me like a charm !

 

So moving the system type to 'custom' fixed my b2s loading issue.  Huge thanks to you and Carny_Priest for that suggestion!  Would you mind sharing your AHK script with me?  I'm having the issue where the VPX isn't terminating now which is an problem because all of my DOF controlled things stay active when a table is exited.

[GInsonic]

 

I recently opened up a thread regarding PBX and full screen issues in PBX forum. Tom did not answer yet, but Carny_Priest convinced me to wait, until the current beta versions of VPM, VPX and BTS will become stable. Meanwhile you should do, like MrKnister suggests above. I also "moved" VP into a custom system using system type "custom" instead of "Visual Pinball". Since I had troubles terminating fullscreen VPX correctly then (process remained active in the background while PBX reappeared), I wrote a little AHK script (VP_Starter), which starts and terminates all VP versions correctly after it examines the database xml and reads corresponding exe from an xml tag similar to <alternateexe>. If everything works right out of the box, you do not need such a script, only move VP to a custom system then !

For now everything works for me like a charm !

 

So moving the system type to 'custom' fixed my b2s loading issue.  Huge thanks to you and Carny_Priest for that suggestion!  Would you mind sharing your AHK script with me?  I'm having the issue where the VPX isn't terminating now which is an problem because all of my DOF controlled things stay active when a table is exited.

 

 

You're welcome ! 

 

Here is my script, please set your actual directories, please see the comments in the script.

 

One more thing: I defined the PBX exit emulator key as "Q", if you defined another key, please change the remap label "~Q" to your key (e.g. "~Esc") in the script !

Attached Files

•  VP_Starter.zip   842bytes   19 downloads
•  PinballX.jpg   13.74KB   16 downloads

Edited by GInsonic, 24 November 2016 - 07:02 PM.

[ClarkKent]

I did not follow the development for the exclusive fs mode but I tried it lately and only got a black pf monitor. Any recommendations?

[TerryRed]

If you haven't updated to the latest PinMAME, and the latest B2S, chances are the "focus" was switched to your B2S monitor while loading the table. Try updating those.

 

With exclusive full screen, VP is running like a typical PC game. That means other windows, including PinMAME, can't be seen on the same screen as your playfield. If you ever switch focus to another screen, window, or program, then your playfield screen may go black.

 

Also, make sure vsync for "VPX in your "graphics card settings" are set to "application controlled".

 

Make sure VPX video options has "FPS Limiter / Vsync" set to 1, and "Max pre-rendered frames" set to 1.

 

Make sure the table you are running is also set to default for "FPS Limiter/ Vsync".

Edited by TerryRed, 01 December 2016 - 07:48 PM.

[ClarkKent]

Still does not work. Didn't I remember that there has to be something changed in the registry?

Edit: Got it! Didn't close VPX while editing the registry. As it makes no difference if ddraw is set to 0 for windowed mode, all ROMs could be changed, I added the value ddraw 0 for the default. All in all the ball runs smoother than in windowed full screen (otherwise there is some small stutter now and then), so it's the better option for me!

Edited by ClarkKent, 03 December 2016 - 05:20 PM.

[ClarkKent]

One problem remaining: I'm using HyperPin (and do not want the other one). It suddenly switches back to HyperPin after the table has been loaded, so I have to Alt-Tab to the Visual Pinball Player. What's the fix for this?

[ClarkKent]

As some tables switches back from the loading screen and immediately switches back to the player it seems that smaller tables loading faster do not have the focus problems. Maybe there is a timeout in the ahk script?

[Drybonz]

Clark, the "bring to front" was integrated into a recent 10.2 beta with a fix from DJRobX.  The ahk script is no longer needed.

[ClarkKent]

I'm talking of the ahk script from HyperPin. That's still necessary.