papps

Hello Pete, I have been reviewing the problems I am having. I know you have removed the issue with NewDeleteVehiclesforAES in the code for AI limiting, but I feel this parameter must be involved in some way. My reasoning is based on my experiences as follows: 1. Version 4.966c worked in Steam as expected, where AES is not available. 2. In Acceleration, V4.966c worked as expected when NewDeleteVehiclesforAES=No. However, when NewDeleteVehiclesforAES=Yes, AI is not culled. 3. Version 4.966j works identically in both Steam and Acceleration. It culls AI at the start according to the ini trafficlimit parameter, but does not continue to cull AI if targetFPS is 0 or the actual FPS is below the target. 4. The "Max AI traffic was 251 aircraft (Deleted 375)" type message does not appear in the log for V4.966j; but in 4.966c it does in Steam and Acceleration when NewDeleteVehiclesforAES=No but not when NewDeleteVehiclesforAES=Yes. I considered your comment about corruption of the flag for culling, but this seems unlikely, as I have tested the two versions in steam and Acceleration and the results are always the same regardless of aircraft or location. I have removed all modules from the dll.xml and exe.xml (except FSUIPC and Traffic toolbox) and all sceneries other than the default sceneries and my traffic files and tested with the MS B737 and I receive identical results. In writing this,I realise I need to test with only the MS Traffic. I suppose it may be possible that a traffic file, plan, or aircraft may stall the culling process. I will try that this evening unless you feel it is a waste of time. Update. I have just tested V4.966j with default scenery, traffic and B737. As the traffic levels are lower, I set Traffic limit to 20 and left TargetFPS at 0. On loading, Traffic was 20 as reported by Traffic toolbox and 0x025c. After running for 5 minutes or so, TrafficToolbox showed 27 and 0x025c reported 15. Regards, Phil

Hello Pete, Thanks for the comprehensive reply. Yes, I understand, but as you will have seen, my frame rate is very low, and I have the target set to 0 in FSUIPC.ini. I attach the ini as requested. So yes, there is a difference here. I had left the values at the default (except for TrafficLimit) as I did not want to confuse matters more. Yes, I have seen this previously. That seems logical, but I do not understand why! I attach the ini as requested. Thanks, Phil FSUIPC-ini.zip

Hello Pete, I thought I'd try the 'j' version in Steam edition; I'm not sure if it should work. However, it exhibits identical issues to FSX Acceleration. That is, it limits AI at the start of the session, but not afterwards - AI increases in the same way. The 'c' version in Steam limits AI to the value set by trafficlimit throughout the session. I am not sure if this is useful information or not, but I include it in case. Back to TrafficLook, I had an older version, V1.551, that I had downloaded previously but don't seem to have run. This version runs fine on my system. For the record, I am running Windows 7 Professional 64bit SP1. Regards, Phil

Hello Pete, This time I have removed all my Lua, added lines to the ini that you requested. The TrafficLimit=150 option remains in the ini.. I started FSX and loaded the same scenario as the previous tests. After the flight loaded, I started Traffic Toolbox, this showed 151 aircraft, as expected with the TrafficLimit at 150. However, over the next short while, this figure steadily increased to 169 never decreasing. I have stopped the flight and attach the log file for you. The AI I am using is a mixture of JF Traffic360 and some plans, including BA, from AIG compiled with AIFP3. Thank you for the time you are spending on this. Phil FSUIPC-Log.zip

I tried, and it seems I can attach a file to another post, so here is the FSUIPC log file from me previous test. Regards, Phil FSUIPC4-1.log

Hello Pete, I appreciate your help with this. Yes,AES is active as I am testing this at Heathrow, where I have a lot of traffic; however, as the engines are running in this scenario, the AES fleet has not appeared. I can test at a default airport where AES is not active if that helps. Sorry, I did not make this clear. In my tests, that I have repeated this morning to get accurate figures, Traffic toolbox is showing around 330 aircraft, fluctuating between 329 and 338. Offset 0x025c is reporting between 316 and 327. I have a Lua routine that displays this figure when the offset changes, but this is sometimes a few seconds behind the change shown in traffic toolbox. When I set Max AI (it is zero in the ini) using offset 0x86e2, the traffic does not reduce to the 150 requested. I cannot attach a file as it tells me I can only upload 10.24kb but the file is only 7k; does it include my previous upload? I have also tested this by setting TrafficLimit=150 in the ini file. When loading, and after a few minutes, there are in excess of 330 aircraft as shown in traffic toolbox. As for trafficlook, I have tried this with AV off and there is no difference. I agree, there must be something stopping it running. I will investigate this further. I hope this information is of use. If you need anything more, I will try and provide it. Thanks again, Phil.

Hello Pete, I have tried the new version, but unfortunately it hasn't made much difference. The Traffic count is now updated, but is around 7 below that shown in Traffic Toolbox. When the limiter is applied, I used 150, the count of AI is unchanged in both 0x025c and Traffic Toolbox. I can still not get Trafficlook to work. There was no ini so I created it but still no UI. Thanks, Phil

Thank you. I look forward to the next update. Actually, I did and that was why I asked the question. When I run TrafficLook, the program executes, but there is no UI. In task manager, I can see the process, but it does not appear in the applications list. I have just tried again to make sure I was not going mad, and the same happens. Usually I try most things before I ask. Oh well! Thanks again. Phil.

Hello Pete, Thank you for your response. Previously I had been using AirTrafficManager to manage AI Traffic, and this still appears to work. My steam version is almost identical to my acceleration version and I checked the two ini files. One difference is that I use AES in Acceleration and indeed had NewDeleteVehiclesForAES=Yes in the in file for Acceleration. In Steam this was NewDeleteVehiclesForAES=No. When I changed NewDeleteVehiclesForAES to No, Acceleration works in the same way as Steam and the values are correct. It is this setting that is causing my problem. I attach the FSUIPC log file as requested, but I do not know how to run TrafficLook. If this is still needed, can you point me to the instructions for this. Thank you. FSUIPC4.log

Hello, I have recently tried using the Traffic limiter within FSUIPC in FSX. FSUIPC is the latest version currently in your downloads section, V4.966c. In FSX Acceleration, I am having two issues, probably related. Firstly, When I use a Lua routine to read the total number of aircraft from offset 0x025c, I believe it reads the number of aircraft at that moment correctly. However, this is not updated; subsequent reads show the same value, and event.offset never picks up a change. This is the same whether the traffic limiter is on or off. When I start FSX at EGLL with Traffic limiter off, TrafficLimit=0 in the ini file, offset 0x025c shows 331 aircraft and this remains static whereas Traffic Toolbox fromthe SDK shows 336 and this number fluctuates by a couple, presumably as aircraft enter and leave the reality bubble. If I turn on the traffic limiter by setting it to 150 using offset 0x86e0, the figures reduce. Offset 0x025c shows 150 and this remains static but Traffic Toolbox shows 229 and again this fluctuates slightly. With FSX Steam Edition, the limiter works as I expect. Using the same airport, the same aircraft, the same AI settings and the same traffic files,with the limiter off in the ini file; offset 0x025c shows around 330 and fluctuates, always one lower than Traffic toolbox. Using the same Lua routines, I set traffic limiter to 150, offset 0x025c shows 150 and Traffic toolbox shows 151. As I say, FSX SE works as I expect, whereas Acceleration does not show an accurate number of aircraft, and although it appears to delete some AI aircraft, it does not reduce the number to the selected figure, nor does it maintain a constant number of AI aircraft. I have seen a report similar to this, but it was reported fixed, I believe in V4.959n. Am i suffering from a similar problem, am I doing something wrong, or is it expected SE will work differently to Acceleration? Thank you for your help.