4027 replies to this topic

[wiesshund]

 

Hi toxie & fuzzel!

 

Here you have an update of the INDER VBS files. The only change is to set to default 5 key to add 1 coin instead of adding 4. Some Spanish people think that's better as it is easier for them to check how many extra games they have obtained

 

Inder_VBS.zip

 

Greetings

JP

 

Thanks JP, will exchange it!

 

 

There are a few translation files i changed
Generically i base it off of
5 coin slot 1 (single coin) 
6 coin slot 2 (single coin if exists)

7 coin slot 3 (Special if machine has a dollar coin or equivalent  type of denomination)

8 bill changer (If used by machine)

mind you i dont use 5 6 7 or 8 as i use the numpad inputs for all of that
but would be same equivalent 

Ive notice others that the default is a multi credit slot

[toxie]

Could you share these? Maybe we should make some of these changes official then?

Read the change log that comes with 10.7

Convenience: https://github.com/v...t/Changelog.txt

[jpsalas]

Hei toxie! You may remove my "arcade physics" files from the release zip, as not a single author have ever asked me about them nor used them in their tables, so I guess they are not needed. Keep the PhysicValues.txt as it is a nice explanation to the default VPX physics, and a good start point to tweak them

 

Thanks

JP

Edited by jpsalas, 21 May 2022 - 06:01 AM.

[wiesshund]

Hei toxie! You may remove my "arcade physics" files from the release zip, as not a single author have ever asked me about them nor used them in their tables, so I guess they are not needed. Keep the PhysicValues.txt as it is a nice explanation to the default VPX physics, and a good start point to tweak them

 

Thanks

JP

 

Hi, my name is chopped liver  

 

All of my tables were updated to JP physics, or came with them the 1st time.

Many of the "not mine" tables on my PC have JP physics, the author just didnt make them that way

[jpsalas]

 

Hei toxie! You may remove my "arcade physics" files from the release zip, as not a single author have ever asked me about them nor used them in their tables, so I guess they are not needed. Keep the PhysicValues.txt as it is a nice explanation to the default VPX physics, and a good start point to tweak them

 

Thanks

JP

 

Hi, my name is chopped liver

 

All of my tables were updated to JP physics, or came with them the 1st time.

Many of the "not mine" tables on my PC have JP physics, the author just didnt make them that way

 

 

I know about you wiesshund But those files just created confusion to the players. It is better with them removed from the official VPX release.

[toxie]

Really? I could also stuff them into a subdirectory then?

[jpsalas]

Really? I could also stuff them into a subdirectory then?

 

Authors are mostly doing their thing (only wiesshund seems to be using them) and many people just ask me what to do with those files.

[wiesshund]

 

Really? I could also stuff them into a subdirectory then?

 

Authors are mostly doing their thing (only wiesshund seems to be using them) and many people just ask me what to do with those files.

 

 

That is both funny and sad, considering you wrote up a nice little short and sweet included PDF doc that explains everything

[studlygoorite]

Curious, my issues persist with VPVR 10.7 (all versions) where some tables will not load, I was wondering if there is a hidden setting somewhere that would make VPVR try to load a table for a longer period of time before giving up? I have read that some have reported long loading times but I don't see that issue and maybe the tables that will not load for me need a bit longer. Note, I have no issues with VPX 10.7. Thanks

[toxie]

Is there some error message?

[studlygoorite]

Is there some error message?

Negative, I can see the loading bar move to full on the .exe but then it just disappears, this goes back to the beginning of March when I was testing the betas. I posted a crash.txt and jsm174 asked me to try the debug version but it still didn't show enough info as the pdb's didn't work....possibly because I have no developer tools on my machine.

[EdwardK]

 

 

Really? I could also stuff them into a subdirectory then?

 

Authors are mostly doing their thing (only wiesshund seems to be using them) and many people just ask me what to do with those files.

 

 

That is both funny and sad, considering you wrote up a nice little short and sweet included PDF doc that explains everything

 

I am not a table author, but I realized using the new physics helped many of the tables.  You just have to make sure that the new physics is mentioned in case someone like me wants to use it.  In my case, I just have to make sure that whatever is installed now is backed up.

Edited by EdwardK, 26 May 2022 - 01:10 AM.

[toxie]

 

Is there some error message?

Negative, I can see the loading bar move to full on the .exe but then it just disappears, this goes back to the beginning of March when I was testing the betas. I posted a crash.txt and jsm174 asked me to try the debug version but it still didn't show enough info as the pdb's didn't work....possibly because I have no developer tools on my machine.

 

Could you please retry with the current debug build? And post the crash.txt?

[studlygoorite]

 

 

Is there some error message?

Negative, I can see the loading bar move to full on the .exe but then it just disappears, this goes back to the beginning of March when I was testing the betas. I posted a crash.txt and jsm174 asked me to try the debug version but it still didn't show enough info as the pdb's didn't work....possibly because I have no developer tools on my machine.

 

Could you please retry with the current debug build? And post the crash.txt?

 

Sure can, this version here? VPinballX_GL-10.7.1-67-91a28b7-Debug-win-x86

[studlygoorite]

Using the above version trying to load Flupper's Whirlwind that launches fine with VPVR 10.6 

Crash report VPX GL rev67 (91a28b7)
============
Process: VPinballX_GL.exe
Reason: 0xE06D7363 - UNKNOWN at 0023:77B6C3A2
Thread ID: 0x810 [2064]

Call stack
==========
77B6C3A2 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE06D7363 0x00000001 0x00000003 0x044fc55c)
00C077C0 VPinballX_GL.exe (0x044FC5A8 0x00EFBD04 0xFFFFFFFFD45BD6F1 0x044fc880)
0056A743 VPinballX_GL.exe (0x000A056C 0x044FC824 0x4AC0BAD0 0x044fc88c)
005690D5 VPinballX_GL.exe (0x000A056C 0xFFFFFFFFD45BD679 0x044FC944 0x044fc8a8)
00613F83 VPinballX_GL.exe (0x4AC0BAD0 0x0DEBA9FC 0x044FC950 0x005f2352)
006102F5 VPinballX_GL.exe (0x00000000 0xFFFFFFFFD45BD7A5 0x044FD774 0x044fc968)
005F2352 VPinballX_GL.exe (0x4AC0BAD0 0x00D64E0C 0x00000000 0x00000000)
005F20AD VPinballX_GL.exe (0x4AC0BAD0 0x00D64E0C 0xFFFFFFFFD45BC975 0x044fd78c)
00665242 VPinballX_GL.exe (0x106FB3B4 0xFFFFFFFFD45BC65D 0x00000222 0x044fd90c)
00668FB7 VPinballX_GL.exe (0x106FB3B4 0xFFFFFFFFCCCCCCCC 0x044FF1B8 0x044fd8f8)
00B8CCA7 VPinballX_GL.exe (0x106FB3B4 0xFFFFFFFFD45BC60D 0x00000000 0xffffffffcccccccc)
00A5FE52 VPinballX_GL.exe (0x00000222 0x00000000 0x00012B50 0x044fd92c)
00AB8D5D VPinballX_GL.exe (0x00000222 0x00000000 0x00012B50 0x044fd948)
0056DDAD VPinballX_GL.exe (0x00000222 0x00000000 0x00012B50 0x00012b50)
0056D86D VPinballX_GL.exe (0x00012B50 0x00000222 0x00000000 0x00012b50)
772F0FCB USER32.dll AddClipboardFormatListener + 0x4B (0x005046D7 0x00012B50 0x00000222 0x00000000)
772E7F9A USER32.dll GetClassLongW + 0x7AA (0x005046D7 0x00000000 0x00000222 0x00000000)
772E7379 USER32.dll GetSystemMetricsForDpi + 0x1459 (0x04E56920 0x00000000 0x00012B50 0x00000000)
772E59AF USER32.dll SendMessageW + 0x6F (0x00012B50 0x00000222 0x00000000 0x00012b50)
772D0989 USER32.dll DefMDIChildProcA + 0x349 (0x04E617C0 0x00000000 0x04E56920 0x00000000)
772D074A USER32.dll DefMDIChildProcA + 0x10A (0x00000000 0x00000000 0x00000001 0x044fdb9c)
772D0658 USER32.dll DefMDIChildProcA + 0x18 (0x00012B50 0x00000022 0x00000000 0x00000000)
00AB5EFC VPinballX_GL.exe (0x00000022 0x00000000 0x00000000 0xffffffffd45bc0e1)
0056E200 VPinballX_GL.exe (0x00000022 0x00000000 0x00000000 0x044fde48)
00AB8DA1 VPinballX_GL.exe (0x00000022 0x00000000 0x00000000 0x044fde64)VPinbal
Environment
===========
Date/time: 26/5/2022, 11:19:46:454
Number of CPUs: 16
Processor type: 586
System: Windows 10 (10.0 19044)

Memory status
=============
Total Reserved: 108836K (106M) bytes
Total Commited: 1534868K (1498M) bytes
Total Free: 2550536K (2490M) bytes
Largest Free: 1692488K (1652M) bytes

Registers
=========
EAX=044FC4E8 EBX=005046D7 ECX=00000003 EDX=00000000
ESI=044FC58C EDI=044FC7F8 EBP=044FDE50 ESP=044FDE3C EIP=0056DDAD
FLG=00000216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

[studlygoorite]

Here is from trying to load Children Of The Corn in VR
 

Crash report VPX GL rev67 (91a28b7)

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

Process: VPinballX_GL.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00B8DEF1

Attempt to read from 0x00000BBC

Thread ID: 0x38FC [14588]

 

Call stack

==========

 (0x00000001 0x124D1090 0x0453C970 0x00982e0c)

 (0x00000002 0x0453C984 0xFFFFFFFFCCCCCCCC 0xffffffffcccccccc)

 (0x00000002 0x00000000 0x00000000 0x00112a46)

 (0x00112A46 0x00000002 0x00000000 0x00000000)

 (0x005046D7 0x00112A46 0x00000002 0x00000000)

 (0x005046D7 0x00000000 0x00000002 0x00000000)

 (0x00000002 0x00000000 0x00000000 0x00000000)

 (0xFFFFFFFFFFFF0B6F 0x00112A46 0x00000002 0x00000000)

 (0x00112A46 0x00000002 0x00000000 0x00000000)

 (0x00000002 0x00000000 0x00000000 0x00000002)

 (0x00000000 0x00000000 0x00000002 0x00112a46)

 (0x00112A46 0x00000002 0x00000000 0x00000000)

 (0x00000002 0x00000000 0x00000000 0x00000002)

 (0x00112A46 0x00000002 0x00000000 0x00000000)

 (0x71AC0970 0x00112A46 0x00000002 0x00000000)

 (0x71AC0970 0x00000000 0x00000002 0x00000000)

 (0x04FC3540 0x00000000 0x00000002 0x00000000)

 (0x0453CDBC 0x00000020 0x0453CE0C 0x77ce4db0)

 (0x00000000 0x0453EB18 0x0453F814 0x00c0cee7)

 (0x00000000 0x00000000 0x0453CE48 0x00000001)

 (0x004F0000 0x00000000 0x046E3C85 0x00000001)

 (0x39317BC3 0x004F15C3 0x004F15C3 0x04380000)

 (0x0453F8A0 0x00C04388 0x0453F8B0 0x7776fa29)

 (0x0453F8B0 0x7776FA29 0x04380000 0x7776fa10)

 (0x04380000 0x7776FA10 0x0453F90C 0x77cd7a7e)

 (0x04380000 0x2A8D7C56 0x00000000 0x00000000)

 (0xFFFFFFFFFFFFFFFF 0x77CF89ED 0x00000000 0x00000000)

 (0x004F15C3 0x04380000 0x00000000 0x00000000)

 

Environment

===========

Date/time: 26/5/2022, 11:37:16:61

Number of CPUs: 16

Processor type: 586

System: Windows 10 (10.0 19044)

 

Memory status

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

Total Reserved: 712112K (695M) bytes

Total Commited: 2429156K (2372M) bytes

Total Free: 1052972K (1028M) bytes

Largest Free: 269376K (263M) bytes

 

Registers

=========

EAX=00000000 EBX=005046D7 ECX=00000000 EDX=047D11FC

ESI=0453C984 EDI=0453C970 EBP=0453F91C ESP=0453F914 EIP=77CD7A4E

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

 

 

Failed to save minidump.

 

 

Lastly, trying to run the latest Space Shuttle VR (Note, attempt #2 the table loaded fine)
 

Crash report VPX GL rev67 (91a28b7)

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

Process: VPinballX_GL.exe

Reason: 0xE06D7363 - UNKNOWN at 0023:77B6C3A2

Thread ID: 0x4380 [17280]

 

Call stack

==========

77B6C3A2 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE06D7363 0x00000001 0x00000003 0x0453bfa8)

00C077C0 VPinballX_GL.exe (0x0453BFF4 0x00EFBD04 0xFFFFFFFFAFD54370 0x0453c2cc)

0056A743 VPinballX_GL.exe (0x00142AC6 0x0453C270 0x279AE7D0 0x0453c2d8)

005690D5 VPinballX_GL.exe (0x00142AC6 0xFFFFFFFFAFD543F8 0x0453C390 0x0453c2f4)

00613F83 VPinballX_GL.exe (0x279AE7D0 0x0E0E960C 0x0453C39C 0x005f2352)

006102F5 VPinballX_GL.exe (0x00000000 0xFFFFFFFFAFD542BC 0x0453D1C0 0x0453c3b4)

005F2352 VPinballX_GL.exe (0x279AE7D0 0x00D64E0C 0x00000000 0x00000000)

005F20AD VPinballX_GL.exe (0x279AE7D0 0x00D64E0C 0xFFFFFFFFAFD550EC 0x0453d1d8)

00665242 VPinballX_GL.exe (0x0F2DB064 0xFFFFFFFFAFD553D4 0x00000222 0x0453d358)

00668FB7 VPinballX_GL.exe (0x0F2DB064 0xFFFFFFFFCCCCCCCC 0x0453F268 0x0453d344)

00B8CCA7 VPinballX_GL.exe (0x0F2DB064 0xFFFFFFFFAFD55264 0x00000000 0xffffffffcccccccc)

00A5FE52 VPinballX_GL.exe (0x00000222 0x00000000 0x000B0E54 0x0453d378)

00AB8D5D VPinballX_GL.exe (0x00000222 0x00000000 0x000B0E54 0x0453d394)

0056DDAD VPinballX_GL.exe (0x00000222 0x00000000 0x000B0E54 0x000b0e54)

0056D86D VPinballX_GL.exe (0x000B0E54 0x00000222 0x00000000 0x000b0e54)

772F0FCB USER32.dll AddClipboardFormatListener + 0x4B (0x005046D7 0x000B0E54 0x00000222 0x00000000)

772E7F9A USER32.dll GetClassLongW + 0x7AA (0x005046D7 0x00000000 0x00000222 0x00000000)

772E7B9A USER32.dll GetClassLongW + 0x3AA (0x050335F0 0x00000000 0x00000222 0x00000000)

772EB75F USER32.dll CallNextHookEx + 0x19F (0x0453D56C 0x00000020 0x0453D930 0x77ce4db0)

77CE4E7D ntdll.dll KiUserCallbackDispatcher + 0x4D (0x050335F0 0x00000000 0x000B0E54 0x00000000)

772E59AF USER32.dll SendMessageW + 0x6F (0x000B0E54 0x00000222 0x00000000 0x000b0e54)

772D0989 USER32.dll DefMDIChildProcA + 0x349 (0x05031910 0x00000000 0x050335F0 0x00000000)

772D074A USER32.dll DefMDIChildProcA + 0x10A (0x00000000 0x00000000 0x00000001 0x0453d6c4)

772D0658 USER32.dll DefMDIChildProcA + 0x18 (0x000B0E54 0x00000022 0x00000000 0x00000000)

00AB5EFC VPinballX_GL.ex0056E200 VPinballX_GL.eVPinbal

Environment

===========

Date/time: 26/5/2022, 11:39:33:226

Number of CPUs: 16

Processor type: 586

System: Windows 10 (10.0 19044)

 

Memory status

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

Total Reserved: 112920K (110M) bytes

Total Commited: 1443372K (1409M) bytes

Total Free: 2637948K (2576M) bytes

Largest Free: 1477132K (1442M) bytes

 

Registers

=========

EAX=0453BF38 EBX=005046D7 ECX=00000003 EDX=00000000

ESI=0453BFD8 EDI=0453C244 EBP=0453D95C ESP=0453D944 EIP=00AB8DA1

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

 

 

Mini dump saved successfully.

[RYSr]

Curious, my issues persist with VPVR 10.7 (all versions) where some tables will not load, I was wondering if there is a hidden setting somewhere that would make VPVR try to load a table for a longer period of time before giving up? I have read that some have reported long loading times but I don't see that issue and maybe the tables that will not load for me need a bit longer. Note, I have no issues with VPX 10.7. Thanks

 

studlygoorite

I also had problems with tables that load fine in VPX 10.6 but crash in VPX10.7 during or just after loading, I noticed that the table rendered but the DMD was not loading then it crashed. I recently updated my  Freezy's DMDext files to version 1.10.2 x86 and most all of the crashes stopped happening. I was using version1.08 before that.

Edited by RYSr, 26 May 2022 - 07:58 PM.

[studlygoorite]

 

Curious, my issues persist with VPVR 10.7 (all versions) where some tables will not load, I was wondering if there is a hidden setting somewhere that would make VPVR try to load a table for a longer period of time before giving up? I have read that some have reported long loading times but I don't see that issue and maybe the tables that will not load for me need a bit longer. Note, I have no issues with VPX 10.7. Thanks

 

studlygoorite

I also had problems with tables that load fine in VPX 10.6 but crash in VPX10.7 during or just after loading, I noticed that the table rendered but the DMD was not loading then it crashed. I recently updated my  Freezy's DMDext files to version 1.10.2 x86 and most all of the crashes stopped happening. I was using version1.08 before that.

 

Thanks, unfortunately I have been on 1.10.2 since day one. Hopefully it's just something that needs an update as I don't know anyone else with the same issues, pretty sure everything is up to date though. People are still switching between using 10.6 shaders for 10.6 tables and 10.7 shaders with 10.7 but I haven't had to switch, staying with 10.7 shaders seems to be fine for my set up. 

[Mrtr32]

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

Edited by Mrtr32, 26 May 2022 - 10:16 PM.

[studlygoorite]

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

Thanks, just checked and yes I have it set to 1....but changing it to 0 didn't fix my issue.