Jump to content
The simFlight Network Forums

Pete Dowson

  • Content Count

  • Joined

  • Last visited

  • Days Won


Pete Dowson last won the day on January 14

Pete Dowson had the most liked content!

Community Reputation

227 Excellent

About Pete Dowson

  • Rank
    Advanced Member
  • Birthday 08/27/1943

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Near Stoke-on-Trent, UK
  • Interests
    Flight Simming, Steam Railways, Travelling, Real / Craft Ale,, worldwide

Recent Profile Visitors

33,347 profile views
  1. Sorry, but is the cocumentation for the function not understandable? If it isn't maybe I should get it improved. As for techniques for using events I'm sure there are plenty of examples available, if not so many in the supplied ZIP, certain in the Forum (mostly in the User Contributions I think). Your questions were not really asking about how to use events, but more as if you hadn't seen the existence yet of event.control. Pete
  2. So, use event.control as I said! The one you "missed" as I pointed out in my earlier reply yesterday. That is exactly what it is for! Pete
  3. It isn't "event.control(65823, 1)"!!! Please do read the documentation! The second parameter it the name of the FUNCTION you want to be called when that event occurs! In that function you can checvk the parameter and act accordingly! Pete
  4. You missed the first line (see the earlier posts for which the later ones were edits): Windows Registry Editor Version 5.00
  5. Do the flaps work fully using the normal P3D default assignments for them? F5 FLAPS_UP F6 FLAPS_DECR F7 FLAPS_INCR F8 FLAPS_DOWN If not then check the A320 documentation or FSLabs support for how to operate them. If they only work using the mouse, then you might need to create mouse macros for them instead. To be sure your assignments are correct 9and theylook ok to me) you can always use FSUIPC's logging -- in this case, enable event logging. Pete
  6. Yes, it was an error in my cutting and pasting. I didn't send a correction becuase it got sorted by the time I looked again after realising the error. If those are the correct VIDs and PIDs, then those entries are the only ones I know. Well a Registry backup is always a good idea before trying any editing on it, so that's okay. Feel safe. Pete
  7. You missed "event.control". The functions in the event library are listed in alphabetical order. It's on page 24 in my copy. Is you Lua code sending those controls? If so, no need to detect them as you'll know. Pete
  8. I don't see much wrong with your settings, but you have the same settings for all aircraft, no profiles for different aircraft. You have throttles all set (twice in fact) for the separate throttles system: 7=2Z,256,F,66423,66426,0,0 -{ TO SIM: AXIS_THROTTLE2_SET, AXIS_THROTTLE3_SET }- 8=2R,256,F,66420,66429,0,0 -{ TO SIM: AXIS_THROTTLE1_SET, AXIS_THROTTLE4_SET }- 9=3X,256,F,65820,0,0,0 -{ TO SIM: THROTTLE1_SET }- 10=3Y,256,F,65821,0,0,0 -{ TO SIM: THROTTLE2_SET }- 11=3Z,256,F,65821,0,0,0 -{ TO SIM: THROTTLE2_SET }- First, it generally is not a good idea to have multiple assignments in this way unless you have a good null zone at the Idle position, and make sure the unused throttles are not moved. Second I think those two assignments to two throttle controls each could be done better by using the mapping provided for that purpose, but that would involve using profiles -- which I think is the better way in any case -- and in fact usually one of the main points of using FSUIPC. There's really nothing inyour axis assignments (at least) which could not be done in the P3D assignments. You can still calibrate in FSUIPC when using those. Finally, to your problem more specifically, I suspect that the A2A cub needs you to assign to the generic throttle (AXIS THROTTLE SET) -- the one calibrated on the first calibration page in FSUIPC's tab. Either that, or just not calibrating in FSUIPC. This is because one of the main advantages in FSUIPC of assigning to the 4 separate throttles is that it sends these on to the simulator as the old (FS98 dated) "THROTTLEN_SET" controls. It does this as those are the only ones providing a reverse range. But some aircraft are programmed in a way that this causes adverse effects. However, in the [JoystickCalibration] section you'll find this parameter: UseAxisControlsForNRZ=No If you have set "no reverse zone" for the throttles, which I assume you have, then setting this parameter to "Yes" instead of No might fix your current problem. I don't know -- it depends on how the A2A Cub has been programmed. If that's all you want to fix it is worth a try. Otherwise I suggest you set up your first profile, one for the Cub, and use the generic assignment for the throttle there. this is worth doing as I'm sure you'll find reasons for other profiles in the future. Pete
  9. Sounds like your settings in FSUIPC are all wrong. Without seeing your FSUIPC5.INI file we cannot help further. Just having FSUIPC installed and running won't change anything, so we need to check what you'd done. Have you any problems with other aircraft? Pete
  10. Are, they are numbers. R just stands for Reference, X is for heXadecimal, 9f260 is the offset in the Gauge file to the function to be executed (which is why mouse macros have to be re-made if you update the aircraft), 55cc is a check value, to make to sure memory at that point is correclty indicating the entry point to avoid a crash if you do update), and 22 is the mouse action code -- see the list in the Advanced User's guid. No, because there's a lot more to it than simply causing a jump to that part of the code. That uses "L:Vars", which isn't in any way the same as calling a function normally called by a mouse click. There are lots of things which may be indicated and controlled by L:Vars, and these often do overlap with the mouse click spots in a cockpit. Where they do the job you want they are more relaible than Mouse Macros and will normally be okay across updates. There's a spacial control you can assign in FSUIPC to list all the L:Vaars in a cockpit, and their current values, and, better, a Lua plug-in you can run to monitor changes in them and show these on screen ("Log lVars.lua"). BTW in P3D4, Lockheed Martin kindly made the "mouse macro" method officially supported with new facilities, and these thereby became more reliable and don't necessarilty change just with updated gauges. Before this the facility was most definitely an ugly hack. Pete
  11. There's no difference whatsoever in how FSUIPC treats the elevator assignments and calibrations compared to those for the other flight controls. It's all the same code, only the name of the control is different. So, there's something odd in the way the elevator is wired, or in your assignments and calibrations. Looking at your assignments, in the INI file, I see: 0=0X,309,D,1,0,0,0 -{ DIRECT: Aileron }- 1=0Y,1,D,2,0,0,0 -{ DIRECT: Elevator }- 9=3X,356,D,1,0,0,0 -{ DIRECT: Aileron }- 10=3Y,185,D,2,0,0,0 -{ DIRECT: Elevator }- Why those very odd Delta values? Those are the minimum changes before they are acted upon. With a 1 it means every single minute change will cause FSUIPC to attempt to honour it. This is normally only used for digital controls where the specific values are needed -- e.g. setting a heading with an axis. I strongly recommend you set them all back to 256, like the rest of the assignments. The log would only have been of interest had you enabled axis logging first and the done a elevator test. It would have been a huge log with a delta of 1 of course, so I would have asked you to change that first in any case. Pete
  12. Nearly my bedtime here. At my age, 76, I don't wait tll midnight. In my younger days i used to work on programming till 3 or 4 am. My most productive hours! Can't do that any more! Weird but winderful, eh! Now try not to change anything! As if! everyone likes changing things. Hopefully though not so disatrously next time! Oddly enough it's precisely those aircraft which don't much like how FSUIPC handles throttles. The other controls are okay, but most folks say you need to assign throttles to the normal Sim controls (Axis ThrottleN Set) and avoid calibration in FSUIPC. That's basically the same as assigning them in the Sim in any case. So the only advantage of doing so in FSUIPC is for the Profiles. The theory is that these aircraft do their own interception of the throtle inputs and that the feeding of controls in from FSUIPC conflicts with those values, making them behave erratically. this doesn't seem to happen with the other flight controls though. Pete
  13. John referred this to me, since it is for FSUIPC4 not FSUIPC5. I've sent you an email. Pete
  14. Sorry, i'm not fully understanding. What "string"? Can you give me an example? Macros don't trigger themselves. You assign them to buttons or key presses. There are event functions in Lua which can trap those. But surely if you want an offset changed instead of the mouse click to be emulated, why bother with the mouse macro in the first place? event.offset will trigger when an offset is changed. You can write to offsets using the ipc library functions. Please refer to the Lua library document. Controls are not Offsets and vice versa. Offsets provide values and can, like controls, trigger actions when changed. Some of those actions may actually use controls, internally to FSUIPC, but many don't. There are many offsets which provide or change values which have nothing to do with controls -- eg, all the Weather stuff. The EVENT logging is just that. It sees the event being triggered in the Sim, no matter whaere it came from (that isn't discernible in any case), and since it is only an event, a transient thing, what offset gets changed as a result is also unknown. One event might cause many offsets to change (eg throtle changes, flight control operation, etc). Even something seemingly simple like AP_MASTER will likely change many things . To determine the state of the aircraft, indeed the entire sim, you look at offsets, and the offset list is the reference for this. To operate the sim you use controls or events, or in some cases, writes to offsets. Pete
  15. What Wideclient issues? Did you put the ServerIPAddr and Protocol parameters into the INI as suggested originally? 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.