Search titles only
By:
Home
Forums
New posts
Search forums
Articles
New articles
New comments
Search articles
Pinball DB
Pinball Tables
Pinball Games
What's new
New posts
New articles
New profile posts
New article comments
Latest activity
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Welcome Back to Digital Pinball Fans -
please read this first
For latest updates, follow Digital Pinball Fans on
Facebook
and
Twitter
Home
Forums
Farsight Studios
The Pinball Arcade / Farsight Studios
Geometry bugs
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="JPelter" data-source="post: 71680" data-attributes="member: 623"><p>The geometry bugs where the ball flies off the table at random spots, or in some cases predetermined spots, are still present on most tables. My personal guess is that in most cases this has something to do with the ball going so fast it exits the geometry between physics frame calculations, or something similar. There are also a few specific situations where the table loses track of a ball in strictly defined areas of the table, or situations (RBION, BH), but those are most likely different issues with the same outcome. I base this assumption on the bugs mostly happening on faster tables. I've yet to see it happening on any EM table. This would be a relatively minor issue if it happening didn't actually completely bug out the game, causing it to become unfinishable. I'm going to try and attempt to explain why I don't understand the way things work currently as far as recovering the game goes:</p><p></p><p>Situation #1: The ball goes somewhere on the table it isn't supposed to, like between the glass and the top of a slingshot. Or on top of a rail instead of in it. You hit call attendant. The game finds the ball and says yeah it's stuck; resetting.</p><p></p><p>Situation #2: The ball exits the geometry of the table. You hit call attendant. The game doesn't find the ball inside the geometry so nothing happens, and your game is buggered for good.</p><p></p><p>My question is this: Why are these two situations not treated identically?</p><p>If the game thinks there's a ball in play, and it can't find a ball in play, there isn't a ball in play. Make the damn attendant reset it. As far as I am aware there's no way to exploit this in any way or form. If there somehow is a way to exploit it, the least Farsight can do is consider it a ball drain and plunge the next one, so the game has a chance to finish. I'm sure Farsight is trying to fix the geometry bugs happening in general, but making the attendant actually continue the game if it doesn't find a ball is an incredibly easy short term fix to at least allow people to get through the game and post scores.</p></blockquote><p></p>
[QUOTE="JPelter, post: 71680, member: 623"] The geometry bugs where the ball flies off the table at random spots, or in some cases predetermined spots, are still present on most tables. My personal guess is that in most cases this has something to do with the ball going so fast it exits the geometry between physics frame calculations, or something similar. There are also a few specific situations where the table loses track of a ball in strictly defined areas of the table, or situations (RBION, BH), but those are most likely different issues with the same outcome. I base this assumption on the bugs mostly happening on faster tables. I've yet to see it happening on any EM table. This would be a relatively minor issue if it happening didn't actually completely bug out the game, causing it to become unfinishable. I'm going to try and attempt to explain why I don't understand the way things work currently as far as recovering the game goes: Situation #1: The ball goes somewhere on the table it isn't supposed to, like between the glass and the top of a slingshot. Or on top of a rail instead of in it. You hit call attendant. The game finds the ball and says yeah it's stuck; resetting. Situation #2: The ball exits the geometry of the table. You hit call attendant. The game doesn't find the ball inside the geometry so nothing happens, and your game is buggered for good. My question is this: Why are these two situations not treated identically? If the game thinks there's a ball in play, and it can't find a ball in play, there isn't a ball in play. Make the damn attendant reset it. As far as I am aware there's no way to exploit this in any way or form. If there somehow is a way to exploit it, the least Farsight can do is consider it a ball drain and plunge the next one, so the game has a chance to finish. I'm sure Farsight is trying to fix the geometry bugs happening in general, but making the attendant actually continue the game if it doesn't find a ball is an incredibly easy short term fix to at least allow people to get through the game and post scores. [/QUOTE]
Verification
Post reply
Members online
No members online now.
Latest posts
Sale speculation thread
Latest: gameaddict4life
Saturday at 12:46 AM
Pinball FX (4)
Master List of Issues: Pinball FX
Latest: gameaddict4life
Saturday at 12:40 AM
Pinball FX (4)
Home
Forums
Farsight Studios
The Pinball Arcade / Farsight Studios
Geometry bugs
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top