4027 replies to this topic

[studlygoorite]

I'll be damned, I just fixed it  

I opened task manager, right clicked "OVRServer_x64.exe and changed it from "normal" priority to "high" priority. All three of these tables now load correctly every time. Just like it says to do in Toby's tutorial, pretty sure I had done it before but maybe an updated something or other switched it back. 

 

Update, after switching back to the regular VPVR 10.7 the tables would not launch again...even after going back to the debug version but after some trial and error I could launch them again. Long story short, it looks like when I swap between VPVR 10.6 and 10.7 (any build) I have to reboot my system and check the setting above to get certain tables to play in 10.7

Edited by studlygoorite, 27 May 2022 - 01:31 PM.

[toxie]

What the.. .. .. This is maximum weird..  :/

@studlygoorite

 

In Visual Pinball Video/Graphics Options:

 

Do you have Maximum Pre-Rendering Frames value at 1 or other value than 0?

 

I experienced some table loading crash issues with this value at 1

 

After changing this value to 0 solved the loading tables issues.

Also extremely weird. Again something i cannot explain.  :/

[Mrtr32]

On a table that causing vpx crash at loading:

I reduced the resolution/size of some high resolution object texture in the image manager and no crash at start

The crash seems related to images size, Pre-Rendring frame value other than 0 and video driver at 4k resilution.

Im running with RTX 3090 at 4k UHD resolution and the lastest Nvidia driver on my new cab.

The same table without any changes dont crash at start with my gforce 1660 ti at 1080p resolution on my old computer

I dont know if the same table crash vpx with AMD video card?

Vpx is rendering the table at loading.

 

 

Here is the two affected tables in 4k setup only on my new Cab with RTX 3090 4k UHD video card:

 

 

Reducing texture of some images size solve the problem for this table:

 

https://www.dropbox.... fixed.rar?dl=0

 

Changing Pre-Rendring frame value from 1 to 0 solve the problem for this other one:

 

https://www.dropbox....2)V1.1.zip?dl=0

Edited by Mrtr32, 27 May 2022 - 12:48 PM.

[studlygoorite]

FYI, 

I just tried the new build "VPinballX_GL-10.7.1-81-40ae29c-Release-win-x86" and had issues. The changelog states " Updated OpenVR to SDK 1.16.8 (currently disabled as its not working with OpenComposite yet, WIP https://gitlab.com/z...R/-/tree/openxr could maybe support it in theory though!)" so I tried a couple of tables with opencomposite (not knowing if the above info means this version of VPVR will "not" work with opencomposite) and the same without opencomposite using SteamVR. I had the same issues with both, 300 VR had a washed out playfield and AC/DC was very dark and did not show a DMD. Oh, and Flupper's Whirlwind still will not launch for me with VPVR 10.7.

[toxie]

Please then try: https://github.com/v...facts/260581783 / https://github.com/vpinball/vpvr/actions/runs/2439532443

(note that that one still has some issues with the DMD/textboxes on some tables, but may solve the other issues you're seeing)

 

 

For all 'normal' VPX users, please give https://github.com/v...7.1-187-ebe5596 a try. This features some UI improvements and a bit of VRAM memory usage savings by vbousquet. He's also currently working on improving main memory usage for textures (which is already done in the VPVR version above).

[studlygoorite]

Please then try: https://github.com/v...facts/260581783 / https://github.com/v...runs/2439532443

(note that that one still has some issues with the DMD/textboxes on some tables, but may solve the other issues you're seeing)

 

 

For all 'normal' VPX users, please give https://github.com/v...7.1-187-ebe5596 a try. This features some UI improvements and a bit of VRAM memory usage savings by vbousquet. He's also currently working on improving main memory usage for textures (which is already done in the VPVR version above).

Great stuff!!  Using VPinballX_GL-10.7.1-94-5d0bf64-Release-win-x86 

All tables load and load quickly...even Whirlwind!!  AC/DC was no longer too dark but 300 was still washed out and there were several DMD issues as you stated. I tested around 10 tables....Thanks

Edited by studlygoorite, 04 June 2022 - 03:33 PM.

[toxie]

Here is the DMD fixed version by vbousquet: https://github.com/v...7.1-102-f1f912d

 

The washed out problem, is it recent, and since which revision?

[studlygoorite]

Here is the DMD fixed version by vbousquet: https://github.com/v...7.1-102-f1f912d

 

The washed out problem, is it recent, and since which revision?

Very nice, v102 is the best yet!! Tested 30-ish tables and everything loaded and worked great!!. Tested the washed out tables 300 and WWF Royal Rumble and two other EM tables (out of 34 not bad) and they were still washed out.

Tested the washed out tables with 9 different versions of VPVR and all were good up to version 47 but then went washy starting at version 55 and stayed washy until this 102

Note, I did not swap out the openvr_api.dll and stayed with the opencomposite version. Thanks again to everyone working on this, me and I'm sure many others appreciate it greatly.

Edited by studlygoorite, 04 June 2022 - 09:50 PM.

[Mrtr32]

@toxie

 

Tried VPinballX-10.7.1-190-10a1d3c-Release-win-x86 and the table Tale From The Crypt VPW v1.22 don't start on my new CAB with RTX 3090 at 4k so start properly on my old computer at 1080p

Same VPX version on the two computer

 

Here is the link for the affected table.

 

https://www.dropbox.... v1.22.zip?dl=0

 

Thanks!

[studlygoorite]

@toxie

 

Tried VPinballX-10.7.1-190-10a1d3c-Release-win-x86 and the table Tale From The Crypt VPW v1.22 don't start on my new CAB with RTX 3090 at 4k so start properly on my old computer at 1080p

Same VPX version on the two computer

 

Here is the link for the affected table.

 

https://www.dropbox.... v1.22.zip?dl=0

 

Thanks!

The fix for this is in the comments....and thanks for this...I missed this update

change line 49 in the script to read like this

dim CabinetMode : CabinetMode = 0

[Mrtr32]

Thanks studlygoorite

 

dim CabinetMode : CabinetMode = 0 at line 49 don't fix de issue for me

 

The table stop loading and VPX stop working with no error message.

 

I don't use VR mode, only as desktop mode with VPX standard

Edited by Mrtr32, 05 June 2022 - 08:02 PM.

[Mrtr32]

Ok

After testing <Tale From The Crypt VPW v1.22> on my CAB with RTX3090 and lastest VPinballX-10.7.1-193-b50a24c-Release-win-x86, same issue, the table don't render completely and crash VPX!

 

I only changed the 3840 x 2160 resolution to 1920 x 1080 in the VPX Video/Graphics options in my cab and the table start without issues!

 

 

Here is my crash report:

 

Crash report VPX rev193 (b50a24c)
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00000000
Attempt to read from 0x00000000
Thread ID: 0x1D90 [7568]

Call stack
==========
00000000  (0x00000000 0x1540ADE0 0x6CFBE8C8 0x71d18b60)
71D18BB3 d3d9.dll (0x0019CE20 0x6CFBE8C0 0x6CFBE8C8 0x220d0f78)
71D04C20 d3d9.dll (0x71D38AD0 0x0019CE60 0x71D047E0 0x00000001)
71D04910 d3d9.dll (0x00000001 0x6CFBE8C0 0x154CE120 0x71d040ab)
71D047E0 d3d9.dll (0x6CFBE8C0 0x00000000 0x06E4BC90 0x0019f3c8)
004BA0C5 VPinballX.exe (0x06E4BC90 0x0019CEB0 0x00640C70 0x00000000)
005E4780 VPinballX.exe (0x00000001 0x00000000 0x035694C0 0x0019cedc)
005E05A6 VPinballX.exe (0x06E4BC90 0x00000000 0x035694C0 0x0019f3c8)
0056AA69 VPinballX.exe (0x035694CC 0x0019CF14 0x00640C70 0x00000000)
0058DAD3 VPinballX.exe (0x00000001 0x03547C70 0x035694C0 0x0019cf50)
0058D634 VPinballX.exe (0x035694CC 0x03547C70 0x000B06A6 0x6cc40d98)
0058CE61 VPinballX.exe (0x0019F3C8 0x00608CA6 0x00000001 0x0019f3c8)
0058CCD8 VPinballX.exe (0x000B06A6 0x0000BF13 0x005FD32F 0x0000bf13)
005F585A VPinballX.exe (0x00425D50 0x000F0696 0x0000BF13 0x000b06a6)
76D6714A user32.dll CallWindowProcW + 0x144A (0x00425D50 0x00000000 0x0000BF13 0x000b06a6)
76D66852 user32.dll CallWindowProcW + 0xB52 (0x03E03AA0 0x00000000 0x00000000 0x00000001)
76D8E1CC user32.dll SetWindowsHookExAW + 0x10C (0x000B06A6 0x00000000 0x00000001 0x000b06a6)
76D7DA3D user32.dll SendMessageA + 0x3D (0x000F0696 0x0000BF13 0x000B06A6 0x00000000)
005FBE48 VPinballX.exe (0x00425D50 0x000806FC 0x00000221 0x000b06a6)
76D6714A user32.dll CallWindowProcW + 0x144A (0x00425D50 0x00000000 0x00000221 0x000b06a6)
76D66852 user32.dll CallWindowProcW + 0xB52 (0x03E0EFE0 0x00000000 0x00000000 0x00000001)
76D8E1CC user32.dll SetWindowsHookExAW + 0x10C (0x000B06A6 0x00000000 0x00000001 0x03547c70)
76D7DA3D user32.dll SendMessageA + 0x3D (0x000806FC 0x00000221 0x000B06A6 0x00000000)
0058D27A VPinballX.exe (0x00000010 0x00000000 0x00000000 0x00000010)
00425DA7 VPinballX.exe (0x00425D50 0x000B06A6 0x00000010 0x00000000)
76D6714A user32.dll CallWindowProcW + 0x144A (0x00425D50 0x00000000 0x00000010 0x00000000)
76D66BDA user32.dll CallWindowProcW + 0xEDA (0x03DD0B50 0x00000000 0x00000010 0x00000000)user32
Environment
===========
Date/time: 5/6/2022, 15:31:11:831
Number of CPUs: 24
Processor type: 586
System: Windows 10 (10.0 22000)

Memory status
=============
Total Reserved: 102468K (100M) bytes
Total Commited: 2211256K (2159M) bytes
Total Free: 1880516K (1836M) bytes
Largest Free: 328356K (320M) bytes

Registers
=========
EAX=1540ADE0 EBX=220D0F78 ECX=00000000 EDX=6CFBE8C8
ESI=6D3DF760 EDI=00000000 EBP=0019D7E8 ESP=0019D7B4 EIP=76D6FAAF
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

Mini dump saved successfully.
 

Edited by Mrtr32, 06 June 2022 - 08:47 PM.

[wiesshund]

@Toxie

 

How is VPX version stamping tables?

Does not seem that it should be reporting this as a version number?

 

 

no such thing as 10.72 ?

[Thalamus]

There is ... anything since Vincents non pf prim collidable change. Still haven't seen this used yet, so, it is a very high chance that you can open it in 10.7.1x and just save it to get rid of the message. Or, better, get the newest. It has many great fixes now.

Edited by Thalamus, 06 June 2022 - 04:16 PM.

[wiesshund]

There is ... anything since Vincents non pf prim collidable change. 

 

Odd, they still version out for me at 10.7.1-193-b50a24c

[jpsalas]

 

There is ... anything since Vincents non pf prim collidable change. 

 

Odd, they still version out for me at 10.7.1-193-b50a24c

 

 

Yes, but is you save a table with this version, and then you try to open it in an older version, then you will get the message that this table was saved with 10.7.2 

[wiesshund]

 

 

There is ... anything since Vincents non pf prim collidable change. 

 

Odd, they still version out for me at 10.7.1-193-b50a24c

 

 

Yes, but is you save a table with this version, and then you try to open it in an older version, then you will get the message that this table was saved with 10.7.2 

 

 

That shouldn't be though, if possible
as it is misleading to the user.

I dropped that in the beta thread

[toxie]

@Toxie

 

How is VPX version stamping tables?

Does not seem that it should be reporting this as a version number?

 

 

no such thing as 10.72 ?

Yes, i know, its confusing. At some point we had to increase the file version one time more often than the actual release version. And since then we're still running one version ahead for the file version.  :/

(as the file version is independent of the release version number)

 

I dropped that in the beta thread

 

Where is that thread?

Also, for the others: Please test this new 10.7.1 beta build, as it has a lot of changes regarding texture memory usage (i.e. uses less now) by vbousquet!

https://github.com/v...7.1-196-993e8c4

Direct link: https://github.com/v...ase-win-x86.zip

 

Then in general a development update: fuzzel and me are both still 'suffering' from too much real life work, but fortunately great devs like vbousquet and jsm174 are moving VPX forward a lot at the moment (thanks for going through that pain )!

So look forward to 10.7.1 / 10.8 (or will it be even called VP11 then???).

[wiesshund]

So look forward to 10.7.1 / 10.8 (or will it be even called VP11 then???).

 

 

 

 

Just dont call it Visual Pinball ME
Pretty sure that naming convention carries a curse

[ryesteve]

Sorry to have to ask, because I'm sure it's been discussed, but I can't find it.  Is there a guide somewhere to configuring the global physics override sets?  I.e. different settings that would represent different eras/types of tables?