373 replies to this topic

[DJRobX]

There is one - but since we don't have any good resources for the table it's hardly worth it.

 

Caveman (Gottlieb 1982 pinball/video game hybrid) has its numeric score display directly above its video screen so the numeric display gets displayed on both playfield and BG if you use FS with B2S. The VP8 desktop table doesn't use the VPM numeric display either so it might be best if the score display where hidden.

As said before - If it's an easy fix it would be nice to have the display hidden but if it's too much of a hassle don't bother. I have it only on my cab because it is an good way to torture my unsuspecting victims, er, guests - not because it looks good.

Same as Granny and the Gators

 

 

OK, yeah ... makes sense to remove the score display and require B2S or the table to display it for that particular case.    I added the nodisp tags and checked that into my repo for Caveman.    It seems to work.  VP 9.x crashes on my laptop trying to play the table, but it did so before i made the change.   It might work better on my cab.   The change itself seems to work fine. 

[tspeirs]

Just to go more back to the original topic but in case you didnt notice I updated PBX and made the fullscreen tweak optional. Although it worked really well for me.

Edited by tspeirs, 08 November 2016 - 08:02 AM.

[osujd]

 

 

The Whitestar DMD thing has always bothered me.   I think those games just have an incorrect DMD size configuration.  The secondary DMD is an extra thing relayed to the table as lights, and shouldn't matter for the main DMD (just like it doesn't on [BLEEP] tables that use an almost identical IO board).

Any idea on where to get older versions of pinball x?  I only see 2.27

 

 

 

If you go to the PinballX download there's a drop-down box for a changelog.  If you pick 2.25 a download link will appear.   That version works fine for me, where 2.27 does not.  

I am still seeing issues even with 2.25 is there any where in pinballx to confirm which version is being used?

 

 

PinballX\log\log.txt

 

Hi Guys,

 

I have tried version 2.25 and version 2.28 w and w/o the full screen hack checked in pinball x setting.  I still continue to get the direct2bs failure.  I have even tried loading it via the "other systems" loader within pinball x.  Any thoughts on what to try next? 

[tspeirs]

Its probably unrleated to the issue then but please check the following is in your pinballx.ini (check spelling).

 

[VisualPinball]

EnableFullScreenExclusiveHack=False

[osujd]

yes it is in there

Attached Files

•  pinballx.ini.PNG   14.93KB   24 downloads

[tspeirs]

I'm not really sure then. Was there a particular version of PinballX that did work for you?

[osujd]

They all have worked fine with true full screen off....I think some of the previous builds worked better but its hard to say since I have updated fairly regularly.

[Umpa]

So there is alot of info here about getting full screen support working with vpx and pinballx. I have 3 screen cabinet and my 3rd screen is used as dmd. I would like to turn on full screen and not have the black bars on the side of my dmd(3rd screen)Can someone list the steps to enable this. If not I will try some trial and error. Thanks!

[Carny_Priest]

Use this beta build and no more black bars:

 

http://www.vpforums....=27063&p=256944

 

set ddraw=0 with SetDMD

 

Current PinballX supports full screen support. 

 

That's it!

[Umpa]

Use this beta build and no more black bars:
 
http://www.vpforums....=27063&p=256944
 
set ddraw=0 with SetDMD
 
Current PinballX supports full screen support. 
 
That's it!

Awesome! Thank you!

[senseless]

I was a bit reluctant to try the true full screen option after reading all the difficulties and the PBX challenges. I tried it with a single table and before I knew it I was focussed on getting every VPX table in true full screen!
 

Overall the difference to windowed is in my honest opinion huge. The playability improved big time and thee main reason is that there is less noticeable lag using the flippers. In addition the whole experience is better as the table is much smoother during play.

 

I'm a true believer now and am glad I read the whole topic. With setting the ddraw=0 I had to change the dmd position slightly but this was not a big effort. I noted down the new settings of the correct dmd position and used these to update the whole registry settings. The find/replace functionality in Notepad++ is a great help in achieving this . Also changed all right dmd position settings in the default profile so new tables will inherit these.

 

Thanks toxie and DJRobX (and all others who helped out) for all the hard work enabling this!

Edited by senseless, 21 November 2016 - 09:43 PM.

[chokeee]

I have the flipper lag in True Full Screen and no lag in Windowed Full Screen. I tryed many settings and the lag is still there. Before True Full Screen I didnt know that such a thing exists Of course in true Full Screen I see better performance and no stutters on "stutter tables" but the flipper lag is terrible. Any ideas?

[Kernel]

How many FPS do you have?

Anyway, try disable v-sync.

Edited by Kernel, 22 November 2016 - 09:55 AM.

[arngrim]

i like the true fullscreen but i don't use it since i have to switch to non true full screen everytime i have to use pbx recorder, so i am lazy and stays on windowed fullscreen..

Sent from tapatalk

[gStAv]

But I can record with pbx latest version in true fs. f4v files that is (or what they are called) without switching

[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.

[Drybonz]

Yes... it works perfectly with PBX for me.  I have never had a problem with it.  You may want to post problems on the PBX forums... I think someone already had a thread about it maybe.

[arngrim]

But I can record with pbx latest version in true fs. f4v files that is (or what they are called) without switching

i don't get it the link between pbx and vp fullscreen, it is vp that handles true fullscreen, what does pbx do more?
, i record outside pbx by drag and drop a vp file to recorder exe and you?

Sent from tapatalk

[gStAv]

Wow, sounds advanced. I just run the PBX, and first time you have to spec the pinballx folder. Then length of video and what you want like bg/pf/dmd poc and/or vid + length, as you know. After that I use the 1st option to rec only missing media and away it goes through the db from pinballx.

If it finds a tsble it loads it automatically and after x sec of rec it encodes it and places it in correct media folder.

So I jusy delet old media for newer tables and run it.

Don't know uf it also works for mp4 but I think it is same-o in size and quality?

Maybe the drag-drop option is whats sinks your boat then...

[DJRobX]

i like the true fullscreen but i don't use it since i have to switch to non true full screen everytime i have to use pbx recorder, so i am lazy and stays on windowed fullscreen..

Sent from tapatalk

 

I just made a .reg export that sets it back to non true full screen and launch that before pbxrecorder, and launch another .reg that puts it back when it's done.

How many FPS do you have?

Anyway, try disable v-sync.

 

And the corollary - if not using vsync, try enabling it.   VPX only works smoothly on my cab when it's on.    Don't really know why.    VP PhysMod is not great either, but old VP9.2 is pretty smooth (thank god, since you can't use VSync on that!)

 

I have tried version 2.25 and version 2.28 w and w/o the full screen hack checked in pinball x setting.  I still continue to get the direct2bs failure.  I have even tried loading it via the "other systems" loader within pinball x.  Any thoughts on what to try next? 

 

 

Some have suggested just leaving a copy of task manager running.   I wish this reproduced on my system, I'm sure I could fix it if it did.   It has something to do with the B2SBackglassServerEXE not being able to find the VP process.  

Edited by DJRobX, 23 November 2016 - 07:22 AM.