Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About vadriver

  • Rank
    Advanced Member
  • Birthday 05/11/1948

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. pete firstly, I continue to use your blended "direct" steering tiller / rudder assigning along with RBL successfully ... with the ngx on P3D4. the ambition for the discussed lua was initially to "mimic" this same behaviour using the separate P3D4 steering (tiller) & rudder set axis for reasons that have now become inappropriate. yes, FSX doesn't blend pedal nosewheel steer & pedal rudder control, but P3D4 i believe does almost well enough ..... well enough not to interfere with i'm thinking if you can "manage" excess pedal nosewheel steer at low (<20kt) groundspeed. one day (though unlikely soon) i might try the airbus addons which "recommend" using P3D4 assignments & but provide limited low speed pedal nosewheel deflections. for now thanks for your time in this. i'm busy "trialling" AIFreezer & will "report" soon (if that's okay) cheers john
  2. pete apologies for the late reply ..... I've been more interested / busy "testing" your AIFreezer.lua & have not had a chance to test the attached (as an [Auto]). your notes will be helpful if I'm on the right track or not. I do however after more observations without the attached believe such a lua might interfere unnecessarily with P3D4's blending of pedal nw steer & rudder control which seems to be an improvement on fsx's pedal blends .... and indeed is a plus for your "direct" options as much as with 65696 (though the later is deflecting pedal nw steer a tad too much at the slowest speeds) cheers john rudscale.txt
  3. pete seems so ..... if looking at state shown by PATC. Maybe an enhancement is to add a "zapper" when crossing the threshold (using 31E4) to clear any TaxiOut or TaxiIn stuck on the runway ! john
  4. using fsuipc5.141e / wideclient 7141 / trafficlook 1650 / P3Dv4.3 / W764 ...... unzipped trafficlook folder aside wideclient outside program files & on main c:\ drive. no rush, enjoy off-line .... as before, I was keen to see what state crossing runways was (@ ksfo for example, traffic departing 28R cross the 28's to taxiway E from the terminals, so freezing might stop an aircraft mid runway whilst I'm on final .... but have zapper ready anyway & / or tweak afcad for 28L only departs). john
  5. but there is the problem ..... i am not getting a screen display with said menu (on my client). the application file is only 17kB ?? john
  6. pete now there's a challenge, imagination certainly, lua ingenuity dubious as you know ..... so decided to "try" TrafficLook" but no joy, don't see "anything" nor a user guide to check (wanted to understand what states apply crossing runways both before & after) the attached shows there's a connection but no "ini" is created in my TrafficLook folder. Your advice please. john WideClient.log
  7. & apologies plus thanks john
  8. pete apart from the discussion in this topic ....freezing !! john
  9. pete I've been reading your notes here & at the P2ATC forum re a lua .... "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". I am unable to find it in 5.141e example's or her ... you advice please. john
  10. Pete I continue to struggle to find the "correct" script" for my little idea ....... but 7 years ago you wrote " (i.e a simple newval = (ipcParam - 16384) / 8 ), then sends it on as the parameter ...." at axis range. Is this the way forward for me, say "newval = ipcParam / 8 and written by 3114 for 3110 as above. Hope it is, John.
  11. pete yes, you were correct. what was needed was.... ipc.writeSD(0x3114, 10000) ipc.writeSD(0x3110, 65696) But then I felt defeated after succeeding with that script only to find it was a fixed position input to the rudder not the change of the axis range I was looking for (my so called rudscale) & then not finding an offset that might (with FSInterrogate2std) ie changing for example as speed varies "11=ER,256,F,65696,0,0,0,*0.9" to "11=ER,256,F,65696,0,0,0,*0.2" whichever, if there was a way, it would only be of likely value if a user found his aircraft had "conflicts" with your "direct to" / mgs / rbl such as those who don't have a separate tiller but would like to use their one & only twist axis for "pedal nosewheel steer" with varying deflections (70o <15kts, 7o otherwise). again thanks for your time & 5.141e. john
  12. pete thanks ...... DU animations now showing correctly. john
  13. I'm guessing that was when I used the tiller particularly towards the end of the log. When you released 5.123c, full deflection was seen on the lower DU, but not with 5.14 when you adjusted the speed calc (as I mentioned last week) (?) I could not find reference in your SDK etc. of the 3114 offset ...... but I've tried to no avail simply the attached as a starter (in Auto, Assigned etc.) rudderscale.zip thanks john
  14. pete attached the ngx logging + profiles for the direct & sim options ideas. it seems I should be able to write a speed contolled lua based on offset 3110 if I can come to grips with the ipcwrite syntax for 2 different axis scales ! john FSUIPC5sim.log b737sim.ini FSUIPC5direct.log b737direct.ini & to mention, in each 2 abandoned take-offs from the same runway in opposite directions after a controls check & some tiller steering for the turnback & off the runway after the 2nd.
  15. pete thanks ..... time is an issue at the moment though it does not stop this "novice" pondering how to use a Lua to change the calibration (scaling) of the same axis. Should be able to do the ngx logging mid week. john

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.