130 replies to this topic

[Data101]

I had the same problem with it crashing on replay.

It was a problem with my windows which i eventually solved by reinstalling windows.

[degagne]

Not sure where to look but here's the crash report
 

Crash report VPX rev4364

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

Process: VPinballX.exe

Reason: 0xE0434352 - UNKNOWN at 0023:7597A892

Thread ID: 0x1FCC [8140]

 

Call stack

==========

7597A892 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE0434352 0x00000001 0x00000005 0x5393f49c)

568C28F1 clr.dll GetMetaDataPublicInterfaceFromInternal + 0x9741 (0x00000000 0xFFFFFFFFA6226AF5 0x24C72764 0x24c65970)

568C3796 clr.dll GetMetaDataPublicInterfaceFromInternal + 0xA5E6 (0x24C72764 0x5393F5B0 0x1FB2979D 0x24c72764)

1FB29911  (0x24C72764 0x5393F5D4 0x1FB29630 0x24c08db8)

1FB2979D  (0x24C08DB8 0x1FB32960 0x24C72764 0x00000000)

1FB29630  (0x24C0AC6C 0x24C08DD4 0x00000000 0x00000000)

1FB2623D  (0x1FB260AF 0x24C5D47C 0x5393F66C 0x1fb25e18)

1FB26118  (0x24C5D448 0x00000000 0x00000000 0x00000000)

557A8604 mscorlib.ni.dll (0x00000000 0x24C0ACFC 0x00000000 0x5393f6c0)

557A8537 mscorlib.ni.dll (0x00000000 0x24C0ACFC 0x00000000 0x24c5d47c)

557A84F4 mscorlib.ni.dll (0x24C0ACFC 0x00000000 0x00000000 0x5393f6f0)

55782D5B mscorlib.ni.dll (0x0ADF92D0 0x5393F738 0x567D22DA 0x5393f780)

567CF036 clr.dll (0x5393F780 0x5393F728 0x568C23D0 0x5393f8b0)

567D22DA clr.dll LogHelp_TerminateOnAssert + 0x92A (0x5393F844 0x24C5D490 0x00000004 0x5393f768)

567D859B clr.dll LogHelp_TerminateOnAssert + 0x6BEB (0x5393F8F0 0xFFFFFFFFA6226671 0x5393F9F4 0x568e9560)

568E9657 clr.dll PreBindAssemblyEx + 0x3557 (0x5393FA90 0x0ADF92D0 0x5393FA34 0x5393f9d8)

5697E1E6 clr.dll CorExeMain + 0x6F06 (0xFFFFFFFFA62266B5 0x00000001 0x5393FA34 0x00000000)

5697E271 clr.dll CorExeMain + 0x6F91 (0xFFFFFFFFA6226541 0x00000001 0x0ADF92D0 0x00000000)

5697E162 clr.dll CorExeMain + 0x6E82 (0x00000001 0x00000000 0x00000001 0x568e9560)

5697E351 clr.dll CorExeMain + 0x7071 (0x00000001 0x00000002 0xFFFFFFFFA62265B9 0x568e9420)

568E9508 clr.dll PreBindAssemblyEx + 0x3408 (0x0C25C1A0 0x00000008 0x2B3F1C40 0x5393fb3c)

56894BB7 clr.dll CoUninitializeEE + 0x135F7 (0x0BD2C520 0x7530FA10 0x5393FFDC 0x774475f4)

7530FA29 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x0BD2C520 0x66C8534C 0x00000000 0x00000000)

774475F4 ntdll.dll RtlGetAppContainerNamedObjectPath + 0xE4 (0xFFFFFFFFFFFFFFFF 0x77467363 0x00000000 0x00000000)

774475C4 ntdll.dl (0x56894B60 0x0BD2C520 0x00000000

Environment

===========

Date/time: 25/12/2020, 15:54:03:720

Number of CPUs: 8

Processor type: 586

System: Windows 10 (10.0 19041)

 

Memory status

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

Total Reserved: 265216K (259M) bytes

Total Commited: 1398108K (1365M) bytes

Total Free: 2530916K (2471M) bytes

Largest Free: 2094912K (2045M) bytes

 

Registers

=========

EAX=5393F3D8 EBX=00000005 ECX=00000005 EDX=00000000

ESI=5393F49C EDI=00000001 EBP=5393FFEC ESP=5393FFE4 EIP=774475C4

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

 

 

Failed to save minidump.

what error is it crashing with?

How easy is it to reinstall windows?

I had the same problem with it crashing on replay.

It was a problem with my windows which i eventually solved by reinstalling windows.

[wiesshund]

Well, you are not using the official released version of vpx, that is a 10.7 beta error, and not the most recent version at that.

so i would suggest reporting it to the beta forum

That is not a table issue.

[degagne]

I reverted to VPX 10.6.1 - same issue when reach REPLAY

Well, you are not using the official released version of vpx, that is a 10.7 beta error, and not the most recent version at that.

so i would suggest reporting it to the beta forum

That is not a table issue.

[wiesshund]

 

I reverted to VPX 10.6.1 - same issue when reach REPLAY

Well, you are not using the official released version of vpx, that is a 10.7 beta error, and not the most recent version at that.

so i would suggest reporting it to the beta forum

That is not a table issue.

 

 

going to have to have toxie look at your crash log

 

is not the table though, i am playing it

only problem i am having is i cant beat beedle's damned score of 18 combos
 

[degagne]

It crashes with other versions of the ST Enterprise table so must be a ROM issue?

 

 

I reverted to VPX 10.6.1 - same issue when reach REPLAY

Well, you are not using the official released version of vpx, that is a 10.7 beta error, and not the most recent version at that.

so i would suggest reporting it to the beta forum

That is not a table issue.

 

 

going to have to have toxie look at your crash log

 

is not the table though, i am playing it

only problem i am having is i cant beat beedle's damned score of 18 combos
 

 

[wiesshund]

doubt it, i can run it on 

st_161h

st_161hc

st_162h

and no issues with any of those roms

 

unless you got a messed up ROM, is probably an issue with your VPX installation or VPM installation

i would show the crash log to toxie, he knows how to interpret it

 

I see it is listing clr.dll a lot

which is net framework, so could be that even.

[Thalamus]

Pretty sure you have a .net issue. Like Weisshund, table doesn't crash for me, neither does nFozzy' version.

[degagne]

SOLVED! with an update to VPinMAME

 

Thanks everyone and especially #87 

wiesshund 

for the VPM update suggestion

[nwwoods]

The 3.3b release version of VPinMAME supports the rom needed for this table.  No need to use a beta 3.4 build, FYI.

[wiesshund]

The 3.3b release version of VPinMAME supports the rom needed for this table.  No need to use a beta 3.4 build, FYI.

 

Well, not for nothing, but you cant run LTD Alien Warrior in 3.3b and LTD Time Machine does not work 100% correctly in 3.3b either
so there are at least some direct advantages to having 3.4, and Votrax emulation is better too

[Emre]

Is there a guide that shows how to add the new 3.02 physics to this table?

[jpsalas]

Is there a guide that shows how to add the new 3.02 physics to this table?

 

This table already have those physics. The only difference between the 3.0 and 3.02 are the walls in 3.02 that have now elasticity falloff, which I use in VPX7 to make the bouncing of the different kind of rubbers. But in this table I used rubbers, so the table has the same physic settings.

 

If you want the only thing you may change is the elasticity falloff of the flippers, which I reduced the default a little in 3.02. So you may reduce it from 1,7 to 1,2. This way the flippers will be a little more bouncy. With 1,7 the flippers are hard and the ball is easier to control.

Edited by jpsalas, 03 April 2022 - 05:17 PM.

[Emre]

Ah ok, thank you

[jpsalas]

UPDATE

 

4.0.0 Updated 21.5.2022

- Updated to my VPX7 physics

- cleaned up graphics & reduced the size of the table

- Added my VPX7 LUT changer to darker the table (hold down LEFT CTRL while change with RIGHT CTRL). Including GI brightness adjustment. Use the LUT changer together with the day/night slider to give the table the level of darkness you prefer.

- Updated my mechanical set of sounds to a more "under the glass" sound, as people seem to like those kind of sounds better. 

- and a few small changes here and there.

[Bertone]

I played over the free days your new Version of the table and it looks with LUT very cool and plays good. But my teensy will do nothing. I also tested the Bigus Version , here I have no dof but teensy works. Do you know how to add teensy to your table ?  Best regars Mike

[digitalarts]

Look what rom is used by the two tables. And then look at DOF config tool, what kind of dof toys / MX toys for these roms are scripted.

[jpsalas]

UPDATE

 

4.3 Updated 1.11.2023

- Updated physics to my Rev3. Including physics materials, flippers and slingshot shapes.

- Updated LUT images, 10 shades and 10 warmer shades.

- Updated to my latest set of mechanical sounds.

- Fixed a little the flashers.

[Imhotep]

Hi friends, when I startup this table it looks like this:

Do I need to adjust some settings? Or what could be the reason?

Thanks so much, Sven

Edited by Imhotep, 09 November 2023 - 02:27 PM.

[Guinness]

Don't take psychedelic drugs before you play?

In all seriousness looks like the bloom has gone crazy, I've noticed that happening with a few tables using the latest 10.8, usually on slingshot bulbs, I just turn the bulb intensity down in editor, but I've never encountered anything that overblown before, and seemingly on every bulb. JP will know best