Perhaps I’m missing something, but when I create a standalone Windows application is does not recognize any of the command line options listed here:
http://unity3d.com/support/documentation/Manual/Command%20Line%20Arguments.html#player
Of course, it might be difficult to tell with -force-opengl (which is what I care about), I did expect to see some difference with -batchmode.
What am I missing here?
[Yes, built with Pro]
When you start a normal game and just run it in batchmode it won’t do anything because it will freeze waiting for you using the gui or even just crash if you have enforced renderings.
You will have to write scripts that work independent of ongui and input.
My headless servers with unity have been running since somewhen last week without a problem.
Yes, I understand that the application should not do anything when I use the -batchmode command line. Yet, my application ignores this and continues to take user input.
The problem is that there is no user input.
The scripts must work on their own by either work automatically (update / fixedupdate) or by beeing setup to do something in Awake / start, unless they only react in response to an even (OnCollisionEnter etc)
OnGUI does not do anything on the headless client.
But I guess we talk about something else so just to reformulate what I originally intend to say: When you use batchmode, no graphics exist, as such any command line argument related to graphics that was used aside of batchmode on the call of the exe will be dropped