Go Back   Orbiter-Forum > Projects > ORBITER: 2010-P1 and newer > Feedback
Register Blogs Orbinauts List Social Groups FAQ Projects Mark Forums Read

Orbiter_ng should have "-s" command line parameter, too Issue Tools
issueid=909 01-25-2012 10:18 PM
Orbiter_ng should have "-s" command line parameter, too
The (handy) -s option should be recognized by the orbiter_ng.exe as well

This parameter is very handy when debugging, so one has not to
click through the launch-pad every time when running "debug" from Visual Studio e.g.

orbiter.exe -s "(Current state)" works
orbiter_ng.exe -s "(Current state)" doesn't

There was also a difference between "c" (lower case) and "C" (upper case) but I can't remember their difference anymore

Issue Details
Issue Type Feedback
Project ORBITER: 2010-P1 and newer
Status Open
Priority 10 - Lowest
Regarding Version 111105
Regarding Version (none)
Users who agree 1
Users who disagree 0
Assigned Users (none)
Tags (none)

01-26-2012 09:05 AM
orb orb is offline
O-F Administrator
Are you executing Orbiter_ng.exe from Visual Studio for debugging? That's not good solution to debug code being run from Orbiter.

"Orbiter_ng.exe" is just a wrapper that executes "Modules/Server/orbiter.exe" with working path set to Orbiter's root directory. When you debug "Orbiter_ng" no breakpoint set in your code will get hit, because different process is loading your modules and doing all the stuff, which is actually "Modules/Server/orbiter.exe".

You can run non-graphics Orbiter the same way as standard Orbiter, by putting command to run "$(OrbiterDir)\Modules\Server\orbiter.exe" and setting working directory to "$(OrbiterDir)".

I can't check it right now but this way you will most likely be able to use the "-s" parameter as well (or is it "-c").
01-26-2012 12:57 PM
Thanks for the hints orb!

I'm currently not at my 'Obiter machine' so I can't check whether the debugger really doesn't work with the 'redirector executable'.
I might confuse the behaviour with the last project I did - I think I only debugged with the 'regular' orbiter.exe ...

But -yeah- the starting of the executable from the "Modules\Server" path should do the trick! I'll check that when I'm back home.

Regardless of the debugging options, the 'redirector executable' should pass all arguments anyway. But that is much less important, when your setup works

As said, as soon I'll get a grip on my 'Orbiter machine' I'll check and give a feedback.

01-26-2012 03:33 PM
Addon Developer
That's how I've set things up for D3D11Client development. "Start debugging" start Moduels\Server\orbiter.exe with working directory set to orbiter's root.
01-26-2012 07:00 PM
O.K. orbs procedure works perfect!
Therfore I've reduced the priority to 'lowest' because there's a solid work-around.
This issue can be closed or kept open as a reminder for the 'redirector executable'.

To sum up the solution:

.\orbiter.exe -s "(Current state)" runs the inline-client
.\Modules\Server\orbiter.exe -s "(Current state)" runs the external graphics client

01-27-2012 02:45 PM
Orbiter Founder
It shouldn't be a problem to modify the orbiter_ng.exe wrapper so that it passes command line arguments on to modules\server\orbiter.exe, so I'll try to fix that.

I was never very keen on the wrapper solution - it would be a lot nicer to have the full server application directly in orbiter's root directory as orbiter_ng.exe. But I haven't found a way to make dll's compiled for orbiter.exe work correctly with an executable with a different name. The entry points in the dlls that link back to the main application seem to be hardwired to orbiter.exe.

Anyway, the current solution seems to work, so not much point in changing it.

Issue Tools
Subscribe to this issue

All times are GMT. The time now is 12:24 PM.

Quick Links Need Help?

About Us | Rules & Guidelines | TOS Policy | Privacy Policy

Orbiter-Forum is hosted at Orbithangar.com
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.
Copyright 2007 - 2017, Orbiter-Forum.com. All rights reserved.