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
Platform Specific
Android
Monster Bash - Frankenstein multiball bug?
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="Baron Rubik" data-source="post: 139244" data-attributes="member: 2280"><p>Sorry man - I'm have no good ideas on this. </p><p>It's odd that only MB is giving issues, and Franky multiball in particular. Do other MB multiballs give you issues? Do other tables with multiball give you issues? </p><p></p><p>I don't think MB is one of the more device intensive tables, this i'd believe are the older alpha numerics like FH or BOP, and I've heard RBION was the one table that just pushed the N10 to far when first out. </p><p></p><p>Couple of things you could try....</p><p></p><p>Firstly - back up 'Saved_data' just in case before fiddling. </p><p></p><p>1 - you could install an older version of the last beta, over the top of your play store install - this would effectively move you back one version, allowing you to see if this was a recent breakage. </p><p>You'd have to delete mb rez and re download with beta installed. </p><p>Once finished with beta - just go to play store and TPA will want to update back to latest play store version (delete and re download rez again). No saved_data loss with this technique. </p><p>Last beta here... </p><p><a href="http://digitalpinballfans.com/showthread.php?p=137790" target="_blank">http://digitalpinballfans.com/showthread.php?p=137790</a></p><p></p><p>2 - uninstall - reinstall of TPA. This will lose your saved_data unless moved or backed up. You can move your tables rez files to make it less painful. If rooted you can move the saved_data file or if not use the helium method from the other post above. </p><p>Data locations for TPA =</p><p></p><p>TABLE DATA = /MNT/SDCARD/ANDROID/DATA/COM.FARSIGHT.ANDROIDPINBALL.JAVAPROJECT/FILES/...</p><p></p><p>SAVE DATA = /DATA/DATA/COM.FARSIGHT.ANDROIDPINBALL.JAVAPROJECT/FILES/saved_data</p><p></p><p>Like you said - you could try cleaning the device a little - but if it runs initially I'd doubt this is the issue - but who knows. </p><p>Good luck mate.</p></blockquote><p></p>
[QUOTE="Baron Rubik, post: 139244, member: 2280"] Sorry man - I'm have no good ideas on this. It's odd that only MB is giving issues, and Franky multiball in particular. Do other MB multiballs give you issues? Do other tables with multiball give you issues? I don't think MB is one of the more device intensive tables, this i'd believe are the older alpha numerics like FH or BOP, and I've heard RBION was the one table that just pushed the N10 to far when first out. Couple of things you could try.... Firstly - back up 'Saved_data' just in case before fiddling. 1 - you could install an older version of the last beta, over the top of your play store install - this would effectively move you back one version, allowing you to see if this was a recent breakage. You'd have to delete mb rez and re download with beta installed. Once finished with beta - just go to play store and TPA will want to update back to latest play store version (delete and re download rez again). No saved_data loss with this technique. Last beta here... [url]http://digitalpinballfans.com/showthread.php?p=137790[/url] 2 - uninstall - reinstall of TPA. This will lose your saved_data unless moved or backed up. You can move your tables rez files to make it less painful. If rooted you can move the saved_data file or if not use the helium method from the other post above. Data locations for TPA = TABLE DATA = /MNT/SDCARD/ANDROID/DATA/COM.FARSIGHT.ANDROIDPINBALL.JAVAPROJECT/FILES/... SAVE DATA = /DATA/DATA/COM.FARSIGHT.ANDROIDPINBALL.JAVAPROJECT/FILES/saved_data Like you said - you could try cleaning the device a little - but if it runs initially I'd doubt this is the issue - but who knows. Good luck mate. [/QUOTE]
Verification
Post reply
Members online
No members online now.
Home
Forums
Farsight Studios
The Pinball Arcade / Farsight Studios
Platform Specific
Android
Monster Bash - Frankenstein multiball bug?
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
