|
Hello, Using Unity 3.5.1 with the following command line options to create a build The build is created and the game can be run, but the screen remains black. Still the game responds to keyboard inputs (ESC for Application.Quit). When I ommit the -nographics option the build has the visuals. The documents don't indicate such a connection. As far as I understand it, we should be able to build on a headless Windows server. Btw. both results can be reproduced on a regular Windows 7 installation (no server). How can we use -batchmode -nographics to create a build on a Windows server without requiring us to install Direct3d etc.? Thanks for any hints! edit: Removed link to forum, apparently the post was removed.
(comments are locked)
|
|
Actually the documentation does tell it
The second sentance, about automated workflows. Automated workflows only work, when you have a windows in focus, otherwise you can't send simulated input commands (i.e. prerecorded user input). Thank you for the info! So I guess possible automated workflows with -nographics
I don't understand why the Unity Editor requires a graphics device to generate a Standalone Player that has visuals. New to UnityAnswers, will wait a bit for more feedback before approving your answer.
Apr 14 '12 at 06:26 PM
Helmut Duregger
Ok, seems to really be the case that this somehow refers to the Editor instance running and the Standalone Player generated. Will suggest to Unity that they make this clearer. Thank you for your answer!
Apr 16 '12 at 01:40 PM
Helmut Duregger
(comments are locked)
|
