4027 replies to this topic

[wiesshund]

Good use of notes

Make notes to self of what you where doing, when you find you are about to pass out on the PC

so when you wake up tomorrow and remember nothing, you can remind your self.

 

[batch]

Shouldn't this file be a   .vpx, not a   .vpp

 

Doesn't appear in the "Visual Pinball Tables (*.vpx)"

[fuzzel]

No its a VP physics file. You can import it and use it as an a physics set.

[batch]

Thanks and sorry !

 

Are all these files the same version than in JP's previous upload ?

Edited by batch, 04 December 2020 - 07:58 AM.

[wiesshund]

dumb question
But what is the definition of the custom keys that can be mapped in VPX?

 

I thought is was simply custom1 custom2 custom3 etc

but if i put in a script 

 

If keycode = Custom1 Then do something
VPX comes back yelling hey hey custom1 not defined, when you press the key mapped to it

Which is kind of funny because it heard said key and yet says i dont know what it is
i mean i could
DIm custom1, custom1 = 30
Dim custom2, custom2 = 31
But that seems to defeat the purpose of mapping it

 

So is there a different definition by which to refer to it in a table script?
I thought that doing that did work previously, but maybe i am wrong?

[Thalamus]

Please weisshund, this is a general question, not a beta related one.

[wiesshund]

Please weisshund, this is a general question, not a beta related one.

 

maybe, except i think it works in vpx 6
I will have to wait till i get to the pc that only has vpx 6 on it and see what is different there than here

[toxie]

Thanks and sorry !

 

Are all these files the same version than in JP's previous upload ?

Yes, the 2.0 one..

As we shipped his earlier improvements/suggestions from some years ago, i thought it's better to be up to date.

[jpsalas]

 

Thanks and sorry !

 

Are all these files the same version than in JP's previous upload ?

Yes, the 2.0 one..

As we shipped his earlier improvements/suggestions from some years ago, i thought it's better to be up to date.

 

 

This Arcade Physics 3.0 fits very well to 10.6

Now that the walls have elasticity falloff too, then I'll have to update some of the materiales (metals, plastic, wood) to use this parameter too, so it will fit 10.7 much better. Even if those kind of materials, which are kind of hard by themselves, will also benefit of the falloff, as it will feel more natural.

[wiesshund]

Well, i breaked it

 

i opened 1 table to look at something, closed it, opened another table
touched the layers pane and poof, did not even have both open at same time.

It still seems a bit touchy about the layers pane

 

Crash report VPX rev4351
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00442933
Attempt to read from 0x0000529D
Thread ID: 0x2C2C [11308]

Call stack
==========
00442933 VPinballX.exe (0x0019E274 0x03103138 0x031030D4 0x0019e274)
00442788 VPinballX.exe (0x00000345 0x0019E274 0x0019E274 0x031030d4)
00427F69 VPinballX.exe (0x0000004E 0x00000345 0x003A045E 0x00030402)
004407F0 VPinballX.exe (0x0000004E 0x00000345 0x0019E274 0x0000004e)
00426122 VPinballX.exe (0x00030402 0x0000004E 0x00000345 0x0019e274)
752FEF6B USER32.dll AddClipboardFormatListener + 0x4B (0xFFFFFFFF8B1474FF 0x7767700D 0x69E85700 0xffffffff8b00001b)
8510247C  (0x7767700D 0x69E85700 0xFFFFFFFF8B00001B 0x75f685f0)
8B1474FF  (0x69E85700 0xFFFFFFFF8B00001B 0x75F685F0 0x3302eb2f)
7767700D  (0xFFFFFFFF8B00001B 0x75F685F0 0x3302EB2F 0x6770a1f6)
69E85700  (0x75F685F0 0x3302EB2F 0x6770A1F6 0xffffffffb0ff0077)
8B00001B  (0x3302EB2F 0x6770A1F6 0xFFFFFFFFB0FF0077 0x000000c4)
75F685F0 SETUPAPI.dll PnpRepairWindowsProtectedDriver + 0x17D0 (0x6770A1F6 0xFFFFFFFFB0FF0077 0x000000C4 0x23ac15ff)
3302EB2F  (0xFFFFFFFFB0FF0077 0x000000C4 0x23AC15FF 0xffffffffc0850062)
6770A1F6 System.ni.dll (0x000000C4 0x23AC15FF 0xFFFFFFFFC0850062 0x308b1674)
B0FF0077  (0x23AC15FF 0xFFFFFFFFC0850062 0x308B1674 0x1074f685)

Environment
===========
Date/time: 5/12/2020, 00:33:48:819
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 111172K (108M) bytes
Total Commited: 1033232K (1009M) bytes
Total Free: 3049836K (2978M) bytes
Largest Free: 2095296K (2046M) bytes

Registers
=========
EAX=00005259 EBX=752E21C0 ECX=0A1A2E18 EDX=00000001
ESI=2ACEA280 EDI=03103138 EBP=6770A1F6 ESP=004260E8 EIP=B0FF0077
FLG=00210206 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

[toxie]

2-way gates are used mostly at the entrance of a ramp where the ball can go both ways, and it triggers a switch.

 

To open a gate manually you used like this: gate.open = True, and to close it: gate.open = False

 

The bug in the gates is that once you have used the gate.open, to open and close a gate, then the gate doesn't animate anymore when the ball goes through it. It simply stays still. I don't know in which VPX revision the gates stopped animating. It is a small bug, but it should be nice if it could be fix it

Fuzzel changed this (i think) with rev 2606, so could you please quickly check with 10.0 and 10.1 (cause it was changed inbetween) for confirmation?

[jpsalas]

 

2-way gates are used mostly at the entrance of a ramp where the ball can go both ways, and it triggers a switch.

 

To open a gate manually you used like this: gate.open = True, and to close it: gate.open = False

 

The bug in the gates is that once you have used the gate.open, to open and close a gate, then the gate doesn't animate anymore when the ball goes through it. It simply stays still. I don't know in which VPX revision the gates stopped animating. It is a small bug, but it should be nice if it could be fix it

Fuzzel changed this (i think) with rev 2606, so could you please quickly check with 10.0 and 10.1 (cause it was changed inbetween) for confirmation?

 

 

I'll do that

[fuzzel]

Well, i breaked it
 
i opened 1 table to look at something, closed it, opened another table
touched the layers pane and poof, did not even have both open at same time.

It still seems a bit touchy about the layers pane

 

Crash report VPX rev4351
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00442933
Attempt to read from 0x0000529D
Thread ID: 0x2C2C [11308]

Call stack
==========
00442933 VPinballX.exe (0x0019E274 0x03103138 0x031030D4 0x0019e274)
00442788 VPinballX.exe (0x00000345 0x0019E274 0x0019E274 0x031030d4)
00427F69 VPinballX.exe (0x0000004E 0x00000345 0x003A045E 0x00030402)
004407F0 VPinballX.exe (0x0000004E 0x00000345 0x0019E274 0x0000004e)
00426122 VPinballX.exe (0x00030402 0x0000004E 0x00000345 0x0019e274)
752FEF6B USER32.dll AddClipboardFormatListener + 0x4B (0xFFFFFFFF8B1474FF 0x7767700D 0x69E85700 0xffffffff8b00001b)
8510247C  (0x7767700D 0x69E85700 0xFFFFFFFF8B00001B 0x75f685f0)
8B1474FF  (0x69E85700 0xFFFFFFFF8B00001B 0x75F685F0 0x3302eb2f)
7767700D  (0xFFFFFFFF8B00001B 0x75F685F0 0x3302EB2F 0x6770a1f6)
69E85700  (0x75F685F0 0x3302EB2F 0x6770A1F6 0xffffffffb0ff0077)
8B00001B  (0x3302EB2F 0x6770A1F6 0xFFFFFFFFB0FF0077 0x000000c4)
75F685F0 SETUPAPI.dll PnpRepairWindowsProtectedDriver + 0x17D0 (0x6770A1F6 0xFFFFFFFFB0FF0077 0x000000C4 0x23ac15ff)
3302EB2F  (0xFFFFFFFFB0FF0077 0x000000C4 0x23AC15FF 0xffffffffc0850062)
6770A1F6 System.ni.dll (0x000000C4 0x23AC15FF 0xFFFFFFFFC0850062 0x308b1674)
B0FF0077  (0x23AC15FF 0xFFFFFFFFC0850062 0x308B1674 0x1074f685)

Environment
===========
Date/time: 5/12/2020, 00:33:48:819
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 111172K (108M) bytes
Total Commited: 1033232K (1009M) bytes
Total Free: 3049836K (2978M) bytes
Largest Free: 2095296K (2046M) bytes

Registers
=========
EAX=00005259 EBX=752E21C0 ECX=0A1A2E18 EDX=00000001
ESI=2ACEA280 EDI=03103138 EBP=6770A1F6 ESP=004260E8 EIP=B0FF0077
FLG=00210206 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

Hopefully fixed with the next update

2-way gates are used mostly at the entrance of a ramp where the ball can go both ways, and it triggers a switch.
 
To open a gate manually you used like this: gate.open = True, and to close it: gate.open = False
 
The bug in the gates is that once you have used the gate.open, to open and close a gate, then the gate doesn't animate anymore when the ball goes through it. It simply stays still. I don't know in which VPX revision the gates stopped animating. It is a small bug, but it should be nice if it could be fix it

Fuzzel changed this (i think) with rev 2606, so could you please quickly check with 10.0 and 10.1 (cause it was changed inbetween) for confirmation?

Really? I think I changed something other and this is some leftover

[fuzzel]

 

 

2-way gates are used mostly at the entrance of a ramp where the ball can go both ways, and it triggers a switch.

 

To open a gate manually you used like this: gate.open = True, and to close it: gate.open = False

 

The bug in the gates is that once you have used the gate.open, to open and close a gate, then the gate doesn't animate anymore when the ball goes through it. It simply stays still. I don't know in which VPX revision the gates stopped animating. It is a small bug, but it should be nice if it could be fix it

Fuzzel changed this (i think) with rev 2606, so could you please quickly check with 10.0 and 10.1 (cause it was changed inbetween) for confirmation?

 

 

I'll do that

 

And fixed. I hope the fix doesn't break any table though.

[jpsalas]

About the gate bug:

 

The gate work fine under vpx 10.0, the first release, version 2460

In 10.1 the gate doesn't work anymore, this is version 2660

 

The bug is this: after you make the gates open and close manually, as many vpm table do (like AFM), then the gate doesn't move naturally anymore. After the ball hits the gate it stays open. The physical gate works as it should, it is just a visual thing.

 

Here it s a test table. I had to build it using VPX 10.0, since 10.0 can't open 10.1 tables or later. But it can be testet on all the VPX versions

 

 

Plunge a few balls to see the gate working as it should. The press the left flipper to open and close the gate manually. After that you'll se that after the ball hits the gate, it doesn't come back down, it stays open.

Edited by jpsalas, 06 December 2020 - 04:48 PM.

[fuzzel]

About the gate bug:

 

The gate work fine under vpx 10.0, the first release, version 2460

In 10.1 the gate doesn't work anymore, this is version 2660

 

The bug is this: after you make the gates open and close manually, as many vpm table do (like AFM), then the gate doesn't move naturally anymore. After the ball hits the gate it stays open. The physical gate works as it should, it is just a visual thing.

 

Here it s a test table. I had to build it using VPX 10.0, since 10.0 can't open 10.1 tables or later. But it can be testet on all the VPX versions

 

test_gate.zip

 

Plunge a few balls to see the gate working as it should. The press the left flipper to open and close the gate manually. After that you'll se that after the ball hits the gate, it doesn't come back down, it stays open.

thanks for the test table... the table works with the latest fix. 

[toxie]

Hi, I don't know the reason but this tables crash with the 10.7 beta 4307 : Half-Life (TBA 2019) and Dragon Ball Z VPX 1.06

Will be fixed with the next build.

@JP: If you experience a script/text editor crash again, can you please post the mini-dump, too?

Cause i cannot find out or repro myself (and i tried really really hard) whats going wrong.

[jejepinball]

Hi, I don't know the reason but this tables crash with the 10.7 beta 4307 : Half-Life (TBA 2019) and Dragon Ball Z VPX 1.06

Will be fixed with the next build.

@JP: If you experience a script/text editor crash again, can you please post the mini-dump, too?

Cause i cannot find out or repro myself (and i tried really really hard) whats going wrong.

 

I don't understand if you have reproduce this bug with Dragonball table or not : I check with the new version 4351 and the table crash too. But I noticed that the crash is only with the original .vpx file from vpforums.org (https://www.vpforums...&showfile=14093). If I load the table with Visual Pinball 10.6 and change the camera settings (and save the table), the table works fine in 10.7 !

Here my crash files and a capture of my video preferences if necessary :

http://dl.free.fr/iV5Bmr4Cy

 

Thank You

Edited by jejepinball, 06 December 2020 - 11:08 PM.

[wiesshund]

Maybe some how some invalid info got saved in the POV settings?

[toxie]

As said, it will be fixed in the NEXT build. 

 

It's a bug i introduced with 10.7 related to the new multithreaded loading of images. And Half Life and Dragon Ball somehow feature a slight corruption of their image data (maybe due to an earlier VP(X) bug), and the new code didn't handle that as well as the old one.