Still can't run tappy chicken

[Maxunit]

I just grabbed UE4 4.2.1 and downloaded Tappy Chicken. I compiled it for my Android Device, which is a Samsung Galaxy S3 I9300 and Tappy Chicken runs fine in Debug mode and ATC. If I open the Dev Console on the Smartphone, it says, that it uses ETC1, but anyway.

EDIT:

I have to correct it a bit. Somehow entities which are defined by Fonts, like the count for the passed obstacles, are not being displayed on my SGS3. On another hand, I have to inform you, that my SGS3 is rooted and has the Android Ice Cold Project ROM installed, which is based on Android 4.4 KitKat. Might be the issue, since another App also has display issues with certain font types.

[KillerSneak]

@Maxunit;84737

I just grabbed UE4 4.2.1 and downloaded Tappy Chicken. I compiled it for my Android Device, which is a Samsung Galaxy S3 I9300 and Tappy Chicken runs fine in Debug mode and ATC. If I open the Dev Console on the Smartphone, it says, that it uses ETC1, but anyway.

EDIT:

I have to correct it a bit. Somehow entities which are defined by Fonts, like the count for the passed obstacles, are not being displayed on my SGS3. On another hand, I have to inform you, that my SGS3 is rooted and has the Android Ice Cold Project ROM installed, which is based on Android 4.4 KitKat. Might be the issue, since another App also has display issues with certain font types.

Same thing here doesn’t work an a Samsung Galaxy S3. I just took the 4.3 source from github and want to compile it. I just need to know the right steps to take firts.

#1 -> build with “Development Editor” - “Win64”
#2 -> rebuild with “Shipping” - “Android”

→ this is where i don’t know what to do. The #1 step is to simply compile the editor itself and make it work. Now to be able to test via direct install to the phone or uploading a signed APK to Google Play Developer Console I need to rebuild/build a Shipping - Android I assume but I can’t find any answers or documentation about this subject. Even Epic’s video on YouTube only shows the “Development Editor” - “Win64” build but nothing is mentioned about rebuilding/building it for other platforms what so ever.

If anybody has info on this I would be glad to hear/read it. This again shows that Epic isn’t sharing it’s resources to be honest. It said tappy chicken was shipped with the 4.2 build, we are on 4.2.1 and still can’t get AdMob and Gamecenter to work. Imho they should push a fix for this. As a indie developer not being able to run ads or gamecenter or even have the functionality to test it is a big big error on epic’s side.

[Michael_Noland]

Hi KillerSneak,

@KillerSneak;91493

Same thing here doesn’t work an a Samsung Galaxy S3. I just took the 4.3 source from github and want to compile it. I just need to know the right steps to take firts.

#1 -> build with “Development Editor” - “Win64”
#2 -> rebuild with “Shipping” - “Android”

You shouldn’t need a Shipping configuration for testing, it’s only needed when you want to get a better idea of the final file size, and to submit to the store, and even then you only need a Shipping game target and should use Development Editor for the Editor (e.g., “Shipping” + “Android”, and “Development Editor” + “Win64”). To change configurations, use the “Solution Configuration” dropdown in Visual Studio, and to change platforms use the “Solution Platforms” dropdown. One or both of these might be hidden by default in Visual Studio Express, I don’t remember exactly.

@KillerSneak;91493

If anybody has info on this I would be glad to hear/read it. This again shows that Epic isn’t sharing it’s resources to be honest. It said tappy chicken was shipped with the 4.2 build, we are on 4.2.1 and still can’t get AdMob and Gamecenter to work. Imho they should push a fix for this. As a indie developer not being able to run ads or gamecenter or even have the functionality to test it is a big big error on epic’s side.

We tried to be as transparent as we could RE: what was shipped and when:

What’s next?

Due to the difference in timeframes, we ended up shipping this release on a branch off of Master instead of 4.2 (all changes have been merged back to Master as of today); most of the changes made it in for 4.2, but a few Android and HTML5 fixes won’t be in the Launcher version until 4.3.

(from https://www.unrealengine.com/blog/shipping-tappy-chicken)

Cheers,
Michael Noland

[Michael_Noland]

@Maxunit;84737

I have to correct it a bit. Somehow entities which are defined by Fonts, like the count for the passed obstacles, are not being displayed on my SGS3. On another hand, I have to inform you, that my SGS3 is rooted and has the Android Ice Cold Project ROM installed, which is based on Android 4.4 KitKat. Might be the issue, since another App also has display issues with certain font types.

The TextRenderComponent was using 32 bit index buffers, which is an optional feature for OpenGL ES2 and isn’t supported on all devices. This was fixed in CL# 2078450 (which missed 4.2 by a few days but will be in 4.3) to use 16 bit index buffers. I can try to dig up the GitHub equivalent changelist if you are building from source.

[EDIT] Here is the commit to master: https://github.com/EpicGames/UnrealEngine/commit/2e07d2efa5580af6080d55c33769f7cf21affcb1#diff-8ffcc4eb9ec7dc5987d8866ea283f337

Cheers,
Michael Noland

[KillerSneak]

@Michael Noland;91603

The TextRenderComponent was using 32 bit index buffers, which is an optional feature for OpenGL ES2 and isn’t supported on all devices. This was fixed in CL# 2078450 (which missed 4.2 by a few days but will be in 4.3) to use 16 bit index buffers. I can try to dig up the GitHub equivalent changelist if you are building from source.

[EDIT] Here is the commit to master: https://github.com/EpicGames/UnrealEngine/commit/2e07d2efa5580af6080d55c33769f7cf21affcb1#diff-8ffcc4eb9ec7dc5987d8866ea283f337

Cheers,
Michael Noland

Any idea/information about the official 4.3 release?

[Michael_Noland]

We were aiming for RC0 today, but I think we missed by just a couple of bugs. After our first release candidate, it typically takes one to two weeks to hit a final candidate, do all of the launch prep stuff, and get it out the door. No promises, but mid-July seems realistic.

Cheers,
Michael Noland

[Maxunit]

@Michael Noland;91603

The TextRenderComponent was using 32 bit index buffers, which is an optional feature for OpenGL ES2 and isn’t supported on all devices. This was fixed in CL# 2078450 (which missed 4.2 by a few days but will be in 4.3) to use 16 bit index buffers. I can try to dig up the GitHub equivalent changelist if you are building from source.

[EDIT] Here is the commit to master: https://github.com/EpicGames/UnrealEngine/commit/2e07d2efa5580af6080d55c33769f7cf21affcb1#diff-8ffcc4eb9ec7dc5987d8866ea283f337

Cheers,
Michael Noland

Thank you for pointing this out, Michael Noland. I am currently using the Launcher and the pre-build Bin version from UE4 4.2.1, but I can also clone the Git source and compile the 4.3 Preview and check out, if it is fixed on the SGS3

[KillerSneak]

@Michael Noland;91755

We were aiming for RC0 today, but I think we missed by just a couple of bugs. After our first release candidate, it typically takes one to two weeks to hit a final candidate, do all of the launch prep stuff, and get it out the door. No promises, but mid-July seems realistic.

Cheers,
Michael Noland

Thanks for the info although I really doubt this problem will be fixed. 4.2.1 runs my game fine 4.3 doesn’t (only a black screen) Is there any info I can supply to get this fixed / help the progress in fixing this problem? I rebuild the source today so it’s the 4.3 version from 09-07-2014 with the latest commits.

[Michael_Noland]

Hi KillerSneak,

Sorry to hear that it’s not working with 4.3. Do you see anything in the device log indicating a crash or failure to load/compile a shader or something, etc…? That’d be the first step I’d try, and I’ll ask around to see if anyone knows about any outstanding S3 issues.

Cheers,
Michael Noland

[Michael_Noland]

Heya,

There is an outstanding bug for 4.3 with GooglePlay that is being looked at right now:

We’re looking at a GooglePlay issue that causes black screen

for dist build, adding:

-keep class com.epicgames.ue4.GameActivity$JavaAchievement {
   public *;
}

to proguard-project.txt in Engine/Build/Android/Java will let it work if player signs in, then runs it again for us, but get a black screen if connection fails or have to sign in with dialog.
We’re still working on it so I’d recommend waiting for full fix.

Cheers,
Michael Noland

[ST64]

I first tested on Android 4.04. When I installed Tappy from an SD card I get a blank screen, then it dies. When I installed it over USB using the included .bat file, it popped up a message box saying GooglePlay needed to be updated. I updated GooglePlay, and it crashed again. Finally I uninstalled GooglePlay and it worked.

This is only my first month with Unreal 4 Engine and I have to say I am very disappointed by the lack of professionalism in this area of the program. Your Editor is top-notch, and you engine is the best in the market, but you completely gloss over the most important part, getting the darn thing distributed. You don’t seem to have any video tutorials on packaging, your manual is also lacking in this regard. If anything, this should be your biggest focus, because the indie market can’t survive on PC alone. I hope you guys get this working very, very soon.

[Edgaras.Randis]

Just got a notification on this thread. First of all, I wasn’t able to run any of the demos of unreal on the phone gs3-4.3 android, second of all, there was a rumor that samsung released a faulty version of android: https://community.verizonwireless.com/thread/812849 . For my understanding it only concerns samsung devices. Report log of full program startup in the first post: http://pastebin.com/3r1nwR4h .

[ST64]

@Edgaras.Randis;93487

Just got a notification on this thread. First of all, I wasn’t able to run any of the demos of unreal on the phone gs3-4.3 android, second of all, there was a rumor that samsung released a faulty version of android: https://community.verizonwireless.com/thread/812849 . For my understanding it only concerns samsung devices. Report log of full program startup in the first post: http://pastebin.com/3r1nwR4h .

This is really frustrating isn’t it? I can’t get anything to work, even a Blank project to work on any of my Android devices. Nobody from Epic really wants to help either.

[RCaloca]

@Edgaras.Randis;93487

Just got a notification on this thread. First of all, I wasn’t able to run any of the demos of unreal on the phone gs3-4.3 android, second of all, there was a rumor that samsung released a faulty version of android: https://community.verizonwireless.com/thread/812849 . For my understanding it only concerns samsung devices. Report log of full program startup in the first post: http://pastebin.com/3r1nwR4h .

Edgaras, I noticed this on your log: Couldn’t find Shader TBasePassForForwardShadingVSTLightMapPolicyLQLDRGamma32 for Material Resource WorldGridMaterial!; are you building from source?

[Edgaras.Randis]

@RCaloca;94001

Edgaras, I noticed this on your log: Couldn’t find Shader TBasePassForForwardShadingVSTLightMapPolicyLQLDRGamma32 for Material Resource WorldGridMaterial!; are you building from source?

If you mean by engine source, then both. With source compiled by myself and executable that comes from unreal launcher. Can’t remember just if the log is from my compiled version or yours.

If it gives any more insight clues, the phone model is European, gt-i9300

[KillerSneak]

Can you guys tell me where to find the log files so I can take a look as well ?

@ Michael Noland If I disable the Gamecenter polling will it work then? I’m now downloading the latest master source as the last 4.3 source (including commit of today) doesn’t compile anymore and gives a ton of errors and will

-keep class com.epicgames.ue4.GameActivity$JavaAchievement { public *; }

Fix the problem for now?

[KillerSneak]

Seems the above helped with fixing the game not running on my devices. At this moment it runs the game but Gamecenter doesn’t seem to work anymore

-keep class com.epicgames.ue4.GameActivity$JavaAchievement {
   public *;
}

to proguard-project.txt in Engine/Build/Android/Java will let it work if player signs in, then runs it again for us, but get a black screen if connection fails or have to sign in with dialog.
*We’re still working on it so I’d recommend waiting for full fix. *

So this temp fix allows me to run the game on my devices again but without Gamecenter or AdMob working so it seems.

[KillerSneak]

Another bump / it runs but like i said gamecenter and admob aren’t working.

The XML layout for the AndroidManifest doesn’t seem to be right if I compare it with the google documentation.

https://developers.google.com/mobile-ads-sdk/docs/admob/play-migration and https://developers.google.com/mobile-ads-sdk/docs/#play-metatag

[KillerSneak]

Doesn’t work, the game loads -> but Play Services doesn’t -> seems the game loads / want’s to connect to the play services but then crashes and asks me if I want to send a crash report.

There are still some major failures with the UE4 engine. Especially when converting a project from an older build to a newer like 4.2.1 to 4.3. Several XML files don’t get updated.

**\Build\Android\AndroidManifest.XML **this file isn’t updated between engine versions mine was missing a ton of play services and admob related entries.
**\Build\Android\proguard-project.txt **this file also wasn’t updated and was missing a lot of entries going from 4.2.1 to 4.3
**\Build\Android\res\values\GooglePlayAppID.XML **this file doesn’t seem to follow the documentation from google. https://developers.google.com/games/services/android/quickstart#step_3_modify_your_code
as it only holds the app_id and no achievement or leaderboard ID’s at all.

according to Google the **\Build\Android\res\values**folder should hold a ids.xml file that contains all the specific ID’s related to your app/achievements/leaderboards

To run the game, you need to configure the application ID as a resource in your Android project. You will also need to add games metadata in theAndroidManifest.xml.

1. Open res/values/ids.xml and replace the placeholder IDs. If you are creating an Android game from scratch, you will need to create this file first.

2. Specify your application ID in the app_id resource.

3. Specify each achievement ID that you created earlier in the corresponding achievement_* resource.

4. Specify each leaderboard ID that you created earlier in the corresponding leaderboard_* resource.

5. Open AndroidManifest.xml and enter your package name in the package attribute of the <manifest> element. If you are creating an Android game from scratch, make sure that you also add the following code inside the <application> element:

The only way to fix this is by deleting the **Application\Build folder and **Application\Intermediate folders

I also want to thank KRushin for providing me with some useful feedback on these subjects.

**EDIT: **made a bug report here ​https://answers.unrealengine.com/questions/68843/engine-updates-dont-update-the-xml-files.html

[KRushin]

@KillerSneak;94936

The only way to fix this is by deleting the **Application\Build folder and **Application\Intermediate folders

I also want to thank KRushin for providing me with some useful feedback on these subjects.

**EDIT: **made a bug report here ​[/SIZE]Engine updates don't update the XML files - UE4 AnswerHub

Glad I can help. Later this week (as 4.3 gets closer to a “final” version, and last few android bugs [for 4.3] gets fixed) I’m going to make a few videos on working with UE4. Basically showing the workflow of publishing,and getting non-gameplay things working [admob/achievements] and all that working, including if your are upgrading from 4.2/4.1 and some problems that can occur (assuming they are not fixed).

Edit: The manual edits are not required (step 1 & 2) , as the engine at compile/packaging time will insert them (assuming you configured your project settings/android settings). But this would be a manual way of doing it (especially if you haven’t done the last thing that killer sneak noted (deleting old/outdated Build/intermediate directories from previous versions of the engine). Therefore, If you are running NEW projects created in 4.3 you don’t have to do any of these steps.