-MadCat-

It's not the high temps in the first place that make an engine fail, it doesn't melt or anything. It's wear and tear, which is greatly increased with too high temps. I didn't engineer that engine, so cannot tell about the safety margin between the gauge markings and when the temperatures really are too high for the used materials and the stress at high power. Now he was just at idle, run the engine with those high temps at high power and I promise it will soon start to run rough and fail quickly if you don't reduce power significantly. Greetings MadCat

Prior to 1.2.7, detelting the entire category for a given controller made all the "grayed out" commands assignable for that controller too. This however doesn't seem to work anymore, as I experienced yesterday too. I needed to take the commands in question out of the keyboard.lua, and place it in the joystick.lua. Hope that will change again! Greetings MadCat

The lack of airflow through the radiator can overheat your engine on the ramp, at idle. As contradictory as it sounds, throttle up to 1200 ... 1300 rpm to blow some more air through the radiator. Radiator doors are supposed to always be fully opened on ground operation. Put them to auto on the runway, prior to takeoff. Warm up the engine at ~1300 rpm. Don't rev higher before oil temp is at least 40°C, then idle no lower than 1000 rpm. That way you should have no trouble with the engine, at least I never have. Greetings MadCat

As I just redid all my controls from scratch, I found 2 errors in the command options for the Huey (Sim). First one is in "Cockpit-Ansicht": "Kamerasicht nach oben rechts, langsam" moves the view down right, instead of up right. "Kamerasicht nach unten rechts, langsam" moves the view up right, instead of down right. Second one is in "Intercom Kontrolltafel": There is no entry to move the selector to the Intercom position. Instead there are two entries for "Interkom Empfängerhauptschalter INT AN/AUS". While one correctly toggles the Intercom switch, the other one sets the selector to the Intercom position. Greetings MadCat

I think you confuse an actual IR jammer with the IR suppression systems that can be mounted to the engine exhausts. Those mix the hot engine exhaust gases with cold air ingested at the front of the "boxes", before expelling that cooled mixture to the rear. If they are installed they work independently from any power circuit, they just work :thumbup: Greetings MadCat

Concerning the lack of response to throtthe adjustments between idle and max with the governor in auto, that's reported and already officially confirmed to currently be wrong. http://forums.eagle.ru/showthread.php?t=117921 The idle - max "switch" came with 1.2.6. Greetings MadCat

If N1 gets stuck again at ~18%, check the EGT if you even have ignition. It sounds very much like you don't. Make sure to position the throttle close enough (on the decrease side) to the idle stop. I assume you know the procedure, just for the sake of an thorough troubleshoot, you may have a look here. I personally cannot confirm a single failed start attempt, ever (provided battery power was sufficient if I started on battery, or I didn't forget any other thing). Greetings MadCat

I've been working on this for quite some time too now (without luck). TARGET doesn't enable you to toggle definitive switch positions, as you would wish for with something like the Warthog throttle. Yet with the example for the master arm it works to just program the up and down commands (guess that's what you meant, cichlidfan). The problem is, that at least I didn't figure out yet, how to edit the .lua-files to make the main fuel switch for example work with 2 separate commands. Off command to switch it off, nothing else, no matter how often you press the off button, and same for the on state. I've managed to edit all the (for me) needed commands for the Shark, apart from the fuel cut-off, those just don't work. But the Huey seems to work totally different here, and I've tried a lot of switches and ways to edit the .lua-files already. +1000 for (a lot) more stateful button commands, pleeeeaaaaaaas BST !!! Or explain how to edit the .lua-files correctly !!! Here another thread on that topic btw. Greetings MadCat

Wire Strike Protection Systems (WSPS) are no gadget exclusive to the military. They are installed on civil helicopters too. Basically it all comes down to the environment the helicopter will be operated in. There is no such thing as "it is uncommon for xy helicopter", and in Vietnam (assuming those are Vietnam pics) they just didn't need WSPS. Today, I'd not fly a helicopter without, only once to a place I could have them get installed at. It can be a lifesaver, so +1 for WSPS on the slick version too! Greetings MadCat

So we are talking totally fictional now?! I'd throw in the Sa-2 Samson from AVATAR. Or, for a little more combat oriented, the lighter Scorpion gunship from the same movie. Or, if that's impossible, I'd be more than happy with an AH-6 Little Bird :music_whistling: Greetings MadCat

Not very practicable to "stretch" virtual joystick travel that the extremes of virtual and physical joysticks are still the same. Look at it this way, you are trimmed 1/4 to the right (considering entire range from left to right, so you are trimmed half way to the right from center position). Then you move your physical joystick 1/2 to the right (from center position), your virtual joystick moves 1/8 to the right (again looking at full virtualy range left to right). Now, without changing trim, you move your joystick 1/2 to the left (from center position), but your virtual joystick suddenly moves 3/8 to the left (of full virtual range again). For the same input left and right, you get different stick travel in game. Not good. A better way would be to keep the input to stick travel at a constant ratio, but build in some threshold. Say you push the joystick fully forward, which would move the virtual stick fully forward too. But, below the surface, the game recognizes a further say 1/4 of max stick travel. That would mean you reach full virtual deflection with 2/3 of physical deflection when trimmed to center. Then you can, up to half virtual forward trim, still reach full backward position (the 1/4 that the virtual axis is enlarged over the full virtual stick travel of the aircraft). As said, the downside is that full virtual deflection is reached prior to full physical deflection, yet the input to virtual deflection would stay at a constant ratio. At the extreme you enlarge the underlying axis that far, that even when trimmed fully forward, you can still reach full backward, but then you double the sensitivity and reach full forward virtually with halfway forward physically. The other way to combat that probelm is, one could get a FFB stick. Hope I got the maths right and explained the idea somewhat understandable. Greetings MadCat

Already lots of skins around, have a look through these: =6&arrFilter_pf[gameversion]=89&arrFilter_pf[filelang]=&arrFilter_pf[aircraft]=&arrFilter_CREATED_USER_NAME=&set_filter=Filter&set_filter=Y"]http://www.digitalcombatsimulator.com/en/files/... http://forums.eagle.ru/showthread.php?t=112890 http://forums.eagle.ru/showthread.php?t=107646 http://forums.eagle.ru/showthread.php?t=103715 http://forums.eagle.ru/showthread.php?t=107612 http://forums.eagle.ru/showthread.php?t=108413 http://forums.eagle.ru/showthread.php?t=106073 http://forums.eagle.ru/showthread.php?t=108070 http://forums.eagle.ru/showthread.php?t=108036 http://forums.eagle.ru/showthread.php?t=107972 http://forums.eagle.ru/showthread.php?t=107750 http://forums.eagle.ru/showthread.php?t=106167 http://forums.eagle.ru/showthread.php?t=106801 http://forums.eagle.ru/showthread.php?t=106570 http://forums.eagle.ru/showthread.php?t=106428 Greetings MadCat

Danke für die flinke Antwort! Sollte in keinster Weise ein Vorwurf sein! Am Ende des Tages ist und bleibt es ein "Spiel" und das Brot auf dem Tisch und Zeit für die Familie ist einfach wichtiger :thumbup: Danke für die Bemühungen! P.S.: Ein paar mehr deutsche Einheiten auch für's "gemeine Volk" wären nett. Denke da zuallererst an die UH-1, die ja auch hierzulande nicht wenig geflogen wird:music_whistling: Natürlich auch an alle ein frohes Neues nachträglich MadCat

Schade, dass die Server in letzter Zeit so selten zu erreichen sind!:( Aber mal 'ne Frage, besteht die Möglichkeit einen der Server auf die 1.2.7 Beta umzustellen ? Grüße MadCat

Albeit you already solved the problem (btw. for others it's always nice to also explain how you solved it), here are some more information. Correct starting procedure and a link to the full manual. http://forums.eagle.ru/showthread.php?t=117551 Without checking myself now, I assume the starter generator wasn't at the START position, so the starter wasn't connected to the battery to even begin with ? Greetings MadCat

The point he made is that DCS wasn't born to then create aircrafts where you have to guestimate large portions of systems and performance envelope. Which, in case of the RAH-66, would be total guesswork. And honestly, I (any many others) share that opinion not to waste time on airframes that aren't declassified enough to not field a total sci-fi product in the end. DCS was created for high fidelity and accuracy, that's what sets it apart from all the other (arcade) flight sims on the market, that's why we love it. But to stay on topic, what about a Sikorsky S-58 ? Big radial engine put in a helicopter, can it get any more awesome !? :) Greetings MadCat

Hi there! Making it possible to change button commands in game is a huge step and I'm very thankful for that ! :thumbup: What about if we could take that even further ? See, all moduels share so many commands, like all the F-buttons and all the view related buttons in cockpit and more. For example, I don't care about all the F-keys too much, so I shifted their original purpose to have all the "pure" keys available for joystick programming. Keyboard is about obsolete (except for chat) once my joystick is all set (thanks to clickable cockpits too). :joystick: As all modules share so many keys, it's a major annoyance to reassign all the F-keys and many more for each module every time it is necessary due to an update or I change my mind about some "global" assignments. Here comes the idea: Why not introduce a "Shared Keys" option in the module pulldown that then sets those keys globally for all modules. Maybe even with a tick box whether or not to use the shared keys or to assign all those commands to each module individually. I think nobody uses 2 different commands for 2 different modules for the same action. Let me know what you think and if this is even possible ! ;) Greetings MadCat

Hallöchen ! Geht's nur mir so, oder sind auch bei anderen die -ESL- Server seit ca. 2 Tagen nicht mehr zu finden ? Habe auf der -ESL- Seite keinen Hinweis auf Wartung oder ähnliches gefunden. Im Gegenteil, Serverstatus "behauptet" sie sind online. IP-Adressen der Server um ggf. direkt zu verbinden fand ich auch bisher nicht. Grüße MadCat

As promised in another thread, I had a look through all the manuals I already found. I cross-checked with the ED-wiki, and these are not in the wiki yet: UH-1H/V Operator's manuals: Link 1 (224 pages) Link 2 (432 pages) UH-1 Aircrew training manual AN/ARN-83 Org. Maint. Manual UH-1H/V Condensed Checklists Hope this helps ! Greetings MadCat

Would be great if you can create .pdf-file for the community and the ED-wiki.:thumbup: Later tonight I will also cross check what manuals I found, that are not on the wiki yet and then post them too. Greetings MadCat

Sorry to resurrect this old topic, but in my eyes it's better than just opening an new one. Question is, did anyone happen to find the manual for the AN/ARN-82 by now ? It's the only missing radio manual for our UH-1 and for the life of me I cannot find it. Please share if you have it, thanks ! Greetings MadCat

Hi Cowboy! Excerpt from UH-1H/V Operator's Manual ( 02.15.1988 ) : 8-22. Starting Engine [...] 4. Throttle - Set for start. Position throttle as near as possible (on decrese side) to engine idle stop. 5. Engine - Start as follows: a. Start switch - Press and hold; start time. Note DC voltmeter indication. Battery starts can be made when voltages less than 24 volts are indicated, provided the voltage is not below 14 volts when cranking through 10% N1 speed. b. Main rotor - Check that main rotor is turning as N1 reaches 15%. If rotor is not turning, abort start. c. START FUEL switch - OFF at 40% N1. d. Start switch - Release at 40% N1 or after 40 seconds, whichever occurs first. Refer to chapter 5 for starter limitations.Maximum starter energize time is 40 seconds with three-minute cooling time between start attempts with three attempts in any one hour. Exhaust Temperature: [...] 625 to 675°C 10 Second Limit for Starting and Acceleration 675°C to 760°C 5 Second Limit for Starting and Acceleration [...] e. Throttle - Slowly advance past engine idle stop to engine idle position. Manually check engine idle stop by attempting to close throttle. f. N1 - 68-73%. [...] NOTE The copilot attitude indicator should be caged and held momentarily as inverter power is applied. 6. INVTR switch - MAIN ON. 7. Engine transmission oil pressures - Check.Engine Oil Pressure: 25 PSI Minimum - Engine Idle 80 to 100 PSI Continuous 100 PSI Maximum Transmission Oil Pressure: 30 PSI Minimum 40 to 60 PSI Continuous 70 PSI Maximum 8. GPU - Dicsonnect. 8-23. Engine Runup [...] 2. STARTER GEN switch - STBY GEN. 3. Systems - Check as follows:a. FUEL b. EngineEngine Oil Temperature: 93°C Maximum Below 30°C FAT 100°C Maximum At 30°C FAT and Above c. TransmissionTransmission Oil Temperature: 110°C Maximum d. Electrical (1) AC - 112 to 118 volts. (2) DC - 27 volts at 26°C and above. 28 volts from 0°C to 26°C. 28,5 volts below 0°C. 4. RPM - 6600. As throttle is increased, low rpm audio warning light should be off at 6100 - 6300 rpm. 5. Fuel control - Check as required (for helicopters without modified fuel control) before first flight of the day as follows:a. GOV RPM INCR/DECR switch - DECR to 6000 rpm. b. Collective pitch - increase slowly until helicopter is light on the skids. Do not exceed 94% N1 or torque limit. c. RPM - Check for the following: (1) If rpm remains at 6000 (no bleed-off) or if bleed-off occurs but returns to 6000 within 4 seconds, fuel control is acceptable. (2) If rpm bleed-off occurs but does not return to 6000, fuel control is not acceptable and helicopter shall not be flown. [...] d. Collective pitch - Decrease to full down. e. GOV RPM INCR/DECR switch - increase to 6600 rpm. [...] 8-40. Engine Shutdown CAUTION If throttle is inadvertently rolled to OFF position, do not attempt to roll back on. 1. Throttle - Engine idle for two minutes. 2. FORCE TRIM switch - ON. [...] 9. STARTER GEN switch - START 10. Throttle - OFF [...] Hope this helps! Greetings MadCat

Something that just came to my mind. Sorry if this has been answered before, I didn't search all the pages in this utterly long thread. Poeple who preordered A-10C get nevada for free, so far so good. It was said, nevada is the first map that will benefit from edge and that the old map will not work with edge as it is a totally different engine. Now those who didn't preorder A-10C are (at first) stuck with the old map. But does that mean they won't be able to benefit from or update to edge at all, given the current map is build with the old engine ? Or is edge compatible with the old map but just the map doesn't take advantage of any of the new stuff edge brings ? Please clarify! Greetings MadCat

Hey there ! That "ignition button" is the idle release button that you need to press to turn the throttle below its idle setting for shut down, which isn't implemented (yet). The actual ignition button is located at the back of the collective and cannot be pushed with the mouse. That's the way the real collective is set up too. Regarding your throttle function, check if you have any conflicts in your control assignments and clean them up if necessary. If the problem reamains, delete the input .lua-files in the user directory, then reassign all the commands in game again. As for the dispensers, they don't work yet but will in the future. Greetings MadCat

I wasn't talking about combat exclusively. Compare the checklists for one and for both engines failure. The checklist for both engines failure will explicitly tell you to drop your ordinance (still only once you established a stable flight attitude), whereas the checklist for one engine failure doesn't. To be fair, neither of the checklists take combat into account. If one engine fails during normal flight, I don't drop my ordinance if I can continue on one engine or even am able to restart the failed one. In the midst of combat, well yeah, get rid of it and your a$$ out of there. Does it help ? Sure it does help in any situation, and I said so too. Sorry if I didn't clearly enough differentiate between combat and normal flight. Greetings MadCat