373 replies to this topic

[TerryRed]

can you show a dof log of a table with one of these b2s?

 

 

Do you mean by just loading the table like normal? That doesn't create a log for me, even though DOF settings shows its enabled.

[arngrim]

you need to define the location of log from the GlobalConfigEditor.exe

 

maybe you need to check your version of .net installed, that it is not the latest

Edited by arngrim, 10 September 2016 - 06:33 AM.

[tspeirs]

I think Terrys issues may be taking us a bit off track with something else and I am not aware why it would work as an external system and not internal. It basically does the same thing pretty much. So sorry, I am not going to address that right now.

Again if you can send me some files that don't work I can test.

[doogie2301]

plus running in standard mode will beat your system into submission... 

 

I don't know, now that I've tried it for a bit, I don't really see much difference, except for a few backglasses that have some crazy lighting going on.  Maybe it's because I have a newish system, although I do have a low end CPU.  Anyway, is there some way to get in touch with Herweh to see if we can get the code for debugging?

[arngrim]

we tried for 2 years to have the code from herweh, without success

[TerryRed]

you need to define the location of log from the GlobalConfigEditor.exe

 

maybe you need to check your version of .net installed, that it is not the latest

 

My location is defined in the GCE. My .net are all up to date, 64 and 32 bit.

 

Do I just run the table from PBX like normal, and the log should be created?

 

 

 

I'm apparently not the only one with this issue.  Not sure what is going on...

Edited by TerryRed, 10 September 2016 - 06:00 PM.

[arngrim]

dof needs to run to write dof logs

[tspeirs]

Just an update. Unfortunately it all works perfectly for me and I cannot duplicate any issues. Maybe because the PC is pretty high Spec. Its an i7 3770. I also have a real DMD but I tested showing the PinMAME window and it still all works fine.

[hauntfreaks]

we tried for 2 years to have the code from herweh, without success

 

 and that some real BS right there... now were stuck with an antiquated piece of software that doesn't even understand the commands copy and paste... 

[arngrim]

that's the main reason we want vp with multiple screens and b2s integrated

[doogie2301]

we tried for 2 years to have the code from herweh, without success

 

That's too bad.  I just discovered an awesome feature I didn't know existed, you can have table-specific ScreenRes files, however it doesn't seem to work in EXE mode, only in Standard.

[TerryRed]

 

we tried for 2 years to have the code from herweh, without success

 

That's too bad.  I just discovered an awesome feature I didn't know existed, you can have table-specific ScreenRes files, however it doesn't seem to work in EXE mode, only in Standard.

 

 

Yah, I found that a while back... bummer that it only works in Standard.

[doogie2301]

 

 

we tried for 2 years to have the code from herweh, without success

 

That's too bad.  I just discovered an awesome feature I didn't know existed, you can have table-specific ScreenRes files, however it doesn't seem to work in EXE mode, only in Standard.

 

 

Yah, I found that a while back... bummer that it only works in Standard.

 

 

As a workaround, I just whipped up a quick and dirty little app that will replace the screenres.txt with the custom table .res file if it exists (and rename the original).  It takes the table filename as the parameter, or "reset" to set it back to what it was.  Now in PinballX I have these launch before and after settings:

 

 

Here's the app if you're interested: https://www.dropbox....eenRes.zip?dl=0.  Needs .NET framework 4.5.2 at a minimum I believe, and like I said it's quick and dirty so there's no error handling or logging if something doesn't work.  In case anyone is wondering why I wanted to do this, I don't like the 4:3 backglasses being stretched to widescreen, so my default screenres has a 4:3 resolution, and now I have custom screenres files for the handful of backglasses that are designed for widescreen.

[TerryRed]

 

 

 

we tried for 2 years to have the code from herweh, without success

 

That's too bad.  I just discovered an awesome feature I didn't know existed, you can have table-specific ScreenRes files, however it doesn't seem to work in EXE mode, only in Standard.

 

 

Yah, I found that a while back... bummer that it only works in Standard.

 

 

As a workaround, I just whipped up a quick and dirty little app that will replace the screenres.txt with the custom table .res file if it exists (and rename the original).  It takes the table filename as the parameter, or "reset" to set it back to what it was.  Now in PinballX I have these launch before and after settings:

 

 

Here's the app if you're interested: https://www.dropbox....eenRes.zip?dl=0.  Needs .NET framework 4.5.2 at a minimum I believe, and like I said it's quick and dirty so there's no error handling or logging if something doesn't work.  In case anyone is wondering why I wanted to do this, I don't like the 4:3 backglasses being stretched to widescreen, so my default screenres has a 4:3 resolution, and now I have custom screenres files for the handful of backglasses that are designed for widescreen.

 

 

After being able to custom size my backglasses to ANY size very easily in BAM for Future Pinball.... I too hate having to squish a 4:3 backglass into 16:9 in VP.  So I was trying to do the same thing for the same reason.

 

I'll have to give that a go when I have more time.

[Carny_Priest]

I'm finally getting around to configuring VPX to run full screen for all my VPX tables. Unfortunately, my DMD screen goes to black every time I try to run in true fullscreen mode. I don't recall that happening when I was testing this earlier. I don't know if it is a NVidia driver thing (I'm using the current driver) or a 1.2 beta thing (r2794). I run a custom resolution on my third display (768 x 432), so I already run most of the VPM DMD games with ddraw=0. Anyone else been having a similar issue?

[TerryRed]

I'm finally getting around to configuring VPX to run full screen for all my VPX tables. Unfortunately, my DMD screen goes to black every time I try to run in true fullscreen mode. I don't recall that happening when I was testing this earlier. I don't know if it is a NVidia driver thing (I'm using the current driver) or a 1.2 beta thing (r2794). I run a custom resolution on my third display (768 x 432), so I already run most of the VPM DMD games with ddraw=0. Anyone else been having a similar issue?

 

Did you by chance do the Windows 10 anniversary update? I did, and it got rid of any custom nvidia settings I had including custom resolutions. Once I recreated my custom resolutions again, it was good to go.

 

Check what kind of scaling method is being used as well as "content type reported to display" which I always have set to "Desktop".   Check to see what is being reported by your display screen (info button) to see if its's blanking out because the freq is out of range,etc....

[Carny_Priest]

It seems to be coming from a slight difference in refresh rate between the DMD monitor and the playfield monitor (60.016Hz vs 60.000Hz). If I use a standard resolution at exactly 60Hz the DMD does not go black. Now, I am trying to figure out how to dial in my custom resolution to be exactly 60Hz and then trick Windows into using it as a standard resolution so that I can run DSR downsampling. Hmm, I didn't have to worry about getting the refresh rate exactly right before true full screen.

[hauntfreaks]

I've seen it come up more lately that people have solved many of these issues like shutter, ripping, slow downs and blank screens by making sure all the monitors are at the same Hz

so I think you're for sure on the right path

[TerryRed]

Sometimes changing the "scaling method" to "perform scaling on - GPU" and "Override scaling mode set by games and programs"...forces your screen to only be scaled by your GPU (instead of the display), and NEVER uses a different freq / resolution. So a custom resolution of 768x432 would still be outputting your monitor's native resolution / freq (confirmed with the "info" button/menu), but the video card will do the scaling instead of the monitor.

 

 This is how I get 21:9 PC gaming with my 4K 16:9 UHD TV at 3840x1640 instead of 3840x2160.

[Carny_Priest]

Sometimes changing the "scaling method" to "perform scaling on - GPU" and "Override scaling mode set by games and programs"...forces your screen to only be scaled by your GPU (instead of the display), and NEVER uses a different freq / resolution. So a custom resolution of 768x432 would still be outputting your monitor's native resolution / freq (confirmed with the "info" button/menu), but the video card will do the scaling instead of the monitor.

 

 This is how I get 21:9 PC gaming with my 4K 16:9 UHD TV at 3840x1640 instead of 3840x2160.

 

Thanks for the tip. This works for me for getting the refresh rate all synced. Got it worked out now.

 

I found that I have to have the GPU do some upscaling now where I could go 1:1 before, but I can retain the aspect ratio so I am good with that.