Jump to content
The simFlight Network Forums
Sign in to follow this  
FlyingBee

FSX not sending position to ADEX

Recommended Posts

Hi All,

 

I'm hoping I can get some help with getting FSX to send the a/c position to ADEX.  I've used both for many years, currently have ADE 1.6 Am a registered user of FSUIPC, latest version.

 

Usually (ie up till now) ADEX shows the a/c position on an airfield being edited. Now, despite being'connected', it shows the a/c at Lat, Long, Alt and Time all zeros. FSX works OK and shows (Shift-Z) the correct coordinates. In ADE I can 'move the a/c to cursor position', and it does so very briefly, then the a/c symbol disappears again and the coordinates remain at zeros.

 

ADE Environment Checker says the connection is active, but the FSUIPC section shown the coordinates at zeros despite being correctly connected. So the problem is, is this FSUIPC somehow not picking up on the coordinates, or is ADE simply not responding as it should. I've posted on their forum, but so far without response.

 

Would very much value some ideas  -  it's difficult to use ADEX effectively without using the a/c as a positioner.

Share this post


Link to post
Share on other sites

ADE Environment Checker says the connection is active, but the FSUIPC section shown the coordinates at zeros despite being correctly connected. So the problem is, is this FSUIPC somehow not picking up on the coordinates, or is ADE simply not responding as it should.

 

There's no way FSUIPC is "not picking up the coordinates". Please close FS down and show me the FSUIPC log file. Past its contents into a message here. You can enclose it using the <> button, above the edit area here.

 

Pete

Share this post


Link to post
Share on other sites

Pete,

 

The log file right now is 190Kb  -  do you actually want me to show the whole thing? Too big to attach, according to the instruction.

Share this post


Link to post
Share on other sites

As Pete says, the log is a text file, please just open it, select all, copy and paste into a message using the button with the <> symbol at the top of the reply box (under the smiley face).

 

Cheers,

 

Ian P.

Share this post


Link to post
Share on other sites

This sometimes happens to me. The solution is to slew the aircraft slightly in FSX and the correct position will be displayed in ADE.

 

George

Share this post


Link to post
Share on other sites

Pause is my usual problem - if I move the aircraft while the sim is paused, the position in ADE is not updated. Unpause briefly, ADE updates, then press pause again.

 

Ian P.

Share this post


Link to post
Share on other sites

Thanks for the comments and suggestions,folks.  I've tried the slew method  -  doesn't help.  I've tried unpausing  -  by cancelling the 'Pause on task' setting it doesn't pause anyway. Doesn't seem to make any difference.

 

I'll copy and paste the log file in its entirety  -  give me a few minutes!

Share this post


Link to post
Share on other sites

Pete,

 

As suggested, I've copied the entire file and tried pasting it into the <> code box. All that happens is that the entire window goes grey. Clearly can't cope with so much text. I'll try copying & pasting a smaller portion.

********* FSUIPC4, Version 4.929 by Pete Dowson *********
User Name="Brian King"
User Addr="brianrhking@compuserve.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
   242878 System time = 29/06/2014 17:29:24
[Continuation log requested by user]
Running inside FSX on Windows 7
Module base=62690000
   242878 LogOptions changed, now 00000000 00000019
   242894  READ0[5432]  6020,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   242894  READ0[5432]  6018,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   242894  READ0[5432]  6010,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   242894  READ0[5432]  0238,   3 bytes: 00 00 00                                         ...
   242956  READ0[5340]  0020,   4 bytes: 00 00 00 00                                      ....
   242956  READ0[5340]  0560,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   242956  READ0[5340]  0568,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   242956  READ0[5340]  0570,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   242956  READ0[5340]  0580,   4 bytes: 00 00 00 00                                      ....
   242956  READ0[5340]  3210,  224 bytes: BE 00 00 00 4F 00 00 00 4D 00 00 00 00 00 00 00  ....O...M.......
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   242956                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097  READ0[5340]  0020,   4 bytes: 00 00 00 00                                      ....
   243097  READ0[5340]  0560,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   243097  READ0[5340]  0568,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   243097  READ0[5340]  0570,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   243097  READ0[5340]  0580,   4 bytes: 00 00 00 00                                      ....
   243097  READ0[5340]  3210,  224 bytes: BE 00 00 00 4F 00 00 00 4D 00 00 00 00 00 00 00  ....O...M.......
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243097                           00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   243175  READ0[5432]  6020,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   243175  READ0[5432]  6018,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   243175  READ0[5432]  6010,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   243175  READ0[5432]  0238,   3 bytes: 00 00 00                                         ...
   243175  READ0[5340]  0020,   4 bytes: 00 00 00 00                                      ....
   243175  READ0[5340]  0560,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   243175  READ0[5340]  0568,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   243175  READ0[5340]  0570,   8 bytes: 00 00 00 00 00 00 00 00                          ........
   243175  READ0[5340]  0580,   4 bytes: 00 00 00 00                                      ....

If this is useful I'll send the whole thing in a series of 'chunks'

Share this post


Link to post
Share on other sites

As suggested, I've copied the entire file and tried pasting it into the <> code box. All that happens is that the entire window goes grey. Clearly can't cope with so much text. I'll try copying & pasting a smaller portion.If this is useful I'll send the whole thing in a series of 'chunks'

 

You are logging things not needed. No wonder the log is large. Switch off ALL logging options please, I asked for none. The log will be very short then!

 

And do NOT press "New Log" as that closes the original log and starts a new one.

 

And i need to see the whole log, with the closing parts after FS is closed.

 

And it needs to be for a currently supported version -- 4.929 is old. Current is 4.934.

 

Just start FS, run the program you have problems with, close FS, show the log. That's all. do not set any options whatsoever.

 

Regards

Pete

Share this post


Link to post
Share on other sites

Pete,

   Last night I tried doing it the way you suggested. The file was still very large (108Kb), and the forum software declined to post my reply as being too large.

 

Now I've backed up that large file, and started again, producing the log as shown here:

********* FSUIPC4, Version 4.934 by Pete Dowson *********
User Name="Brian King"
User Addr="brianrhking@compuserve.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
   100886 System time = 02/07/2014 07:16:32
[Continuation log requested by user]
Running inside FSX on Windows 7
Module base=64A70000
   186656 Sim stopped: average frame rate for last 85 secs = 11.5 fps
   192880 System time = 02/07/2014 07:18:04
   192880 *** FSUIPC log file being closed
Average frame rate for running time of 93 secs = 11.6 fps
G3D fix: Passes 22090, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

If it's not showing you enough info, let me know. I could send you segments of the large file  -  start, close-down, some bits from the middle  -  or I could let FSX run for longer or carry out some manoeuvres, later today and send the log again. Meanwhile, work beckons!

Share this post


Link to post
Share on other sites

Last night I tried doing it the way you suggested. The file was still very large (108Kb), and the forum software declined to post my reply as being too large.

 

Don't ever bother to try to post text files in any case. It is always best to simply paste their contents into a message. If you ever do need to attach files, ZIP them first. Even a huge text file ZIPs pretty small!

 

If the file is large it must be because you have logging options still checked. Just make sure all options are unchecked on the logging tab BEFORE closing FS down, then when you start it up again the log will be normal.

 

Now I've backed up that large file, and started again, producing the log as shown here:********* FSUIPC4, Version 4.934 by Pete Dowson *********

 

And yet you STILL went to the logging tab and pressed "New Log" just like I asked you not to! :sad:

 

Anyway, the little it does contain (as a result of aborting the start-up log and starting a new one, again), does show that FSUIPC is working fine, no problems at all -- unless they are occurring during the first 3 minutes which would have been detailed in the normal, original, log.

 

Your frame rate of a mere 11.6 fps seems terribly low.

 

Pete

 

Share this post


Link to post
Share on other sites

Pete,

 

I suspect I'm not explaining myself adequately.  I did not try simply posting the log file. I opened it, copied it in its entirety (108Kb), pasted it into the <> box as part of a reply. It told me the post was too large, and didn't post it. The logging options are all unticked.

 

I then backed up that log file, because I realised that I wouldn't be able to send you that one unabridged. The only way I could send a small enough file was to start again, and that's what I did. I still have the backed up 108Kb file, if it's of any use to you, but I can only post it in chunks.

 

You say that from what you can see, FSUIPC is working OK. But clearly something is not right. Your comment about the fps rate is not surprising  -  it tends to be low, usually when situated at a complex add-on airport and with large amounts of AI overhead. However, this is nothing new, but the fault as between ADE, FSUIPC and FSX is new.

 

The only things hat have changed recently, software-wise, have been an upgrading of FSUIPC (a few months ago) to 4.929, though now up to 4.934, and an upgrade of ADE which I did to try to correct this fault. Didn't do the trick.

 

I'll run through the whole procedure again, to make sure.

Share this post


Link to post
Share on other sites

Pete,

 

OK, I've been through the procedure again:

 

Opened FSX, selected an airport, a/c at runway. Slew a little way then slew off.

Opened FSUIPC from the menu bar. Select Logging tab. All logging options are off. No changes made on FSUIPC.

Check Shift-Z  -  correct lat and long.

Opened ADE, load airport file. It's on auto-connect. The red coordinates say all zeros.

Opened ADE Env Checker  -  all satisfactory, but the FSUIPC section gives coordinates as all zeros, despite being correctly connected.

Close Checker and ADE.

Close FSX.

Open FSUIPC4.log, select all, copy; paste into <> as below.

********* FSUIPC4, Version 4.934 by Pete Dowson *********
Reading options from "F:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=65580000
User Name="Brian King"
User Addr="brianrhking@compuserve.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       47 System time = 02/07/2014 17:24:49
       47 FLT path = "C:\Users\B\Documents\Flight Simulator X Files\"
       78 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       93 FS path = "F:\FSX\"
      561 LogOptions=00000000 00000001
      561 SIM1 Frictions access gained
      561 Wind smoothing fix is fully installed
      561 G3D.DLL fix attempt installed ok
      561 SimConnect_Open succeeded: waiting to check version okay
      561 Trying to use SimConnect Acc/SP2 Oct07
     4321 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)
     4321 Initialising SimConnect data requests now
     4321 FSUIPC Menu entry added
     4352 c:\users\b\documents\flight simulator x files\Start-up setting.FLT
     4352 F:\FSX\SimObjects\Rotorcraft\Bell206B\Bell_206B_JetRanger.AIR
   147561 Sim stopped: average frame rate for last 70 secs = 13.7 fps
   601898 Sim stopped: average frame rate for last 377 secs = 12.5 fps
   630447 System time = 02/07/2014 17:35:20
   630447 *** FSUIPC log file being closed
Average frame rate for running time of 463 secs = 12.7 fps
G3D fix: Passes 22053, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

Share this post


Link to post
Share on other sites

I suspect I'm not explaining myself adequately.  I did not try simply posting the log file. I opened it, copied it in its entirety (108Kb), pasted it into the <> box as part of a reply. It told me the post was too large, and didn't post it. The logging options are all unticked.

 

You say that from what you can see, FSUIPC is working OK. But clearly something is not right. Your comment about the fps rate is not surprising  -  it tends to be low, usually when situated at a complex add-on airport and with large amounts of AI overhead. However, this is nothing new, but the fault as between ADE, FSUIPC and FSX is new.

 

The only things hat have changed recently, software-wise, have been an upgrading of FSUIPC (a few months ago) to 4.929, though now up to 4.934, and an upgrade of ADE which I did to try to correct this fault. Didn't do the trick.

 

I'll run through the whole procedure again, to make sure.

 

A run of FSX with FSUIPC installed, just starting FS, running it for a short time, then closing it, produces a very small log. Only selecting logging options will extend it. Since I've never yet seen you first log (you always click the "New Log" button for some unknown region) I can't tell what you have set -- it is logged in the early parts.

 

For the log to get to 108Kb it would need to contain a minimum of 1300 lines even if all were full to 80 characters each. There is no way a log with no options selected will get that long. Here's a typical log file just loading FSX, running a couple of other programs (which have no effect on the log anyway) and closing FS after five minutes or so. the file itself is just 3kb. 108kb is HUGE. Please tell me what sort of lines you see in it which are not on this one:

 

********* FSUIPC4, Version 4.934 by Pete Dowson *********
Reading options from "E:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=0DA30000
User Name="Pete Dowson"
User Addr="petedowson@btconnect.com"
FSUIPC4 Key is provided
WideFS7 Key is provided
       78 System time = 02/07/2014 17:48:29
       78 FLT UNC path = "\\LEFT\FSPLANS\"
      125 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      156 FS UNC path = "\\LEFT\FSX\"
     4165 LogOptions=00000000 00000011
     4165 SIM1 Frictions access gained and basic values patched
     4165 Wind smoothing fix is fully installed
     4165 G3D.DLL fix attempt installed ok
     4165 SimConnect intercept for texts and menus installed ok
     4165 SimConnect_Open succeeded: waiting to check version okay
     4165 Trying to use SimConnect Acc/SP2 Oct07
     9797 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     9797 Initialising SimConnect data requests now
     9797 FSUIPC Menu entry added
     9906 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
     9921 \\LEFT\FSPLANS\738 EGCC Cold and Dark.FLT
     9921 \\LEFT\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.AIR
    10062 Memory in use: 517Mb, Avail=3579Mb
    70325 Memory in use: 748Mb, Avail=3348Mb
   130588 Memory in use: 830Mb, Avail=3266Mb
   184861 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
   185438 System time = 02/07/2014 17:51:34, Simulator time = 17:48:39 (16:48Z)
   189135 Aircraft="Boeing 737-800 Paint2"
   190259 Starting everything now ...
   190321 Using "E:\FSX\Modules\DLL\GFDEV.DLL", version 2.2.2.0
   190321 GoFlight GFP8 detected: 2 devices
   190321 GoFlight GFT8 detected: 2 devices
   190321 GoFlight GFRP48 detected: 2 devices
   190337 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   191553 Advanced Weather Interface Enabled
   193363 Memory in use: 1107Mb, Avail=2989Mb
   253595 Memory in use: 1156Mb, Avail=2940Mb
   313843 Memory in use: 1169Mb, Avail=2927Mb
   314888 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   314888 Sim stopped: average frame rate for last 130 secs = 29.3 fps
   324123 System time = 02/07/2014 17:53:53, Simulator time = 17:50:45 (16:50Z)
   324123 *** FSUIPC log file being closed
Average frame rate for running time of 130 secs = 29.3 fps
G3D fix: Passes 13117, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 112 Allocs, 112 Freed
********* FSUIPC Log file closed ***********

 

I then backed up that log file, because I realised that I wouldn't be able to send you that one unabridged. The only way I could send a small enough file was to start again, and that's what I did.

 

But by "starting again" you mean pressing the New Log button which closes and renames the current log (adding a .1) and starts a new one, without of course all the essential startup information.

 

You say that from what you can see, FSUIPC is working OK. But clearly something is not right.
 
But this is something only the author of the program which is trying to interface to it correctly can deal with. I cannot support all FSUIPC client applications. If you simply want proof that FSUIPC can ad is able to supply data correctly please download the SDK and run FSInterrogate to view the assorted offsets at will. Or run one of my own example utilities such as TrafficLook or WeatherSet2.
 
Your comment about the fps rate is not surprising  -  it tends to be low, usually when situated at a complex add-on airport and with large amounts of AI overhead. However, this is nothing new, but the fault as between ADE, FSUIPC and FSX is new.

 

I would class frame rates as low as 11 as unflyable. My worst airport is UK2000 Heathrow Extreme, latest version (with the new Terminal 2), with realistic traffic levels, and than can drop to as low as 18. i wouldn't like it lower than that! ;-)

 

Regards

Pete

Share this post


Link to post
Share on other sites

OK, I've been through the procedure again:

 

I see you figured out how to get a short log after all! ;-)

 

And, yes, everything looks fine. There's nothing there which can cause FSUIPC not to supply the correct data to any program which is asking for it correctly. If it is supplying only zeroes, as I think you said, then I can only think there's a fault in SimConnect, which is the part of FS which supplies the data. All FSUIPC does is map the data into an offset memory area for programs to read.

 

Just to check this aspect (i.e. SimConnect reception),  I'm going to ask you to actually add logging now. Load up just FS -- NOT any client program, in case it is that which is somehow clobbering things.

 

Please go into the Logging tab and on the right-hand side enter these offsets and types in the relevant columns:

 

0560 as type UIF64

0568 as type UIF64

6010 as type FLT64

6018 as type FLT64

 

Then check the 'normal log' option below.

 

This will first log the current position values. Slew or move the aircraft a ways, so it receives more changes.

 

This will log several for each change of position -- the 0560/0568 values are very precise, the 6010 and 6018 less so. Keep it short but by all means just post an extract if it gets long.

 

The log should show what is being actually returned by SimConnect for the latitude and longitude. Here's an example (the 0560 and 0568 values are in FS internal units, so don't worry about them being so different).

 

   663207 Monitor IPC:0560 (UIF64) = 5940739.3454
   663207 SimRead: 0560="PLANE LATITUDE"
            FLT64: 53.4572990817
   663207 Monitor IPC:0568 (UIF64) = 4267551246.7788
   663207 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -2.29798669918
   663238 Monitor IPC:6010 (FLT64) = 53.4573
   663238 SimRead: 6010="GPS POSITION LAT"
            FLT64: 53.4572912577
   663238 Monitor IPC:6018 (FLT64) = -2.2980
   663238 SimRead: 6018="GPS POSITION LON"
            FLT64: -2.29797546725
   663238 Monitor IPC:0560 (UIF64) = 5940740.3509
   663238 SimRead: 0560="PLANE LATITUDE"
            FLT64: 53.4573081288
   663238 Monitor IPC:0568 (UIF64) = 4267551091.8271
   663238 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -2.29799968708
   663269 Monitor IPC:0560 (UIF64) = 5940741.1814
   663269 SimRead: 0560="PLANE LATITUDE"
            FLT64: 53.4573156023
   663269 Monitor IPC:0568 (UIF64) = 4267550963.8280
   663269 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -2.29801041584
   663300 Monitor IPC:0560 (UIF64) = 5940742.0104
   663300 SimRead: 0560="PLANE LATITUDE"
            FLT64: 53.4573230622
   663300 Monitor IPC:0568 (UIF64) = 4267550836.0607
   663300 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -2.29802112517

The Monitor line is what FS is putting into the offset for applications to read, and these two following show the actual Simconnect name for the value and what it returned, in normal degrees, in floating point.

 

Regards
Pete

Share this post


Link to post
Share on other sites

Ah, I've just notice an anomaly from your log, after examining it more closely. I don't think FSUIPC is actually starting. Here's the critical part in the log I showed:

 

   184861 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
   
185438 System time = 02/07/2014 17:51:34, Simulator time = 17:48:39 (16:48Z)
   189135 Aircraft="Boeing 737-800 Paint2"
   190259 Starting everything now ...

 
This occurs after the flight has fully loaded, some 90 seconds (in my case) after the Flight/AIR file was identified here:
 
     9797 FSUIPC Menu entry added
     
9906 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
     
9921 \\LEFT\FSPLANS\738 EGCC Cold and Dark.FLT
     
9921 \\LEFT\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.AIR

 

In your log the whole sequence ends before getting to the state where everything is ready:

 

4321 FSUIPC Menu entry added
4352 c:\users\b\documents\flight simulator x files\Start-up setting.FLT
4352 F:\FSX\SimObjects\Rotorcraft\Bell206B\Bell_206B_JetRanger.AIR
147561 Sim stopped: average frame rate for last 70 secs = 13.7 fps
601898 Sim stopped: average frame rate for last 377 secs = 12.5 fps
630447 System time = 02/07/2014 17:35:20
630447 *** FSUIPC log file being closed

 
The only time I've seen this was in a version of P3Dv1 where the flight being loaded was already in Paused mode. Unpausing it got past the problem. I think this was fixed in a later version of P3Dv1.
 
So, first, can you tell me if the flight you are loaded is paused?
 
Second, can you enable "Extras" logging (one of the Logging options), close FS down, then just run it and close it when it is ready to fly, producing a short log like before? The Extras logging produces those
 
Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
 
lines, giving me the "ready to fly" status.
 
The other thing FSUIPC needs to receive from SimConnect before it starts properly is the Aircraft name. it needs this in case of assignments to profiles and so on. 
 
After this, there are some other logging options we can apply to see why it isn't starting. One other thing you can try is changing aircraft, in case for some reason SimConnect can't supply its name.
 
Regards
Pete

Share this post


Link to post
Share on other sites

Pete,

 

OK, Ive done exactly as per your instructions. But as you'll see, it suggests that it is (a) unaware of my actual lat/long, but (b) doesn't seem to have logged my slew movements.  I slewed the a/c a couple of hundred yards to one side of the runway, slewed down to the far end and back, but none of that shows up.

********* FSUIPC4, Version 4.934 by Pete Dowson *********
Reading options from "F:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=65580000
User Name="Brian King"
User Addr="brianrhking@compuserve.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       32 System time = 02/07/2014 18:42:18
       32 FLT path = "C:\Users\B\Documents\Flight Simulator X Files\"
       63 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       78 FS path = "F:\FSX\"
      546 LogOptions=00000000 00000001
      546 SIM1 Frictions access gained
      546 Wind smoothing fix is fully installed
      546 G3D.DLL fix attempt installed ok
      562 SimConnect_Open succeeded: waiting to check version okay
      562 Trying to use SimConnect Acc/SP2 Oct07
     4306 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)
     4306 Initialising SimConnect data requests now
     4306 FSUIPC Menu entry added
     4337 c:\users\b\documents\flight simulator x files\Start-up setting.FLT
     4337 F:\FSX\SimObjects\Rotorcraft\Bell206B\Bell_206B_JetRanger.AIR
   262113 Monitor IPC:0560 (UIF64) = 0.0000
   262113 Monitor IPC:0568 (UIF64) = 0.0000
   262113 Monitor IPC:6010 (FLT64) = 0.0000
   262113 Monitor IPC:6018 (FLT64) = 0.0000
   319537 Sim stopped: average frame rate for last 57 secs = 12.8 fps
   325824 System time = 02/07/2014 18:47:43
   325824 *** FSUIPC log file being closed
Average frame rate for running time of 72 secs = 13.0 fps
G3D fix: Passes 22004, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

Not what I expected, from your very clear explanation.

Share this post


Link to post
Share on other sites

OK, Ive done exactly as per your instructions. But as you'll see, it suggests that it is (a) unaware of my actual lat/long, but ( B) doesn't seem to have logged my slew movements.  I slewed the a/c a couple of hundred yards to one side of the runway, slewed down to the far end and back, but none of that shows up.

 

Please see my subsequent message, above.

 

Back later ... dinner time, flake out a bit. I'll catch up before bed-time.

 

Pete

Share this post


Link to post
Share on other sites

Pete,

 

I do appreciate your time on this crazy problem, and don't let me intrude on your very necessary meal times and down-time!

 

You'll see my previous log, with the lat/long at zeros. I have now followed up your instruction to add in the 'extras', with the following results:

 

104Kb log file. I've therefore copied and pasted the 'intro', followed by a small portion of the 'Too many requests' listing, and finally the end section.

FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       31 System time = 02/07/2014 19:26:30
       31 FLT path = "C:\Users\B\Documents\Flight Simulator X Files\"
       63 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       63 FS path = "F:\FSX\"
      546 LogOptions=00000000 00000011
      546 SIM1 Frictions access gained
      546 Wind smoothing fix is fully installed
      546 G3D.DLL fix attempt installed ok
      546 SimConnect_Open succeeded: waiting to check version okay
      546 Trying to use SimConnect Acc/SP2 Oct07
     4321 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)
     4321 Initialising SimConnect data requests now
     4321 FSUIPC Menu entry added
     4353 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
     4353 c:\users\b\documents\flight simulator x files\Start-up setting.FLT
     4353 F:\FSX\SimObjects\Rotorcraft\Bell206B\Bell_206B_JetRanger.AIR
     4509 Memory in use: 430Mb, Avail=3666Mb
     4914 Monitor IPC:0560 (UIF64) = 0.0000
     4914 Monitor IPC:0568 (UIF64) = 0.0000
     4914 Monitor IPC:6010 (FLT64) = 0.0000
     4914 Monitor IPC:6018 (FLT64) = 0.0000
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3333, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4474 [0x0117A]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3335, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4477 [0x0117D]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3337, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4480 [0x01180]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3339, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4483 [0x01183]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3341, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4486 [0x01186]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3343, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4489 [0x01189]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3345, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4492 [0x0118C]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3347, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4495 [0x0118F]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3349, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4498 [0x01192]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3351, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4501 [0x01195]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3353, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4504 [0x01198]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3355, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4507 [0x0119B]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3357, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4510 [0x0119E]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3359, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4513 [0x011A1]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3361, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4516 [0x011A4]
    47128 Exception 12 "TOO_MANY_REQUESTS", Ref 3363, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4519 [0x011A7]

   (and so on........)

95894 Exception 12 "TOO_MANY_REQUESTS", Ref 5571, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4877 [0x0130D]
    95894 Exception 12 "TOO_MANY_REQUESTS", Ref 5574, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4871 [0x01307]
    95894 Exception 12 "TOO_MANY_REQUESTS", Ref 5577, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4988 [0x0137C]
   125207 Memory in use: 1342Mb, Avail=2754Mb
   160385 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
   160385 Sim stopped: average frame rate for last 71 secs = 13.2 fps
   165938 System time = 02/07/2014 19:29:16
   165938 *** FSUIPC log file being closed
Average frame rate for running time of 85 secs = 13.4 fps
G3D fix: Passes 22080, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

The flight was loaded up as a 'free flight', and not paused.  The log shows the aircraft name, so I haven't changed a/c at all. At no point does the log say Ready-To-Fly=Y, although the a/c was happily ready at the runway and would have taken off if I had chosen. Perhaps I'll do that, see if it makes any odds?

 

 

Share this post


Link to post
Share on other sites

I have now followed up your instruction to add in the 'extras', with the following results:

 

104Kb log file. I've therefore copied and pasted the 'intro', followed by a small portion of the 'Too many requests' listing, and finally the end section.

 

The "too many requests" error is a SimConnect problem I've rarely seen. What's changed since the previous log? Just enabling Extras logging doesn't change that. 

 

Have you actually got over  500 AI aircraft loading and running at the start of the program?  It looks like simply requesting data on them all is overflowing SimConnect's buffers.  I have seen it happen occasionally, but generally it's a symptom of something else going wrong. It might be worth testing with the AI traffic turned off (sliders to zero) to see if it's something there that's stopping things proceeding normally. It will also certainly help a lot with those dreadful frame rates! ;-)

 

The flight was loaded up as a 'free flight', and not paused.  The log shows the aircraft name

 

No it doesn't. It identifies the FLT file and the AIR file. the aircraft name is the one from inside the CFG file, and is logged as in the line in the log I pasted:

 

189135 Aircraft="Boeing 737-800 Paint2"

 

Assuming things aren't (always) getting snarled up in a SimConnect buffer filling loop, it remains a mystery. Here's some other logging I need you to enable now:

 

Before running FS, edit the FSUIPC4.INI file, adding these two lines to the [General] section:

 

Debug=Please

TestOptions=x800

 

This will log more information about what FSUIPC is waiting for before it thinks you are "ready to fly".

 

Oh, the other thing, please now use the exact same build I'm using here, 4,934f download using this link:

 FSUIPC4934f.zip

It isn't that I think this will behave any differently (it has some interim changes for a P3D beta, that's all). It's just that I want the code to match exactly in case I need to dig further.

 

Pete

Share this post


Link to post
Share on other sites

Pete,

 

I think you may have cracked it, with your suspicions about the sheer quantity of AI traffic.  I reduced AI traffic (all types) to zero, re-started, slewed a bit.  Started ADE which is now behaving correctly, showing my lat/long and showing the a/c symbol as it should. Closed down, and, the log file being enormous (presumably as a result of the extra logging options which you specified just now, added to the .ini file) I've again selected the initial and final sections of the log file, as well as an interim section that includes the a/c name, to copy. The rest is simply endless positions as I slew around.

********* FSUIPC4, Version 4.934f by Pete Dowson *********
Reading options from "F:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=65580000
User Name="Brian King"
User Addr="brianrhking@compuserve.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       62 System time = 03/07/2014 07:25:50
       62 FLT path = "C:\Users\B\Documents\Flight Simulator X Files\"
       93 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       93 FS path = "F:\FSX\"
      577 LogOptions=00000800 00000011
      577 SIM1 Frictions access gained
      577 Wind smoothing fix is fully installed
      577 G3D.DLL fix attempt installed ok
      577 SimConnect_Open succeeded: waiting to check version okay
      577 Trying to use SimConnect Acc/SP2 Oct07
     2496 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)
     2496 Initialising SimConnect data requests now
     2496 FSUIPC Menu entry added
     2527 ## EV_SIM=stop
     2527 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
     2527 c:\users\b\documents\flight simulator x files\Start-up setting.FLT
     2527 F:\FSX\SimObjects\Rotorcraft\Bell206B\Bell_206B_JetRanger.AIR
     2527 ##: ST_SIM=stop
     2667 Memory in use: 415Mb, Avail=3681Mb
     3073 Monitor IPC:0560 (UIF64) = 0.0000
     3073 Monitor IPC:0568 (UIF64) = 0.0000
     3073 Monitor IPC:6010 (FLT64) = 0.0000
     3073 Monitor IPC:6018 (FLT64) = 0.0000
    32588 ##: ST_SIM=stop
    35162 ##: ST_SIM=stop
    37908 ##: ST_SIM=stop
    39140 ## EV_START
    39140 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    39140 ## EV_SIM=start
    39171 Monitor IPC:0560 (UIF64) = 5756697.3212
    39171 SimRead: 0560="PLANE LATITUDE"
            FLT64: 51.8012106786
    39171 Monitor IPC:0568 (UIF64) = 4293134758.0228
    39171 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.153601558828
    39171 Monitor IPC:0568 (UIF64) = 4293134758.0232
    39171 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.153601558801
    39203 Monitor IPC:6010 (FLT64) = 52.4524
    39203 SimRead: 6010="GPS POSITION LAT"
            FLT64: 52.4523611111
    39203 Monitor IPC:6018 (FLT64) = -1.7373
    39203 SimRead: 6018="GPS POSITION LON"
            FLT64: -1.73730555556
    39203 Monitor IPC:0568 (UIF64) = 4293134758.0235
    39203 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.153601558768
    39203 Monitor IPC:0568 (UIF64) = 4293134758.0240

     then.....

  39437 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.153601558313
    39468 Monitor IPC:0568 (UIF64) = 4293134758.0294
    39468 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.153601558277
    39468 Monitor IPC:0560 (UIF64) = 5756697.3211
    39468 SimRead: 0560="PLANE LATITUDE"
            FLT64: 51.8012106785
    39468 Monitor IPC:0568 (UIF64) = 4293134758.0298
    39468 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.153601558241
    39499 ## WHYSTART: SOON: (0366=Y || (0264=N && 3365=Y)) && (3D00=N || (0580=Y && 0264=Y))
    39499 ##                 ... and no class #32770 window!
    39499 System time = 03/07/2014 07:26:29, Simulator time = 07:25:53 (06:25Z)
    39499 Aircraft="Bell 206B JetRanger Paint1"
    39499 Monitor IPC:0568 (UIF64) = 4293134758.0304
    39499 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.153601558196
    39499 Monitor IPC:0568 (UIF64) = 4293134758.0309
    39499 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.15360155815
    39530 Monitor IPC:6010 (FLT64) = 51.8012
    39530 SimRead: 6010="GPS POSITION LAT"
            FLT64: 51.8012106785
    39530 Monitor IPC:6018 (FLT64) = -0.1536
    39530 SimRead: 6018="GPS POSITION LON"
            FLT64: -0.153601558241
    39530 Monitor IPC:0568 (UIF64) = 4293134758.0313
    39530 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.153601558116
    39546 Monitor IPC:0568 (UIF64) = 4293134758.0317
    39546 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.153601558083
    39577 Monitor IPC:0568 (UIF64) = 4293134758.0321

and so on.......  100105 Monitor IPC:0568 (UIF64) = 4293150750.7807

   100105 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.152261061346
   100137 Monitor IPC:0568 (UIF64) = 4293150750.7795
   100137 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.152261061449
   100168 Monitor IPC:0568 (UIF64) = 4293150750.7783
   100168 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.152261061554
   100183 Monitor IPC:0568 (UIF64) = 4293150750.7771
   100183 SimRead: 0568="PLANE LONGITUDE"
            FLT64: -0.15226106165
   100355 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   100355 Sim stopped: average frame rate for last 61 secs = 34.6 fps
   100355 Average weather filter write interval in that time = 939.1 msecs
 
   105955 System time = 03/07/2014 07:27:36, Simulator time = 07:27:29 (06:27Z)
   105955 *** FSUIPC log file being closed
Average frame rate for running time of 61 secs = 34.6 fps
Average weather filter write interval in that time = 939.1 msecs
G3D fix: Passes 17409, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 81 Allocs, 81 Freed
********* FSUIPC Log file closed ***********

 

 

 

 

 

If this all looks OK, I will now have to consider what to do about the AI!  For some years I've had lots of it, most of the major airlines with their schedules, and recently been compiling a UK GA set of flightplans to populate the local skies with GA a/c. Looks as if I've overdone it!  Never had the problem with ADEX before, so it must have reached a critical mass.

 

Anyway, it looks as if your efforts have paid off. What do you reckon?

Share this post


Link to post
Share on other sites

I think you may have cracked it, with your suspicions about the sheer quantity of AI traffic.  I reduced AI traffic (all types) to zero, re-started, slewed a bit.  Started ADE which is now behaving correctly, showing my lat/long and showing the a/c symbol as it should. Closed down, and, the log file being enormous (presumably as a result of the extra logging options which you specified just now, added to the .ini file) I've again selected the initial and final sections of the log file, as well as an interim section that includes the a/c name, to copy. The rest is simply endless positions as I slew around.

 

Right. But I'd still like to understand why so much traffic makes things stall. I don't know what SimConnect's limit on numbers of pending data requests is, but evidently it was being exceeded, and one of the results was that it never accepted requests for certain vital items of data which FSUIPC waits for before starting everything properly.

 

One way I might tackle it, if i can and once I know more, would be to ration the requests for data on AI traffic.  However, if I never ask for data on more than, say, 250 aircraft, I may not get to those which are in range, so not then populating my traffic tables correctly for the nearest ones on ground and in the air.

 

Another possibility is to avoid any AI traffic scanning until AFTER the initialisation stage is well completed.  It does order things in that way, but it looks like there's insufficient gap. I might incorporate a multi-second delay after starting everything up before asking for anything to do with AI.

 

Odd that FSX has been going now for 9 years or more and this hasn't cropped up as a problem before. What AI traffc are you using?  Looks like you are in or near London, so do you have lots of traffic for all the London area airports?

 

Just so I can be sure of exactly what is happening, before deciding what to do, could you please do one more test. Remove all of the monitoring offsets (easiest way is to delete the [Monitor] section in the FSUIPC4.INI before running FS).  Re-enable all your traffic, as before, in order to induce the problem, then show me the log, at least as far as when is appears to fail to provide your Lat/Lon. The "TestOption" logging you added will tell me what data FSUIPC is waiting for.

 

If this all looks OK, I will now have to consider what to do about the AI!

 

 

I don't see the "## Starting everything now ..." line -- maybe it's in the part of the log you omitted? If so, then it's all okay.

 

 Looks as if I've overdone it! 

 

 

Yes. In my opinion you made it unflyable too -- but maybe you just want to sit and watch AI instead? ;-). Look at your average frame rate without all that traffic:

 

 100355 Sim stopped: average frame rate for last 61 secs = 34.6 fps

 

However, I don't like anything stopping FSUIPC working correctly like that, so I'll need to consider what to do about it also.  When I do decide, I'd be grateful if you could then again overload FSX so you can test the changes for me!

 

Regards

Pete

Share this post


Link to post
Share on other sites

Pete,

 

I can well appreciate that it would be unsatisfactory to leave it at that  -  and I'm happy to try this and that to see if we can get to the bottom of the issue.

 

As you suggested, I've deleted the [monitor] section and tried several scenarios. Setting Commercial AI to 100% is OK. Adding in GA AI is OK, as it is if I add in the ships and the freeway traffic. It's when I add in airport traffic at full density that it 'fails'  -  as indicated by the failure of ADEX to show the correct lat/long.  So it seems to be a fairly critical amount of traffic that causes the problem. I'll go back in a bit and try the airport traffic on its own.

 

Meanwhile, here's the log with all the AI at full density  -  again, just showing you the relevant parts of the log:

********* FSUIPC4, Version 4.934f by Pete Dowson *********
Reading options from "F:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=64F60000
User Name="Brian King"
User Addr="brianrhking@compuserve.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       32 System time = 03/07/2014 16:19:43
       32 FLT path = "C:\Users\B\Documents\Flight Simulator X Files\"
       63 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       63 FS path = "F:\FSX\"
      546 LogOptions=00000800 00000011
      546 SIM1 Frictions access gained
      546 Wind smoothing fix is fully installed
      546 G3D.DLL fix attempt installed ok
      546 SimConnect_Open succeeded: waiting to check version okay
      546 Trying to use SimConnect Acc/SP2 Oct07
     4322 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)
     4322 Initialising SimConnect data requests now
     4322 FSUIPC Menu entry added
     4353 ## EV_SIM=stop
     4353 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
     4353 c:\users\b\documents\flight simulator x files\Start-up setting.FLT
     4353 F:\FSX\SimObjects\Rotorcraft\Bell206B\Bell_206B_JetRanger.AIR
     4353 ##: ST_SIM=stop
     4509 Memory in use: 432Mb, Avail=3664Mb
    34367 ##: ST_SIM=stop
    36926 ##: ST_SIM=stop
    39484 ##: ST_SIM=stop
    42043 ##: ST_SIM=stop
    44601 ##: ST_SIM=stop
    47159 ##: ST_SIM=stop
    49718 ##: ST_SIM=stop
    52276 ##: ST_SIM=stop
    54835 ##: ST_SIM=stop
    57393 ##: ST_SIM=stop
    59078 Weather Mode now = Theme
    59078 C:\Users\B\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
    59109 Exception 12 "TOO_MANY_REQUESTS", Ref 3338, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4459 [0x0116B]
    59109 Exception 12 "TOO_MANY_REQUESTS", Ref 3340, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4462 [0x0116E]
    59109 Exception 12 "TOO_MANY_REQUESTS", Ref 3342, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4465 [0x01171]
    59109 Exception 12 "TOO_MANY_REQUESTS", Ref 3344, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4468 [0x01174]
    59109 Exception 12 "TOO_MANY_REQUESTS", Ref 3346, Index param -1 on RequestDataOnSimObject for AI Aircraft id=4471 [0x01177]

    and so on.....

[0x01AEF]
   105379 Exception 12 "TOO_MANY_REQUESTS", Ref 6326, Index param -1 on RequestDataOnSimObject for AI Aircraft id=6897 [0x01AF1]
   105691 Exception 12 "TOO_MANY_REQUESTS", Ref 6328, Index param -1 on RequestDataOnSimObject for AI Aircraft id=6899 [0x01AF3]
   105878 ##: ST_SIM=stop
   107360 ## EV_START
   107360 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
   107360 ## EV_SIM=start
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6334, Index param -1 on RequestDataOnSimObject for DDEF 3
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6335, Index param -1 on RequestDataOnSimObject for DDEF 4
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6336, Index param -1 on RequestDataOnSimObject for DDEF 5
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6337, Index param -1 on RequestDataOnSimObject for DDEF 6
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6338, Index param -1 on RequestDataOnSimObject for DDEF 7
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6339, Index param -1 on RequestDataOnSimObject for DDEF 9
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6340, Index param -1 on RequestDataOnSimObject for DDEF 10
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6341, Index param -1 on RequestDataOnSimObject for DDEF 11
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6342, Index param -1 on RequestDataOnSimObject for DDEF 14
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6343, Index param -1 on RequestDataOnSimObject for DDEF 15
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6344, Index param -1 on RequestDataOnSimObject for DDEF 16
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6345, Index param -1 on RequestDataOnSimObject for DDEF 17
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6346, Index param -1 on RequestDataOnSimObject for DDEF 19
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6347, Index param -1 on RequestDataOnSimObject for DDEF 21
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6348, Index param -1 on RequestDataOnSimObject for DDEF 24
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6349, Index param -1 on RequestDataOnSimObject for AI Aircraft id=6610 [0x019D2]
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6351, Index param -1 on RequestDataOnSimObject for AI Aircraft id=6553 [0x01999]
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6355, Index param -1 on RequestDataOnSimObject for AI Aircraft id=6551 [0x01997]
   107423 Exception 12 "TOO_MANY_REQUESTS", Ref 6358, Index param -1 on RequestDataOnSimObject for AI Aircraft id=6564 [0x019A4]

    and more......

[0x019B0]
   118717 Exception 12 "TOO_MANY_REQUESTS", Ref 7370, Index param -1 on RequestDataOnSimObject for AI Aircraft id=6584 [0x019B8]
   120012 Exception 12 "TOO_MANY_REQUESTS", Ref 7372, Index param -1 on RequestDataOnSimObject for AI Aircraft id=6962 [0x01B32]
   121010 ##: ST_SIM=start
   123522 ##: ST_SIM=start
   125113 Memory in use: 1334Mb, Avail=2761Mb
   126034 ##: ST_SIM=start
   128608 ##: ST_SIM=start
   131166 ##: ST_SIM=start
   133740 ##: ST_SIM=start
   136298 ##: ST_SIM=start
   138810 ##: ST_SIM=start
   141384 ##: ST_SIM=start
   143942 ##: ST_SIM=start
   146485 ##: ST_SIM=start
   149059 ##: ST_SIM=start
   151633 ##: ST_SIM=start
   154207 ##: ST_SIM=start
   156750 ##: ST_SIM=start
   159324 ##: ST_SIM=start
   161867 ##: ST_SIM=start
   164410 ##: ST_SIM=start
   166953 ##: ST_SIM=start
   169527 ##: ST_SIM=start
   172101 ##: ST_SIM=start
   174675 ##: ST_SIM=start
   177264 ##: ST_SIM=start
   179869 Exception 12 "TOO_MANY_REQUESTS", Ref 7399, Index param -1 on RequestDataOnSimObject for AI Aircraft id=6963 [0x01B33]
   179869 ##: ST_SIM=start
   182397 ##: ST_SIM=start
   184940 ##: ST_SIM=start
   185439 Memory in use: 1404Mb, Avail=2692Mb
   187451 ##: ST_SIM=start
   190025 ##: ST_SIM=start
   192568 ##: ST_SIM=start
   195126 ##: ST_SIM=start
   197747 ##: ST_SIM=start
   200321 ##: ST_SIM=start
   200945 ## EV_STOP
   200945 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
   200945 Sim stopped: average frame rate for last 93 secs = 12.8 fps
   200945 ## EV_SIM=stop
   206670 System time = 03/07/2014 16:23:09
   206670 *** FSUIPC log file being closed
Average frame rate for running time of 93 secs = 12.8 fps
G3D fix: Passes 22390, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 5 Allocs, 5 Freed
********* FSUIPC Log file closed ***********

The AI that I use is all taken off FlightSim or Avsim,  supplying the aircraft separately  -  not one of the 'packages'.  There is certainly a high density of traffic over UK  -  all flights of all the significant airlines is included, but worldwide.  Yes, it would be excellent if FSX (or FSUIPC) could ignore and not try to initialise traffic from beyond a certain range  -  providing it can then initialise stuff 'on-the-fly' as you pass into an area previously 'uninitialised', while on a long-haul flight.  As far as ADEX is concerned, I can obviously just turn down the AI density while doing editing work.  But it's the hit on the frame rates that is problematic. My AI has grown slowly over the years so I've probably not noticed the slow deterioration in fps.  I use a lot of Gary Summons' excellent scenery, which must affect somewhat the fps, though probably less so these days than in the past, such are his clever techniques.

 

Anyway, let me know what further tests you would like.

Share this post


Link to post
Share on other sites

As you suggested, I've deleted the [monitor] section and tried several scenarios. Setting Commercial AI to 100% is OK. Adding in GA AI is OK, as it is if I add in the ships and the freeway traffic. It's when I add in airport traffic at full density that it 'fails'  -  as indicated by the failure of ADEX to show the correct lat/long.  So it seems to be a fairly critical amount of traffic that causes the problem. I'll go back in a bit and try the airport traffic on its own

 

The airport traffic is filtered out in FSUIPC, and is only read (to see if it needs to delete duplicates for AES/GSX) if the parameter "DeleteVehiclesForAES" is set to "No", the ground vehicles shouldn't matter. Perhaps you could check?

 

Yes, it would be excellent if FSX (or FSUIPC) could ignore and not try to initialise traffic from beyond a certain range

 

FSX only generates traffic within its "reality bubble", which I think is 80nm around the user aircraft. FSUIPC ignores all but the nearest 96 on ground and 96 in the air -- that's a limitation of the offset tables it maintains. However, in order to determine which of the aircraft are the nearest it has to read all of them, and compute their distance according to yours and their latitude/longitude.

 

I could limit the range for the data being supplied by SimConnect to less than the "reality bubble" size, but one of the main uses of the tables is for TCAS, and that can be up to 80 nm I think. I'll check further on that.  (My range is 200 km, based on the bubble size).

 

It would be nice if I could restrict the range for ground aircraft separately, but it isn't an identifiable group -- of course they change status in any case. As it is I am checking aircraft parked at airports up to 80 nm away just to see if they are withing the nearest 96.

 

I use a lot of Gary Summons' excellent scenery, which must affect somewhat the fps, though probably less so these days than in the past, such are his clever techniques.

 

I have them all, and what makes them heavy on performance is mostly AI traffic.  The latest verston of EGLL Extreme, with the Terminal 2 open, was a HUGE performance killer on my PC and I had to turn the traffic down quite a bit. It's just the sheer number of gates -- more gates, more aircraft.

 

Pete

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.