I’m just not sure if I should make any effort towards moving to it for new projects yet.
I’ve got a live app up, but it’s in a very controlled environment. The main issue I ran into is device processing power, and some odd rendering issues on certain devices. The engine is supposedly not optimized yet so that could change.
I also read that G2 is going to be ready for production apps very soon, so you may as well start playing with it now.
Best.
Yeah, but my concern is how soon is “soon” in Corona’s time distortion field.
I fear pushing new projects into G2.0 and then waiting for it to get a performance stability point to move forward.
I guess I’ll stick with the old engine for now and just tinker with G2 like I am now.
If you’re not needing specific features of G2 then stick with a daily or public for sure. 
Best.
Unless the old engine is going away “soon,” too.
I may just make the leap to G2 and hope I don’t hit major issues.
My issues have mainly been widget related. The other ones I ran into have all been fixed up. So dive in!
We are close to being able to finalize our project - kickers for us right now are:
Android Resuming corrupting snapshots
Waiting for Snapshot:save() capability
Social sharing plugin won’t let us share an image that is in the documents folder (bug submitted)
If you’re considering working on a new project, you should move to G2.0.
The current G2.0 daily build is a lot more polished than what we had even a few weeks ago. That means G2.0 is going out of Beta very soon. Once that happens, all active development/maintenance will be on G2.0.
However, you’ll still be able to use the last public release and, if you have access to them, previous G1.0 daily builds. This is useful for folks who are far along in their existing projects.
re: snapshot:save(). This won’t make it in the upcoming release. Have you tried passing the snapshot to display.save()?
http://docs.coronalabs.com/tachyon/guide/graphics/knownIssues.html
Ah. It looks like someone decided to update the known issues page in the past 24 hours. About 85% of the issues that were there are gone now.
I’m definitely using G2 for all my current projects to make them future proof from the start. However, there still are some issues I hope to be fixed before I release. I’d be very interested to know if there are any performance improvements in G2 when layering lot of transparent images and using blending modes heavily.
I’ve got a live app up, but it’s in a very controlled environment. The main issue I ran into is device processing power, and some odd rendering issues on certain devices. The engine is supposedly not optimized yet so that could change.
I also read that G2 is going to be ready for production apps very soon, so you may as well start playing with it now.
Best.
Yeah, but my concern is how soon is “soon” in Corona’s time distortion field.
I fear pushing new projects into G2.0 and then waiting for it to get a performance stability point to move forward.
I guess I’ll stick with the old engine for now and just tinker with G2 like I am now.
If you’re not needing specific features of G2 then stick with a daily or public for sure.
Best.
Unless the old engine is going away “soon,” too.
I may just make the leap to G2 and hope I don’t hit major issues.
My issues have mainly been widget related. The other ones I ran into have all been fixed up. So dive in!
We are close to being able to finalize our project - kickers for us right now are:
Android Resuming corrupting snapshots
Waiting for Snapshot:save() capability
Social sharing plugin won’t let us share an image that is in the documents folder (bug submitted)
If you’re considering working on a new project, you should move to G2.0.
The current G2.0 daily build is a lot more polished than what we had even a few weeks ago. That means G2.0 is going out of Beta very soon. Once that happens, all active development/maintenance will be on G2.0.
However, you’ll still be able to use the last public release and, if you have access to them, previous G1.0 daily builds. This is useful for folks who are far along in their existing projects.
re: snapshot:save(). This won’t make it in the upcoming release. Have you tried passing the snapshot to display.save()?
http://docs.coronalabs.com/tachyon/guide/graphics/knownIssues.html
Ah. It looks like someone decided to update the known issues page in the past 24 hours. About 85% of the issues that were there are gone now.