Pete Dowson

Well, if it provides friction facilities, maybe the FSUIPC Lua friction functions could be implemented for P3D4. I don't know. John Dowson pointed this possibility out to me and maybe it could go on the list for future implementation. I assume the DLL has to be re-issued for each new version of P3D4, as for some of the things it mentions it must surely be hacking ito the P3D code. I've been avoiding making FSUIPC5 version dependent because P3D4 is such a live and ongoing project. It would be up to the user to provide the correct DLL for FSUIPC5 to detect and access. Pete

Strange. I've not touched that part of the code since it last worked ok! I've got a lot of catching up to do over the next few days. i'll try to get to it next week. Pete

The method and details don't change, no matter what 'rigs' you install upon. You are making an error -- all three parts must be correct and EXACTLY as per your registration. Copy and paste Name, Email and Key to be sure. Pete

All you can really do with two buttons is send the Flaps incr and Flaps decr controls, which move one detente up or down. This surely is sufficient. What more would you want to do, jump detentes? Why? You can't do that in a real aircraft. Pete

Yes, '\n' is two characters: '/' and 'n'. A new line is '\n'. You are using the wrong Escape character. All of the special characters use \,. For a single \ you need \\. Pete

That's just adding data to tables. It doesn't involve anything in the Sim itself. It was only ever used by on-line ATC systems (VATSIM etc) so that other users aso on-line can be seen with TCAS. Why not use SimConnect directly? Most all of the FSUIPC program interface facilities were implemented in FSX and P3D just so that older (FS9) programs could still be used. Small enhancements to expand those capabilities were added on request, but I am most reluctant to implement such larger facilities when such programs should by now all be using SimConnect. (BTW originally Microsoft expected SimConnect to completely take over from FSUIPC, which is why they invited me over to Seattle to discuss this -- at that time i also expected this). There are better ways. Mostly I use programs which handle all this. The main step is to get the plan loaded into the Sim. That is easy, and several do that already -- ProATC/X and Pilot2ATC will load the cleared plan into the Sim when you get clearance. And other programs like ActiveSky, and maybe EFB and FS-FlightControl, either do load such plans automatically on option, or such facilities have been requested and are pending. I think having the central source of the plan being the one operational in the Sim is by far the best solution. FSUIPC does provide the full pathname for that plan. For other purposes, you need to Plannig program to output the resulting plan in whatever formats you need, and placed in the correct folder for quick and easy loading. PFPX in my planner and it certainly provides such facilities. Pete

When uninstalling in the device manager did you confirm to remove drivers too? That means any Windows drivers, and also removes entried from the Registry. It is that last part which is important, as the Saitek installers seem to often screwe the registry entries up, and uninstalling just the Saitek software doesn't appear to correct them. Don't forget to re-boot after ininstalling. Re-connect the device just befor re-boothing or soon after. Pete

That's good. I'm glad it can be done, but there have been so many adverse reports in the past that I generally advise otherwise. Pete

Writing 0x00001400 to offset 3340 sets virtual buttons 64,18 AND 64,19 as "pressed". Why are you pressing two buttons? Not only that, you are "releasing" buttons 64,0-17 and 64,20-31. Writing 0x00002400 is similar but presses 64,18 and 64,20, and releases all the rest on virtual joystick number 64. Writing 0x00001400 to offset 29F0 says toggle button 0 on virtual joystick 20 (0x14), which doesn't exist --- as it says, virtual joysticks are from 64 to 72. Similarly writing 0x00002400 there toggles button 0 on vurtual joystick 36 (0x24), which of course also doesn't exist. Please do refer to the descriptions of these facilities. Pete

The cabin pressurisation readings are as supplied by SimConnect -- FSUIPC doesn't do anything but place the readings as supplied. I assume the "King Air B-200 da F1" is an add-on aircraft. Maybe it does its own cabin pressure simulation. if so, the built-in simulation wouldn't be working the same, and not related to your outlet valve settings or door states. I've checked those offsets with the default King Air and they work fine. Pete

I'm pretty sure they just stay in TaxiOut or TaxiIn state and press on blindly. Pete

I'm afraid I don't have it. The link was provided by Luis Damas, as it says. However you'll find the 2.0.2 package eaily with Google or another search app. For example, try http://luaforge.net/projects/luasocket/ Pete

Sorry, I don't understand. What happens when you run TrafficLook? No screen display at all? Or a good traffic display with no menu bar, or what? The menu contains just "File" and "Help", with the Help only showing an "About" option. The File item has "Print", "Ground Traffic Only" , "Airborne Traffic Only", "Refresh", "autorefresh" and "Exit" options. I'm off-line now for about 10 days, though I may be able to do some work next Monday or Tuesday. I can try to help, but you should know, that the TrafficLook and WeatherSet utilities are only demos of specific aspects of FSUIPC offset access, and are not really supported and certainly not maintained. They use standard Windows facilities and have not been changed in any real way for years. The menu is defined in the resoource data of the program, so If it isn't appearing, something must be wrong with the EXE, or with the standard libraries used in Windows. Pete

I'm surprised you managed to get revere working on an axis in the first place. I'm always being told that the PMDG Boeings need normal Axis controls without calibration in FSUIPC (to avoid conflicts with the PMDG code reading directly). Reverse is normally done by programming a button to repeatedly send throttle reducing controls (normally F2 or its control equivalent), with a throttle cut (F1) being sent on button release to bring it back to idle. With Saitek throttles there's a suitable button pressed when you pull the levers right back. Pete

Sorry, I don't understand what that means. Do you mean you have calibrated both throttle axes with a reverse zone, in FSUIPC Calibration? What buttons? You haven't mentioned any buttons. Are these something else you've assgned, and if so, to what control? That sounds like you have multple assignments. Are you assigning in your Sim (FS9, FSX, P3D1-3, or P3D4?)or in FSUIPC? If the latter you must disable controllers in the Sim. Sorry, but you haven't really supplied any information. Pete

TrafficLook really needs no user guide. What's to document? The only menu is self-explanatory, surely? The "states" are as reported by SimConnect. Exactly what they mean is reasonably obvious when you watch. "Clearance", TaxiOut", TakeOff1, TakeOff2 (I think the difference between those two is permission to line up, and rolling, but I've only deduced that from watching. Crossing runways doesn't have a state. that's just taxiing as far as they are converned. Why do you want to access the INI? it only saves changes you make, like Window positions for Airborne and Ground, and column positions if you move them or resize them. It isn't intended to be user-accessed. Pete

FSUIPC is not doing anything unless it is told to, and it most certainly cannot make Windows "act strangely", whatever that means. Are you assigning everything in FSUIPC? If so, do you have multiple joystick control connections? Unless you use Joy Letters to identify them (see chapter in User Guide), they can easily get mixed up on Windows upgrades, hardware changes and disconnections/reconnections. If the "settings" you are talking about are P3D ones, then FSUIPC cannot be responsible as it doesn't touch any of those. If you want more help here I think you need to be much more specific about "settings" and "strangely", as these are rather meaningless without any detail. Crashes of Windows can result in all sorts of corruptions of essential control files. One easy thing to try is to delete your Prepar3D CFG file and let P3D build another. You'd need to set up again but t isn't too much of a chore. Otherwise your problems are more likely to be some corruption in P3D. FSUIPC is 100% reliant on SimConnect and the PDK interfaces. If those are corrupted then the results are unpredictable. without FSUIPC or other such add-ins being used, corruptions in those areas probably wouldn't be so noticeable. In the end an uninstall and re-install of P3D itself might be the only way. Best thing to do in future is to make regular system backups so you can restore to the most recent fully working system after a serious system crash. Pete

You can also use Mouse Macros. They are quite good generally in P3D4, though currently there's a difficulty in that the programming for them doesn't stay constant. L-M are fixing that. Pete

You posted in a reference subofrum, where it won't be answered. I've moved it to the Support forum, which is for requests for Support. I didn't think active Sky needed any such mapping, but you would be best asking in the Active Sky forum. Certainly, nothing to do with WideFS or FSUIPC needs such. Network access has become much more complex with recent Windows versions. I used to think Windows 7 was complex enough. Windows 10 is much more so. Luckily I have only one Win10 PC and managed somehow to sort out some sort of reasonable access from my other PCs, but don't ask me what contortions I went though. Sorry. I'm sure you'll find good help somewhere, but I don't think this is the place. Pete

But that INI file contains no defined profile called "DHC"! Have you sent an INI from another sim installation? The profile lists you have in that fie which mention DHC are just these: [Profile.DHC-8-400] 1=MJC8Q400_SAS 2=MJC8Q400_AUB and [Profile.Milviz DHC-3] 1=Milviz DHC3 Turbine 2 2=MilViz DHC3 Turbine Amphib 1 3=Milviz DHC3 Turbine 1 So, with this INI file, your DHC assignments in your "Milviz DHC-3.ini" file are not being used by any aircraft. Did you manually change the [Axes.DHC] and other such section names? That's not good. What you actually should have done is simply abbreviate one of the aircraft name entries in the main Profiles section. i.e. [Profile.Milviz DHC-3] 1=DHC The Profile name still stays "Milviz DHC-3" as you originally set. How did you misunderstand this so much? The "ShortAircraftname" facility means what it says, listing short parts of the aircraft name instead of the complete name that gets listed when you assign profiles automatically. It's nothing at all to do with Profile names. Pete

I have got it working okay here, with no hardware but some routines added to try to simulate what would be received. Please test it on the actual hardware and let me know: PFChid64_5127_TEST.zip Pete

You've not provided the correct file. it's controlled in the main FSUIPC INI file. Is an aircraft with the shortened name "DHC" listed in the [Profiles.DHC] section of your INI file? I think you are mixing up the Profile Name (which can be anything) and the list of aircraft assigned to that Profile. Pete

Are they known L:Vars? Do you know thay work? Test by assigning a keypress (temporarily perhaps) to that Lua file and use that first. If they are proven to work, maybe they are sent too early, after the aircraft is seen to load but before the graphics are full drawn. You could try putting a delay in at the start (ipc.sleep). How are they normally lowered? If that by a control? Pete

Well, obviously I don't need FSUIPC5.DLL -- that's my program and what you installed and want to use. The file needed, and which is probably in error, is the DLL.XML file -- this one (of which you already pasted in a small and corrupted section back on September 30th!): C:\Users\Kaptanking\AppData\Roaming\Lockheed Martin\Prepar3D v4\DLL.XML Find that, and ZIP that one instead! You could then also try deleting it then re-running FSUIPC Installer. That will work because FSUIPC will install a good version of DLL.XML. But I noticed you also have Active Sky installed, so that may then complain and need its DLL installing. Pete

Ah, you mean this bit: or preventing runway incursions on approach, with P3D4 and FSUIPC 5.14 or later (to be released this weekend), there are AI Traffic Freeze and Release controls added. These operate on all the AI aircraft in "Taxi out" mode. I'm supplying a Lua plug-in example with the release which freezes them when the gear is lowered on approach (or, for fixed gear aircraft, full flaps are engaged), and releases them on touch down. If you'd repro'd this in the first place i could have checked and replied properly. Obviously the AIFreezer.lua plug-in should have been included in the Example Lua Plugins ZIP with FSUIPC release 5.14, but checking now I see it missed out. Sorry about that. i'll make sure it is included in the next update. Meanehile, here it is: just save this to a file called AIFreezer.lua: -- NOTE: For use with FSUIPC 5 only -- This small plug in, which should be pre-loaded: for example, by adding -- [Auto] -- 1=Lua AIfreezer -- to your FSUIPC5.INI file. -- It freezes taxi-out AI traffic when you lower your gear, -- and releases them when you touch down. -- For aircraft with non-retractable gear, it checks the state of -- the Flaps instead, expecting full flaps for landing. (amend where -- noted for other flap settings). function GroundCheck(off, val) if ipc.val ~= 0 then ipc.control(1149) -- Freeze AI off if user landed ipc.log("AI taxiout traffic released") end end function GearCheck(off, val) if val >= 16383 and ipc.readUW(0x0366) == 0 then ipc.control(1150) -- Freeze AI on if gear just lowered (whilst in the air) ipc.log("AI taxiout traffic frozen") end end function FlapsCheck(off, val) -- See if gear is fixed first: if ipc.readUB(0x060C) == 0 then if val >= 16383 and ipc.readUW(0x0366) == 0 then ipc.control(1150) -- Freeze AI on if now full flaps set when in the air ipc.log("AI taxiout traffic frozen") end end end event.offset(0x0366, "UW", "GroundCheck") event.offset(0x0BE8, "UD", "GearCheck") event.offset(0x0BDC, "UD", "FlapsCheck") Pete