Comments on: Six Different 3D and 2D Iphone Game Engines http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/ ManiacDev.Com Fri, 10 Sep 2010 08:11:00 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: I wanna make an iPhone game…now what? « iPhone Friend http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/comment-page-1/#comment-4235 I wanna make an iPhone game…now what? « iPhone Friend Thu, 22 Jul 2010 22:56:15 +0000 http://maniacdev.com/?p=82#comment-4235 [...] game (a 2D over head tile map shooter) I chose cocos2d although there are many others (good lists here and here). Why did I choose cocos2d and why would I suggest it to other newbie game [...] [...] game (a 2D over head tile map shooter) I chose cocos2d although there are many others (good lists here and here). Why did I choose cocos2d and why would I suggest it to other newbie game [...]

]]> By: sio2interactive http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/comment-page-1/#comment-1067 sio2interactive Sun, 18 Apr 2010 07:46:13 +0000 http://maniacdev.com/?p=82#comment-1067 There's also an alternative that gives you the opportunity to develop directly for iPhone and iPad on Windows using Microsoft Visual C++. Take a look at: http://www.youtube.com/watch?v=e_I8MK8cfYI For more information visit: http://sio2interactive.com/SIO2_iPad_and_iPhone_3D_Game_Engine_Download.html There’s also an alternative that gives you the opportunity to develop directly for iPhone and iPad on Windows using Microsoft Visual C++.

Take a look at:

http://www.youtube.com/watch?v=e_I8MK8cfYI

For more information visit:

http://sio2interactive.com/SIO2_iPad_and_iPhone_3D_Game_Engine_Download.html

]]> By: sio2interactive http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/comment-page-1/#comment-7005 sio2interactive Sun, 18 Apr 2010 07:46:00 +0000 http://maniacdev.com/?p=82#comment-7005 There's also an alternative that gives you the opportunity to develop directly for iPhone and iPad on Windows using Microsoft Visual C++. Take a look at: http://www.youtube.com/watch?v=e_I8MK8cfYI For more information visit: http://sio2interactive.com/SIO2_iPad_and_iPhone_3D_Game_Engine_Download.html There’s also an alternative that gives you the opportunity to develop directly for iPhone and iPad on Windows using Microsoft Visual C++.

Take a look at:

http://www.youtube.com/watch?v=e_I8MK8cfYI

For more information visit:

http://sio2interactive.com/SIO2_iPad_and_iPhone_3D_Game_Engine_Download.html

]]> By: sjdude http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/comment-page-1/#comment-974 sjdude Sat, 10 Apr 2010 17:01:10 +0000 http://maniacdev.com/?p=82#comment-974 @RW: Thanks very much for an insightful, real world review of Unity3D. @RW: Thanks very much for an insightful, real world review of Unity3D.

]]> By: sjdude http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/comment-page-1/#comment-7004 sjdude Sat, 10 Apr 2010 17:01:00 +0000 http://maniacdev.com/?p=82#comment-7004 @RW: Thanks very much for an insightful, real world review of Unity3D. @RW: Thanks very much for an insightful, real world review of Unity3D.

]]> By: RW http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/comment-page-1/#comment-909 RW Sat, 03 Apr 2010 08:16:36 +0000 http://maniacdev.com/?p=82#comment-909 I have used Unity3D Iphone for over 9 months. Here are the objective pros/cons. Pros: 1. The editor is very good and meshes well with rapid prototyping design methodology. 2. The community is very helpful. Many useful snippets of code have been contributed to the public, and this will save you a lot of time. Some are critical (read GUIManager2) and would take months to recreate yourself. 3. You can script in 2 different scripting languages - Jave and C# (Boo is not supported for iPhone). 4. Because you are scripting and dealing with the engine at a high level, you won't get bogged down with low level details. Cons: 1. You can't use SVN/CVS or any other version control software. Unity uses binaries that change constantly. So if you are going to work on a project with more than 1 person, you realistically have to buy their asset server. (They have been claiming for a long time they will make it work with SVN but selling their asset server is a revenue stream for them; don't expect it anytime soon). This makes their costs deceptive when doing a price comparison. Until very recently you had to buy Unity Pro just to get the asset server even if you only wanted Unity Iphone (they are different). The total cost for all that came out to around $2k. So you think "oh it is just $300 bucks," but that is just the teaser to get you into the door. 2. You can't use the iPhone simulator. Unity writes instructions directly for the ARM processor. So the iphone simulator will not work. You will realistically need to test on an actual device. 3. #2 can also lead to problems when apple has a bug. For example, because of a bug with apple you can't compile Unity iPhone for an OS greater than 3.0. So if there is some feature in 3.1 or 3.2. You won't be able to use it. 4. Unity GameObjects have 2 initialization phases, Start and Awake, and their non-deterministic behavior can very subtly and harshly bite you in the ass if you don't know what you are doing. 5. If you script in C#, you will want to install parallels or its like to simultaneously run windows and Visual Studio C#. Mono is just not good enough. This means buying a windows license and parallels type software. Overall the engine is is good. Time is money and you will probably get your game to market much faster than other engines. But you will pay more for this engine and its features. I have used Unity3D Iphone for over 9 months. Here are the objective pros/cons.
Pros:
1. The editor is very good and meshes well with rapid prototyping design methodology.
2. The community is very helpful. Many useful snippets of code have been contributed to the public, and this will save you a lot of time. Some are critical (read GUIManager2) and would take months to recreate yourself.
3. You can script in 2 different scripting languages – Jave and C# (Boo is not supported for iPhone).
4. Because you are scripting and dealing with the engine at a high level, you won’t get bogged down with low level details.

Cons:
1. You can’t use SVN/CVS or any other version control software. Unity uses binaries that change constantly. So if you are going to work on a project with more than 1 person, you realistically have to buy their asset server. (They have been claiming for a long time they will make it work with SVN but selling their asset server is a revenue stream for them; don’t expect it anytime soon).

This makes their costs deceptive when doing a price comparison. Until very recently you had to buy Unity Pro just to get the asset server even if you only wanted Unity Iphone (they are different). The total cost for all that came out to around $2k. So you think “oh it is just $300 bucks,” but that is just the teaser to get you into the door.
2. You can’t use the iPhone simulator. Unity writes instructions directly for the ARM processor. So the iphone simulator will not work. You will realistically need to test on an actual device.
3. #2 can also lead to problems when apple has a bug. For example, because of a bug with apple you can’t compile Unity iPhone for an OS greater than 3.0. So if there is some feature in 3.1 or 3.2. You won’t be able to use it.
4. Unity GameObjects have 2 initialization phases, Start and Awake, and their non-deterministic behavior can very subtly and harshly bite you in the ass if you don’t know what you are doing.
5. If you script in C#, you will want to install parallels or its like to simultaneously run windows and Visual Studio C#. Mono is just not good enough. This means buying a windows license and parallels type software.

Overall the engine is is good. Time is money and you will probably get your game to market much faster than other engines. But you will pay more for this engine and its features.

]]> By: RW http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/comment-page-1/#comment-7003 RW Sat, 03 Apr 2010 08:16:00 +0000 http://maniacdev.com/?p=82#comment-7003 I have used Unity3D Iphone for over 9 months. Here are the objective pros/cons. Pros: 1. The editor is very good and meshes well with rapid prototyping design methodology. 2. The community is very helpful. Many useful snippets of code have been contributed to the public, and this will save you a lot of time. Some are critical (read GUIManager2) and would take months to recreate yourself. 3. You can script in 2 different scripting languages - Jave and C# (Boo is not supported for iPhone). 4. Because you are scripting and dealing with the engine at a high level, you won't get bogged down with low level details. Cons: 1. You can't use SVN/CVS or any other version control software. Unity uses binaries that change constantly. So if you are going to work on a project with more than 1 person, you realistically have to buy their asset server. (They have been claiming for a long time they will make it work with SVN but selling their asset server is a revenue stream for them; don't expect it anytime soon). This makes their costs deceptive when doing a price comparison. Until very recently you had to buy Unity Pro just to get the asset server even if you only wanted Unity Iphone (they are different). The total cost for all that came out to around $2k. So you think "oh it is just $300 bucks," but that is just the teaser to get you into the door. 2. You can't use the iPhone simulator. Unity writes instructions directly for the ARM processor. So the iphone simulator will not work. You will realistically need to test on an actual device. 3. #2 can also lead to problems when apple has a bug. For example, because of a bug with apple you can't compile Unity iPhone for an OS greater than 3.0. So if there is some feature in 3.1 or 3.2. You won't be able to use it. 4. Unity GameObjects have 2 initialization phases, Start and Awake, and their non-deterministic behavior can very subtly and harshly bite you in the ass if you don't know what you are doing. 5. If you script in C#, you will want to install parallels or its like to simultaneously run windows and Visual Studio C#. Mono is just not good enough. This means buying a windows license and parallels type software. Overall the engine is is good. Time is money and you will probably get your game to market much faster than other engines. But you will pay more for this engine and its features. I have used Unity3D Iphone for over 9 months. Here are the objective pros/cons.
Pros:
1. The editor is very good and meshes well with rapid prototyping design methodology.
2. The community is very helpful. Many useful snippets of code have been contributed to the public, and this will save you a lot of time. Some are critical (read GUIManager2) and would take months to recreate yourself.
3. You can script in 2 different scripting languages – Jave and C# (Boo is not supported for iPhone).
4. Because you are scripting and dealing with the engine at a high level, you won’t get bogged down with low level details.

Cons:
1. You can’t use SVN/CVS or any other version control software. Unity uses binaries that change constantly. So if you are going to work on a project with more than 1 person, you realistically have to buy their asset server. (They have been claiming for a long time they will make it work with SVN but selling their asset server is a revenue stream for them; don’t expect it anytime soon).

This makes their costs deceptive when doing a price comparison. Until very recently you had to buy Unity Pro just to get the asset server even if you only wanted Unity Iphone (they are different). The total cost for all that came out to around $2k. So you think “oh it is just $300 bucks,” but that is just the teaser to get you into the door.
2. You can’t use the iPhone simulator. Unity writes instructions directly for the ARM processor. So the iphone simulator will not work. You will realistically need to test on an actual device.
3. #2 can also lead to problems when apple has a bug. For example, because of a bug with apple you can’t compile Unity iPhone for an OS greater than 3.0. So if there is some feature in 3.1 or 3.2. You won’t be able to use it.
4. Unity GameObjects have 2 initialization phases, Start and Awake, and their non-deterministic behavior can very subtly and harshly bite you in the ass if you don’t know what you are doing.
5. If you script in C#, you will want to install parallels or its like to simultaneously run windows and Visual Studio C#. Mono is just not good enough. This means buying a windows license and parallels type software.

Overall the engine is is good. Time is money and you will probably get your game to market much faster than other engines. But you will pay more for this engine and its features.

]]> By: Robert http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/comment-page-1/#comment-4149 Robert Thu, 28 Jan 2010 22:36:06 +0000 http://maniacdev.com/?p=82#comment-4149 Bork3D was just tested last night w/ iPad. After a two-line modification the engine runs flawlessly as a native iPad application. Bork3D was just tested last night w/ iPad. After a two-line modification the engine runs flawlessly as a native iPad application.

]]> By: mayurshah http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/comment-page-1/#comment-4150 mayurshah Thu, 28 Jan 2010 17:44:08 +0000 http://maniacdev.com/?p=82#comment-4150 Hi, We have Cocoas2D with developer and used that for one of game development and we get good result now we are developing same game with 3D in iPhone and using OpenGL and other - Thanks Hi, We have Cocoas2D with developer and used that for one of game development and we get good result now we are developing same game with 3D in iPhone and using OpenGL and other – Thanks

]]> By: Robert http://maniacdev.com/2009/04/6-different-3d-and-2d-iphone-game-engines/comment-page-1/#comment-762 Robert Thu, 28 Jan 2010 14:36:06 +0000 http://maniacdev.com/?p=82#comment-762 Bork3D was just tested last night w/ iPad. After a two-line modification the engine runs flawlessly as a native iPad application. Bork3D was just tested last night w/ iPad. After a two-line modification the engine runs flawlessly as a native iPad application.

]]>