Restore "Ignore All Default Libraries" to default.
I did that, the .dll is still 3 kb (with VS 2008), instead of ~100 kb (as it should be) when I compile it with VS 2015.
Any reason you are using delay loading?
It's from the Payload Manager SDK doc.
3. Define the PayloadManager.dll as a delay loaded dll. If you are using MS Visual Studio open project properties and add to Linker/Input/Delay Loaded DLLs value PayloadManager.dll.
But I still get this warning...
Code:
1>LINK : warning LNK4199: /DELAYLOAD:PayloadManager.dll ignored; no imports found from PayloadManager.dll
...even if it is defined via a filepath.
Code:
1>LINK : warning LNK4199: /DELAYLOAD:C:\Users\user\Desktop\Orbiter\orbiter_m\Modules\PayloadManager.dll ignored; no imports found from C:\Users\user\Desktop\Orbiter\orbiter_m\Modules\PayloadManager.dll
Having nothing defined as a delay loaded .dll doesn't change the .dll being only 3 kb.
---------- Post added at 11:47 PM ---------- Previous post was at 06:03 PM ----------
It is basically compiling as if the property pages aren't even there.
---------- Post added 02-06-16 at 11:38 AM ---------- Previous post was 02-05-16 at 11:47 PM ----------
Okay, the real mistake I made was starting a new project in VS 2008 and selecting
"General -> Empty Project" instead of
"Win32 -> Win32 Console Application"
I was wondering why I required something called "stdafx.h" (sorry for not telling you about that)
:facepalm:
The .dll is now at a reasonable size, and everything works
except Payload Manager is still not showing up in the scenario editor. I even made sure to follow every direction in PayloadManager_SDK.pdf, such as adding this:
Code:
//Scenario Editor definations
DLLCLBK void secInit (HWND hEditor, OBJHANDLE hVessel){
/* Here you can define your own Scenario Editor vessel-specific pages .........
.........
.........
*/
// Define PayloadManager Scenario Editor interface PayloadManager::DefineScenarioEditorPage(hEditor, hVessel);
}
and adding this to my .cfg file.
Code:
EditorModule=[My_vessel_dll_name]
I even included the "Now it is necessary to tune Payload Manager for your ship" parameters from the PM_demonstrator code.
Also, certain words aren't showing up in blue. Does that have anything to do with the problem?
---------- Post added 02-07-16 at 11:32 AM ---------- Previous post was 02-06-16 at 11:38 AM ----------
Finally found the source of the problem: I didn't define the EditorModule in the .cfg file properly.
Code:
EditorModule=[My_vessel_dll_name]
(I had put EditorModule=[M-III] when I should have put EditorModule=M-III/M-III, as that was where I put my .dll: */Modules/M-III/M-III.dll)
---------- Post added at 02:00 PM ---------- Previous post was at 11:32 AM ----------
I compiled the same code with VS 2015. And it also works there.