4027 replies to this topic

[kiwi]

 

it seems that Data East tables up to Hook, the length of the playfield is 42 inches, the tables after are 46 inches long.

Secret Service measures 107cm X 51.5cm.

 
Star Trek 25th is a little longer 42-5 / 8, with an error of +/- 1/4 of an inch.

Where is this info from? Did you measure yourself? Cause there is so much conflicting info out there for all those playfields..  :/  Thanks

 

A verified measure comes from this post,

https://www.vpforums.org/index.php?showtopic=42372&page=2#entry430764
and the rest from this discussion,

https://vpinball.com/forums/topic/playfield-dimentions/

[jpsalas]

 

 

 

 

The walls in the image are there to stop the ball from falling through the cut outs? Are they still set to collideable? Are they placed below the PF (-0,02)?

I tried that trick on one table that I've already reported to Fuzzel, I created a pf mesh, had the ball fall through at the plunger, created a wall that was supposed to fix that, but, didn't work either. So, this is not 10.7 only related. I don't think I ever solved it and didn't roth talk something about ball mass related to pf meshes ? Was that fixed ?

 

 

This has not been fixed.  I've been putting walls under my playfield meshes and seems to be an acceptable work around for the time being.  I do think this should be a priority though as I'm sure this is messing with proper physics behavior in a number of scenarios.

 

I tried the TZ Skitso mod playfield_mesh. I copied the mesh to the example table but I can't see that the ball is falling through the playfield. However if I set the factor to 1 for reducing the poly count (in the physics tab) I can see this immeadately. The collision code for a playfield mesh is the same as for every other collidable primitive. But when you reduce the details of a mesh with that option in the physics tab of the primitive properties you will get this issue soon or later even with a factor of 0.1.

So I think it's a precision thing when you reduce the polys because the hitmesh is also reduced by this option.

 

Good catch! The polygon reduction algorithm is NOT optimized to keep silhouettes constant, so things like holes can degenerate pretty quickly (i.e. also grow larger than expected). I think i will force playfield meshes to always run at full hit mesh precision then? Or should i still leave it to the authors??

 

 

I think the best is to remove that VPX, and leave it to the authors to reduce the mesh as they prefer. I think this is the best way to keep the playfield working as intended by the author.

[toxie]

Hmmm.. But unfortunately MM has that setting already set to 0..

 

JP: The thing is that one can already set the param to 0 in the physics tab.. So i'm kinda mixed about this..

[Thalamus]

There seems to be some issues playing the new release of Sword of Fury by Sliderpoint - hitting the spinnners.

 

"I have a strange problem when the ball enters the semicircle ADVANCE MAGIC TARGET it simply disappears, then the sound is heard that it is on the table…It happens every time I play

VPX_7_beta_rev4066"

 

https://vpinball.com.../3/#post-177263

 

Just tried the table on latest 10.6 without issues. Commented with what I see on the next post.

[markrock76]

Is there a way to make switching monitor orientation easier for fullscreen users?  I am thinking of changing my monitor orientation from landscape to portrait in nvidia settings where I will need to change table orientation from 270 to 0.  But in doing so all tables have to be reconfigured.  And in my playing around with them I can not get them to look the same as with a 270 orientation.  Shouldn't just changing them to 0 rotate the table and keep all other settings correct?  On a side note I currently keep the ball aspect settings at Cabinet anti-stretch the ball but when switching to a monitor portrait orientation I have to change that to Don't stretch the ball as the Cabinet anti-stretch setting looks very bad.  Let me know if I am missing something obvious or if any thing can be done to make the switch to portrait orientation easier.  Thank You.

[fuzzel]

Wrong thread!

[markrock76]

If you are referring to my post I assumed it would need to be a new feature that is why it is posted here.  If not please ignore and I will go back in to hiding.

[fuzzel]

If you are referring to my post I assumed it would need to be a new feature that is why it is posted here.  If not please ignore and I will go back in to hiding.

It read like a personal problem than a feature request. But regarding your question, I don't have a clue how this can be done easier on a per table basis.

[markrock76]

Thank You.  

 

If you are referring to my post I assumed it would need to be a new feature that is why it is posted here.  If not please ignore and I will go back in to hiding.

It read like a personal problem than a feature request. But regarding your question, I don't have a clue how this can be done easier on a per table basis.

 

[sasa12345]

There seems to be some issues playing the new release of Sword of Fury by Sliderpoint - hitting the spinnners.

 

"I have a strange problem when the ball enters the semicircle ADVANCE MAGIC TARGET it simply disappears, then the sound is heard that it is on the table…It happens every time I play

VPX_7_beta_rev4066"

 

https://vpinball.com.../3/#post-177263

 

Just tried the table on latest 10.6 without issues. Commented with what I see on the next post.

Also some tables won't work with pinballx, if you return 10.6 ver everything is fine(pinballx no administrator)

[BionicToothpick]

If this is the wrong thread, please advise. The command reference that came with the 10.6 download has an asterisk for Kicker Drawstyle,

 

However I am able to change the drawstyle, I don't think that should have an asterisk.

[Thalamus]

 

There seems to be some issues playing the new release of Sword of Fury by Sliderpoint - hitting the spinnners.

 

"I have a strange problem when the ball enters the semicircle ADVANCE MAGIC TARGET it simply disappears, then the sound is heard that it is on the table…It happens every time I play

VPX_7_beta_rev4066"

 

https://vpinball.com.../3/#post-177263

 

Just tried the table on latest 10.6 without issues. Commented with what I see on the next post.

Also some tables won't work with pinballx, if you return 10.6 ver everything is fine(pinballx no administrator)

 

If the tables work in 10.7, then it is PinballX that needs to change, not VPX.

[jejepinball]

Hi, I find an issue with all 10.7 beta (rev4066 too) : when you use the menu Edit/Select element (Ctrl-Shift-E), the application crash.

 

I find another issue with 10.7 beta (rev4066) : the application crash in loading of the table “The Web (Pro Pinball) The_Web VPX 1.2”. The table don’t appear in the editor, it crash before.

[supered]

Hi, I find an issue with all 10.7 beta (rev4066 too) : when you use the menu Edit/Select element (Ctrl-Shift-E), the application crash.
 
I find another issue with 10.7 beta (rev4066) : the application crash in loading of the table “The Web (Pro Pinball) The_Web VPX 1.2”. The table don’t appear in the editor, it crash before.

I had the same issue with the app crash when using the option “select element”.
In my case it was a table that I was working on in 10.6. I opened it in 10.7, played a little with the layers (adding more layers, moving items).
When I reversed to my table before playing with layers, the issue wasn’t there.
So I think it has to do something with the 11+ layers ?!?


Verzonden vanaf mijn iPhone met Tapatalk

[fuzzel]

If VPX crashes for you please post the crash.txt file you'll find it in the same folder where you loaded the table.

[Thalamus]

@fuzzel : For The web, mentioned above, I was able to reproduce, but, there is no crash.dmp or *.txt - just dies.

[fuzzel]

It looks like that the current beta has a problem with the old WAV handling in The Web.

@Toxie can you take a look? It crashes in pinsound.h -> line 84. IsWav() does a strcmp with an inline strrchr() call to search for '.' but the path doesn't have '.' and so the returned string offset is null

Edited by fuzzel, 04 May 2020 - 12:15 PM.

[bord]

 

it seems that Data East tables up to Hook, the length of the playfield is 42 inches, the tables after are 46 inches long.

Secret Service measures 107cm X 51.5cm.

 
Star Trek 25th is a little longer 42-5 / 8, with an error of +/- 1/4 of an inch.

Where is this info from? Did you measure yourself? Cause there is so much conflicting info out there for all those playfields..  :/  Thanks!

I have dimension manager changes, too.

 

Williams EM playfields are 20.25" x 42".

Same question here. 

 

Yes, measured myself on a stripped Williams 1965 EM. Can provide photos, too.

[cyberpez]

 

 

it seems that Data East tables up to Hook, the length of the playfield is 42 inches, the tables after are 46 inches long.

Secret Service measures 107cm X 51.5cm.

 
Star Trek 25th is a little longer 42-5 / 8, with an error of +/- 1/4 of an inch.

Where is this info from? Did you measure yourself? Cause there is so much conflicting info out there for all those playfields..  :/  Thanks!

I have dimension manager changes, too.

 

Williams EM playfields are 20.25" x 42".

Same question here. 

 

Yes, measured myself on a stripped Williams 1965 EM. Can provide photos, too.

 

 

A guy I work with measured his ST 25th.  A KLOV member measured his bttf for me.

[sliderpoint]

Would it be possible to add 'Surface' column to the select elements window?

 

Thanks!

-Mike