Can someone share their settings?

No matter what I do, simply opening WMR portal/Steam VR causes the GPU to run out of memory. My settings aren't that high (using only 5GB out of 11 when not in VR). Any suggestions?

You should have a DllStart or module_init function in your dll that the simulator calls on load. That's where you should do the panel pointer assignment.

Look up the C: var module example in the SDK for how to set up the import table.

Are you running a C++ gauge or a C++ module loaded via the dll.xml?

I don't use swf files. All my camera work has been in C++ PDK texture rendering displays.

There isn't a gauges.lib. You got something like this in your code somewhere? GAUGESIMPORT ImportTable = { { 0x0000000F, (PPANELS)NULL }, { 0x00000000, NULL } }; GAUGESLINKAGE Linkage = { 0x00000013, module_init, module_deinit, 0, 0, FS9LINK_VERSION, { &gaugehdr_ACM, &gaugehdr_Sys, 0 } };

This might help:

https://forums.vrsimulations.com/suppor ... ia_C.2B.2B

Setting the instrument sim vars has always been rather hit or miss with weird behaviour for me. I would recommend taking the raw velocity values and atmospheric parameters and calculating your own instrument indications using your own vars. I should point out that setting body velocity to true is no...

I have no problems integrating body velocity Z, but I work in a dll, not a exe. I set my SimConnect data request to return every sim frame (and the flag that sets it to return on change is not added), and I call my integration functions from that particular request case. That way it doesn't get call...

If the gauge is a dll then there is no way it would even be modifiable.

In your realism settings, is Display Indicated Airspeed selected or Display True Airspeed?

It actually is quite clean if you make a wrapper class for it and use enums and arrays for the string names and IDs and create some read and write functions.

You can use the IGaugeCCallback system.

Best description on how to use C: vars is found here:

https://forums.vrsimulations.com/support/index.php/TacPack_SDK#CVars_via_C.2B.2B

My examination of the IR shaders and P3D materials and material scripting SDK shows that they do simulate actual IR, but you will find it hard to get anything useful from the render target pixel data since the output is always normalized.