iTGB 1.3 Planning
by Michael Perry · in iTorque 2D · 06/01/2009 (10:50 am) · 218 replies
The iTorque Updates Blog contains the iTGB Roadmap, which announces plans for v1.3. Here is a recap:
iTGB 1.3: The highest priority is upgrading the engine to work with the 3.0 OS and SDK for iPhones. This includes compatibility and integrating the new features.
* Compile iTGB against 3.0 SDK, with GCC 4.2
* Full motion video playback, with examples exposed to script
* Displaying pictures from device library
* Playing music from device library
* Camera access from device
In addition to 3.0 compatibility and new features, the following improvements to the base engine will be made.
* Integration of Melv May’s memory reduction code
* Significant load time reduction
* PVR for cell-based sprite sheets
* New iPhone features exposed to TorqueScript via C++ handlers
* Gesture callbacks for swipe, pinch, and zoom
* More documentation on creating optimized games, using iPhone specific features, and general reference to frameworks (engine code)
* Community member contributions
o Vibration by Dave Calabrese
o Loading and saving game data to device by Dave Calabrese
o Multi-Touch and gestures by Dave Calabrese and Justin Mosiman
* General optimizations that will increase fps
Please use this thread to post feedback about the upcoming features, or 3.0 specific functionality you might be interested in. Try not to clutter this with current bugs or 1.2 issues, which are addressed elsewhere.
iTGB 1.3: The highest priority is upgrading the engine to work with the 3.0 OS and SDK for iPhones. This includes compatibility and integrating the new features.
* Compile iTGB against 3.0 SDK, with GCC 4.2
* Full motion video playback, with examples exposed to script
* Displaying pictures from device library
* Playing music from device library
* Camera access from device
In addition to 3.0 compatibility and new features, the following improvements to the base engine will be made.
* Integration of Melv May’s memory reduction code
* Significant load time reduction
* PVR for cell-based sprite sheets
* New iPhone features exposed to TorqueScript via C++ handlers
* Gesture callbacks for swipe, pinch, and zoom
* More documentation on creating optimized games, using iPhone specific features, and general reference to frameworks (engine code)
* Community member contributions
o Vibration by Dave Calabrese
o Loading and saving game data to device by Dave Calabrese
o Multi-Touch and gestures by Dave Calabrese and Justin Mosiman
* General optimizations that will increase fps
Please use this thread to post feedback about the upcoming features, or 3.0 specific functionality you might be interested in. Try not to clutter this with current bugs or 1.2 issues, which are addressed elsewhere.
About the author
Programmer.
#142
So I’m right in thinking that the problem in the game crashing after 20-25 minutes due to memory leaks is still in 1.3 and the only way of getting rid of it is via the following process, if you can get it to work?
http://www.garagegames.com/community/forums/viewthread/100397/2#comment_form
For me personally, the important things to see from the next / this upgrade is this memory leak been plugged without having to mess around in XCode (which I personally can’t get to work) and improved loading times would be nice along with general overall speed increases and file size reductions if possible.
I would personally like to see a totally solid foundation before any of these new features are added.
Any news on when the Final version of 1.3 will be coming out as this is classed as a beta?
Thanks,
Mike.
09/19/2009 (11:29 am)
Hello,So I’m right in thinking that the problem in the game crashing after 20-25 minutes due to memory leaks is still in 1.3 and the only way of getting rid of it is via the following process, if you can get it to work?
http://www.garagegames.com/community/forums/viewthread/100397/2#comment_form
For me personally, the important things to see from the next / this upgrade is this memory leak been plugged without having to mess around in XCode (which I personally can’t get to work) and improved loading times would be nice along with general overall speed increases and file size reductions if possible.
I would personally like to see a totally solid foundation before any of these new features are added.
Any news on when the Final version of 1.3 will be coming out as this is classed as a beta?
Thanks,
Mike.
#143
09/21/2009 (1:43 pm)
@Michael Perry: Hey, just wondering I know you were busy with GDC and whatnot but now that GDC is over what is the ETA on that blog? Looking forward to reading it. 
#144
Let's have a 1.3 that is correct as released, not one that we all have to modify the source on to make it work.
Please?
@Michael - thanks for all your hard work, it is appreciated! Please get 1.3 completely solid before moving on?
09/21/2009 (2:39 pm)
I also vote for something solid, solid, solid, WITH Melv's memory reduction code as promised. I don't want to spend my time correcting mis-spellings and other simple to fix problems like I do every day with 1.2.Let's have a 1.3 that is correct as released, not one that we all have to modify the source on to make it work.
Please?
@Michael - thanks for all your hard work, it is appreciated! Please get 1.3 completely solid before moving on?
#145
09/21/2009 (5:18 pm)
Who will be the successor to His Blogship? Will he be good, better, or worse? I'm still pacing back and forth over the fact that he says it's his last!
#146
09/23/2009 (5:13 pm)
Deathlike silence... Why do I feel like this engine is being abandoned? At the very least someone could take a few minutes to post a freakin' blog.
#147
@BeyondtheTech - To clarify what I stated, I am withdrawing from the community for a while. My involvement will be restricted to documentation feedback threads and IRC. This means no more blogs (after this final one) or forum crawling.
09/23/2009 (5:19 pm)
The engine is not being abandoned. We have a new road map planned all the way to next year. The one part holding back the blog posting is that I'm not sure how to message the most important part. I have to check with higher authority to find out what I'm allowed to say about the new team.@BeyondtheTech - To clarify what I stated, I am withdrawing from the community for a while. My involvement will be restricted to documentation feedback threads and IRC. This means no more blogs (after this final one) or forum crawling.
#148
09/23/2009 (5:21 pm)
There are still some business issues on the back end, but I think everyone will be quite happy with the announcement.
#149
I'm sure you can appreciate that long periods of silence can cause some trepidation, and perhaps feelings of resentment. Especially given the history with this engine.
I think what this community needs right now is more communication rather than less.
09/23/2009 (5:29 pm)
Thanks for the replies. I'm sure you can appreciate that long periods of silence can cause some trepidation, and perhaps feelings of resentment. Especially given the history with this engine.
I think what this community needs right now is more communication rather than less.
#150
09/23/2009 (6:23 pm)
@Patrick - Understandable. We are looking into getting someone to take replace me on the site and continue to help David with support. 
#151
Thanks!
09/23/2009 (11:06 pm)
Hey, Michael. Are you planning to give us an updated or final iTGB anytime soon? The current beta iTGB has bugs (i.e mouse input is broken).Thanks!
#152
09/24/2009 (3:17 pm)
@Johnny - Mouse input seems to be working for me. I doubt I will be changing anymore code myself.
#153
09/24/2009 (4:34 pm)
Im sure the email notification had you linking to Tim Newell's code change (Thanks Tim)..is that change already in 1.3? I just went to make the change and it looks to already be there?
#154
09/24/2009 (5:41 pm)
mouse drag is broken.
#155
@Bret - Elaborate. Broken doesn't describe the situation.
09/24/2009 (5:45 pm)
@Daryll - Turns out it is already supported. It just needs to be toggled, which has been discussed in the forums.@Bret - Elaborate. Broken doesn't describe the situation.
#156
Similar to Daryll's question, I was going to ask what is new because both 1.2 and 1.3 beta have the two lines of code.
09/24/2009 (6:14 pm)
What happened to Tim Newell's post? I can't find it on the main page and after going through the email link the thread is now locked.Similar to Daryll's question, I was going to ask what is new because both 1.2 and 1.3 beta have the two lines of code.
#157
There's been a lot of discussion in this thread about it.
Basically you never get onMouseDragged event callbacks.
09/24/2009 (6:56 pm)
@MichaelThere's been a lot of discussion in this thread about it.
Basically you never get onMouseDragged event callbacks.
#158
09/24/2009 (7:31 pm)
@Justin: I think the post was made in error. There is no memory issue. We are at war with Oceania ;)
#159
My game is ready and complete. the only reason I'm waiting for 1.3 is so you could listen to your own music while playing the game.
Not trying to rush you guys. not at all! I just want to know if I should wait or release as is.
Thanks.
09/25/2009 (2:44 pm)
Can we get a very rough eta? something in the lines of 1.3 is coming in the next month. or 1.3 is not coming in the next month.My game is ready and complete. the only reason I'm waiting for 1.3 is so you could listen to your own music while playing the game.
Not trying to rush you guys. not at all! I just want to know if I should wait or release as is.
Thanks.
#160
Can we get some news please on what is going on. It's been a while now since the "Beta" release came out. Some feed back would be nice. It's starting to get really annoying now all this silence.
Thanks,
Mike.
09/29/2009 (4:03 pm)
Is there any one there????Can we get some news please on what is going on. It's been a while now since the "Beta" release came out. Some feed back would be nice. It's starting to get really annoying now all this silence.
Thanks,
Mike.
Torque Owner Onyx
Default Studio Name