Command Line Android Build - Graphics Issues

Archived Forums Questions & Answers
1

Hi all,

I’m encountering a strange issue with our command-line driven automated android builds. Suddenly, I’m seeing strange graphics issues with command line authored builds that don’t appear in builds produced via the Editor.

The code to produce the command line builds is straightforward, and worked flawlessly until very recently. I use the following call:

BuildPipeline.BuildPlayer(scenes, path, BuildTarget.Android, BuildOptions.none);

The sudden divergence between automated builds, and manual builds is puzzling. The glitches seem to involve certain textures containing alpha. I’m not sure what BuildOptions I should specify to produce a build to the same specification as the editor - I assumed (and this seemed valid up until recently) that the project’s build settings would be picked up.

Does anyone have any idea as to what the issue might be?

That's a good question and one whose answer I'd be interested in, too. I have similar problems, where some objects which are there in manual builds disappear in the automated builds. To begin with, I thought it was because the automated build took place on a virtual server without a real graphics card, and it was failing for some reason because of that. But your post seems to indicate this is not the case.

 –

No, the settings from a BuildPlayer call do not read project settings, they overwrite them. What kind of artifacts are you seeing?

 –

CHPedersen there is a command line argument for disabling the need for a graphics card. The command is -nographics and it must also use -batchmode. We had the same problem where are servers couldn't build originally because they had no graphics device.

 –

One example - we have a texture for a semi-transparent light halo around a lamp. On a manual build it looks fine. On the automatically produced build, however, it looks glitchy. There is still transparency, but the texture does not look right at all.

 –

Hmm. And the same machine is building AND running both builds? We once had an issue where a particular shader worked fine on my development station but did not function at all in the target hardware. Just trying to eliminate the possibilities here.

 –

2 Answers

2
2

This issue disappeared when we upgraded Unity to 4.3.3.

3

Running OSX 10.12.6
Android SDK 25 (7.1.1)

I’m having a similar issue with the latest 5.x and 2017.x versions. I’m able to build the project from Unity, and run the following build script from the IDE with no issue. However, if I run the build script from the CLI, a different sized APK is produced and there are serious graphic issues

CLI Command:

Unity -nographics -batchmode -projectPath ~/myProject -executeMethod BatchBuild.AndroidBuild -quit -logFile /dev/stdout

Build Script:

public class BatchBuild : MonoBehaviour {
	static string[] scenes = EditorBuildSettings.scenes.Where(s => s.enabled).Select(s => s.path).ToArray();

	[MenuItem("Build/Android")]
	static void AndroidBuild() {
		var outputFile = Path.GetFullPath(Path.Combine(Application.dataPath, @"../output/androidBuild.apk"));

		if(File.Exists(outputFile)){
			File.Delete(outputFile);
		}

		var options = BuildOptions.Development;

		BuildPipeline.BuildPlayer(
			scenes,
			outputFile,
			BuildTarget.Android,
			options
		);
	}
}