Question Missing module statement in Orbiter.log

[Blake]

I've noticed my addon module does not have a module load statement in the Orbiter.log file. For example, the addon vessels in a scenario appear:



...

000000.000: Finished initialising world
000000.000: Module DeltaGlider.dll ....... [Build 160828, API 160828]
000000.000: Module LuaInline.dll ......... [Build 160828, API 160828]
000000.000: Module ShuttleA.dll .......... [Build 160828, API 160828]
000000.000: Finished initialising status
...


I've scoured the docs to see if there is something I must add, but I'm finding nothing. Everything appears to work fine, so I'm a bit confused why these lines would be missing.


What am I missing?


Orbiter 2016, Inline client.

 

[GLS]

If you "addon module" is a vessel, and it is declared correctly in the scenario, then it should show up there. If it is a MFD or a plugin, then it must first be activated in the Modules tab on the Launchpad.

 

[Blake]

It's a vessel, here is a typical section from a scenario:

SR-01:SR71r
  STATUS Landed Earth
  POS -80.6825940 28.5969240
  HEADING 330.01
  ALT 1.807
  AROT 67.454 33.964 10.328
  RCSMODE 0
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000
  NAVFREQ 94 524
  APU 0
  AUTOPILOT 0 0 0 0 0 0
  AVIONICS 1 90 0 1 0
  CARGOBAY 0 0 0.000000
  CANOPY 0 0 0.000000
  FUELCELL 0
  HYDROGEN 1.0000 0
  GEAR 1 1.000000
  OXYGEN 1.0 0
  POWER 1 1 0
  PROPULSION 0 0 1072693248 0 0
  AIRBRAKE 0
  LIGHTS 0 0 0 0
  CLOCK 153 0 0
  SHUTTERS 0
  HOVER 0 0.000
  RETRO 0 0.000
END

Everything loads and runs fine. There are no errors in the log file, or even when running in the debugger.

Its not a big deal, except it seems to indicate something is not loading someplace. But I cannot figure out what.

 

[GLS]

Do you have the InitModule function?

 

[Blake]

Do you have the InitModule function?

Thanks, I have not needed that yet so I have not implemented it. However that did get me looking more closely at the MODULE rather than VESSEL. Missing InitModule is not the issue, where #define ORBITER_MODULE is located is the issue.



Some time ago I moved OrbiterAPI.h and OrbiterSDK.h into the StdAfx.h file. This greatly improves build times, but I did not move the #define ORBITER_MODULE into that file. I put it in there before the Orbiter .h files and now my module shows up in the Orbiter.log.


Apparently the VESSEL can still be created and used even if the MODULE its located in is not recognized as such by Orbiter.


Thanks for the help.