Jump to content
The simFlight Network Forums

ark1320

Members
  • Content Count

    226
  • Joined

  • Last visited

  • Days Won

    4

ark1320 last won the day on July 27 2017

ark1320 had the most liked content!

Community Reputation

5 Neutral

About ark1320

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Colorado, USA

Recent Profile Visitors

1,882 profile views
  1. I have updated the autothrottle lua scripts to work with Mach# as well as IAS in knots. Each autothrottle script defaults to airspeed values in Knots below its crossover altitude, and in Mach# above its crossover altitude. The crossover altitude for the TurboJet and CRJ scripts is currently set at about 29000ft. For the TurboProp and C441 scripts it is set at about 24000, and at about 22000 for the MU2 script (crossover altitudes can be changed with a text editor). When a script is activated you will see When climbing or descending through the crossover altitude the autothrottle automatically switches to Mach# or Knots, respectively. In addition, a key or button can be setup through FSUIPC to manually switch the autothrottle back and forth between knots and Mach# at any time.The corresponding A/T target speed displays when the script is running looks like this AutoThrot3C441.lua AutoThrot3CRJ.lua AutoThrot3MU2.lua AutoThrot3TrbJet.lua AutoThrot3TrbPrp.lua SetUp Autothrottle Lua Scripts.docx
  2. Thanks Thomas. I still haven't figured out a way to reliably trigger the problem. Al
  3. I agree the P3Dv5 menu flickering issue has gone away with HF2. That flickering was quite slow -- maybe seconds between "flicks". The flicking I'm talking about here is quite fast -- maybe 5 times/sec -- makes it hard to read the display. However, it doesn't seem to always happen. If I can determine how to make it happen reliably I'll send you a script to try. Thanks very much for the offer to help! Al
  4. I have a Lua script that runs in a continuous loop and displays various flight parameters in a simconnect message window using ipc.display() as shown below . The flight data display is updated about every two seconds. This script runs fine in P3Dv4.5HF3 with a nice steady display. However, when using the same script In P3Dv5 (with or without the Hot Fixes) after a few minutes the simconnect message window display begins to flicker at a high rate, and stopping and restarting the script does not stop the flickering display. I use FSUIPC6 for both sims with the latest version of Win10 Pro. I realize this is likely not a FSUIPC problem, but am posting here to see if any other FSUIPC Lua script users have come across a similar display issue with P3D5 and might have some insight into the cause. Thanks, Al
  5. My FSUIPC6.ini file has somehow ended up with two "General" sections, one headed by !1=![General] and one headed by just [General]. I would guess this is not normal and don't know how it happened. Are the entries under !1=![General] actually being used? Should I delete one of these General sections? Thanks for any advice on this. A;
  6. OK, I understand, thanks very much for the feedback! Al
  7. Can an instruction like event.key() be used inside a processing loop to act like an interrupt in other languages? I would like to detect a key stroke while a while true do loop is processing, and after the function associated with event.key() has finished, I want the processing loop to continue. Thanks, Al
  8. I assume the above means all single and double floating point values are noted as such, and all others are integers. Thank you, very helpful! Al
  9. Some offsets specify the numerical format of the value in the offset, but others do not. Just for example, the offset for Indicated airspeed shows: 02BC 4 IAS: Indicated Air Speed, as knots * 128 So the question that comes up is should this 4 byte (32 bit ) value be read using ipc.readSD(), ipc.readUD(), or ipc.readFLT()? Since the format is not specified for this offset (while the format for some other offsets are) is there an implication that any of the above ipc.read instructions will work and the Lua interpreter will make the necessary conversion, or do you have to read and display the value to see what it looks like, or what? Would appreciate any general guidance for these type of situations. Thanks, Al
  10. AutoThrottle_TJ.lua, AutoThrottle_TP.lua and AutoThrottle_CRJ.lua are simple PID (Proportional, Integral, Derivative) implementations of an Autothrottle for TurboJet, TurboProp, and the AeroSoft CRJ aircraft, respectively (the Aerosoft CRJ is somewhat of a special case because of unique throttle coding). These scripts work reasonably well on the Flysimware Learjet35A, Falcon50, MU-2, and on the Aerosoft CRJ aircraft. I have been told the Autothrottle.TJ script works with the Aerosoft DC-8. I'd be interested in hearing how these scripts work on other aircraft. There are parameters at the top of the scripts that you can experiment with if necessary for a particular aircraft. The TurboJet and TurboProp scripts assume standard FSX or P3D throttle coding and should work for aircraft with up to four engines. To try out an autothrottle put the script in your modules folder and use FSUIPC in the usual way to assign a key or button to the appropriate script to activate it. When activated a window will open asking for a target IAS between 50 and 500 Kts. Of course you need to use a target IAS that is reasonable for the a/c. If the A/T is running you will need to call the script again to change the target IAS, or to turn the A/T off by entering a * instead of an airspeed value. You could also use the FSUIPC LuaKill option to quickly exit a script. It is best that the AP is on and the a/c is stable and reasonably close to your target IAS when the A/T is activated. If you ask for large IAS changes it can take a while for the IAS to finally settle down. When the A/T is running you will see a green bar across the top of your screen with the target A/T IAS. Note that you can grab the right side of the green bar with your mouse and resize the bar down to a small display. You can also drag and reposition the green bar to where you want it. AutoThrottle_CRJ.lua AutoThrottle_TJ.lua AutoThrottle_TP.lua
  11. That was it, and I don't even know where those particular quotes came from -- I only have one quote key on my keyboard. I guess it was the font I was using at the time. Thank You, John! Al
  12. Members 5 213 posts LocationColorado, USA Report post Posted 15 minutes ago I can't get the simple Lua test script below to work. I have assigned a key to load the script, and IF I comment out the event.button line, the script at least loads and I get the "Loaded" message. However, with the event.button line in, apparently the script does not even load since I do not get the "loaded" message, and there is no response to a button push. The event.button joystick arguments of 1, 1 are the joy# and button# I get in the FSUIPC6 Button and Switches window when the corresponding button is pushed. I have also tried replacing the first 1 argument with its joy letter in quotes, "J", but that does not seem to make any difference. Below are the joystick assignments from the FSUIPC6.ini file. I cannot figure out what I'm doing wrong. Thanks for any ideas. Al Win10/64 P3D4.5HF3 FSUIPC6.08 [JoyNames] AutoAssignLetters=No J=Logitech Extreme 3D J.GUID={EC24C380-3676-11E3-8001-444553540000} R=Saitek Pro Flight Rudder Pedals R.GUID={F5D4F4C0-FF57-11E5-8001-444553540000} Y=Saitek Pro Flight Yoke Y.GUID={F5D4F4C0-FF57-11E5-8002-444553540000} B=BU0836A Interface B.GUID={D89CA0A0-B3FD-11E6-8001-444553540000} 1=Logitech Extreme 3D 1.GUID={EC24C380-3676-11E3-8001-444553540000} 2=Saitek Pro Flight Rudder Pedals 2.GUID={F5D4F4C0-FF57-11E5-8001-444553540000} 3=Saitek Pro Flight Yoke 3.GUID={F5D4F4C0-FF57-11E5-8002-444553540000} 4=BU0836A Interface 4.GUID={D89CA0A0-B3FD-11E6-8001-444553540000} Lua Test Script function Taxi_Test(a,b,c) ipc.writeSTR(0x3380, " TAXI "); ipc.writeSW(0x32FA, 4); ipc.sleep(4000) return end -- Main program ipc.writeSTR(0x3380, " Loaded "); ipc.writeSW(0x32FA, 3); ipc.sleep(3000) event.button(1,1,3, “Taxi_Test”)
  13. I tried turning on VSync and TB but unfortunately still get the flickering. I don't use ViewGroups. Al
  14. I did post on the L-M forum and they reported they are aware of the problem and are working on it. I've now determined the menu flicker rate is proportional to FPS. When I have FPS locked at 30 in the sim I get the flicker about every 11.6 seconds. If I lock the FPS at 60 and use a default a/c so I can get about 60 FPS on average, the menu flickers about every 5.7 seconds. If I lock the FPS at 15, the menu flickers about every 22.8 seconds. So double the actual FPS and the flicker rate doubles; half the actual FPS and the flicker rate is half. I have VSYNC and TB off. As for the Enhanced Atmospherics (Beta) texture option, I also get small white flashing at times. I guess that's why it's only a Beta. Al
×
×
  • 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.