As Kuddel wrote before, you need to be careful with your working directory. You invoked the call from the Scenarios directory, you should do it from the Orbiter root instead.
C:\Orbiter2016\Modules\Server\orbiter.exe -s "C:\Orbiter2016\Scenarios\$CH-5%.scn"
.C:\Orbiter2016
), it should start Orbiter as expected.cd C:\Orbiter2016
C:\Orbiter2016\Modules\Server\orbiter.exe -s "C:\Orbiter2016\Scenarios\$CH-5%.scn"
Thank you very much for your patience and guidance, I can already complete the scene simulation I want to carry out....and (sorry about not making that clear): the curly braces in the parameter must not be entered; they were just there to mark scenarioPath as being a variable.
So your command line would be:C:\Orbiter2016\Modules\Server\orbiter.exe -s "C:\Orbiter2016\Scenarios\$CH-5%.scn"
.
If this is executed in your working directory (C:\Orbiter2016
), it should start Orbiter as expected.
In "batch-file" style this would be:
Code:cd C:\Orbiter2016 C:\Orbiter2016\Modules\Server\orbiter.exe -s "C:\Orbiter2016\Scenarios\$CH-5%.scn"
Yes, I can complete related operations now, and now I am making a program for this function to wake up. Thank you very much for your patience and guidance.As Kuddel wrote before, you need to be careful with your working directory. You invoked the call from the Scenarios directory, you should do it from the Orbiter root instead.
...and (sorry about not making that clear): the curly braces in the parameter must not be entered; they were just there to mark scenarioPath as being a variable.
So your command line would be:C:\Orbiter2016\Modules\Server\orbiter.exe -s "C:\Orbiter2016\Scenarios\$CH-5%.scn"
.
If this is executed in your working directory (C:\Orbiter2016
), it should start Orbiter as expected.
In "batch-file" style this would be:
Code:cd C:\Orbiter2016 C:\Orbiter2016\Modules\Server\orbiter.exe -s "C:\Orbiter2016\Scenarios\$CH-5%.scn"
thanks for your adviceI would test it running in windowed mode instead of full-screen -- anytime Orbiter loses focus (e.g., via alt-TAB) when in full-screen mode, it breaks with the message shown above, in my experience, at least. But you can run Orbiter in windowed mode instead of full-screen, and then the focus loss is not an issue.