Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

Capt. Crash

members
  • Content Count

    35
  • Joined

  • Last visited

Community Reputation

14 Good

About Capt. Crash

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

1594 profile views
  1. Good evening, I fly the F-14B, I have searched and have been unable to find the solution to making the lantirn work. I turn it on, set up ATTK, get the IR screen up, hit CTRL+F and move the joystick control input displaying (Vol. 6 P18, #6). At this point I have my target, and when I press the trigger to lase the target and the L begins to flash. But i have no TTR information. I have tried using the G100 MFD CRSR key bind but to no avail either. The manual is very vague and I am having a heck of a time trying to get this to work. What is the correct sequence of steps to get a properly auto laser designated target using GBU-10/12's? Thanks in advance for the help Crash
  2. I'm still around, just rarely these days as you can tell....I don't fly the twin otter anymore but I am still willing to share my experiences. I am currently flying the CRJ-200/700/900 I don't know about the hot fix compatibility. Has anyone tried it? Blue Skies, Crash
  3. I'll look into this on the 24th. I'm working until then and it looks like a 14 hour day tomorrow
  4. On occasion when we have moved the prop levers quickly, the props hunt in the real aircraft too. FSX has a problem with forces when it comes to props, i'm still dialing in the prop_tc value which i think is the seconds per degree of movement (kind of a backwards unit to me). right now it's set to 0.008, maybe 0.006 might be better? Edit: for those of you who want to try a different prop_tc value try 0.006. also, remember 96%np is max so before you firewall for take off, bring your prop levers back to 88%, that should give you 96%Np [PROPELLER] prop_tc = 0.006 //0.008
  5. It sounds like your power application is too quick, we power up to 15-20 lbs of torque, let the T5 peak and start cooling then over 3ish seconds get up to take off power. In the airplane the power levers move around 18inches so there is a lot more movement than in a pc throttle, which means your small throttle movements are exaggerated in the sim.
  6. It should work with the 3 bladed props, but the CFG/airfile edits in place only account for the 4 bladed version. So any other 300 wheel variants will perform like a 4 bladed Hartzell prop aircraft. the performance is slightly different and the GG speed is slightly lower at idle. 3 bladed props are louder and bigger but perform a bit better. From the point of view of the sim pilot, nothing really changes. The 3 bladed hartzell prop aircraft has an Idle GG of 51% vs 58% for the hartzell 4 bladed. The prop MOI is probably a bit different but ultimately it will still follow the same-ish book values. nothing of significance.
  7. I run into this with the baron sim in the redbird I manage. CTRL+F1 or an axis movement assigned in FS does not feather the prop, ALTHOUGH it may put the lever in the feathered position on the model. the additional ctrl+F2 command is required to send it into feather. FSUIPC is good at managing this. Glad you like it Bliksimpie!
  8. When we shut down the aircraft, the props are feathered and that run down time is accurate. If you want an example of how long an unfeathered prop takes to spin down: https://youtu.be/oMhkCx7GcRI?t=61. That is a geared engine too which is direct drive, a free wheeling turbine like the PT-6A would take even longer. The spool times are accurate. Thanks for the help! Let me know if you have any other questions. Here is our shutdown checklist: Parking Brake: Set ( C ) Bleed Air / Air Conditioner: OFF (FO) Generators: OFF ( C ) Power Levers: IDLE ( C ) Prop Levers: Feather ( C ) Fuel Levers: Stabilized Idle, OFF ( C ) External Lights: OFF (FO) Avionics Masters: OFF (FO) --END CHALLENGE RESPONSE-- the rest of the items are captain items like boost pumps and what not There are no auto-feather mechanisms in the Twin Otter that are used outside of Take-Off. Once the auto feather system is shut-off, the only way to feather is with the prop lever. There is also no unfeathering accumulator, so there is no way to unfeather the prop in flight without reaching the minimum governing rpm to bring it out of feather via an air-start. The reason for this is the prop reduction gear box is lubricated by an engine driven pump which only works if the power section (gas generator) is running. The prop/gearbox turbine shaft is not directly attached to the Gas Generator (hence free turbine) One error in the video, the prop lever only changes the fuel schedule to the engine on start up, not in flight. Prop levers full forward below 50F and 3000 feet pressure Alt to allow the second stage fuel nozzles to come on earlier. Above 50F or above 3000ft pressure alt: Prop levers feather to delay the second stage ignition to prevent a hot start. So if you could unfeather the prop in flight, without the GG turning to get at least 80PSI of oil pressure you will eat the gear box and seize the prop in place. Our emergency checklist calls for the immediate feathering of the prop if the GG runs down due to shut down or failure to avoid severe gearbox damage.
  9. Thanks Reinhard, Any subsequent versions which come out will have a datestamp in the zip file. Regards Crash
  10. Ok Everyone! Here are the files to my alternative FDE and engine system for the DHC-6-300. Please note these files are going to be minimally supported by me because I usually work 5 days a week, working 80 hours flying twin otters. With that said, installation is simple, the zip file is the same name of the aircraft where the files should be put. READ THIS: http://forum.aerosoft.com/index.php?/topic/88611-updated-fde-to-twin-otter-updated-2842015/ <--this is the original post with the actual changes made and what they do. Rule 1! BACK UP YOUR Aerosoft_DHC6_300_WHEEL. Put it in a safe place because this is like taking the red pill, there is no going back. Rule 2! DO NOT distribute these files without my permission and Aerosoft's permission. I spent several weeks getting the tweaks right. Rule 3! YOU are test pilots by using this change. If you have problems, let me know EXACTLY what you were doing before the error, when it occurred and send screen shots/video. anything to help me and the other pilots reproduce the error. I am not responsible for your use/misuse of these files or any harm that comes to it Unzip the contents of the Aerosoft_DHC6_300_WHEEL.zip file into the Aerosoft_DHC6_300_WHEEL folder located in your Microsoft Flight Simulator X\SimObjects\Airplanes\ directory. When it asks you to either merge or overwrite, click yes and yes. That's it. What these files do: They simulate the DHC-6-300 using 4 bladed hartzell propellers and rewrite the turbine engine code to match observed temperatures, autofeather system, Fuel flow, torque etc. in our aircraft. It's as close as I can get it for now. This will cause all the DHC-6-300's from aerosoft to use the same code, EVEN if the air and cfg changes are not utilized. THIS WILL CAUSE A MISMATCH IN PERFORMANCE. Meaning the DHC-6-300 floats, tundra etc any Aerosoft_DHC6_300_XXX will use the _WHEEL gauge code but will not use the cfg/air file changes because those are aircraft variant specific. If this is not what you want. Copy the original TW_System folder from the wheel version to all the other 300 variants then copy & Rename the provided panel-ALT.cfg file to the other variants and rename it panel.cfg, making sure to overwrite the original (make sure to back up the original). I will update this post as necessary to clarify any items that come up. Have fun fly safe **** NOTE FROM AEROSOFT ***** These files are to be regarded as 3rd party "Alternative" FDE's and Aerosoft can/will not provide any kind of support for issues occuring when using these files. Since the altered files are legible property of Aerosoft, the agreement with Capt. Crash is that he is allowed to upload his files to this forum. This means that the files must not be distributed in any form by others or elsewhere. The Aerosoft Twin Otter Extended is now 1½ year old and is regarded as a finished product. New features and updates are not planned for the time being. At some point it´s necessary for a company like Aerosoft to let go of a project and spend their resources elsewhere. Therefore there are also no plans to include these files in possible upcoming hotfixes. As a code developer I am still willing to make smaller hotfixes if they can easily be accomplished. I´m also willing to support Capt. Crash if he should need my help. I want to thank Capt. Crash for his great contribution. On behalf of Aerosoft. Finn Jacobsen Aerosoft_DHC6_300_WHEEL.zip
×
×
  • Create New...