Release Candidate 0.12.15 is available!
Release Candidate 0.12.15
Fixes:
- More memory clean-up and fixes for Mac creator. You should now notice decreased CPU usage and memory footprint in OSX Yosemite.
- Fixed a memory leak in the project editor view.
Known Issues:
- Using the Home button may not release all of the memory used from the Scene Editor or Preview. Pressing the back button will resolve this issue.
Report Any Bugs
If you find bugs in the Release Candidate, let us know! We'll be watching the forums, support tickets and bug database for info on this. Once we're all happy with the state of the build then we'll make it stable.
Take a moment to review the "known issues" section of the release notes before reporting any bugs. No need to duplicate reports on what we already know, right?
Thanks for your help!
Go Get It!
See the release notes here:
http://gamesalad.com/download/releaseNotes/creator/rc
Download the release candidate here:
http://gamesalad.com/download/releases
Scroll down until you see "Release Candidates
Comments
Nice!
Thank you!
Great! Hope to see a stable soon.
Same here!
Thank you!
Thank you. Fingers crossed for a new Stable Release soon.
Very nice! Looking forward to better performance in Yosemite.
Thanks GS!
Thank you GS team!
Thank u ...expecting 64bit support as soon as early
Thnx! Great JOB!
As NimbleBug said, 64 bits compatibility for IOS store, is added? Otherwise .. rejected I guess...
I will tell you soon
@BlackCloakGS Not sure what's happening but whenever I click into a table, I'm unable to click back to the Home/Scenes/Actors tabs because the screen becomes distorted and then have to restart the creator which doesn't seem to solve the problem. Anyone else experiencing the same?
Yep @supafly129 , @BlackCloakGS, once you have opened a table to edit it, the creator gets completely confused.
Home or Back-buttons will not let you leave the table editing screen. Switching to a Scene will show a corrupted screen, mixing the table and scene view as depicted by @supafly129.
Good find. Just fixed the issue and sent it to QA.