Matt Rix
Matt Rix
This shouldn't be a big issue for most projects, but for some where there are LOTS of sprites in memory, the RXProfiler stuff could get heavy. This isn't really a...
The issue is that the FDebugFrameRateGraph tries to create a new texture every time it's created. This should be an easy fix (although really the frame rate graph shouldn't need...
This is kind of an edge case, but it shouldn't be too hard to handle. The harder part will be on the developer's end where they'll have to unload everything...
Whit requested this feature: https://twitter.com/wtrebella/status/358366023633739776 It makes sense if you want to switch resolution levels at runtime (not something I really recommend, but technically possible).
See: http://www.reddit.com/r/futile/comments/1ijiwa/othertolocal_issues/ As usual, the issue has something to do with the lazy instantiation of the transform matrix.
I feel like I might be doing something dumb with the uv sampling I'm doing on the textures, specifically for very small atlas elements of 1x1 or 2x2. I should...
I thought this wouldn't happen if the editor scripts are in a /Editor folder, but I guess I was wrong. The solution is just to wrap the whole thing in...
Integrate with the built-in Unity physics engine. Create a separate physics library/engine/thing to do this so that it doesn't overcomplicate the normal Futile stuff. It'll probably be stored as a...
The FButton may still be calling TouchMoved and TouchEnded. It probably just needs if(!_isEnabled) return; at the start of each method. Also, make sure to consider the scenario where a...