1972 replies to this topic

[Drybonz]

 notice playfield is visible?

 

Yeah... something in the script is definitely not working the same way it used to.

[wiesshund]

 

 notice playfield is visible?

 

Yeah... something in the script is definitely not working the same way it used to.

 

if you can isolate that, then we can see what is it doing and how is it trying to do it.
and how it relates to changes.

[Slydog43]

My VR issues seem very strange, but at least its not a VPX thing.  My Quest 2 on v51 of firmware worked great with the latest 10.8 GLx86, yeah!  It then upgraded to V53 and once again it seems fairly solid.  I'm running with Virtual Desktop over 5G WiFi.  Then I tried my Quest Pro with V53 and once again it is a stuttering mess.  I tried with a cable and its better but still not right.  Not sure what the F Meta are doing, but HMDs are definitely going down hill without John Carmack, very sad.  Hopefully it will get straightened out with new VD beta which I will try next.  

 

Anyone else using a Quest Pro?  How is your experience?  It did work great 6 months ago

 

VPX team, sorry not your fault.

 

Just figured it out, my Quest Pro was only connected to my VR PC via 2.4 Wifi, as soon as I changed to my dedicated 5G WiFi all is great again, sorry to waste everyone's time.  I'm such a moron most of the time

Edited by Slydog43, 30 May 2023 - 09:06 PM.

[studlygoorite]

My VR issues seem very strange, but at least its not a VPX thing.  My Quest 2 on v51 of firmware worked great with the latest 10.8 GLx86, yeah!  It then upgraded to V53 and once again it seems fairly solid.  I'm running with Virtual Desktop over 5G WiFi.  Then I tried my Quest Pro with V53 and once again it is a stuttering mess.  I tried with a cable and its better but still not right.  Not sure what the F Meta are doing, but HMDs are definitely going down hill without John Carmack, very sad.  Hopefully it will get straightened out with new VD beta which I will try next.  

 

Anyone else using a Quest Pro?  How is your experience?  It did work great 6 months ago

 

VPX team, sorry not your fault.

I am using Quest Pro and have no stuttering. I am on v54 using link, I do remember a few builds back where I had issues because the version in the headset and the PC version did not match, had to wait for the PC to catch up. I have tried VD wireless and had bad lag, found out it was the Oculus Debug Tool, I had "Encode Bitrate" (pretty sure is was that) set to 300 which was fine for wired (link) but did not work for wireless. Changing this setting back to default and my stuttering isses were gone.

[Drybonz]

Have reported at https://github.com/v...ball/issues/525

 

This was marked as fixed today.

[wiesshund]

 

 notice playfield is visible?

 

Yeah... something in the script is definitely not working the same way it used to.

 

 

 

Hey, i know what your issue is with defender.

Prim Object playfield mesh.
Turn off static rendering

[Drybonz]

Prim Object playfield mesh.

Turn off static rendering

Hey, i know what your issue is with defender.

 

Yeah, that was it.  Good call.  Do we know why this suddenly happened and if it's related to a change in the last few beta builds?

[wiesshund]

 

Prim Object playfield mesh.

Turn off static rendering

Hey, i know what your issue is with defender.

 

Yeah, that was it.  Good call.  Do we know why this suddenly happened and if it's related to a change in the last few beta builds?

 

It is due to some of the new rendering capabilities
Exactly which, off top of my head, i do not know.
I'd have to go through the logs of changes in 10.8

I think it has to do with how those particular prims are made
and what all is baked into them.

Because not all prims are affected, but a lot of prims are just simple ones.

[fripounet]

Crash report VPX GL rev1205 (1a70aa3)
============
Process: VPinballX_GL64.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0033:00007FFEB384FD23
Attempt to read from 0x6C539000
Thread ID: 0x14C4 [5316]

Call stack
==========
FFFFFFFFB384FD23  (0x00000000 0xFFFFFFFFB3801531 0x00007FFE 0x0000826b)

Environment
===========
Date/time: 31/5/2023, 01:07:24:189
Number of CPUs: 8
Processor type: 8664
System: Windows 10 (10.0 22621)

Memory status
=============
Total Reserved: 619064K (604M) bytes
Total Commited: 2634864K (2573M) bytes
Total Free: 940312K (918M) bytes
Largest Free: 3528128K (3445M) bytes

Registers
=========
RAX=00000001 RBX=8BAC7CF0 RCX=085C0000 RDX=0000824A
RSI=22B63A08 RDI=22B63A08 RBP=000186A0 RSP=0805FE10 RIP=B384FD23
FLG=00010216 CS=0033 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

 

[studlygoorite]

 

Prim Object playfield mesh.

Turn off static rendering

Hey, i know what your issue is with defender.

 

Yeah, that was it.  Good call.  Do we know why this suddenly happened and if it's related to a change in the last few beta builds?

 

With static rendering checked, VPX is supposed to disable any dynamic behavior but this was not always enforced with previous versions.

[wiesshund]

 

 

Prim Object playfield mesh.

Turn off static rendering

Hey, i know what your issue is with defender.

 

Yeah, that was it.  Good call.  Do we know why this suddenly happened and if it's related to a change in the last few beta builds?

 

With static rendering checked, VPX is supposed to disable any dynamic behavior but this was not always enforced with previous versions.

 

 

LoL
It be enforced now.
Seems to be turning off the entire behavior of the playfield.

On the upside, you can use the most amusing things for the backdrop.
It's now the Bettie Page table LOL

[Drybonz]

Well, this is good stuff to have documented in the beta thread for anyone else with similar problems.  Thanks for the help, I have it all set up now (fixed the rails too).

 

*edit*  Looks like this was just fixed actually, in build 1548, just now.  Thanks, Vbousquet.

Edited by Drybonz, 30 May 2023 - 11:37 PM.

[wiesshund]

Well, this is good stuff to have documented in the beta thread for anyone else with similar problems.  Thanks for the help, I have it all set up now (fixed the rails too).

 

*edit*  Looks like this was just fixed actually, in build 1548, just now.  Thanks, Vbousquet.

 

Kind of, but i cant tell if it is a "Fix" or a reversion of feature?

Have to wait for Vbousquet to clarify i guess.

Edited by wiesshund, 31 May 2023 - 01:45 AM.

[Cadorna]

Thanks to all of you for your hard work. I'm on VP 10.8.0 v1138 GL x64. 3D Stereo SBS does not work. Only the left side of the screen is shown and a black screen on the right side.

Edited by Cadorna, 01 June 2023 - 07:07 PM.

[Slydog43]

There is a newer build 1189 available, might as well upgrade and try that one.

[wiesshund]

@Toxie

Do you know why vidflashcap can not display any pixels from a freezy virtual DMD window?

i mean it does see the windows but the capture is just black.

[Cadorna]

There is a newer build 1189 available, might as well upgrade and try that one.

 

Thanks. Same thing with v1189

[Mike DA Spike]

 

• Is there a way to support screen recording with ffmpeg when using OpenGL?  For example, when initiated via PinballY frontend, this no longer to work and just records a black screen when using the GL version, but works fine for the 10.8 beta 2 non-GL version.  I did do a quick bit of research on their website but came up empty.  If it helps, below is an example of the CLI that's used.. I'm assuming use of GDI is the issue but not sure how/if this can be worked around?
  

  ffmpeg.exe" -y -loglevel warning -thread_queue_size 32  -f gdigrab -framerate 30 -offset_x 6400 -offset_y 0 -video_size 4096x2160 -i desktop -c:a none -t 15 -probesize 30M -rtbufsize 2000M  -c:v libx264 -threads 8 -qp 0 -preset ultrafast "C:\vp\apps\PinballX\Media\Visual Pinball\Table Videos\The Addams Family (Bally 1992).tmp.mkv"

 

When I record my screen via PinballX, the screen is captured completly :

ffmpeg.exe -f gdigrab -framerate 60 -offset_x 0 -offset_y 0 -video_size 3440x1440 -t 00:00:20 -i desktop -c:v libx265 -crf 25 -preset fast -pix_fmt yuv420p -movflags +faststart "test.mp4"

maybe try a later version of ffmpeg and change the GDIgrab to DDAgrab ( see https://ffmpeg.org/f...rs.html#ddagrab )

ffmpeg.exe   -filter_complex ddagrab=0,hwdownload,format=bgra -framerate 60 -offset_x 0 -offset_y 0 -video_size 3440x1440 -t 00:00:20 -c:v libx265 -crf 25 -preset fast -pix_fmt yuv420p -movflags +faststart "test.mp4"

Edited by Mike DA Spike, 02 June 2023 - 04:25 AM.

[StiggieV]

Oh wow! Thanks to everyone involved in this amazingness. This beta couldn't have come at a better time for me. I just days ago unboxed a new laptop with a gen12 i7 and rtx3070 that out performs my aging gen3 i7-3770k gtx1070 desktop setup by far. I played a bit of cyberpunk 2077 with the ray tracing on and it looked and played so good (first time ever using ray tracing). I just set out on a month long work trip (the reason for the laptop purchase) and sadly didn't think to pack my quest 2 headset, but i am so jazzed to get back home and get it working with this new build. I love vpvr on my old setup but always had to lower setting and mess with things to get decent fps on the 1070, now and then seeing glimpses of how great it could look but with bad fps. I can't wait to finally crank those settings up and actually have it playable, it's going to be so cool. It was a struggle for me to get vr working on my old setup, I couldnt find an up to date guide so there was allot of trial and error but I finally got it going. one of the head scratching hurdles I faced (and have seen others face in the forums) was mismatching the vpx version and the vpvr version, so this sweet merger should help allot of struggling people never have that problem again. Thank you!

Edited by StiggieV, 02 June 2023 - 07:15 PM.

[hitman2304]

There is new beta in town:

https://github.com/v...runs/5160713713