aleos

Thank you for your answer, Pete. I consider using simconnect in the further development of a weather control.

Hello, Pete. I've tested those issues with FSX and P3D 2.4 with FSUIPC 4.937 installed on both. Is this a new bug in P3D's SimConnect? Have you checked the actual SimConnect METAR strings which are being sent to SimConnect, because all the NWI does is make FSUIPC build those strings. I'm pretty certain it's always been okay with FSX and SP2/Acceleration versions of SimConnect. It looks like FSUIPC generate incorrect metar string for wind layers. I can set 3 layers of winds by setting metar: GLOB 151552Z 20000KT&D100NG 20202KT&A200NG 20404KT&A400NG CLR 15/05 Q1013And I get 3 layers of winds. As I think similar configuration set to NWI generates metar: szMETAR="GLOB 151041Z 20000KT&D100NG 20202KT&A200NG 20404KT&A200NG 0050&B0&D1 CLR 15/05&A24 Q1013 "And I get only first 2 layers. Count of layers is 2 because in NWI generated metar second and third layers have similar altitude. In FS2004, for which the NWI was devised, it was only possible to have one visibility layer. Trying to use more never worked. Therefore the original design was for one layer. The additions was done in such a way as to not break existing programs. And yes, the layers all count. I suspect the Global weather facility in SimConnect only allows one layer still. The global setting is really only used as the initial default for weather stations not yet set up. Thank you for your explanation about the visibility structures. But I have found strange addition in visibility blocks in metar string. When visibility layers count 0, NWI however adds one thin layer: 0050&B0&D1When visibility layers count is greater than 0, it also adds one thin extra layer. Check the METAR string being sent. It sounds like some odd changes in the SimConnect weather interface have been introduced. Please just double-check using the string versions -- you can get those by FSUIPC's logging or SimConnect logging. If P3D have changed these things I suggest you might want to look at sending the METAR strings yourself rather than use the NWI. I'd hoped folks would have moved on by now from that system devised in 2003 to match the binary hacked interface into FS2004. You can send the strings via FSUIPC if you'd prefer not to use SimConnect directly. a ) It is really a P3D bug. Even when I set cloud turbulence by metar string, Light turbulence replaces None. On FSX such a setting works properly. b ) Both FSX and P3D sets precipitation base altitude in 10 times less. I set to NWI 1000 feet (converted to meters of course) and get metar: szMETAR="GLOB 151055Z 20000KT&D100NG 20202KT&A200NG 20404KT&A200NG 1609&B1&D1499 0050&B1500&D1 5ST020&ST010FNVN010N 15/05&A24 Q1013 "It sets 100 meters not 1000 in both FSX and P3D. So precipitation base altitude in metar is tens of meters, not a hundreds. As a result, difference between altitude in NWI and real setting. Hmm. Sounds like quite a few of the bugs in FSX's weather facilities have been carried over into P3D and maybe even made worse. Of course FSUIPC has no control over "artefacts" I'm afraid. Not tested more. If I understand correctly, you recommend to use METAR for setting weather in FSX and P3D. I don't want to use simconnect directly for saving simplicity in the my application. So, should I use offset 0xB000 for setting metar? Does it matter what a day and time to set in metar after icao code? What a correct sequence for setting the metar for: 1) an arbitrary weather station 2) global (and replace weather on all stations) 3) all station was not set? And how to get a global and station weather?

I have several issues with setting weather via NWI. I use FSUIPC 4.937 and Prepar3d 2.4. Wind layers. All is good when count of layers <= 2. If count of layers is greater than 2, it applies incorrectly. Seems like data (except UpperAlt) in all layers, except for the first two, are shifted by 1. I wrote a workaround for layers with indexes greater 2. I can describe my solution if it neccessary. Visibility. a ) Why visibility is broken into two parts: a field Vis and an array UpperVis? Is this correct to count Vis as a first layer and layers from an array as a consequent layers? b ) When I write visibility layers to global section of the NWI, only layer from Vis is applying. When I read visibility layers from the NWI global section, I also get only first layer in Vis. Clouds. a ) When I write cloud turbulence 0, it apply as 1 in P3D. So I can't set no cloud turbulence. All other values works well. b ) Precipitation base altitude apply to P3D weather 10 times less. So I should to multiply this altitude by 10 before set it. It is not bad solution, but it reduces this altitude's available range to write. When I set up a lot of layers of clouds, winds and temperatures, a graphical artefacts are appear in the sim. In some cases weather in the sim simply disappear and weather set to clear (visually).

Thank you very much. This is a great solution.

Thanks for your answer, Pete. I will look for other ways to.

Hello, Pete. I am developing an application to manage the simulator (Prepar3d, FSX). I need to know when the Sim load saves or change aircraft model in order to update displayed information in my application. I have found, that I can use offsets: 0x3F02 for load detection and 0x32FC for change aircraft model detection. My problem is that those offsets' values don't increment if selected load name or aircraft model the same as before. Aircraft model change detection in case of same model is not so much need. But load detection with the same load file is required, because in this case can change weather, position and many other parameters and its need to be refreshed. Is there a solution for such tasks?