Pete Dowson

You seem to display a listing actions for 1, 2 and 3, but then wait for keypresses 0, 1 and 2. Have you used FSUIPC's Key/Button logging to see what it thinks is happening to your keypress. 0, 1 and 2 may be taken previously. I've tested your program but with ipc.lineDisplay("callNew1") etc, in place of the ipc.runlua lines, and it works fine. I've also used it with runlua just to be sure it all will work. Enable Button/key logging, and maybe also Event logging. The log will show what the Key presses are doing, and Lua programs starting. Pete

The FSUIPC INI file is generated by FSUIPC, and records all of your settings. if a default INI, with none of your settings at all, causes problems you certainly have something very strange going on -- because with no settings -- no assignments, no calibrations, no options selected -- FSUIPC is really only there as a service to other programs (as if unregistered), and plug-ins (if registered). There's really nothing that can "stop" FSUIPC's dialog opening if selected, so that is really strange. It sounds like a Simconnect problem, as the optios part is totally at Simconnect's mercy. Have you thought of reinnstalling the Sim? Your log file isn't closed. Do you wait till the sim is completely closed before grabbing it? The log is missing all of the useful information at the end. The Sim isn't fully closed immediately its window disappears. Apart from that, the log shows no attempt to enter the options and shows all is well except for the missing stuff at the end. Pete

In the next release there will be three new controls: Traffic freeze toggle Traffic freeze on Traffic freeze off The way it is done is by sending Slew toggle controls to each relevant aircraft (i.e. those in Taxi out state). There's no "on" and "off" slew controls, so FSUIPC keeps a note of what state you've set. If you load a new flight then the aircraft will all load in unslewed state in any case, so it is reasonably safe, it is just that you may occasionally need to use the toggle control twice. Best to use the on or off for clarity. Also, in my tests, it can sometimes happen that the control doesn't actually get to an aircraft. There may be so many and Simconnect so busy, that is misses some in the queue. However, this seems to be a rare occurrence, and for me it only happened when i sped the sim up to 4x so that the traffic got a move on! 😉 Pete

The states in which AI can be are: "init", // 0 "sleep", // 1 "flt plan", // 2 "clearance", // 3 "push back 1", // 4 "push back 2", // 5 "startup", // 6 "pre taxi out", // 7 "taxi out", // 8 "takeoff 1", // 9 "takeoff 2", // 10 "T&G depart", // 11 "enroute", // 12 "pattern", // 13 "landing", // 14 "rollout", // 15 "go around", // 16 "taxi in", // 17 "shutdown", // 18 The aircraft are actually off the ground in part of TakeOff-2, and 11 (I think), 12, 13 and 16 are flying. As you see, there's no actual "hold" state I can detect. I can certainly allow those in "TakeOff-1" and "TakeOff-2" states to continue and only stop the others. I think, in fact, that you'd want those on the ground in states 14-18 to continue also. and those in states 0-3 are still parked. So you'd only want to freeze those in states 4-8 at most, and maybe only 8 (taxi). Of course take-off1" might be just before thay enter the runway and therefore need freezing too. I'm not really sure. I'll watch in TrafficLook to see. If the addition is an assignable control, like the Zapper, then more sophisticated actions could be programmed via Lua plug-ins -- like automatically operating the freeze when you lower the gear, perhaps, and releasing them when you are on the ground. But i think I would prefer to leave that level of sophistication to folks' imaginations and ingenuity. Pete [LATER] Watching the traffic with TrafficLook running so I can see the States, it appears that they Hold in "taxi-out" state. Once in "TakeOff-1" mode they move onto the runway. "TakeOff-2" mode is actually accelerating down the runway. So, I think the freeze should only operate on "Taxi-Out" state. Pete

Well, a control would be by button assignment. I certainly wouldn't consider checking other variables. And surely it is only the one's which have take-off clearance which will encroach upon the runway? It would be up to you to press a button of key, then again after. Pete

First make sure all options are unchecked, and that you haven't calibrated the throttel on section 1. Then go to P3D and make sure you have disabled controllers there. That most definitely indicates that you have the axes assigned in P3d. go into P3D options and DISABLE the controllers. Don't worry about unassigning them, just disable them. (Last section there). Pete

You could do this with an add-on program, reading the traffic details and sending commands using the AI aircraft IDs. It would make a good utility program -- though aren't such actions already performed by existing programs, Traffic Manager or similar? When you say "slew" do you mean moving AI traffic back or forth? Quite a complex job if you want them to stay on the taxiways. I don't really think this is a suitable facility for FSUIPC -- it is definitely an add-on utility job. Probably best directly interacting via SimConnect. If you only mean using slew mode on all ground aircraft to freeze them in place, then that would be a relatively easy job, but what if they've already encroached upon your runway? I'm not enhancing FSUIPC4 any more, so if I did do anything like that it would only be in FSUIPC5 (i.e. for P3D4). Pete

Not initially, as we don't know hat to look for. The default logging will show whether FSUIPC is running okay. Be sure to close the session, after observing your problems of course, before getting the log -- there's more useful information at the end. How do you "generate a new FSUIPC INI"? That file is created for you and maintained via the FSUIPC Settings. There's nothing that can be set in the INI which will stop FSUIPC settings opening. The FSUIPC install is correct if the FSUIPC entry appears in the menu. There's then nothing else to it except the DLL itself in the Modules folder. I've really no idea how you "regenerated" the INI file. You can edit it or delete it, but I don't understand what you are doing. Pete

Yes, that's one way to run a plug-in. Correct. None of the assignable Lua controls other than Lua <name> and LuaDebug <name> actually load and run a plug-in. they are all designed to talk to or affect the way a running plug-in acts. There's no point in toggling a flag from one state to another n a plug-in which has just been loaded -- it might as well simply assume such a toggle in the first place. Yes. Scripts intended to remain running can be loaded via [Auto] sections, or by macro, or by other Lua plug-ins, or, still, by assignment to a Lua <name> control. The difference between a plug-in designed to stay running and one which just does something and terminates is the presence of event functions which tell it to wait for something to happen -- like a flag being toggled, or an offset changing, and so on. If you want to assign a key or button to a plug-in which just does something and exits, but you want it to do somethnig different each time, use the parameter value when assigning to Lua <name>. That's passed to the plug-in as the variable "ipcPARAM". Pete

You've attached a lot of files, all of them unfortuately not relevant. The main one needed in the FSUIPC4.LOG file. I'm using GSX with no problems, but then I am using P3D4 now. I see you are still on one of the original FSX versions. Hmm. Sorry. Definitely a matter for their support forum then! Pete

Thanks. I'll try it here in the morning. Pete

If it is that big then it isn't the same corruption I've seen so far. Anyway, it should ZIP up very small. Try a process of elimination on your add-ons. something is causing the problems. Pete

Normally after deleting it a new one is created by P3D (though possibly only when closed?). Instead of deleting it you could try copying it yourself from the Weather folder in P3D. I think that's all P3D does in any case. But if one of your add-ons then corrupts it almost immediately on starting P3d, it will obviosly give some problem. But it sounds like that must happen later. It would be nice to determine what add-on is doing it as it certainly isn't P3D itself. I've been trying to get L-M to perform some sort of checks on this file before using it blindly. I don't know which add-on is corrupting it, but the bad ones I've seen so far are pretty much the same -- just around 200-300 bytes instead of the required kilobytes. L-M say they cannot reproduce any problems, but I think that this is only because the symptoms are so varied. Usually, for me, such a file just crashes P3D. But others have had things like add-on menus not appearing and other strange issues. I believe bits of memory are somehow being corrupted, but this varies system to system. Do you have Dropbox or something similar, where you could put the bad wxstationlist.bin file, and send me a link. You can't email it and I don't think this forum will allow it as an attachment. Link to petedowson@btconnect.com. Then I'll see what it does here, and forward it to L-M as more evidence. Pete

That's a very strange symptom. It certainly doesn't happen here, on Win7 or Win10. There have been strange things reported in P3D4.3 which eventually narrow down to actual memory corruptin due to a bad "wxstationlist.bin" file. You could try deleting that before starting P3D4. I'm actually planning to automatically delete that file at the end of a session. P3D will make a new one in any case. (You'll find it in the AppData folder, next to the P3d CFG file). Otherwise I really cannot think what could be doing it. SimConnect is not "installed" by FSUIPC. FSUIPC interfaces directly to the SimConnect interface built into P3D itself. Programs only install and use separate SimConnect DLLs when they are designed to interface to legacy versions (any of three FSX versions), or need to run on a networked PC. Pete

How do you pan in different directions with just mose wheel up / down? Does the click switch directions with Ezdok? If you are using a mouse, why not just use FSUIPC's MouseLook? Holding the wheel down (clicked) and moving the mouse itself left/right/forward/back? Pete

Hmm. Sorry, then ... maybe that new program ("ChasePlane" ?) which gets good reviews will help. Otherwise you can try Lua but I don't think it will be as smooth as a proper PAN_VIEW assignment. Maybe there's another program which turns mouse operations into assignable joystick axis inputs? Pete

Okay. the order is correct for FSUIPC5, but i'm worried about the non-ASCII character in your name. I'm not sure how that works in my Installer. I'll try here ... [LATER] I've run the Installer, and registered with the exact details from your purchase, and it works fine. It generates the FSUIPC5.KEY file which contains the exact details listed for your purchase. So, either you are making a mistake or, for some reason, the characters you are entering are using some different encoding from your keyboard. I don't have the non-ASCII characters and don't know how to enter them, so I simple copied and pasted each field separately into the installer's fields. I respectfully suggest, again, that you do the same! I also note that when you started this thread (whilst I was away) you had a problem with the Registered version, and that you only destroyed your registration by deleting everything. So if you successfully registered once, what are you doing differently now? The installer hasn't changed. Pete

So how would you be able to pan properly? You could only go up and down not side to side. Or does Ezdok change from one to the other on a click? And if you have Ezdok with the facility, why need another way? Pete

I'm afraid you have not calibrated properly at all: Aileron=256,256,256,256 Elevator=384,384,384,384 Rudder=0,0,0,0 LeftBrake=-16380,16383 RightBrake=16127,16127 The only one there with a chance of success in the Left Brake. None of the others have any range of values between any two parts. Also you have 2 throttles, 2 Prop Pitch, and 2 Mixture controls assigned "direct to fSUIPC calibration", but have not attempted to calibrate them. Please refer to the Calibration chapter in the user guide and follow the numbered steps for each axis in turn. Pete Pete

I don't know if you bought the right one. I can't search for "anbrod1" in the data base. I need the nmae and order number. The SAME name and the SAME email as in the Registration? Did you cut and paste as I suggested? Also, it is easy in the code to mistake 1's and I's and 2's and Z's. COPY AND PASTE. Pete

How would you pan using a click? Do you mean a mouse wheel moving not only round but also rocking left and right? There are no easy assignment facilities in FSUIPC for using the mouse wheel for panning. But you could do it using a Lua plug-in --there are events for receiving and even trapping mouse wheel movements both horizontal and forward/back. But interpreting these to do directional panning would probably not be as smooth as using a normal POV assigned to PAN_VIEW, which does it all. Does Prosim offer such a facility? Pete

Sorry, what percent in a flightplan? i don't understand? Does the slider not limit the AI? I've never used anything but add-on traffic providers -- MyTraffic6, UT2, UTlive, Traffic Global. Sometimes more than one of those together. UT2 andUTLive, because they inject the traffic, not using BGLs, have their own "slider". Pete

You are most certainly not entering the registration details correctly. ALL THREE PARTS MUST BE CORRECT!!! Also check that you are entering and FSUIPC5 key, notone for FSUIPC4 or FSUIPC3. Pete

Last time these symptoms were reported it turned out to be a corrupt wxstationlist.bin file., being read by P3D. I've asked L-M to check this file before using it, but they want an example of one which causes the problem first. So could you find it please (in your Appdata P3D folder, next to the P3D CFG file), rename it as a .txt file (precaution to get it sent ok), then ZIP it up and send it to me at petedowson@btconnect.com. THEN delete it. P3d will make a new one in any case. This happens more recently than before -- I think there are some add-ons making temporary (oceanic?) weather stations and somehow leave the file in a bad state. I'm even considering auto-deleting the file in FSUIPC, but that would have to be during session closure as it would be needed for the current session. Pete

There's no way FSUIPC is hacking into Sim code to stop an aircraft being 2spawned". It simply receives information about aircraft as they are created, moved, deleted, whatever, THEN it uses the parameters you set to determine which ones, if any, should be dleeted. If you notice such stutters, then you need to adjust settings. I would not advise having traffic sliders up to 100% with a low limit value like 50 and a traffic program which creates hundreds of aircraft when approaching a busy airport. It's all a matter of getting a balance. I get some small stuffers when approaching a big airport, but I found they are the same with no traffic allowed at all (not by my limiter). They are actually due to the "spawning" of the airport buildings and so on. Pete