Can't read AI Traffic Identity Strings in FSX

[Paul Henty]

Hi Pete,

I've been trying to use the FSUIPC facilities for 'Reading full AI Traffic identity strings' at 0xD000. This is for FSX, using FSUIPC version 4.520.

I can't get this to work. I keep getting back 48 zeros.

I'm think I'm doing everything right as described in the documentation, although I note it says this is untested in FSX and requires feedback. Maybe this isn't working?

Here is the log of an attempt in case I'm doing something daft:

********* FSUIPC4, Version 4.520 by Pete Dowson *********
User Name="Paul Henty"
User Addr="paul.henty@"
FSUIPC4 Key is provided
WideFS7 Key is provided
[Continuation log requested by user]
Running inside FSX (using SimConnect Acc/SP2 Oct07)
Module base=61000000
Wind smoothing fix is fully installed
   536828 System time = 23:24:25, Simulator time = 17:27:56 (16:27Z)
   536828 LogOptions changed, now 00000000 0000000D
   546891 WRITE0  D004,   4 bytes: 01 00 00 00                                      ....
   546891  READ0  D008,   4 bytes: E9 FB E9 01                                      ....
   546891 WRITE0  D00C,   4 bytes: 0E FE FF FF                                      ....
   546891 WRITE0  D000,   4 bytes: 10 10 00 00                                      ....
   546891  READ0  D008,   4 bytes: D6 D9 EA 01                                      ....
   546891  READ0  D010,  48 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   546891                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   546891                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   702781 Sim stopped: average frame rate for last 166 secs = 18.4 fps
   708969 LogOptions changed, now 00000000 00000001

Also, I had to generate this log by running my app on the FS computer. I usually develop on a different machine via WideClient, but the log wouldn't record any IPC reads I made via WideClient. It did log the IPC writes OK though. I'm using WideClient.exe version 6.7.8.0.

Thanks for your help,

Paul

[Pete Dowson]

I've been trying to use the FSUIPC facilities for 'Reading full AI Traffic identity strings' at 0xD000. This is for FSX, using FSUIPC version 4.520.

I can't get this to work. I keep getting back 48 zeros.

You are right! It doesn't work in FSUIPC4. I think you must be the first person who's tried it.

I used this Lua plug-in:

ipc.writeUD(0xD004, 1)
timestamp = ipc.readUD(0xD008)
ipc.writeUD(0xD00C, ipcPARAM)
ipc.writeUD(0xD000, 0)
while 1 do
  timestamp2 = ipc.readUD(0xD008)
  if timestamp2 ~= timestamp then
     tailnum = ipc.readSTR(0xD010, 48)
     ipc.display("Tailnum for " .. ipcPARAM .. " = " .. tailnum)
     ipc.exit()
  end
  ipc.sleep(10)
end

and simply assigned a KeyPress to it with the parameter (passed to Lua as ipcPARAM) giving the AI ID (the -ve of the Reference shown in TrafficLook).

The above Lua program works fine in FSUIPC3 but not in FSUIPC4. I shall get onto this tomorrow - it is getting too late to investigate this tonight!

Thanks. I'll get back to you.

Also, I had to generate this log by running my app on the FS computer. I usually develop on a different machine via WideClient, but the log wouldn't record any IPC reads I made via WideClient. It did log the IPC writes OK though. I'm using WideClient.exe version 6.7.8.0.

Reads by WideServer don't get passed to FSUIPC, they don't really act in the same way. when a client first reads something, WideServer gets it directly from the FSUIPC offset store, and adds it to a chain of offsets that particular client wants. Then, any time the value changes, an update is automatically sent to the client. The client application is actually reading direct from a local copy of an updated offset store. Because of this, there's always an enforced delay in responding to the first request for any offset, but thereafter it is instantaneous, being from local memory.

Obviously Writes can't be treated in that way, so they get logged in FSUIPC. WideClient offset operations can be logged by the logging options in WideClient.

Regards

Pete

[Pete Dowson]

I'll get back to you.

Okay. It was a silly typo, easily fixed. Should have been tested years ago -- thanks for reporting it!

Please download interim version 4.522 soon. The link will be provided in the Updates and Goodies Announcement above as soon as I've uploaded the build.

Regards

Pete

[Paul Henty]

Please download interim version 4.522 soon.

Thanks Pete - it's all working now.

WideClient offset operations can be logged by the logging options in WideClient.

Ah, WideClient has logging too. I'd better go read the docs. :oops:

Regards,

Paul