4035 replies to this topic

[batch]

JLouLouLou, ouvre un script et fais une recherche du mot "saucer"

 

[JLouLoulou]

@Ben Logan , @The Loafer , thanks for the information.

@batch ben je n'ai pas mon pc avec moi

Envoyé de mon Redmi Pro en utilisant Tapatalk

[Rawd]

Good question, Lou. Here's a saucer image. It's the recessed "hole" in the middle of the picture below:

 

 

JPSalas made some magnet code for these many years ago, that when set correctly, creates a very realistic effect.

[Ben Logan]

So many truly game-changing improvements and contributions from JP over the years!

[javier1515]

I don't know if it was already reported but the ramps don't stay collidable.

 

Thanks for more and mord good work my friends.             

[fuzzel]

what is this ?
 

Spinner and emreels

[toxie]

I don't know if it was already reported but the ramps don't stay collidable.

 

Thanks for more and mord good work my friends.             

Do you have a more exact repro case/steps?

[supered]

Running build 4035.

 

For some reason I can add a new layer, move items to that layer (for example a layer containing all light seq), but after saving the file, the new layer is gone. It looks like it only happens with light seqences.

 

 

When creating a new layer and move a bumper and a light seq to it, save it, the layer is saved, the bumper is member of the new layer but the light seq is gone from this new layer and again on it original layer.

 

Also noticed at some point of time, ALL the light seqences are pointing to the aLights collection, and not to the collections a programmed them to.

But that can have happend by my mistake, I am unable to reproduce this.

 

And, more of a "Nice To Have", I would like a confirmation box before deleting a complete layer with items on it.

I clicked the "minus" button on accident, and the layer was directly gone..........

Edited by supered, 23 April 2020 - 08:01 AM.

[fuzzel]

The layer handling for light seq is fixed in the next update. Also in the next update a message box asks the user if you really want to delete a complete layer.

[supered]

The layer handling for light seq is fixed in the next update. Also in the next update a message box asks the user if you really want to delete a complete layer.

Thanks man, keep up the amazing work :-)


Verzonden vanaf mijn iPhone met Tapatalk

[WhenLit]

rev4035 is up:

 

- remove double window resizing on start
- fix wrong primitive property updates
- fix enter key handling in script editor
- WinXP support added again

 

Hello,

 

Avast says that VPinballX.exe is infected by IDP.ARES.Generic.

The CRC-32 in the zip file and on my disk for VPinballX.exe are identical.

Any idea?

Edited by WhenLit, 23 April 2020 - 10:25 AM.

[fuzzel]

VPinballX.exe is packed with UPX32 executable packer. Some antivirus tools are a bit too nervous about this packer. For example on virustotal.com only the antivirus tool Comodo is reporting the exe as "Packed.Win32.MUPX.Gen@24tbus" and all other 71 have no problem with it. So it's a false positive and you can ignore it and/or changing your antivirus tool.

rev4040 is up:

 

- add confirmation message box when deleting a complete layer
- fix layer handling for lightseq
- fix size of plunger visual properties
- fix for autoplungers by mfuegemann
- fix crash when importing old physics sets
 

[javier1515]

I don't know if it was already reported but the ramps don't stay collidable.
 
Thanks for more and mord good work my friends.             

Do you have a more exact repro case/steps?

add a new ramp by default it appears to me that it is not collidable, I select to make it collidable but it does not take the action

Enviado desde mi SM-A205G mediante Tapatalk

[supered]

rev4040 is up:

 

- add confirmation message box when deleting a complete layer
- fix layer handling for lightseq
- fix size of plunger visual properties
- fix for autoplungers by mfuegemann
- fix crash when importing old physics sets
 

Thanks!

I can confirm that the fix for layers handling ligtseq is now working.

Also VERY NICE to see the confirmation box when deleting a layer.

 

Also found (during previous build 4035) that when adding a timer to the playfield, it was not usable in the script(s)

I see that in build 4040 I don't have this issue. Did you change something?

 

But..... another issue found.

When using the option "Edit->Select Element" , vpx10.7 crashes without any message or warning.......

[sliderpoint]

Any chance you can make a new "Ball Guide" object?  It would just be similar to the flat ramp object, but upside down so it has a top and some ends and it's 2.94 units wide. Have the physics of walls (minus the sling part).

 

-Mike

[kiwi]

Custom colors saved with the table are missing.

 
The color preview of the flasher is always black (in its property panel).

 
To display the layer of an object on the bottom bar, I have to select two objects.

 
From the main window I detached the Toolbar,
how do you hang up the Toolbar on the main window?

 

Thanks

[fuzzel]

add a new ramp by default it appears to me that it is not collidable, I select to make it collidable but it does not take the action

Enviado desde mi SM-A205G mediante Tapatalk

 

The code handling the collidable checkbox is missing in that build. Will be fixed in the next one
 

Also found (during previous build 4035) that when adding a timer to the playfield, it was not usable in the script(s)

I see that in build 4040 I don't have this issue. Did you change something?

 

But..... another issue found.

When using the option "Edit->Select Element" , vpx10.7 crashes without any message or warning.......

 

I can't reproduce both issues. I can create a timer and I can see and use it in the editor/script.

The SelectElement works for me too.
 

[batch]

VPX_7_beta_rev4040

 

When you change the value (was 555) of a parameter, you can't validate with the "enter" key

 

 

You have to click outside the element (in this case a ramp) and then to click again on it, to see the value has changed

 

 

And it's the same for the feature "undo"

Edited by batch, 23 April 2020 - 03:36 PM.

[fuzzel]

Custom colors saved with the table are missing.

 
The color preview of the flasher is always black (in its property panel).

 
To display the layer of an object on the bottom bar, I have to select two objects.

 
From the main window I detached the Toolbar,
how do you hang up the Toolbar on the main window?

 

Thanks

What custom colors do you mean? which settings? I can change the background color/table lights as expected and they are also saved

The color button for flashers will be fixed in the next update. Same for the status bar and displaying element information (layer names) of single selected elements.

 

To move the toolbar back grab the dialog titlebar drag it to the main editor and in middle of the left main editor window a small icon appears. Drag'n drop the toolbar dialog on this and it will attach it to the left side of the window.
 

VPX_7_beta_rev4040

 

When you change the value (was 555) of a parameter, you can't validate with the "enter" key

 

 

You have to click outside the element (in this case a ramp) and then to click again on it, to see the value has changed

 

 

And it's the same for the feature "undo"

yes it's a known issue. The enter key is a special key that is a bit tricky to handle. I see if I can find a fix for it.

[supered]

add a new ramp by default it appears to me that it is not collidable, I select to make it collidable but it does not take the action

Enviado desde mi SM-A205G mediante Tapatalk
 

The code handling the collidable checkbox is missing in that build. Will be fixed in the next one
 

Also found (during previous build 4035) that when adding a timer to the playfield, it was not usable in the script(s)
I see that in build 4040 I don't have this issue. Did you change something?
 
But..... another issue found.
When using the option "Edit->Select Element" , vpx10.7 crashes without any message or warning.......
 

I can't reproduce both issues. I can create a timer and I can see and use it in the editor/script.
The SelectElement works for me too.
 

Yes, the timer does function in 4040, but I HAD issues with it in previous build.
I’ll test the Select Element with an empty table, maybe it’s because I used the table I’m working on


Verzonden vanaf mijn iPhone met Tapatalk