1488 replies to this topic

[Fusionwerks]

Feature request:
Ability to swap playfield images via script.
I hope the playfield prim isn't an alternative to this option.
I've always wanted to do a certain original table, but would require playfield image swapping

[wrd1972]

Ditto above

[ClarkKent]

If the playfield can be a primitive now, there must be a way to display the texture in the editor. Otherwise there is no possibility to place all objects correctly as the drilled holes in the playfield can not be seen anymore.

[fuzzel]

If the playfield can be a primitive now, there must be a way to display the texture in the editor. Otherwise there is no possibility to place all objects correctly as the drilled holes in the playfield can not be seen anymore.

That is still possible. There is no change in the editor. You see the playfield and the additional primitive. Move the prim to a hidden layer and enable the playfield image in the editor as usual.

Feature request:
Ability to swap playfield images via script.
I hope the playfield prim isn't an alternative to this option.
I've always wanted to do a certain original table, but would require playfield image swapping

Well that's still not possible because of the static render step that bakes the static reflection elements to the playfield.

[STAT]

Please don't kill me: still no Way for 2 Screens over VPX ?
Hell, yes i wanted to Play Banzai Run on my 2 Screen Cab

[fuzzel]

Please don't kill me: still no Way for 2 Screens over VPX ?
Hell, yes i wanted to Play Banzai Run on my 2 Screen Cab

That is on my to-do list for VP11

[STAT]

Hey wheres the Extra-Like Button … thank you

[toxie]

There is a problem with the prim playfield if you start the table more than once. You have to reload the table every time to get the correct behavior. A fix will come tomorrow.

 

Yup, sorry.. Bad testing on my end when i did some changes..  :/

Oh, and btw: If you see any differences in physics behavior between the new primitive playfield and the old built-in one, please let me know, because the code definetly has some historical differences..

[toxie]

 

Thanks.  it does seem to work fine with the older FreeImage.dll any idea why the new one would be a problem?  win10x64 build 1607 (yes a little old build, work computer, wonder if that's the issue).

 

 

I reverted the version back to 3.17.0, as we do not need to use 3.18.0 specificially..

[fuzzel]

rev3537 is up:

- revert to FreeImage 3.17.0
- fix special playfield primitive rendering issue and update example table
- add missing changes to changelog.txt
 

[Slydog43]

OMG, thanks for the exporting of script feature.  I wrote a utility to do this that was a bit buggy but kinda worked.  I can now export all table scripts and grep them to find a table that has a feature I'm looking for to copy/modify.   I think this is very great!!!

Edited by Slydog43, 01 November 2018 - 11:01 AM.

[BorgDog]

I just tried out the plunger.position stuff.  the numbers are backwards on the digital. 

 

On my cab with a plunger mech, when at rest I get a reading of 2 (this is with park of .1666), at full pull back I get 25, if I push forward from park I get to 0. 

 

On my laptop I get 20 at rest and 0 at full pull when enable mechanical plunger is checked, and 25 at rest and 0 at full pull when enable mechanical plunger is not checked. Of course there is no way to push forward on the plunger with just a keyboard (at least that I know of), but it should bounce forward on plunger release and at least momentarily be forward of rest (the animation does).

 

So we're getting somewhere, but still needs some tweaking to be useful.

[toxie]

So what do you suggest, except for making it inverse?

[Thalamus]

Mentioned in the old 10.5 thread - I feel it is bordeline to be called a bug.

 

I think it would make more sense if you in sound-manager choose 'reimport from', that if the old sound has x/y coordinates set, They should be re-used instead of zeroed out.

[ClarkKent]

 

If the playfield can be a primitive now, there must be a way to display the texture in the editor. Otherwise there is no possibility to place all objects correctly as the drilled holes in the playfield can not be seen anymore.

That is still possible. There is no change in the editor. You see the playfield and the additional primitive. Move the prim to a hidden layer and enable the playfield image in the editor as usual. 

 

 

OK, but on raised playfields (like mini playfields or such) that are done with primitives you can not see the texture at all. So please display at least a low resolution texture for that kind of primitives.

[BorgDog]

So what do you suggest, except for making it inverse?

 

The issue is that the numbers need to work the same for digital and analog plunger.  I'm trying to create a unconventional ball launch mechanism that will visually be a primitive animation.  That primitive animation needs to follow along with the plunger and the ball resting against it.  I don't know if all mechanical plungers give the same results either, I am currently using an earlier model zeb's plunger.  It appears, at least to me, that the current visible plunger animation works the same for both, so maybe that could be tapped for values?  that it returns different values if mechanical is enabled or not is kind of weird but shouldn't effect my particular use as i will always have it enabled.. at least on my current project.

 

Thanks for working on this.

[unclewilly]

Sweet

[toxie]

 

So what do you suggest, except for making it inverse?

 

The issue is that the numbers need to work the same for digital and analog plunger.  I'm trying to create a unconventional ball launch mechanism that will visually be a primitive animation.  That primitive animation needs to follow along with the plunger and the ball resting against it.  I don't know if all mechanical plungers give the same results either, I am currently using an earlier model zeb's plunger.  It appears, at least to me, that the current visible plunger animation works the same for both, so maybe that could be tapped for values?  that it returns different values if mechanical is enabled or not is kind of weird but shouldn't effect my particular use as i will always have it enabled.. at least on my current project.

 

Thanks for working on this.

 

 

Okay, so then for now i just made it inverse (i.e. matching the mech plunger). Just give me some more hints in case you need a different behavior.

[bord]

Is it possible to allow mesh textures to behave like flashers? For example, Image A/Image B and a variety of image blend options? Would really make texture changing based on lighting states easy and attractive.

[fuzzel]

Is it possible to allow mesh textures to behave like flashers? For example, Image A/Image B and a variety of image blend options? Would really make texture changing based on lighting states easy and attractive.

I don't want to go that way. Flashers are simple plates where you combine two separate textures and blend them together into the frame buffer.
Doing that with meshes would add another layer of complexity and than it's hard to add other lighting options in the next versions.