• 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.

P3D v4 Gauge size

C

Capn_Geoff

Messages
76
I have a tactical display gauge - kind of like a round radar display. Works fine in 32 bit FSX. In P3Dv4, though, when I get the pgauge->size.x and pgauge->size.y the y is correct but the x is *always* 0. If I deliberately set it to, say the same as y all the calculations that use it work fine, but when I get back to the callback, during the next iteration x is set back to zero. If I resize the gauge (ie make it a window in P3D and resize it) the y changes correctly but the x stays stubbornly at zero. Anyone seen this behavior? I have a couple of gauges that rely on the size variables being set properly... Any help?
 
You made sure to use the v4 Gauges.h? You can't use the same Gauges.h that FSX/older versions used because a number of members in the gauge header struct are now 64bit not 32bit.
 
Thank you so much! Yes, indeed I was using the old header. What a pain to change all the callbacks - like over 70 of them - but it makes sense to have them be pointers rather than an integer - although in C one could easily get away with it. Radar display gauge is working as it used to. Woo Hoo!
 
Easy way to do things so you don't have to keep changing:

Code: 
#ifdef _M_X64
#include "lx64\\Gauges.h"
#define PUSERDATA UINT_PTR
#else
#include "lx86\\Gauges.h"
#define PUSERDATA UINT32
#endif

Then you only have to replace the type of the 3rd parameter of your gauge callbacks (and any userdata pointer casts) with the PUSERDATA type and then changing target platform will automatically compile the desired type.
 
You must log in or register to reply here.
Back
Top