A few quick questions about iTorque 2d and Torque 2d

#1 1. iTorque 2D has gone through significant optimizations and editor changes to improve the deployment and runtimes for iOS devices. It introduces things like level datablocks, iOS device settings from the editor, etc. It has also been stripped of some Torque 2D features, like 3D shape rendering and a project deployment dialog. There's more, but that will be covered in the new FAQ.

2. Nope.

3. Nope

4. The two engines are wildly different. iTorque 2D is 100% pure 2D development. A real sprite manager, true 2D collision, focused 2D editor. You will primarily be working in C++ and TorqueScript, but you can also write some features in Objective-C. As for how difficult it would be to pick up, that really depends on your level of experience as a game developer and iPhone dev in general

5. http://docs.garagegames.com/it2d/official/. Start there to learn the basics.

#2 Okay that's all good to here. I know Unity and Torque 2d are very different I was really just saying I have some experience making simple games.

I just have one question left really: What are the differences between iTorque 2d on the Mac and iTorque 2d on Windows? and what would I have to do to publish a game to the app store made in iTorque 2d on Windows?

#3 Oh yeah one more thing, is there anywhere to get a free trial of iTorque 2d?

#4

Quote:What are the differences between iTorque 2d on the Mac and iTorque 2d on Windows?

Windows: You write your engine code in Visual Studio. You have access to Torsion.

OS X: You write your engine code in Xcode. You can write and compile Objective-C code. You can deploy to simulator and an iOS device

Quote:what would I have to do to publish a game to the app store made in iTorque 2d on Windows?

You cannot do this from Windows. You would have to move to a Mac to finish deployment.

Quote:Oh yeah one more thing, is there anywhere to get a free trial of iTorque 2d?

Afraid not. We only offer a trial for Torque 2D. This is not a perfect 1:1 representation, but a lot of the editors, features and scripting are shared. Not everything, but enough to give you an idea of the basic work flow (aside from deployment).

#5 Okay, and yes I know I can't publish from a PC. I really just want to know how much work I will have to do on the Mac I transfer it to before publishing.

#6 The more objective-c code you need to write, the sooner you should be on a Mac. If you are the kind of person who likes to test early and often, you should be running your app on a device from day one. There is nothing unique about the Windows build. It cannot do anything the Mac build can't. In some ways, it is gimped because it can't handle Objective-C coding and device testing.

#7 So I could just buy the license for iTorque 2d, download it, start working, then when I get a mac just download it onto the Mac without paying any more?

#8 @Michael - That is correct. You can download the engine and editors for both platforms, then just move your projects between the two.

We just released a preview build of 1.4.1, which is more stable and works out of the box. We will be releasing the final version of 1.4.1 soon, which is what you would want to work with.

#9 I am aware I can move the project, I just want to make sure I will not be paying for the engine again when I move to the Mac.