The RequestCloudState SimConnect function was never implemented by Microsoft so it has never returned the correct cloud state data from inside the sim. Hence the need to 'reverse engineer' a solution, and access the data from the sims memory map. This is the reason why using such a method is very invasive and fraught with problems, for example it never works after FSX-SE or P3D post a new compiled update, something SE does very frequently.

 

The SimConnect link could be fine, just the response in the sim code at the other end. That needs to be corrected or linked to the SimConnect request event correctly. Whatever, it should be a straight forward fix for both LM and DG. Most likely no need for a new SimConnect version, just a fix in the sim code.

 

Stephen :-)

Rob I'm afraid I'm going to be a bit selfish since I don't use SE. Time for LM to lead the way again I think K

Always nice to have options.

 

Stephen :-))

 

 

The RequestCloudState SimConnect function was never implemented by Microsoft so it has never returned the correct cloud state data from inside the sim.

 

Yes, but that's also why I suspect it maybe a 2 sided change and perhaps more significant than initial estimations ... unless they can keep the parameters intact and DWORD for dwFlags is enough to cover any other requirements that might result.  Also, I would imagine there needs to be some solution to this statement in SDK:

 

 

 

The defined area can cross the Equator or the Greenwich Meridian, but it cannot cross the Poles or the International Date Line.

 

Otherwise the Radar (resulting data structure - SIMCONNECT_RECV_CLOUD_STATE) will just not work until the aircraft (i.e. requester) is not polling those coordinates.  Is this perhaps why it wasn't implemented?

 

But now you got me thinking, need to get some archived nasty ASN weather over the poles and see what happens.

 

Cheers, Rob.

No problem with poles or dateline. You simply patch many requests together which is what you need to do anyway as the cloud state data is limited in size for each request.

 

I think the request is ok. It's just the returned data was never completed and some meaningless cloud type data is returned. It's as though the sim code was never completed and some test or dummy data was returned.

 

Stephen :-)

Stephen, I'm not a lover of hacks or paying full whack for a product I am unlikely to use fully or very often (ASN for me would be wxr in NGX only), so I would vote for opus producing a dll of your own to enable wxr capabilitles please.

 

Happy to pay a bit extra for that (yes even to hifi if they sold wxr dll separately, but we know thars not going to happen!)

 

Cheers K

 

Agreed! Otherwise we might never get a solution. After all, it's been many months and no proposals made whatsoever, be it the internal code function, REX own .DLL, etc.