General Question How do I turn this off? (image included)

[Victor_D]

I know it is probably a very stupid question, but I don't know where else to ask. I need to get rid of that white line with some sort of info that's displayed in the bottom left corner:

I don't know if or how I turned it on, but it has been driving me crazy.

 

[Woo482]

It looks like an addon using a debug string to me, have you tried disabling all modules and just running a scenario without any addon vessles? that should get rid of it

 

[Victor_D]

Thank you so much. It seems it was the LolaMFD module that's been doing it.

(I wasn't sure when it first appeared, so it had never occurred to me that a MFD addon could do this.)

 

[Izack]

(I wasn't sure when it first appeared, so it had never occurred to me that a MFD addon could do this.)

AFAIK any module (vessel, MFD, plugin) can make a debug string.

 

[Lucy]

Any addon written in C++ or Lua can print that string (In C++ you print to it with printf or sprintf or some other variant on that theme), it's in the SDK docs as oapiDebugString() - printing data to that location spits it to screen as you've seen. Strictly speaking, final-version addons should not include those calls, as it's a debug tool and not a means of providing user information (better to draw on the HUD, MFD or panel instruments instead, those are established areas to print details to), but I know for instance AMSO makes use of this message space for printing mission details, as does UCGO and a few others.

There's no way to "turn it off", as it's an implicit part of the module, so the only way to stop it is to disable the module, like Woo482 said, or if it's your module, comment the call out in your source and recompile it.

 

[RisingFury]

DebugString in a released addon... how unprofessional...

 

[garyw]

DebugString in a released addon... how unprofessional...

Released but never finished. There are quite a few addons that make use of the Debug string for quick n dirty info displays.

 

[Wishbone]

AMSO uses them for menus. Which is a good thing, compared to the horror of thinking and typing in octal numbers...

 

[Izack]

AMSO uses them for menus. Which is a good thing, compared to the horror of thinking and typing in octal numbers...

I wish more authors would use pop-up dialog boxes for those functions, like Atlantis' RMS control and R13L panel.

 

[Lucy]

From the SDK documentation:

This function should only be used for debugging purposes. Do not use it in published modules!

From this I understand it doesn't matter what stage of development the addon is in, it should not be published with calls to oapiDebugString() active in it.

 

[orb]

There's no way to "turn it off", as it's an implicit part of the module, so the only way to stop it is to disable the module, like Woo482 said, or if it's your module, comment the call out in your source and recompile it.

There is a simple way to "turn it off" for all the debug strings displayed by any module in Orbiter - just use the plug-in module from attached in this post archive.

It replaces Orbiter's debug string character buffer address returned by oapiDebugString with a dummy one.

For anyone interested how it's done, the source code is included.

 

[Linguofreak]

From this I understand it doesn't matter what stage of development the addon is in, it should not be published with calls to oapiDebugString() active in it.

Didn't LOLA pretty much get released as-is after the author's sudden death, though? He may never have intended for oapiDebugString to be active in the released MFD.

 

[Mandella]

Didn't LOLA pretty much get released as-is after the author's sudden death, though? He may never have intended for oapiDebugString to be active in the released MFD.

Unless I am misremembering, Lazy D's final (although unfinished) release did not have this string, but it was left in by one of the good intentioned supporters as an aid to debugging. The version of Lola we are using now is still considered "beta," with an open invitation for any who can to complete and correct.

In fact, isn't the source code included in the most recent download? If someone who understood the code wished to make a quick correction to it to remove the debug string, I'm sure it would be appreciated by many.

 

[Izack]

In fact, isn't the source code included in the most recent download? If someone who understood the code wished to make a quick correction to it to remove the debug string, I'm sure it would be appreciated by many.

I'm pretty sure that could be accomplished with ctrl+f and a semicolon.

 

[Lucy]

I'm pretty sure that could be accomplished with ctrl+f and a semicolon.

And a //. >.>

 

[Izack]

And a //. >.>

Thus "pretty sure" I guess.
This is why my username isn't orange. :lol: