SA-WXR installed and running but how do you...

Gents,

I used to run the SAWXR on the same pc as the Magenta CDU but it slowed the entire CDU down to a crawl, I now migrated it to the PC running Magenta CPT ND, but i cant get it to work, guess it cant find the Net Dir.. this is my old cfg file any hints?


Alternate Window Name = BFMSCDU
TitleBar visible = 1
Focus Change Event = 1
Bitmap Export Directory = C:\games\CDU\NetDir
Disable Output when in Bitmap Export Mode = 1
Get PM Range = 1
Simulate current PM WX Mode = 1
Set PM Update Rate = 7
Autostart = 1

And talking about the ND's lately i am seeing lots of stuttering and loss of FPS on the ND's when Fixes and or Terrain are active, this did not happen before.

Peter

Hello Peter. Is this dirctory Bitmap Export Directory = C:\games\CDU\NetDir on the machine that SA_WXR is running on now? I don't think it is but that path points to a local directory on that machine. Go into one of your PM programs and get the netdirectory from that. This should get it up and running.

Hi Rob,

you are correct, the cfg file i enclosed was the old one, and SA WXR used to be on that machine which also has the CDU and the netdirectory..

Now im trying to run it form the pc that runs the ND's..

I don't think it works that way, the instructions say not to do that...

As a follow-up to my earlier message about slow updates in the ND when pressing buttons assigned to tilt down and tilt up I've discovered that when a button is pressed the value in the SA-WXR display is changed virtually immediately.

The problem appears to be getting that info to the ND. If Florian was more responsive I'd post the question on his forum but as things stand there appears to be more chance of a response from Elvis!! :cry:

Cheers,

Quote:

---

Originally Posted by Ray Proudfoot

The problem seems to be sending data to SA-WXR from a button on the FS machine via WideFS / the network, for it to process that data and to send the relevant info back via the same path to FS.

---

Hi Ray and others. I don't think the problem is to send data to sa_wxr from fsuipc. Because on my setup (sa_wxr on cdu pc) I have cdu window on top of sa_wxr and when I minimize the cdu so that I can see sa_wxr screen there's an immediate respons to the buttons I'm pressing while the info on the ND is lagging a couple of seconds.

Quote:

---

Originally Posted by sas550

Hi Ray and others. I don't think the problem is to send data to sa_wxr from fsuipc. Because on my setup (sa_wxr on cdu pc) I have cdu window on top of sa_wxr and when I minimize the cdu so that I can see sa_wxr screen there's an immediate respons to the buttons I'm pressing while the info on the ND is lagging a couple of seconds.

---

Hi Anders,

Looks like you just missed my latest message. I agree with your findings. :D

So how do we fix it? :sad:

Sadly both software developer involved seems to have more important things to do. :(

So the issue seems to be in the "hooks" that are in place to connect the network data flow between the two separate programs. Both programs work in stand alone mode. This interface gets the data from one program to the other and vice versa. Sounds like, as I mentioned above, there is a "handshaking" issue between the two and the data gets "held" for a long time.

SO... the real question is WHO developed these hooks? The folks from PM.... or the SA_WXR developer? That would be ther person who needs to fix the code.

best,

..................john

Has anyone tried playing with the PM update setting in the SA_WXR software? Maybe this will help?