4027 replies to this topic

[Thalamus]

Black Belt

 

Crashes on loading - did not on previous 10.7 release (4154).

https://vpinball.com...y-1986-v1-0-sp/

 

D&D

Very low and muffled sound from 7.1 setup - works perfectly in 10.6.1 and older.
Can switch in between 10.7 beta and 10.6 series, always same issue on 10.7.
Happens on all 10.7 I've tested (many of the later - not everyone tested)

Sometime still just crashes on exit from latest (4194).

https://vpinball.com...ons-bally-1987/


 

Edited by Thalamus, 05 July 2020 - 11:24 AM.

[fuzzel]

I couldn't repro that. But I think it's the result from an old bug that wrote more than 8 tables to the registry. Try to remove all recent table entries in the registry and start again. That should fix it (hopefully)

[kiwi]

I couldn't repro that. But I think it's the result from an old bug that wrote more than 8 tables to the registry. Try to remove all recent table entries in the registry and start again. That should fix it (hopefully)

The new extra tables are only added (momentarily) to the recent list, if I close and reopen VPX the list is of 8 tables,

the windows registry works as it should, the entries are always 8.

[fourbanks]

Black Belt

 

Crashes on loading - did not on previous 10.7 release (4154).

https://vpinball.com...y-1986-v1-0-sp/

 

D&D

Very low and muffled sound from 7.1 setup - works perfectly in 10.6.1 and older.
Can switch in between 10.7 beta and 10.6 series, always same issue on 10.7.
Happens on all 10.7 I've tested (many of the later - not everyone tested)

Sometime still just crashes on exit from latest (4194).

https://vpinball.com...ons-bally-1987/


 

same here with this table only 

[fuzzel]

Crash.txt please

[toxie]

Black Belt

 

Crashes on loading - did not on previous 10.7 release (4154).

https://vpinball.com...y-1986-v1-0-sp/

 

By a sideeffect this loaded properly before, and now after all the cleanups this shows up (finally) as a real bug. Fix coming up.

[Rawnei]

Did more research into Microsoft AMSI due to the performance issues it's causing, AMSI is Microsofts way of stopping fileless attacks (VBScript, Powershell, etc) and it's an API that AV products can choose to use or not.

 

In Windows Defender it's been kind of hard implemented, it's tied to the Real-Time Protection setting, add exclusions in Windows Defneder does not affect Real-Time Protection only scans so only way to disable AMSI in Windows Defender is to toggle Real-Time Protection Off (bad).

 

In some products for example Sophos Home edition they haven't implemented AMSI integration (yet?) so it does not happen there even with Sophos version of real-time protection, I tried this.

 

In some premium products for example Kaspersky Total Security 2021 they are supposed to have AMSI exclusive options for disabling that specifically and being able add exclusions (see https://help.kaspers...n-US/186114.htm), since they are paid products I haven't tested that.

 

Hopefully we get more and better options for this in the future.

[fourbanks]

Crash.txt please

Crash report VPX rev4194

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

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0041F8EB

Attempt to write to 0x73616C70

Thread ID: 0xD78 [3448]

 

Call stack

==========

0041F8EB VPinballX.exe (0x00736473 0x00000000 0x414D4F54 0x0019cbd0)

004E9A33 VPinballX.exe (0x07DE86E8 0x0314F870 0x0019D148 0x00000424)

0052E231 VPinballX.exe (0x07E07DE0 0x75BD9F20 0x778F0000 0x07e07de0)

77B70A2B ntdll.dll LdrResolveDelayLoadedAPI + 0x17B (0x778F0000 0x77944434 0x00000000 0x76fdd980)

77918239 coml2.dll Coml2DllGetClassObject + 0xFD9 (0x77944434 0x77949050 0x00000000 0x0019cd54)

779209C9 coml2.dll WriteClassStm + 0x11A9 (0x00000000 0x07E47428 0x77900D28 0x00000000)

77900D19 coml2.dll StgOpenStorage + 0xA169 (0x00000000 0x00000000 0x00000000 0x00000000)

77900D28 coml2.dll StgOpenStorage + 0xA178 (0x0000000C 0x0019CCD4 0x00000000 0x76b38f40)

77B752FE ntdll.dll RtlAllocateHeap + 0x3E (0x00000000 0x00000000 0x00000000 0x76bd77b0)

778F72A0 coml2.dll StgOpenStorage + 0x6F0 (0x0000C000 0x00000000 0x0019CEE4 0x00000000)

778F6DD9 coml2.dll StgOpenStorage + 0x229 (0x0019D934 0x0061ABAA 0x00000000 0x0019d6d4)

0052DB44 VPinballX.exe (0x0319E838 0x0314F870 0x0019ED1C 0x0019e760)

0052DBCE VPinballX.exe (0x0019E35E 0x0019E760 0x0019E35E 0x0019e278)

005B77D8 VPinballX.exe (0x0019E35E 0x00000000 0x75A8D7C0 0x0019dfcc)

005AA45D VPinballX.exe (0x00000000 0x00000001 0x565C3A43 0x61757369)

005A9D30 VPinballX.exe (0x00000000 0x00000001 0x00250000 0x0074f928)

005AA885 VPinballX.exe (0x00400000 0x00000000 0x030A47CA 0x00000001)

005D04E3 VPinballX.exe (0x00250000 0x76D3F970 0x0019FFDC 0x77b97084)

76D3F989 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x00250000 0xFFFFFFFFBE07DDDC 0x00000000 0x00000000)

77B97084 ntdll.dll RtlGetAppContainerNamedObjectPath + 0xE4 (0xFFFFFFFFFFFFFFFF 0x77BB62BB 0x00000000 0x00000000)

77B97054 ntdll.dll RtlGetAppContainerNamedObjectPath + 0xB4 (0x02F0A490 0x00250000 0x00000000 0x78746341)

 

Environment

===========

Date/time: 5/7/2020, 13:22:00:835

Number of CPUs: 8

Processor type: 586

System: Windows 10 (10.0 19041)

 

Memory status

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

Total Reserved: 55200K (53M) bytes

Total Commited: 210780K (205M) bytes

Total Free: 3928260K (3836M) bytes

Largest Free: 2095456K (2046M) bytes

 

Registers

=========

EAX=73616C70 EBX=73616C70 ECX=00000000 EDX=00000000

ESI=0AA9BDA4 EDI=00000000 EBP=0019FFEC ESP=0019FFE4 EIP=77B97054

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

 

 

Mini dump saved successfully.

[toxie]

 

I couldn't repro that. But I think it's the result from an old bug that wrote more than 8 tables to the registry. Try to remove all recent table entries in the registry and start again. That should fix it (hopefully)

The new extra tables are only added (momentarily) to the recent list, if I close and reopen VPX the list is of 8 tables,

the windows registry works as it should, the entries are always 8.

 

Found it, fix coming up.

 

Crash.txt please

Mini dump saved successfully.

 

and this is for D&D, right?

[fourbanks]

 

 

I couldn't repro that. But I think it's the result from an old bug that wrote more than 8 tables to the registry. Try to remove all recent table entries in the registry and start again. That should fix it (hopefully)

The new extra tables are only added (momentarily) to the recent list, if I close and reopen VPX the list is of 8 tables,

the windows registry works as it should, the entries are always 8.

 

Found it, fix coming up.

 

Crash.txt please

Mini dump saved successfully.

 

and this is for D&D, right?

 

D and D is fine all good including sound. the crash report above relates to the table black belt in that it crashes on opening  many apologies if i was not that clear above 

Edited by fourbanks, 05 July 2020 - 01:27 PM.

[fourbanks]

i should add that there is a sound defect on the D&D table before the table has loaded' the sort of sound you get when you put 2 speaker cables that touch each other 

Edited by fourbanks, 05 July 2020 - 01:36 PM.

[toxie]

Thanks, but Black Belt is already fixed now.

[fourbanks]

Thanks, but Black Belt is already fixed now.

do i need to update the beta

10.7 beta

or the table for the fix ?

[fuzzel]

The next update fixes it.

[fourbanks]

The next update fixes it.

thank you. so just to recap the table Black Belt closes on opening with the Crash report VPX rev4194 as above and the table D&D has in my case a sound defect before the table opens. once opened the table and sound are correct 

[kiwi]

The layer filter seems not to take into account the first letter of the element names.

 
For example, if I type Drain it finds nothing,
instead if I type Rain I find the layer with the drain.

[fuzzel]

The layer filter seems not to take into account the first letter of the element names.

 
For example, if I type Drain it finds nothing,
instead if I type Rain I find the layer with the drain.

The filter is case sensitive. So you really have to type 'Drain' to filter only that element. 'drain' won't work.

[kiwi]

I have this crash when I try to open my table, this does not happen with the previous revision.

 

Crash report VPX rev4194
============
Process: VPinballX4194.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 001B:0041F8EB
Attempt to write to 0x73616C50
Thread ID: 0xB90 [2960]

Call stack
==========
0041F8EB  (0x00000000 0x00000000 0x00000000 0x00000000)

Environment
===========
Date/time: 7/7/2020, 20:46:21:750
Number of CPUs: 4
Processor type: 586
System: Windows XP

Memory status
=============
Total Reserved: 19756K (19M) bytes
Total Commited: 106192K (103M) bytes
Total Free: 1971140K (1924M) bytes
Largest Free: 1045540K (1021M) bytes

Registers
=========
EAX=73616C50 EBX=73616C50 ECX=00000000 EDX=00000000
ESI=061ED574 EDI=00000000 EBP=00000065 ESP=0000006D EIP=00000000
FLG=00010212 CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000


Failed to save minidump.

 

 
I noticed that the two-way gates register two Hits, when he is hit by the ball,
if you could have an option that when hit, it register a single hit.

[toxie]

Which one is 'my table' ? 

[kiwi]

It is a table not yet released, I can send it to you if you need it for testing.

 
This is the table that with Win 10 I have unstable frames and a lot of stutter,

I think it's the combination of Win 10 protections and this display,

https://www.vpforums...s&showfile=4272

but that's another less important story.