1972 replies to this topic

[JulianR]

Hi, I noticed in VPX 10.8 the message sign that says "3D Stereo is enabled but currently toggled off..." shows in the middle of the playfield and stays there for a very long time. This is quite annoying in my current setup. In previous versions it was showing on top of the playfield and only for a few seconds.

Is there a way to restore that sign to the way it behaves in 10.7? Can I do something to prevent that for showing? 

 

Thank you very much!

Julian

[am1001]

Hi. Not sure if this is possible - but when I open a VPX table in VR mode I can move the table up and down but not move it forwards and backwards not change angle of tilt of the table or field of view etc. I have adjusted the interactive controls but when I resume table it goes back to the default view. It works non-vr but not in vr.

Does anyone know how to easily do this.

Thanks

Alistair

[studlygoorite]

Hi. Not sure if this is possible - but when I open a VPX table in VR mode I can move the table up and down but not move it forwards and backwards not change angle of tilt of the table or field of view etc. I have adjusted the interactive controls but when I resume table it goes back to the default view. It works non-vr but not in vr.

Does anyone know how to easily do this.

Thanks

Alistair

Not sure what headset you are using but if using Meta Quest for example, be sure to center your view to where you will be standing when playing before launching a table. You shouldn't have to adjust tilt or FOV, Try with "Table Setup/Scale Table To Width (found in Preference/VR Settings) deselected, and when the table loads just hit "0" or "5" or whatever button you have assigned to center your table.

[dacstyle]

Hello friends, I just wanted to let you know that if you enable the MSAA Samples, you will not be able to edit the POV in the new window mode. It may mess up some textures, like ramps.

[studlygoorite]

Staged Flippers you say?  https://github.com/v...runs/5777069359

[wiesshund]

Staged Flippers you say?  https://github.com/v...runs/5777069359

 

Yes, keep in mind that(the machine translation) only pertains to 1 table (that i personally know of, there may be two actually)
Grand Lizard is a deviation from the normal use of the system 11 controller.
Like LTD did with the LTD4 controller in Haunted Hotel, Williams stole inputs and outputs, and reprogrammed the controller to have a staged right upper flipper (but not the upper left flipper)

 

May want to read over this thread
Please allow mapping of staged flippers in VPX · Issue #651 · vpinball/vpinball (github.com)

[jpsalas]

Hi toxie & vbousquet, maybe this error means something to you. It happens quite often when I run a table and I press q to go back to the editor, then it crashes with this error. It doesn't happen all the time, only from time to time. I use the vpx8 dx9 x86 version, and it happens on all the version numbers I have tried:

 

 

Crash report VPX rev1347 (3d585e7)

============

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00436C9B

Attempt to write to 0x274011D4

Thread ID: 0x1B80 [7040]

 

Call stack

==========

00436C9B VPinballX.exe (0x00000010 0x00000000 0x00000000 0x0004081c)

00575941 VPinballX.exe (0x00000010 0x00000000 0x00000000 0x00000010)

00436697 VPinballX.exe (0x00436640 0x0004081C 0x00000010 0x00000000)

77073026 USER32.dll CallWindowProcW + 0x716 (0x00436640 0x00000000 0x00000010 0x00000000)

77072AAA USER32.dll CallWindowProcW + 0x19A (0x040D96B0 0x00000000 0x00000010 0x00000000)

7707C98F USER32.dll GetPropW + 0xFF (0x0019EF8C 0x00000020 0x0019F0A4 0x77d286a0)

77D2876D ntdll.dll KiUserCallbackDispatcher + 0x4D (0x040D96B0 0x00000000 0x00000000 0x00000001)

77088928 USER32.dll SetWindowsHookExAW + 0x198 (0x00000000 0x00000000 0x00000001 0x2f13f380)

770E56FD USER32.dll SendMessageA + 0x3D (0x0004081C 0x00000010 0x00000000 0x00000000)

 

Environment

===========

Date/time: 7/8/2023, 02:57:10:875

Number of CPUs: 16

Processor type: 586

System: Windows 10 (10.0 22621)

 

Memory status

=============

Total Reserved: 234368K (228M) bytes

Total Commited: 869504K (849M) bytes

Total Free: 3090368K (3017M) bytes

Largest Free: 2095668K (2046M) bytes

 

Registers

=========

EAX=00000000 EBX=00000000 ECX=0019F1A8 EDX=03719D10

ESI=274011D0 EDI=00000010 EBP=00000000 ESP=0019F058 EIP=005730A4

FLG=00010206 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

 

Mini dump saved successfully.

[Mike DA Spike]

If I set the 'Environment Emission' through the 'Adjust camera' dialog for VR and I save the POV, the next time it launcges yhe table, this setting is set to default again.
Should this setting be writen to the <customsettings> as well in the pov file?
If this should be written, I could create a github issue, but not sure if it is a bug, or if its just me

[wiesshund]

If I set the 'Environment Emission' through the 'Adjust camera' dialog for VR and I save the POV, the next time it launcges yhe table, this setting is set to default again.
Should this setting be writen to the <customsettings> as well in the pov file?
If this should be written, I could create a github issue, but not sure if it is a bug, or if its just me

 

that "SHOULD" be saved in the POV and override the defaults on table load

It is NOT being saved in the POV as i just made a POV and looked, and its missing.

Even if you use legacy POV it is missing

Open a bug

<?xml version="1.0" encoding="UTF-8"?>
<POV>
    <desktop>
        <LayoutMode>0</LayoutMode>
        <inclination>0</inclination>
        <fov>45.000076</fov>
        <layback>-9.7999907</layback>
        <lookat>51.799725</lookat>
        <rotation>0</rotation>
        <xscale>1</xscale>
        <yscale>1</yscale>
        <zscale>1</zscale>
        <xoffset>0</xoffset>
        <yoffset>-57.458069</yoffset>
        <zoffset>-563.10327</zoffset>
        <ViewHOfs>0</ViewHOfs>
        <ViewVOfs>14</ViewVOfs>
        <WindowTopXOfs>0</WindowTopXOfs>
        <WindowTopYOfs>0</WindowTopYOfs>
        <WindowTopZOfs>370.54193</WindowTopZOfs>
        <WindowBottomXOfs>0</WindowBottomXOfs>
        <WindowBottomYOfs>0</WindowBottomYOfs>
        <WindowBottomZOfs>138.95322</WindowBottomZOfs>
    </desktop>
    <fullscreen>
        <LayoutMode>2</LayoutMode>
        <inclination>2</inclination>
        <fov>77</fov>
        <layback>70.099998</layback>
        <lookat>25</lookat>
        <rotation>270</rotation>
        <xscale>0.88400149</xscale>
        <yscale>0.94400072</yscale>
        <zscale>1</zscale>
        <xoffset>0</xoffset>
        <yoffset>370.54193</yoffset>
        <zoffset>1296.8967</zoffset>
        <ViewHOfs>0</ViewHOfs>
        <ViewVOfs>-10.100002</ViewVOfs>
        <WindowTopXOfs>0</WindowTopXOfs>
        <WindowTopYOfs>0</WindowTopYOfs>
        <WindowTopZOfs>258.54193</WindowTopZOfs>
        <WindowBottomXOfs>0</WindowBottomXOfs>
        <WindowBottomYOfs>0</WindowBottomYOfs>
        <WindowBottomZOfs>138.95322</WindowBottomZOfs>
    </fullscreen>
    <fullsinglescreen>
        <LayoutMode>1</LayoutMode>
        <inclination>1</inclination>
        <fov>77</fov>
        <layback>15</layback>
        <lookat>50</lookat>
        <rotation>0</rotation>
        <xscale>1</xscale>
        <yscale>1</yscale>
        <zscale>1</zscale>
        <xoffset>0</xoffset>
        <yoffset>370.54193</yoffset>
        <zoffset>1296.8967</zoffset>
        <ViewHOfs>0</ViewHOfs>
        <ViewVOfs>22</ViewVOfs>
        <WindowTopXOfs>0</WindowTopXOfs>
        <WindowTopYOfs>0</WindowTopYOfs>
        <WindowTopZOfs>370.54193</WindowTopZOfs>
        <WindowBottomXOfs>0</WindowBottomXOfs>
        <WindowBottomYOfs>0</WindowBottomYOfs>
        <WindowBottomZOfs>138.95322</WindowBottomZOfs>
    </fullsinglescreen>
    <customsettings>
        <SSAA>-1</SSAA>
        <postprocAA>-1</postprocAA>
        <ingameAO>-1</ingameAO>
        <ScSpReflect>-1</ScSpReflect>
        <FPSLimiter>-1</FPSLimiter>
        <OverwriteDetailsLevel>0</OverwriteDetailsLevel>
        <DetailsLevel>5</DetailsLevel>
        <BallReflection>-1</BallReflection>
        <BallTrail>-1</BallTrail>
        <BallTrailStrength>0.49019608</BallTrailStrength>
        <OverwriteNightDay>0</OverwriteNightDay>
        <NightDayLevel>52</NightDayLevel>
        <GameplayDifficulty>20</GameplayDifficulty>
        <PhysicsSet>0</PhysicsSet>
        <IncludeFlipperPhysics>0</IncludeFlipperPhysics>
        <SoundVolume>100</SoundVolume>
        <SoundVMusicVolumeolume>100</SoundVMusicVolumeolume>
    </customsettings>
</POV>

[Mike DA Spike]

If I set the 'Environment Emission' through the 'Adjust camera' dialog for VR and I save the POV, the next time it launcges yhe table, this setting is set to default again.
Should this setting be writen to the <customsettings> as well in the pov file?
If this should be written, I could create a github issue, but not sure if it is a bug, or if its just me

 
that "SHOULD" be saved in the POV and override the defaults on table load
It is NOT being saved in the POV as i just made a POV and looked, and its missing.
Even if you use legacy POV it is missing

Open a bug

<?xml version="1.0" encoding="UTF-8"?>
<POV>
    <desktop>
        <LayoutMode>0</LayoutMode>
        <inclination>0</inclination>
        <fov>45.000076</fov>
        <layback>-9.7999907</layback>
        <lookat>51.799725</lookat>
        <rotation>0</rotation>
        <xscale>1</xscale>
        <yscale>1</yscale>
        <zscale>1</zscale>
        <xoffset>0</xoffset>
        <yoffset>-57.458069</yoffset>
        <zoffset>-563.10327</zoffset>
        <ViewHOfs>0</ViewHOfs>
        <ViewVOfs>14</ViewVOfs>
        <WindowTopXOfs>0</WindowTopXOfs>
        <WindowTopYOfs>0</WindowTopYOfs>
        <WindowTopZOfs>370.54193</WindowTopZOfs>
        <WindowBottomXOfs>0</WindowBottomXOfs>
        <WindowBottomYOfs>0</WindowBottomYOfs>
        <WindowBottomZOfs>138.95322</WindowBottomZOfs>
    </desktop>
    <fullscreen>
        <LayoutMode>2</LayoutMode>
        <inclination>2</inclination>
        <fov>77</fov>
        <layback>70.099998</layback>
        <lookat>25</lookat>
        <rotation>270</rotation>
        <xscale>0.88400149</xscale>
        <yscale>0.94400072</yscale>
        <zscale>1</zscale>
        <xoffset>0</xoffset>
        <yoffset>370.54193</yoffset>
        <zoffset>1296.8967</zoffset>
        <ViewHOfs>0</ViewHOfs>
        <ViewVOfs>-10.100002</ViewVOfs>
        <WindowTopXOfs>0</WindowTopXOfs>
        <WindowTopYOfs>0</WindowTopYOfs>
        <WindowTopZOfs>258.54193</WindowTopZOfs>
        <WindowBottomXOfs>0</WindowBottomXOfs>
        <WindowBottomYOfs>0</WindowBottomYOfs>
        <WindowBottomZOfs>138.95322</WindowBottomZOfs>
    </fullscreen>
    <fullsinglescreen>
        <LayoutMode>1</LayoutMode>
        <inclination>1</inclination>
        <fov>77</fov>
        <layback>15</layback>
        <lookat>50</lookat>
        <rotation>0</rotation>
        <xscale>1</xscale>
        <yscale>1</yscale>
        <zscale>1</zscale>
        <xoffset>0</xoffset>
        <yoffset>370.54193</yoffset>
        <zoffset>1296.8967</zoffset>
        <ViewHOfs>0</ViewHOfs>
        <ViewVOfs>22</ViewVOfs>
        <WindowTopXOfs>0</WindowTopXOfs>
        <WindowTopYOfs>0</WindowTopYOfs>
        <WindowTopZOfs>370.54193</WindowTopZOfs>
        <WindowBottomXOfs>0</WindowBottomXOfs>
        <WindowBottomYOfs>0</WindowBottomYOfs>
        <WindowBottomZOfs>138.95322</WindowBottomZOfs>
    </fullsinglescreen>
    <customsettings>
        <SSAA>-1</SSAA>
        <postprocAA>-1</postprocAA>
        <ingameAO>-1</ingameAO>
        <ScSpReflect>-1</ScSpReflect>
        <FPSLimiter>-1</FPSLimiter>
        <OverwriteDetailsLevel>0</OverwriteDetailsLevel>
        <DetailsLevel>5</DetailsLevel>
        <BallReflection>-1</BallReflection>
        <BallTrail>-1</BallTrail>
        <BallTrailStrength>0.49019608</BallTrailStrength>
        <OverwriteNightDay>0</OverwriteNightDay>
        <NightDayLevel>52</NightDayLevel>
        <GameplayDifficulty>20</GameplayDifficulty>
        <PhysicsSet>0</PhysicsSet>
        <IncludeFlipperPhysics>0</IncludeFlipperPhysics>
        <SoundVolume>100</SoundVolume>
        <SoundVMusicVolumeolume>100</SoundVMusicVolumeolume>
    </customsettings>
</POV>

Done https://github.com/v...ball/issues/668

[wiesshund]

Staged Flippers you say?  https://github.com/v...runs/5777069359

 

If you are interested, i have made actually a lot of headway in actually implementing staged flippers
without resorting to script hacking etc.

Making script correct is required though, which i have noticed a lot of tables people are pointing me to do are not, but the corrections are easy.

[Mrtr32]

After testing VPX8 Beta latest build, most tables seems to work very well so the Whirlwind 4K from flupper1 don't work.

 

Trying to add coins and start the table without success and pinball missing warning appear.

 

The table play fine with the latest VPX7 build from github (same setup).

 

Is someone having the same issue?

Edited by Mrtr32, 07 August 2023 - 10:08 PM.

[tosay]

After testing VPX8 Beta latest build, most tables seems to work very well so the Whirlwind 4K from flupper1 don't work.

 

Trying to add coins and start the table without success and pinball missing warning appear.

 

The table play fine with the latest VPX7 build from github (same setup).

 

Is someone having the same issue?

 

I'm having an issue that sounds similar, with tables Blood Machines and Iron Man Vault Edition (VPW). Blood Machines won't start, and Iron Man won't register coins (then if I hit 7 to add a credit it still won't start).

 

I'm using 64-bit Beta4. I didn't see those problems in Beta3, so I opened an issue just now in github: https://github.com/v...ball/issues/669

[jpsalas]

Whirlwind 4K from flupper1 works very well with VPX8, I guess your problem is a rom problem, delete the nvram to reset the rom, and I'm sure it will work again.

And the problem with Blood Machines and Iron Man Vault Edition (VPW),  may be that you are using the 64 bits VPX but you do not have the pup system in 64 bits too. Both tables are using the PuP system, so try first with the 32 bits (x86) version of VPX8, and if they work, then you need to update to 64 bit the PuP and maybe other addons you may have.

[Mrtr32]

Thanks for the tip JP!

 

I'm using whirl_l3.zip rom from vpuniverse since a years

 

Tested ipdb rom version with the same result, the table dont accept coins and is not playable.

 

Flushed nvram and cfg rom files before testing.

 

I'm on my Windows 7 Pro test computer with NVIDIA Gforce GTX 1660 ti

Whirlwind 4k V1.1 downloaded from vpforums.org

 

If I revert back to VPX7, i'm having no issues with the table and the rom.

Edited by Mrtr32, 08 August 2023 - 12:04 PM.

[Mike DA Spike]

Thanks for the tip JP!
 
I'm using whirl_l3.zip rom from vpuniverse since a years
 
Tested ipdb rom version with the same result, the table dont accept coins and is not playable.
 
Flushed nvram and cfg rom files before testing.
 
I'm on my Windows 7 Pro test computer with NVIDIA Gforce GTX 1660 ti
Whirlwind 4k V1.1 downloaded from vpforums.org
 
If I revert back to VPX7, i'm having no issues with the table and the rom.

What version of vpinmame are you using ?

[Mrtr32]

VPinMAME-sc-3.6-369-102e419-win-x86

 

Tried the latest VPinMAME-sc-3.6-483-88b80ab-win-x86 version with same result.

 

[tosay]

And the problem with Blood Machines and Iron Man Vault Edition (VPW),  may be that you are using the 64 bits VPX but you do not have the pup system in 64 bits too. Both tables are using the PuP system, so try first with the 32 bits (x86) version of VPX8, and if they work, then you need to update to 64 bit the PuP and maybe other addons you may have.

 

Thanks JP. I had installed the "PinUP Player x64 Plug-in/Drivers" (assuming that's what you mean). But I also tried the latest 32-bit VPX 10.8 (build 1348) and still had the problem. And yet I don't have either problem with the X64 Beta3 version. It's really strange, since another user couldn't duplicate either issue (although I did see another report of the Blood Machines problem on that table's discussion). There must be some other factor here.

[Drybonz]

 But I also tried the latest 32-bit VPX 10.8 (build 1348) and still had the problem. 

 

Unless I'm misunderstanding your problem, you have to have all the same parts... all x64 vpx, b2s, PuP, etc... any part you are using has to be x64 if you want to run the heavier x64 tables.

[IOIIOOO]

I'm a little confused by the Direct X vs GL versions at this point.  if I am manually updating the version that came with Baller Installer, would I update using the DirectX or GL version?