iTorque 2D 1.4.1 Preview Details
by Michael Perry · in iTorque 2D · 02/11/2011 (5:45 pm) · 27 replies
iTorque 2D 1.4.1 *PREVIEW*
In your accounts is a preview of iTorque 2D 1.4.1. This build does not represent the final release, but it does contain many bug fixes promised for the 1.4.1 release. Consider this a bug fix preview, not a final. This is the thread to post observations. For new bugs, create new threads using the bug reporting standard.
Expectations
This build has not gone through our full QA process. It has only passed acceptance criteria, which means it is usable. Issues may still be discovered during testing, even by you. Know that this does not fully represent the final product, but does give you a chance to see if it will meet your needs. There are always outlier issues that crop up when opening up testing to a massive user base. The best way to test on multiple systems is to bring you all into the fold.Setup
If you have any previous installations of iTorque 2D, you will need to remove them completely. This build is not tested for compatibility with multiple installations and is not expected to "play nicely".On Windows: you will want to run the uninstaller and delete the engine preferences directory. Ex: C:/Users/Mich/App/Data/Roaming/TorquePowered.
On OS X: You can delete the entire iTorque 2D directory (no uninstaller) and remove the preferences directory. Ex: Users/Mich/Library/TorquePowered.
The installers for iTorque 2D 1.4.1 are guided. Just follow the instructions and you should be able to start building out of the box.
Known Issues
- DOCUMENTATION IS INCOMPLETE. We are still adding new tutorials and will be completely removing old docs that do not apply to iTorque 2D 1.4.1. In this preview build, you will see some missing content or find old TGB docs that do not seem to work with iT2D. Know this will be taken care of in the final release.- DEMOS ARE INCOMPLETE. We have removed the older demos that were not documented, were confusing or flat out did not run. You can see we are in the process of adding new demos that contain more interesting content and show off more features. The MusicPlayerExample is a finished demo, but will only work properly on a device if you have music in your iOS library. The foundation of the Shooter demo is in the installer, but it does not contain all the assets, game play or flow. The final demo should have clearly defined beginning, game play and ending. This will also be coupled with a tutorial. There will also be a Rainy Day demo for both iPhone and iPad.
- Particle emitter fixes not fully in place, will be for final release.
- Compiler warnings in example projects. We are still working on modifying our code to reduce the number of warning spit out by Xcode. More than just making it very difficult to debug problems, warnings are the pain in the arm before the heart attack. We will reduce as many as we can without having to completely refactor systems.
- Not tested against Xcode 4
- Multi-touch enhancement not in place yet
- Opening or creating another project from an existing one causes a reset of the editor screen
- Windows 7/Vista users without admin access and UAC turned on must run as an administrator. Read this thread for solution
- Older projects not tested against new build. No guarantee of perfect porting yet.
About the author
Programmer.
#2
02/11/2011 (5:51 pm)
Since we've got a lot of new users, this is a good time for everyone to refresh themselves/read for the first the Bug Reporting standard for the forums.
#3
02/11/2011 (5:52 pm)
This be the thread to post observations. For new bugs, create new threads using the bug reporting standard Scott posted. 
#4
02/11/2011 (6:02 pm)
Woot~ Builds OOB with only 67 errors, most of which are saying string constants to char* are deprecated or otherwise related to such. <3 
#5
Very nice and clean release, but still a ton of warnings with the beta SDKs. You'll get the numbers down over time, I'm sure. It's a moving target, so we can only try to catch up. I'll post a feature suggestion or two.
02/11/2011 (6:17 pm)
Having looked at it, I think Xcode 4 won't be a huge issue yet. It might be more frustrating trying to use the current version than fixing any incompatibilities later ;)Very nice and clean release, but still a ton of warnings with the beta SDKs. You'll get the numbers down over time, I'm sure. It's a moving target, so we can only try to catch up. I'll post a feature suggestion or two.
#6
02/11/2011 (6:49 pm)
@Ken - Warnings or errors? 
#7
02/12/2011 (4:29 am)
thanks for the release. hope to find some time to toy with it this weekend :)
#8
02/12/2011 (3:06 pm)
Just warnings, Mich. Nearly all of them saying that conversion between a const string to char* is deprecated and whining about the deprecation of the cString call. :P 
#9
02/14/2011 (6:46 pm)
Not sure if this is because I did a full merge of 1.4.1 over a 1.4 build, however I found that I was completely unable to set the project orientation to anything but Portrait. Attempting to change it to Landscape caused the device to stay in Portrait mode, and the rendering of the game to rotate and be squished (imagine a Landscape game playing in a Portrait display, but oriented in Portrait mode).
#10
02/14/2011 (7:09 pm)
When you say a "full merge", what do you mean? Keep in mind the two versions are not going to place nice with each other at all.
#11
1. Did just merge the source code and not scripts?
2. Are you working with a new project or an old one?
02/15/2011 (7:14 am)
@Dave - Some questions:1. Did just merge the source code and not scripts?
2. Are you working with a new project or an old one?
#12
02/17/2011 (10:39 am)
Is there a proper change log somewhere for this?
#13
02/17/2011 (10:50 am)
@Justin - I did not generate one for the Preview, but I will have one for the final release. 
#14
03/02/2011 (8:17 am)
@Perry: is there any ETA for final release 1.4.1? 
#15
03/03/2011 (3:18 pm)
@Michael - Could you give us an update on the progress with 1.4.1 please? 
#16
03/03/2011 (9:05 pm)
Yes please provide an update, I am eager to start going through tutorials that won't frustrate me.
#17
03/03/2011 (11:42 pm)
Hey everyone. Just flew back into town. 11:43pm here. Came in, hugged the wife, patted the dogs, then got on to see what's happening in the forums. I will post an update tomorrow.
#18
The content of the future releases is going to make everyone very, VERY happy. Once those plans are put on paper, we would be willing to release them so you all know what to expect.
03/05/2011 (9:16 am)
QA has to perform a regression test on everything fixed from the from the preview. That starts Monday, which gives me time to wrap up the docs. Additionally, while I was at GDC last week I had some lengthy discussions about iTorque 2D 1.4.1 and future versions of the engine with the owners, Eric and Dexter. They were extremely helpful in helping me plan out future development.The content of the future releases is going to make everyone very, VERY happy. Once those plans are put on paper, we would be willing to release them so you all know what to expect.
#19
03/05/2011 (11:05 am)
These are excellent news. Thanks and happy development.
#20
03/15/2011 (7:55 am)
We start our final QA pass today. A QA pass typically lasts 5-6 days. I'm not expecting anymore surprises. We were able to find a few more critical bugs, like iPad support being busted, editor crashes and work flow, 4.3 compiler errors and so on. This is the homestretch. 
Torque Owner Scott Wilson-Billing
MeYuMe