AJMurray

HI all, I'm having an issue with weather in FSX, specifically when using the Project Magenta instructor station. The general idea is that my application synchronises the weather across any given number of clients from the server. This works fine on its own, the weather stays in sync nicely. The problem arises when the user attempts to set the weather using the PM Instructor station in parallel with my application, it crashes FSX. I originally thought the problem may have been the ulSignature variable was denying PM access and that was somehow causing FSX to crash, but I've since gone to using a zero value for the signature to leave access rights for PM and the same crash happens. All other PM functions seem to work fine without issue. The process I'm following is: Create a NewWeather structure, populate ulSignature field with zero, populate chICAO field with 'GLOB'. Write the NewWeather structure to 0xCC00, call process. Read the NewWeather structure from 0xCC00, call process. NewWeather nw; nw.ulSignature = 0; nw.chICAO = "GLOB"; if(!FSUIPC_Write(0xCC00, 1024, &nw, &dwFSUIPCResult) || !FSUIPC_Process(&dwFSUIPCResult)) { printf("Modifying weather structure failed!\n"); } if(!FSUIPC_Read(0xCC00, 1024, &nw, &dwFSUIPCResult) || !FSUIPC_Process(&dwFSUIPCResult)) { printf("Reading weather structure failed!\n"); } Has anyone had this issue before? Can anyone see anything obvious that might be causing PM to bunk out FSX? Is it possible that PM is seeing the GLOB variable and freaking out?

Ah I see now, NWI seems like the way to go. I've educated myself. A few questions about the process... 1. When setting the weather dynamics to zero, the readme mentions that I should write 0 first, then the command. As I understand it the whole structure has to be written at once, so does this mean I should set the uDynamics variable in the structure, write it, then set the uCommand variable, write it again, then do a process call? 2. Should I write the NW_CLEAR command every time I set the weather, or only once at application startup? Is this the same for NW_EXACT? 3. When reading out a weather structure, it mentions writing the chICAO and uSignature variables before reading, should these be written to the write area at 0xC800 or to the read area at 0xCC00? Thanks for your help on this one, unfortunately I'm not onsite at the simulator to be able to write this stuff on the fly so I'm trying to nail everything down before I head out there!

Hello all, I'm currently trying to sync FSX weather between a master PC and a client IG and am having a few issues with things not working. It's seemingly simple and I'm sure I'm just missing some FSX settings or a step or two in the process. Anyway what I'm doing: - Reading the METAR string out of the master by reading 2048 bytes from 0xB800 - Changing the ICAO (in this case YMML) to GLOB inside the string so as to make the settings global (have also tried leaving the ICAO intact) - Sending the string over the network the the client and writing the 2048 bytes to 0xB000 After this, a loading screen appears on the client, seemingly loading new weather settings, but after loading the weather remains the same. I've also tried reading 1024 bytes from 0xC400 and writing them to 0xC800 with the same result. And also setting the string using SimConnect, again same result. Is there possibly a setting in FSX that could be overriding my weather sets? It mentions in the FSUIPC documentation that there's a facility provided to force FSX into global-only weather, but doesn't explain much more. Does anyone have any ideas?