• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Encountered a strange problem once again

Messages
66
Country
china
Following the MicrosoftESP_Drawing_Panel_Gauges_with_GDI+_MSDN, I code a GDI+ gauge dll.
On one of the computer P3D run well and I can see the GDIPlus_Gauge!TransparentGauge, but the dll can not be loaded on another computer.

I am surprised that in the same way why one computer can run p3d well ?
But the other computer do not to load the dll, not even the [void FSAPI module_init(void)] is being called, not even the dll load is failed, like this dll does not exist.

The panel.cfg is the same, all the simobjects datas are the same.

Only p3d.cfg dll.xml exe.xml is different, is that a great influence?

How to set p3d to load a gauge dll?

My way: copy the GDIPlus_Gauge.dll and the following image resources to the local P3D\Gauges directory.
 
Change your solution configuration from Debug to Release. Also make sure that the libraries for the Visual Studio version you are using are installed on that other computer.
 
I got it.
Microsoft says that:GDI objects are not displayed correctly on multiple monitors in Windows 7 or in Windows Server 2008 R2.
 
Change your solution configuration from Debug to Release. Also make sure that the libraries for the Visual Studio version you are using are installed on that other computer.
Hello,kun, I am ready to use directx to make gauges, but curDevice = (IDirect3DDevice9*)(((DXGAUGEHDR*)(gauge))->getDevice()); the curDevice is NULL,have you encountered this problem yet?
 
If you are using P3D v2 or greater, D3D9 is no longer in use. Check out the Texture and Effect Render Plugin sample in the PDK documentation.
 
If you are using P3D v2 or greater, D3D9 is no longer in use. Check out the Texture and Effect Render Plugin sample in the PDK documentation.
Yes, My P3D is V2.4,Texture and Effect Render Plugin sample can be used normally.
But, I want render some texture like UI with D3D(have alpha), only Texture and Effect Render Plugin can be uesd?
 
Yes. Note the Effect Render plugin part of Texture and Effect Render sample. It renders directly on screen, rather than cockpit view. Or you can add a Texture object to an XML gauge which the texture rendering system can draw to, and then put that XML gauge in a 2D panel window.
 
Yes. Note the Effect Render plugin part of Texture and Effect Render sample. It renders directly on screen, rather than cockpit view. Or you can add a Texture object to an XML gauge which the texture rendering system can draw to, and then put that XML gauge in a 2D panel window.
My gauges is dynamic, so XML gauge is not applicable. And I think Effect Render plugin that render transparent(alpha) effect to it would be difficult.
For now, GDI+ is a good choice.
 
I don't quite see how it is difficult. The very sample given in the PDK documentation is transparent.
 
Back
Top