JB3DG

Active IPs in the military. Small correction to be pedantic: it's the T-45C. KLN-900.

seems this got lost in the noise. Avsim admins? Any ideas?

A few years ago there was an article on the Wright Brothers that went into detail on their journey to develop the first functional airplane. Where can I find it?

There's a reason I have enjoyed working for him for more than 11 years now 🙂

You aren't. Some of our projects have been lessons learned that we are in no hurry to repeat and we have always tried to do our best to get things to work for users.

Curious which aircraft these were? I know the Phantoms at least had more bugs but they represented a much earlier development style that we wanted to get out of and improve (it took me 4 years of work on them which it should have taken less than 4 months). Our T-38C on the other hand is vastly better and enjoys the favor of AETC's IPs and our upcoming training products are of the same quality.

Its not compatible with MSFS, except for the outer wrapper we use to retain some commonality within the limits provided by the MSFS low level graphics API which is already a repackaging of NanoVG. Our library is based on external low level custom shader based APIs. And MSFS doesn't give us access to that internal rendering pipeline, which is the whole point of my gripe, that we can do stuff in P3D gauge graphics wise that simply cannot be done, or cannot be done to the same performance level in MSFS.

I do have a gripe with the limitations we are getting with the display drawing as they won't provide us access to the internal D3D rendering pipeline like P3D does. I wrote the hardware accelerated 2D vector and raster graphics library in use internally at Milviz and it is leaps and bounds ahead of NanoVG both in performance and ease of use. On the one hand, knowing by experience how hard of a task it is to create a 2D graphics library from scratch I have some sympathy for those like NVG's creators who undertake the endeavor, but what I have seen both with NVG and Direct2D is API designers overcomplicating the task considerably and not taking advantage of hardware capabilities to the degree that they could. There are some displays, particularly on the newer Garmin, Proline, and Honeywell big screen displays that get far too complicated for GDI and NanoVG to handle without turning performance into a slideshow. Custom shaders and draw call batching become critical to simulating these massive and complex displays to the degree we would like to do.

Everyone on holiday at the moment.

Just managed to dodge getting twisters here in Chattanooga. It was strangely warm for December just before this line hit us.

Last I checked, the Milviz store has it now.

There are actually 5 levels available in the FSX metar format. Moot though as we are not using it. We have our own way of locating general area precipitation intensities and then controlling it to sync with cloud densities.

The Master caution reset is a small black button on the right console by the generator switches. Provided your fuel isn't too low it should go out. As for the INS targets, you made sure you are getting your hemispheres correct in the lat/lon inputs (ie N/S/E/W)? Also, the longer you let the align light blink (without letting the aircraft move) the more accurate your position will be. It does drift and requires position updates at times.

As the developer, I see no logical reason to prevent these gauges from working alongside the WXAdvantage. There may be some slight differences in the precipitation map on screen and the precipitation out the window depending on how the weather engine is controlling the precipitation, but the WXAdvantage should run just fine. Furthermore, I would appreciate those having such issues to report directly to us on the WXAdvantage support forum (http://www.realenvironmentxtreme.com/forums/index.php?/forum/179-milviz-rex-wx-advantage-radar/), and note if these gauges are involved. @rstough he could be missing any one of several libraries preventing the gauge from loading.