Search results

It would also dramatically increase the app's size on disk and in RAM making memory pressure become an issue.

We got a few requests for this during holiday season last year. The conclusion was: "The company that made this accessory is no longer in business. It is a proprietary controller that we have no plans to support."

This should be fixed in the next update. As for the framerate issues on Mavericks: the engine developer is aware of it and will be investigating it when he gets a chance.

We optimized our usage of the GPU and that resulted in better performance on our lower-end devices (iPhone 3GS and iPad 1) as well as resolved the stuttering on mid-range devices (iPhone 4S, iPad 2, iPad Mini). These optimizations will be in the next major release scheduled sometime this month.

They did mention improving performance on the iPhone 4; they probably just listed the lowest supported device.

I don't recall hearing plans for either. ):

Oooh shiny. *downloads* Edit: Installed. My iPhone 5 hasn't burst into flames yet. (:

iPad 1 - suffers from limited RAM and VM space, making our app likely to get terminated due to memory pressure. Also limited by CPU and GPU. We use the lower level of detail model set for performance reasons. iPad 2 / iPad Mini - the problem of the iPad 1's memory pressure gets resolved, but the...

I took the build back to when Fish Tales was released and it has the octagon-shaped rings... O_o

Yeah, the lower-end devices (iPad 1, iPad 2, iPad Mini (1st gen), iPhone 3GS, and iPhone 4(S)) use a lower level-of-detail for the sake of performance. I couldn't isolate what caused the FPS drop with the latest patch; I suspected it was the TestFlight SDK I put in but the performance was...

Pretty sure (as in I'm looking at the code that does it and the version history of it dating back 12+ months) that the orientation of the device is locked by us while the table is in play. It wasn't until September/October last year that we added the ability to change orientation while in the...

Not sure what would be causing performance issues app-wide on the iPad 2's... I'll investigate this when I'm in on Monday.

I need the actual .crash file so I can symbolicate the call stack.

It should be the apostrophe/quote (' or ") key.

I plan to submit a build to Apple tomorrow. (: http://reviewtimes.shinydevelopment.com/

It's possible. I didn't receive any crash logs until just recently though.

I'm not getting this crash -- would it be possible for you to send your crash report to support@pinballarcade.com? This page explains how to gather the report (Getting Crash Logs Without Xcode): https://developer.apple.com/library/ios/qa/qa1747/_index.html

I've isolated the cause of this crash. Typically our render thread is blocked before the app is fully backgrounded but it seems that it not consistently the case anymore. I've put in a fix for this and my TestFlight data indicates it is successful...

There should be a "Launch Ball" button on the right side of the screen.

You may need to backup your save data (remote) via the options menu and reinstall the app. It sounds like your savedata has somehow been corrupted and your camera values (like your touch scheme) are invalid and are resulting in undefined behavior.