| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | |||
7889 Hits


| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | |||

UT3 and Cry Engine are high end engines and do not favour those devices."Favour", no matter your definition of it, is incorrect. Not only is the engine perfectly suited to a mobile platform, but it works on all mobile platforms. Additionally, it has already been licensed multiple times.
Secondly, the UT3 engine DOES NOT WORK with android devicesWrong in every way.
I know this because I work with the UT3 engineIt's the Unreal Engine 3, not the Unreal Tournament 3 engine. You have made this mistake multiple times, and your inability to even know the difference between the base U3 engine and the UDK shows that you probably haven't even PLAYED a U3 engine game, let alone touched the source code.
Whichever way you look at it, the whole Unreal Engine numbering system is deeply confusing.Unreal Engine 1
All I Know is when I said Android is not working on UT3, I meant UDK (AKA UE3).No, do you need a reminder what you said?
Secondly, the UT3 engine DOES NOT WORK with android devicesYou said that the "UT3" engine, which can only be the engine that UT3 uses (Unreal Engine 3) does not work on android. It does, and even the UDK, which uses Unreal Engine 3, works. You should really stop trying to twist your words to escape how wrong you were, as you're only being more wrong. Keep going, though - I'm sure there's still something left for you to get wrong.
I made the mistake of calling it UT3 in one post.1x http://www.esreality.com/?a=post&id=2089904#pid2089904
That's simply bad grammar not a fundamental mistake.It's a mistake that you wouldn't make if you actually used Unreal Engine 3, or even knew anything about it. You don't.
Secondly, you have to pay a license fee to Epic UDK to make money from UDk.The license fee for selling UDK games is $99, up to $50,000 in sales. What does this have to do with anything?
You really should stop telling medo not do something when you have no idea. I do use the UDK which is why I said Android is not running on it, and to the best of my knowledge, that is still true.Again, UDK is free to use, and to develop for. A small fee is required for charging money for your app, but an actual full license for the Unreal Engine 3 would come with far more support/tools/power, and a very large price tag. In the link YOU provided to try to argue that it doesn't work, it SAYS that it works. The problem isn't the information, it's you.
What you're saying is Android runs on the version that costs a shitload of money, while iOS runs on the version that costs's next to nothing.Any UDK license costs $99 if you plan to charge for it, regardless of platform. You can already create UDK games for Android, but you must simply wait for google to fix the issue on android before they can actually be used.
So its not really a case of whether android does or does not run on UE3, its more of a case of what version.UDK is a toolkit for developing Unreal Engine 3 games. Do you not know what an engine is?
Bottom line is most people apart from established devs with 10's or 100's of thousands are not going to be able to produce a game at present on that engine.Epic isn't the one that needs to fix anything - Google does. Read your link. You can already develop for android just fine, and it will be perfectly ready for the platform once Google fixes the issue. This issue applies equally to everything on android, including other engines.
THose using iOS can. At least until Epic implement it in UDK.
Which is the thing most devs will get excited about.
I said it was not on Android Via UE/T3 becuase I was referring to the UDK which I admitted was an oversignt by me because I was so focused on the UDK.Need a reminder of what you said again? Here, let me help you:
As far as I am aware, and its pretty convoluted thanks to epics naming structure.Try to keep up with your lies. At least read your old posts to make sure that you don't step on your own toes.
When you said U3, you also brought UDK into the equation becuase UDK uses UE3.
I alsosaid "Anyone making a game for mobile devices will want it to work on iOS and Android". They are both important markets for time being, but Android is reeling it in.And anyone making a game for both markets can make it on both.
That's a matter of opinion and one that assumes that the game is going or needs to be high end. Ue3 is pretty expensive, so unless the device can utilise the features of the engine that make it stand out, you might well find its not needed. There are fairly decent pc's out there that struggle to run UDK at good frame rates. So a high end engine may not be needed.Is it? Please point me to another high end engine that you can even license, that has already been confirmed for both mobile platforms, and that has even remotely as reasonable a license agreement.
Again, I did not switch anything, I based my original opinion on UDK, which was quite easy to do because you STILL can't export android to UDK to best of my knowledge. You STILL needed to pay a licese fee. To make games with UDk.Making games with UDK is free. Please point to any engine that you can use to develop a game that allows you to sell it without paying a license fee. Hell, it doesn't even have to be on the same level of quality as U3. This is not even an argument, and has nothing to do with the discussion. You were trying to argue the merits of a tech5-based engine on mobile platforms, and id has never had any sort of reasonable license for small developers. Again, you're just giving yourself more ways to be proven wrong.
The only thing I'm guilty of is overlooking the fact that I based my original focus on UDk which I did becaue.No high end engine is working on Android, so you're guilty of trying to make UDK look bad when the problem is Android itself. You're guilty of trying to make it seem like licensing UDK to sell is a big deal, when EVERY engine requires it, but none are as reasonable.
A) iOS was working on UDK
B) Android was not.
C) You still needed to license UDK
my two main arguements was that Android was not working on U3, becuase I was referring to UDk (BECAUSE , which you yourself are not promoting over the fully licesed version which is beyond the reach of most people in the modding community.I promote both, since the U3 engine is quite good. U3 engine has amazing scaling ability on the PC, and supports many platforms. UDK supports all platforms (but is waiting for a fix by google so that they can be published on Android) and has the best independent developer license that I've ever seen for the quality of the product.
Easy mistake to make when you do more in life than just talk about things you read on forums.For anyone with any knowledge of the engine, you most specifically wouldn't have made the mistake of referring to it as the "UT3" engine. Not only could that not be confused with UDK, but it's not even an engine. You even spent a good portion of this post trying to make it seem as if Epic has some difficult naming structure for the engines, when they only have 3 engines, and they are very obviously named.
To this day, it still appears to not be supported in UDK and the reasons for doing so are NOT JUST because of the filesize.Why don't you ask them, since that's exactly what THEY SAID, even in the link you tried to use to say that it didn't work.
If that was the case then why not just enable and put extra pressure on google.
Also in my original point, I said "UT3 and Cry Engine are high end engines and do not favour those devices."I never mentioned cryengine, and it has nothing to do with the discussion. The fact remains, you tried to say that "UT3" was not "favoured" on mobile platforms, and you were proven completely wrong. Do you need a reminder of what I said to you in response? The only reason we are here at this point is because you feel the need to keep making up excuses for why you were so wrong - you should have just ragequit the thread when you were first proven completely wrong.
Not just U3.
On the point of high end engines, I don't believe you need a high end engine for a good looking mobile game. A company like Epic/Crytek/idExcel at the high end market, its easier when you can't go all out.Fine, what mid-range or even low end engine are you referring to that competes with U3? Go ahead, show me this engine that "favours" mobile platforms, and that is has no license cost for you to sell games that are produced with it. I'm all ears!
If you would like to continue agree to export a standalone executable from inside UDK that runs and Andorid. Nothing fancy. Just a cube or something to show proof of concept so no fancy skills required.Reading skills are required, and you don't have them. I don't know how many times I'm going to have to point it out to you.