Jump to content
The simFlight Network Forums

Pete Dowson

  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Pete Dowson

  1. What's changed in RC? I thought it was unsupported and no longer developed? Certainly nothing's changed in the information it gets through FSUIPC to do that trick. I was always lazy in those days. I just used the FSUIPC Zapper and event land in spite of being told to go around. No doubt I would have lost my licence with RC, but I use P2A these days. AI control or even ATC interaction hasn't arrived for P2A yet, but, nevertheless, for the sort of short flights I indulge in it keeps me busy enough. In any case takeoff status for AI just isn't enough to prevent runway encroachment. That's why the Traffic Freeze controls were added to FSUIPC -- they freeze all AI ground traffic in "taxi out " mode, so you can catch them before they get to the runway. This is used by the supplied "AI Freezer.Lua" plug-in (look in your Example Lua Plugins). That freezes AI automatically when you do things on final approach, and releases them after you land. Read the details in the file. Pete
  2. Still, though, judging by the difference between those IN and OUT values, the braking amount is being substantially reduced at the start -- still negative when the axis reached +4800. IN=4800, OUT=-128 I saw that all the axes are assigned "direct" and calibrated in FSUIPC. I didn't think the PMDG Boeings liked that for some of the controls. Perhaps toe brakes is one of them (or two rather). Though I suppose really the main question is why is it okay until P3D is restarted. I see only one of the NGXu's is assigned in that Profile: 1=PMDG 737-800NGXu BW Ryanair EI-DAL I assume it is always thant one being reloaded? Pete
  3. Ouch! When I originally asked about " another joystick driver package", that would have included whatever that "configurator tool" is, and that I knew nothing about. If that is appearing in the P3D addons menu, then it IS running, and probably has settings which need to be removed to avoid conflicts. If you want to use FSUIPC for assignments and so on then really you'd be safer uninstalling that other joystick driver package, or certainly disable it. Pete
  4. Okay. That confirms controllers are off in P3D. Can you go ahead and try the same profile with a different aircraft now, please. Pete
  5. So far neither of the Logs have ben complete. You've been starting a "New Log", which means we don't get all the very important information at the start, logged by FSUIPC before your session begins fully. I suspect that will show that you still have controllers enabled in P3D. Look to see if you have a line like this: 21031 Controllers are set to OFF If not then controllers are still enabled in P3D. You have two strange meaningless lines in your Twin Piper profile for Button assignments: 6=U3,15,C0,0 -{Custom control: <0>}- 7=U3,14,C0,0 -{Custom control: <0>}- Delete those as, although they should do nothing, they are a little worrying. The aircraft itself seems to be doing some strange things without buttons being involved in any case: in the first log you provided there were many AP_PANEL_ALTITUDE_OFF controls occurring -- for no apparent reason -- whilst in the second log this had changed to TOGGLE_MASTER_BATTERY. Very strange that they occur and even stranger that they changed between sessions. I'm starting to suspect that the aircraft installation is corrupted, so, as well as double-checking that controllers are in fact disabled in P3D, please try your existing Twin Piper assignments on a different (default) P3D aircraft. You can temporarily add any other to the Twin Piper profile (you can always delete its entry in the [Profile.Twin Piper] section after the test. It doesn't matter if it has the wrong number of engines -- it isn't a flight test but just a test to see what events are generated when you operate those switches. Pete
  6. As the documentation does explain, the Ignore facility in the assignment tab is merely to ignore it whilst assigning, in case an axis is constantly jittering and so supplanting the one you want before you can get to assign it. To "ignore" an axis for a specific aircraft or profile you simply delete its assignment. If it isn't actually assigned it is ignored when you are back in the cockpit. This is what profiles are for. Pete
  7. It's the aircraft title, as selected in the sim, and and logged by FSUIPC in a line like this: 137796 Aircraft="ProsimB738 PBR 2020 - British Airways" So, it can contain any or none of the things you ask, depending on the supplier's whim and also on you should you have edited the "title=" line in the Aircraft.CFG file. Of course you can use any part of the name, as long as it does identify it or a group correctly and uniquely. Pete
  8. There's no "deactivation" process. The key will remain valid. All you need to do is make sure you enter the exactly correct Name and Email, as well as the key. You are making a mistake. Use cut and paste. Pete
  9. He's posted many messages since May last year. There's one in this thread from as recent;y as April 27th this year: Pete
  10. You'll need to show us your settings (the FSUIPC6.INI file), and an FSUIPC6.log with both Event and Button logging enabled and you briefly operating those switches. This sort of thing is nearly always due to multiple assignments, usually controllers not disabled in P3D, or another joystick driver package also installed. Pete
  11. Not an "offset" (offsets are places in memory where data is kept for reading or sometimes writing), but a "custom control". And it may need a non-zero parameter which you've omitted. The parameters are mostly mouse codes which are also listed in the SDK. How are you starting the Lua plug-in? It doesn't load and run itself. You either need to assign it to a button or keypress to load it, or, more usually, load it via an entry in an [Auto] section in the INI file -- presumably on for the Profile you are using for the NGXu, e.g [Auto.NGXu] 1=Lua TEST Try testing the control actually does what you want first by assigning to the button directly in FSUIPC assignments and maybe having a parameter. Pete
  12. You can certainly make it much more predictable that way. The fast/slow turning rotary facility may have to be quite extreme, timing-wise, to get a really usable result. It would be much much better written as a proper program and compiled rather than an interpreted script. The Lua script is useful in two ways: 1. An alternative way of reading buttons -- directly from a USB HID device 2. Another example along with the others of a Lua script. All of the examples are provided for folks to use as a basis of developing their own. Pete
  13. Yes, it appears so. I never noticed that before! The button number is "corrected" to be the same as that FSUIPC would recognise here: mask = logic.Shl(1, Rotaries[j]-1) I don't know how that oddity arose. It is easily corrected of course, by using mask = logic.Shl(1, Rotaries[j]) Odd that this example has survived at least five years with no one spotting that! Pete
  14. I surely didn't? You did actually imply that you were completely new to FSUIPC, only just having got it because of a third party recommendation. The starting point then is normally to browse the documentation, even before purchase just in case you decide it isn't for you. Sorry if you took such a recommendation as an insult! Dealing with controls devices is one of assignment, for buttons and axes, and calibration to get the axis controls responding to your satisfaction and to suit the aircraft. Assignment methods and calibration facilities are major parts of the documentation, and whether your devices are Honeycomb or not those are still relevant. I don't have any Honeycomb devices, but there have been lots of contributions here in the Forum. I made such a suggestion so you could get some more specific hints if you find you then need to. Pete
  15. The PFC driver is identical except to make it recognise that FSUIPC7 is an EXE instead of a DLL. It needed to know because it attaches to FSUIPC and uses functions exported by it. If there's some built-in text which hasn't been changed then that's because it is built in, and is the same on FSUIPC5, FSUIPC6 and FSUIPC7. I could generalise that if so (to "FSUIPC"). But if you are referring to something being logged then tthat seems odd. So, can you please be explicit. Where are you seeing this? If you are getting the documented panels for PFC then the PFC driver is running okay. Otherwise you'd see nothing. I would just like to know if the indication is an incorrect run-time indication or an unchanged built-in text. Pete
  16. The object of the Rotaries Lua is to convert the two "real" button presses (one for each direction) as seen from your rotary into four "virtual" button presses -- two for each direction, one fast, one slow. Then you assign to those. The list of buttons you set into "Rotaries = { ..." tell the script which pairs of real buttons it should look for, whilst the resulting virtual buttons will be adjacent pairs (slow and fast) on joystick 64 or 65 for each real button. So your list of two { 0, 1 } is correct for one rotary which operates real buttons 0 and 1. The rotaries example was really provided as an example of programming a rotary on any kind of HID device connected to USB. With a joystick recognised by FSUIPC you will get the real button presses being seen as well as the virtual buttons programmed in this plug-in. The IgnoreThese facility John mentioned will help when assigning to the correct virtual buttons, avoiding confusing when trying to do the assignments. For a single rotary you will get your real button 0 converted to virtual buttons 64,0 and 64,1. and similarly your real button 1 converted to virtual buttons 64,2 and 64,3. The code in the plug-in copes with up to 16 rotaries, so would then use up all 32 buttons both virtual joysticks 64 and 65. Then in order to get a reliable fast versus slow turning recognition you will probably need to adjust the timings, i.e. these two: FastTimeLimit = 60 -- Adjust to taste Pollrate = 20 -- same as 50 times per second With those figures, if button pulses are seen less often than 60 mSecs apart they are counted as "fast", otherwise they are "slow". Note that if you enable Lua logging, as you have done, things will be much slower in any case! There's no harm in adjusting the poll rate too, as you have done. Note also that it is normal to assign whatever it is you want to both "press" and "release", because the rotary presses on one click and releases on the next. That would list two rotaries, one pressing 0 one way 11 the other way, and the other pressing 1 one way and 10 the other. The buttons you assign will be "virtual" buttons, not the real ones, and there will be 4, two for each direction. The Lua script is converting your real ones according to the speed you turn the knob. Pete
  17. I'm afraid MSFS cannot properly deal with on-screen displays and windows from applications. We are hoping Asobo will rectify this in due course. Best to enable normal logging and, if you want the results in real time, enable the FSUIPC console log. That's what i do. Pete
  18. Didn't you install it and read at least some of the documentation first? Purchasing something without not whether you need it or how to use it is a little foolhardy. It does advise you to download it and install it first. Anyway, there are lots of lots of threads about using FSUIPC with Honeycomb devices, including I believe a very informational turorial or guide. Check the FAQ subforum, User Contributions, and other threads headed about thesee davises. Pete
  19. It's built into the FSUIPC user interface. There's a section about it in the User Guide -- "User profiles for all control settings". Please do refer to it. Pete
  20. These are instructions for separate use of the LorbySceneryExporter. MakeRwys does it all for you -- it runs the exporter automatically. So just follow the MakeRwys instructions, not the Lorby ones! It doesn't need "Powershell". Just run it "as administrator". To avoid forgetting this, I simply right-click on the MakeRwys EXE, selection Properties-Compatibility and check "run as administator" there. After that it will always be okay. No, leave as it is. "REQUIRED" just means it's essential or the sim won't load. I don't think any normal scenery needs it or wants it. Sorry, I'm not checking your scenery. If it works, it's okay. That file is nothing to do with MakeRwys. As the log says, The CFG file being used is: "F:\P3D\MakeRwys_Scenery.cfg" I suggest you stop fussing and get on with flying. Your original problem was a corrupted P3D scenery.cfg file. You fixed that. Pete
  21. Just have two profiles, one for each controller set. You axis assignments and calibrations will depend on which profile you use. Pete
  22. Really this is a question for Lorby, as it is his program which cannot get over the problem with your corrupt Scenery.CFG file. You have these bad entries near the beginning of the file: [UK2000 Common Library] Active=FALSE [UK2000 Leeds Xtreme] Active=FALSE [UK2000 Newcastle Xtreme] Active=FALSE I've no idea how they got there, but as they are not [Area.nnn] sections they seem to stop the Lorby program in its tracks. Looking at the rest of the file it all seems to be default -- no add-on scenery there. So you might as well delete the Scenery.CFG file, then run P3D to let it generate a good one. I think Lorby's AddOnOrganizer program also has an optionto check and repair corrupt CFG files (but i'm not sure). Pete
  23. Okay, then it is definitely a long path name problem, and for some reason the method using \\?\ before the pathname proper isn't working. The last line before the crash is: ***** Processing MSFS official scenery (Asobo=-1) "\\?\D:\WpSystem\S-1-5-21-2263347563-3261326988-2989552293-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\Official\OneStore\fs-devmode\Edition\templates\AssetGroups\SimObjects\airplanes\singleprop-empty\SimObjects\Airplanes\MyCompany_AssetName\" which, without that \\?\ part, is precisely 260 characters - the old MAX_PATH length. Looking at me installation, the next path after that would have been: "\\?\D:\WpSystem\S-1-5-21-2263347563-3261326988-2989552293-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\Official\OneStore\fs-devmode\Edition\templates\AssetGroups\SimObjects\airplanes\singleprop-empty\SimObjects\Airplanes\MyCompany_AssetName\model\" which would be the longest name so far, and over the maxiumn path length that the Windows API normally handle. Oddly, though I also have MSFS installed with its data files on a different drive, my path for this is still via the C:\users folders, which appear to link to my E:\WpSystems folder where the data actually resides, thus: "\\?\C:\Users\Peter\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-devmode\Edition\templates\AssetGroups\SimObjects\airplanes\singleprop-empty\SimObjects\Airplanes\MyCompany_AssetName\texture\" So, the longest path I'm getting is 244 (to which will be added the individual BGL file names, if the folder contains any scenery type files). I don't understand why your MSFS installation has succeeded in placing the data into your D:\WpSystems folder ywt not provided a link in the default :C\Users folder as mine has. What have you done differently, I wonder? The \\?\ prefix evidently doesn't work to allow the long pathnames (despite the MS documentation stating so). So I'm only left with two suggestions: 1. Make sure your Win10 is fully up to date. (Win 2004 or 20H2) 2. Try the registry edit. See https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/?utm_content=buffer5b5de&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer You might also ask in MSFS support forums why your installation doesn't work through links in C:\Users. Maybe there's a way of creating the links there. In fact, try this: In explorer go to C:\Users\Peter\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe Are the folders there? Can you click on them and see the folders and files within? If so, then the links are still working and there's an error in your UserCfg.opt file. This is a text file and, running an editor "as administrator" you can edit it. Find it here: C:\Users\Terry\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt The last line will be the one to change. It probably points to your D:WpSystems folder. Change it to: InstalledPackagesPath "C:\Users\Terry\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages" If this doesn't work I'm afraid I'm out of ideas. Pete
  24. The only version it states here and on SimMarket that is for FSX and P3D 3 — ie FSUIPC 4. But you should download it, install it, and at least read some of the documentation before purchase, as it states. Pete
  25. Well, yes -- a lot of complicated work, indeed. Okay. Hope you can move on with your project now. Pete
  • Create New...

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.