
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 |
18944 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.
Secondly, the UT3 engine DOES NOT WORK with android devices
I know this because I work with the UT3 engine
Whichever way you look at it, the whole Unreal Engine numbering system is deeply confusing.
All I Know is when I said Android is not working on UT3, I meant UDK (AKA UE3).
Secondly, the UT3 engine DOES NOT WORK with android devices
I made the mistake of calling it UT3 in one post.
That's simply bad grammar not a fundamental mistake.
Secondly, you have to pay a license fee to Epic UDK to make money from UDk.
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.
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.
So its not really a case of whether android does or does not run on UE3, its more of a case of what version.
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.
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.
As far as I am aware, and its pretty convoluted thanks to epics naming structure.
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.
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.
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.
The only thing I'm guilty of is overlooking the fact that I based my original focus on UDk which I did becaue.
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.
Easy mistake to make when you do more in life than just talk about things you read on forums.
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.
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."
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.
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.