P3D v4 64-Bit DLL Guages

[SkippyBing]

I've been using the ESP example DL gauge for various projects up to P3D3 with no real problems, mainly so I can use SimConnect to tweak the engine handling, add external stores etc. Obviously with the move to 64-bit they need to be recompiled, however after setting the project to 64-bit and pointing towards the P3D4 inc and lib files I get the following error:

error C2440: 'initializing' : cannot convert from 'overloaded-function' to 'PGAUGE_CALLBACK'

along with that I get a second message:

IntelliSense: no instance of function template "GDIPlus_Gauge::Callback" matches the required type g:\Users\Bing\Dropbox\Gauges\GDI+Gauge\GaugeDeclarations.cpp 26 1 GDIPlus_Gauge

The associated block of code is:

GAUGE_HEADER_FS1000(
GAUGEHDR_VAR_NAME,
GAUGE_W,
transparent_gauge_name,
&gaugeTransparent_element_list,
gaugeTransparent_mouse_rect,
GDIPlus_Gauge::Callback<TransparentGauge>,
0L, 0L,
gauge_guid2,
0, 0, 0, 0, 0);

To eliminate anything I may have done I went back to the original example code which generated exactly the same problems. Has anyone got any ideas what might need updating to get the code to compile for 64-bit?

 

[JB3DG]

You have to use the v4's gauges.h. The 3rd parameter of the gauge callback is no longer a UINT32 but a UINT_PTR. The user_data member in your gauge header is also a UINT_PTR now instead of UINT32.

 

[SkippyBing]

Naruto, thanks for the pointers, I think I've solved that problem, I was using the v4 gauges.h but hadn't made the UNIT32 UINT_PTR.
But now I get the errors listed below, so I'm not sure if I've solved the initial problem or just made it worse!

 

[ronh]

What version of VS are you using I see 1900 and 1800 - 1900 VS2015, 1800 VS2013. You need VS2015. Or what is your platform set to?

It's very confusing.

https://en.wikipedia.org/wiki/Microsoft_Visual_C++

 

[SkippyBing]

Ahh I'm still on VS2013, I'll see if updating to 2015 fixes it.

 

[JB3DG]

Yes VS2015 is required for v4's SimConnect lib.

 

[SkippyBing]

Sweet thanks guys, that seems to be compiling happily now so any remaining problems are due to my poor use of the SimConnect API!!
Really appreciate it.

 

[spatialpro]

Looking good Phil! ;-)

 

[Novicok100]

Hi, everyone!

I am using D2DGauge example available on this forums.
It compiles and works successfully on FSX, as it makes sense for P3D x64 I have to recompile the library and use the newly provided SDK (Simconnect & Gauges.h).

GAUGE_HEADER_FS1000(
GAUGEHDR_VAR_NAME,
GAUGE_W,
opaque_gauge_name,
&gaugeOpaque_element_list,
gaugeOpaque_mouse_rect,
D2DGauge::Callback<OpaqueGauge>,
0,
0,
gauge_guid1,
0, 0, 0, 0, 0
);



And change one method definition to:
template <class T>
inline void FSAPI D2DGauge::Callback(GAUGEHDR* gau, int serviceId, UINT_PTR)
{
switch(serviceId)
{
}
}

But Prepar3D 4.2 keeps crashing if the library dll is placed into panels folder or if placed in addons folder the gauge doesn't work.

Do we need to make more changes when switching from fsx to p3d?

Has anyone experienced something similar?


Off-topic:

Spoiler: SSJ100 EFB

 

[Novicok100]

Ahh, I found the error by myself, so in gauges registration callback we have to use UINT_PTR instead of UINT32 ...


template <class T>
inline void FSAPI D2DGauge::Callback(GAUGEHDR* gau, int serviceId, UINT_PTR)
{
switch(serviceId)
{
case PANEL_SERVICE_CONNECT_TO_WINDOW:
assert(gau->user_data == 0);
gau->user_data = reinterpret_cast<UINT_PTR>(new T);
reinterpret_cast<T*>(gau->user_data)->mCanvas = reinterpret_cast<PELEMENT_STATIC_IMAGE>( gau->elements_list[0] );
break;
...
}
}