Jump to content

ark

Members
  • Content Count

    2,222
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

429 Excellent

About ark

  • Rank
    Member - 2,000+

Profile Information

  • Gender
    Male
  • Location
    Colorado, USA

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

2,306 profile views
  1. Remind me why you need the modified mdl file with this latest version of the Falcon? Al
  2. Have you tried version 2.0b without any modifications or alternative mdl files? Al
  3. Tony -- thanks very much for the Performance Manual link and info. I have added the link under our Falcon50 Reference Information thread. Al
  4. Ariel -- what sim are you using? And do you use any third party shader addons, etc. Al
  5. After some additional experimentation I have updated both the Lua script and XML 2D popup gauge versions of the Poor Man's Autothrottle. Throttle movement should now be smoother with the Lua script A/T, and I added some coding protection to both forms of A/T to prevent out of range throttle values. EDIT: BTW, when using the Lua script A/T 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. I find that convenient. The A/Ts are still available here: Lua script A/T: https://www.dropbox.com/s/ia0k97e823hs86r/Autothrottle Lua Script.zip?dl=0 2D Popup gauge A/T: https://www.dropbox.com/s/lcx89iqoums71bj/AutoThrottle XML.zip?dl=0 Al
  6. Yes, the closer the a/c IAS to the target A/T IAS when you turn the A/T on, the less the simple A/T will hunt. I don't understand the context of your ENG sync question -- are you asking wrt the A/T? I don't really know the details of what ENG sync is supposed to do. I think it just reduces that wa-wa sound you get when the two engines 'beat' against each other sound-wise. Hopefully someone more knowledgeable will respond with the correct info. Al
  7. Try this: taxi_lt_switch=ipc.readLvar("L:SW_TAXI_LIGHTS") -- get current taxi light switch value:0=off, 1=on if taxi_lt_switch==nil or (taxi_lt_switch~=0 and taxi_lt_switch ~= 1) then ipc.writeLvar("L:SW_TAXI_LIGHTS",0) -- lights off elseif taxi_lt_switch == 0 then ipc.writeLvar("L:SW_TAXI_LIGHTS",1) -- taxi lights on ipc.writeLvar("L:XMLSND68",1) -- switch sound elseif taxi_lt_switch==1 then ipc.writeLvar("L:SW_TAXI_LIGHTS",0) -- taxi lights off ipc.writeLvar("L:XMLSND68",1) --switch sound end Al
  8. And of course you could always increase the thrust scalar to 1.1 to see what VS could be maintained up to 41000ft, although what that would do to the fuel burn I don't know. Thanks very much for the feedback -- go stuff, and I'm sure of interest to others. Al
  9. As discussed above, I tried changing the update_interval to 0.1 seconds in the A/T Lua script and I think the A/T performance was somewhat better, so the Lua script A/T controller in my Dropbox at https://www.dropbox.com/s/ia0k97e823hs86r/Autothrottle Lua Script.zip?dl=0 has been updated to use this new value. No changes were made to the XML 2D popup gauge version of the A/T. Al
  10. The suggested static thrust (engine) change is about a 7% increase. I wonder how doing that would compare to just changing the thrust scalar to 1.07 instead -- maybe the thrust scalar would provide a boost at all altitudes? Do we have any test pilots out there willing to do some test flights and report back? Al
  11. Now that sounds like an interesting idea -- thanks Jim. Al Edit: Should we be surprised an A&P mechanic suggested we change all the engines! 😉
  12. All Flysimware products are 40% off from 21 through 26 May 2020 in honor of Memorial day. Although this sale includes all stores selling Flysimware products, my experience is it's best to purchase directly from the developer. Not only does this better support the developer, but product updates are more readily available. Al
  13. To some degree users can tailor the performance of the Falcon 50 to suit their needs. In the aircraft.cfg file (which is in the main aircraft folder) there are engine and aircraft parameters you can tweak. Unless you have the necessary experience, this is easier to experiment with than with the air file: For example: [TurbineEngineData] fuel_flow_gain = 0.0065 //Gain on fuel flow inlet_area = 4.2500 //Square Feet, engine nacelle inlet area rated_N2_rpm = 29920 //RPM, second stage compressor rated value static_thrust = 3500 //Lbs, max rated static thrust at Sea Level afterburner_available = 0 //Afterburner available? reverser_available = 1 //Thrust reverser available? ThrustSpecificFuelConsumption = 0.6 //Thrust specific fuel consumption (Jets) AfterBurnThrustSpecificFuelConsumption = 0 //TSFC with afterburn/reheat engaged [jet_engine] thrust_scalar = 1.0 [flight_tuning] cruise_lift_scalar = 1.0 parasite_drag_scalar = 1.0 induced_drag_scalar = 1.0 So if you would like to increase the thrust of each engine by 10%, change the thrust scalar value from 1.0 to 1.1, etc. Information on the aircraft.cfg file parameters can be found here: http://www.prepar3d.com/SDKv3/LearningCenter/simobjects/aircraft_configuration_files.html Al
×
×
  • Create New...