Pete Dowson

Well, you could enable event logging in FSUIPC's Logging facilities, and see if they are logged, but then again, I think they are only logged when SimConnect accepts them and signals this to FSUIPC. Pete

These are the assignments you made for the various axis ranges: 4=VS,BR,13000,15000,66851,0 -{ TO SIM: AXIS_SLEW_ALT_SETEntering=VIEW_CAMERA_SELECT_1 }- 5=VS,BR,10000,12000,65636,0 -{ Entering=COM_RADIO_WHOLE_DEC }- 6=VS,BR,4500,6500,65603,0 -{ Entering=FLAPS_DOWN }- 7=VS,BR,0,3000,1025,0 -{ Entering=heading bug inc fast }- 8=VS,BR,-6000,-2000,66855,0 -{ Entering=VIEW_CAMERA_SELECT_5 }- 9=VS,BR,-9500,-7000,66856,0 -{ Entering=VIEW_CAMERA_SELECT_6 }- 10=VS,BR,-14000,-10500,66857,0 -{ Entering=VIEW_CAMERA_SELECT_7 }- Now, of those, I'm pretty sure that Asobo have not yet linked up any of the View or Camera events. At present i think you are forced to making keypress assignments instead. You can still do that with your ranges -- the FSUIPC control for Key press and Release is 1070, and its parameter is the Keycode + 256*Shift code. The Advanced User's guide gives you these value. Use the keypresses already assigned in MSFS, or assign your own if preferred. I would have thought that FLAPS DOWN would work, but maybe check it by a separate assignment. Same goes really for the other two. You also shouldn't have any axis assignment as well, so delete this line: 3=VS,256,F,65870,0,0,0 -{ TO SIM: AXIS_SLEW_ALT_SET }- It is that which results in that confusing added comment on the first defined range. Pete

Just ZIP log files -- they ZIP up really well. You did attach a log file earlier. If you keep the actions you need to reproduce the problem just once (i.e. one attempt, no more the log should still be fairly small in any case. Pete

When you calibrate in FSUIPC the way the controls work is different. That's why I suggesting Resetting your calibration -- i.e pressing the Reset button on the calibration tab, so they are no longer calibrated! And making sure you assigned to the Axis ... controls, not direct to FSUIPC. Pete

So that was the only change? Since the only change is the updated aircraft, either that went badly wrong, or it is faulty. Don't they have a website for support? One remote possibility is that they changed to methods like those used by some PMDG and Aerosoft aircraft -- doing their own interception of the throttle axes so that calibrated values in FSUIPC are bypassing that and being ignored. However, that is a very big change if so. Still really a question for their support, but you could try resetting the calibration in FSUIPC and assigning only to the Axis Throttle Set controls. Pete

Ah, I had forgotten that! Old age is having such effects these days. 😞 I have just checked the source, and that option is still implemented! Sorry, I've no idea what other corrections and improvements made over these last three years would be affecting ProATC/X in a bad way. If you do find anything when examining the data do please let me know. Pete

Well enough, thank you, but feeling my age (78 this year) -- aching knees, painful back and hips. Slowly becoming a couch potato, except I insisted on getting another dog when the last one died, to force me to get exercise and fresh air every day! 😉 Really missing holidays. We had been going on about 6 trips (steam trains around the world) till this pandemic ruined everything. Can't wait for them to start again! Regards Pete

Yes, I saw that thread. Pete

I assume you needed the PFChid module also to link the PFC Cirrus to FSUIPC and thence to FS2004? Support in MSFS is similar, but it is now a 64-bit simulator, and FSUIPC7 is an external program instead of being an internal module. Otherwise things are similar. You need FSUIPC7 installed, and the latest PFChid64.DLL module as well, in the same folder as FSUIPC7.EXE. These parts are available on the website http://fsuipc.com/. Pete

As far as I am aware you cannot separate the Community folder from the main scenery and aircraft folder next to it. And I don't think you can move them. The best thing to do is bite the bullet, and uninstall MSFS completely, then re-install in a different folder or different disk drive. There will still be some stuff in the default locations, but most there will just be links to wherever you put it. Choosing a different location is easy enough if you bought it from the MS-Store, but, I am sorry, I don't know if the Steam one is the same. Maybe someone else can advise about that. Also ask on the AVSIM MSFS support forum instead of MS's own. Pete

No, it is the exact opposite! The unregistered version provides the programming interface for developers. That's how FSUIPC was when it started back in 1997 (for FS98). Later the USER facilities were added, and it is those which require registration. For the user FSUIPC is like a box of tools. You use just what you need. When starting to use it the only PDF you really need to refer to (and not sit down and read through if that is what it boggling your mind) is the User Guide. Best to just first read the introductory sections so you get an idea of what it is about. Then you merely refer to the sections relating to the part (the tool) you find you need to use or think might be helpful. The contents list will help there. All that should really have been done before you paid for it, as recommended on the sales websites. You get the programmers interface without paying, in case you have any of the many add-on applications which use it, and you get the documentation installed so you can review whether you really want it. This is all no different for FSUIPC7 than it was for any version since FS2004 days. As it says on the sales website, you download and check installation and review documentation before purchase. There are no refunds -- that is the same policy applied to all downloadable software products from SimMarket and most if not all other software suppliers. Pete

So I assume, then, that you think the command line option I offered 6 messages back, to revert the No Draw Hold type encodings, won't be of use. Never mind then. Pete

Topics aren't purged! I just clicked on your name and see many topics in which you contributed or started dating right back to 2010. Why don't you try the same? Pete

It probably doesn't recognise P3D5 as it dates well before its existence. I cannot support such an old version. Please just stop using it. If you want to check Taxiway data you would be far better off checking the source of the data put into T5, not T5 itself. That is all in the log, "Runways.txt" and is exactly in the order and types which the BGLs contain -- i.e. Taxipoints: numbered #0 upwards Parking places/gates: with optional names, and # reference numbers Taxipaths: with a # name number or runway number, each just linking two points by their number and giving the width Taxiways: derived by MakeRunways from the above, tying a series of # numbered taxipoints together in order. These will be fragmented where there are gaps (often "faults" detected by ADE, of which there are many in UK2000 EGLC -- see ADE fault finder). Taxinames: giving the actual names relating to the # name numbers. To see how this works, select a small airport. The larger ones have reams of data to wade through. Note that the data eventually placed into the files, like T5, is derived from the last entry for that airport (unless previous ones are not Deleted -- Deletions are listed in a separate entry beforehand. The files in Runways.txt are in the order which P3D processes them to make sure the later ones override the earlier ones. I really don't think I can help you any further than this. Pete

There's a 4.91 still downloadable. MakeRwys491.zip. But no 5 version before 5.10. The main change from 4.xx to 5.xx was 32- to 64-bit. Not sure where you think using anything like this will get you, though. If you have a three year old version and you are happy with it, why not stick with it? Pete

The 4.84 version is very old -- over 3 years in fact -- and a lot of corrections to it would have occurred in response to user reports. I don't have such old source to compare. To determine if the up to date one is correct I can only suggest you use ADE to examine the taxipath segments for your examples. I'm pretty sure the ProATC/X problem was because of the correction to the hold short points. I could consider a command line option to revert to the earlier classification, but that's as far as I can go, really. Pete

If third parties create aircraft which have their own systems, and don't provide any sort of facilities to do specific things, then there's not much you can do, really. Maybe there's some local panel variable (L:Var) you can write to, but that would need researching. You could ask on the PMDG support forum -- someone might have solved it. You can list current L:Vars and their values by assigning a keypress or button to the FSUIPC control "List Lvars". Look through those to see if there are any relating to the payloads. There's also a plug-in Lua file provided "Log L:Vars" which will log then as they change, so that might make it clearer. Pete

No version of FSUIPC has ever installed into an aircraft folder. It is not an aircraft! Far from it. It installs into the Modules folder of Flight Sim. I think you need to update your FS2004. No one uses version 9.0. You can still get the update to 9.1. Try for instance https://flyawaysimulation.com/downloads/files/2795/flight-simulator-2004-update-v91/ Note also that FSUIPC3 is well past its last support date. Pete

Good. Thanks. Pete

No. As far as FSUIPC (and, really, anything else) is concerned these are separate events. Pete

I suspect those aircraft have their own systems, separate to those inbuilt to P3D. In the Sim do the regular menus for these work with them? Pete

What do you mean "ROTOR BRAKE 70024"? What does ROTOR BRAKE have to do with it? The 70024 is a control or event number. Program this as a <custom control> in FSUIPC. Pete

Don't you think this would be better asked of ProSim? Since you are bypassing ProSim's system, assigning into the Sim, I'm not sure that can be helped. With more up to date versions ProSim say you must assign everything in ProSim, nothing in FSUIPC or P3D. I assume that would be best in their version 1 as well? I think that's what i did but version 1 was so long ago now that I forget. Don't forget that the Sim itself also handles ordinary light GA planes which can have mechanical links for the controls rather than hydraulic. Pete

Did you not try the DELAY option in the [Programs] section, as documented in the FSUIPC Advanced Users document? Pete

Well, if you are using the version posted here for testing a while ago, there is a difference, of course. Or did you disable the new action by setting the time to zero? Pete