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
Pinball Arcade Tables
Stern Tables
Ripley's Believe it or Not! (2003)
Sigh, why do I bother?
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="Zaphod77" data-source="post: 101240" data-attributes="member: 2101"><p>I believe the issue is that the engine doesn't interpolate between frames. this explains how the ball can just warp through objects when moving fast. It happens more ofte on smartphones because they tend to have frame rate hiccups when you get text messaged and when other apps phone home and stuff.</p><p></p><p>SO this is why a test under ideal conditions doesn't reveal the bug.</p><p></p><p>I think there are serious errors with the code to determine if you can or can't call an attendant. Here's how it should work.</p><p></p><p>THe location of all balls should be tracked by the engine itself at all times. If any ball is outside the playable area, it shoudl get poofed and returned to plunger.</p><p></p><p>If all balls are touching switches, then they are considered in play, and not stuck.</p><p></p><p>Captive balls are a special case. they are considered in play and ineligible for movement if they are in their designated zones. if a captive ball it out of that zone it should be returned to it.</p><p></p><p>if there is exactly one ball free floating, attendent call should take 15 seconds. after then without a switch tripped, the ball should be relocated to plunger.</p><p></p><p>If multiple balls are free, then require long enough for the game to go into ball search.</p><p></p><p>Now it coudl be that all balls are "taken" and yet the game is stuck. THis means the emulation missed an event. in this case the right thing to do is most likely to move the ball that's not in the trough that tripped the last switch to the plunger lane, if it's not a captive ball. If it happens again, or if no ball was outside of the trough, then move the last ball to enter the trough to the plunger lane. I believe this shoudl cover any case.</p><p></p><p>THere is one more case. it could be that a ball is stuck in a place it can score forever. the software should catch this. if the same switch is tripped a certain number of times in a row with no intervening switches, then this is a "beneficial malfunction" and your score is invalidated. "sorry, machine out of order" , and the game is force quit. (and yes this can happen in real life)</p></blockquote><p></p>
[QUOTE="Zaphod77, post: 101240, member: 2101"] I believe the issue is that the engine doesn't interpolate between frames. this explains how the ball can just warp through objects when moving fast. It happens more ofte on smartphones because they tend to have frame rate hiccups when you get text messaged and when other apps phone home and stuff. SO this is why a test under ideal conditions doesn't reveal the bug. I think there are serious errors with the code to determine if you can or can't call an attendant. Here's how it should work. THe location of all balls should be tracked by the engine itself at all times. If any ball is outside the playable area, it shoudl get poofed and returned to plunger. If all balls are touching switches, then they are considered in play, and not stuck. Captive balls are a special case. they are considered in play and ineligible for movement if they are in their designated zones. if a captive ball it out of that zone it should be returned to it. if there is exactly one ball free floating, attendent call should take 15 seconds. after then without a switch tripped, the ball should be relocated to plunger. If multiple balls are free, then require long enough for the game to go into ball search. Now it coudl be that all balls are "taken" and yet the game is stuck. THis means the emulation missed an event. in this case the right thing to do is most likely to move the ball that's not in the trough that tripped the last switch to the plunger lane, if it's not a captive ball. If it happens again, or if no ball was outside of the trough, then move the last ball to enter the trough to the plunger lane. I believe this shoudl cover any case. THere is one more case. it could be that a ball is stuck in a place it can score forever. the software should catch this. if the same switch is tripped a certain number of times in a row with no intervening switches, then this is a "beneficial malfunction" and your score is invalidated. "sorry, machine out of order" , and the game is force quit. (and yes this can happen in real life) [/QUOTE]
Verification
Post reply
Members online
No members online now.
Home
Forums
Farsight Studios
Pinball Arcade Tables
Stern Tables
Ripley's Believe it or Not! (2003)
Sigh, why do I bother?
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
