-MadCat-

Been there, done that. As of now, with a bit of training, I became quite proficient with that maneuver :lol: Always best to only place it at the very very end of the program! Greetings MadCat

The checklist for one engine failure in flight assumes that one engine is entirely failing on you, not just damaged resulting in some power loss. As the engine failed anyway, it is a precautious action to cut off fuel supply, preventing possible engine fire or help fighting it if already on fire. I'd say, keep the engine running as long as it can, if necessary place the engine control levers in emergency and return to base if possible. Dropping ordinance actually is only necessary if you cannot maintain level flight with engine levers at emergency at 110...120 km/h (no less than 70 km/h), but yes it does make things easier in any case. As long as the engine doesn't fail entirely, keep it running and get home asap. If an engine fails without battle damage and given you have the time, you can try to restart it. Yet never attempt to restart an engine you previously shut down because of fire or battle damage! Remember: Always fly the aircraft first, only then deal with other emergencies! Many start dealing with the engine fire (or other emergencies), without establishing a stable flight attitude to begin with. A fire will not kill you within 30 seconds, crashing the aircraft when not focusing on flying first will kill you in an instant! Greetings MadCat

The lasers for target ranging and for missile guiding are 2 different ones (actually 3, 1 for ranging and 2 for guiding). The time that runs down after missile launch is the estimated missile flight time +6 seconds (cooldown for the guidance lasers). About the ranging laser and laser burnout: Everytime you press the button to lock a target, the laser ranger is fired for about 10 seconds to measure exact distance. That is not necessary however. In case you don't move too much during missile launches and there isn't much elevation difference between the individual targets, it is enough to range once for the first target, then move the piper from target to target and launch the missiles without locking every single target individually. Weapon fire computer is quite good at recalculating the distance based upon the Skhval movement from the first lock. Just keep this in mind: 5 series per flight, each series consists of 16 cycles of 10 seconds with 5 seconds interval between the cycles. Between each series you need to wait 30 minutes. What does this mean, as it at first confused me too: You can fire the ranging laser 16 times (locking a target), wait 15 seconds between every lock (10 seconds burn time, 5 seconds cooldown). After that you need to wait 30 minutes before you can can fire it another 16 times. So even with deploying all your 12 missiles, you should be able to do this with 1 series and have 4 "shots" left for random ranging (in case you lock each and every target). Follow that restriction and you should have no trouble burning your laser. Switching it off doesn't make any difference! Greetings MadCat

Don't honestly know if it was already mentioned. Please add all the definite button commands that are either not implemented at all (yet), or at the moment just work as toggle switches. Things like the anti collision switch, governor, main fuel switch, etc. For all those toggle switches I already tried to create stateful commands in the .lua files, to no avail at all. Please add all those definite switch positions! Greetings MadCat

Usually I say to myself it isn't worth commenting on many topics. But I just have to write some last words on this whole topic. ED/BST did make a mistake with putting the MI-8 on a 60% sale 2 weeks after it went for pre-purchase, period. Then they did a wonderful thing to grant a discount for 1 future purchase to all those who jumped the train 2 weeks "too early", very honorable! With that I say ED turned this to a good end. The problem was, the entire time, that people are not angry because they have to pay full price. The issue was to pay full price when there was a 60% sale just 2 weeks later. Then again, Wags didn't say a single word about less sales or reduced discounts. Just that in the future no pre-purchase betas may be included in any sale, which is a good thing in my eyes. I'd say, put them on sale only a few months or so after final release, not while still in beta. Drop the price 10...15% while it's in beta, to actually give a little reward to all those early adopters who already buy a product that still is in beta testing. I'm sure everyone will gladly pay that price. If you believe in the product even though it still is in beta and want to support it? Great, buy early and have a 10...15% discount, but be prepared to maybe come across problems as it's still in beta testing. You don't believe in the product while it's in beta or just don't want to support that specific module? That's ok too. Buy the final release if you like, but deal with a slightly "higher" price or wait for the first sale. That would be nothing but fair. Sorry if I hurt any feelings, but I can't stand that "you guys who complained now ruined it for all of us, it's your fault and your fault only" b§&ls\!t anymore. Put it aside already and move on! My 2 cents, like them or don't MadCat

In general, it's a good thing to let everyone know how you actually got it fixed. In the event of others searching the forum with a similar problem, they don't run into a dead end without a clear answer on how you really got it fixed. Just saying. Greetings MadCat

Have a look at the co-pilot's instrument board. Greetings MadCat

Looks like a top secret pod for biological warfare agents :megalol: Please, a Skyraider would be soooo awesome !!! Greetings MadCat

There seem to be several bugs with the homing operation of the FM radio. First is the horizontal needle, that should indicate signal strength. No matter how far away you are from the beacon you are homing on, the needle is always all the way up and does not move the slightest. Second is an "auto-lock" behavior to the closest airfield beacon when you set 75.0MHz to home onto. Tuning the correct frequency does nothing on the CDI. 75.0MHz works all the time no matter what frequency the beacon has and it jumps to a new beacon when that one is closer than the previous. Third, but only tested once, is the ability to receive signals even when deep in the mountains on the bottom of a valley. Seems odd to receive signals from a beacon about 40km away while surrounded by high mountains. Greetings MadCat

The reason to fly everything that's available in one world is the simple idea that DCS:World was created for. A toolbox with all the tools right at your fingertips to make whatever you want. Missions that actually make sense can be created as well as missions that don't make any sense whatsoever and are for pure fun. It really is as simple as that, to make everything possible for the users and mission creators. Greetings MadCat

As said, I anticipated the MI-8 to not go on sale before final release. And there have been occasions in the past, where all modules were like 60% off, except for FC3 I think it was that was only 10% off or so. I'd not complain if the newly released beta would be just 10% off, but 60% ?! Sorry I have to use my grey matter for more important things than to keep track when there might be sales. Yes I am angry and it's my right to be. Not going to attack anyone personally, but this finally taught me to patiently wait for a sale when a new beta is released. Next time when a new beta is relaesed say so if there is going to be a sale withing the next 2...3 weeks. I'm sure this sale didn't find its way on the schedule just hours ago...

Last time I got a beta the first day !!! I got the MI-8 with confidence that there would not be a sale before it's out of beta and the sale with the UH-1 would not repeat again. And now this... Still being a student for some more days, I don't yet have money to throw out the window. Like my opinion or not, but this sale, 2 weeks after beta release, I feel I got screwed... :mad:

Before opening a new bug report or a new thread, I think the following fits best in this topic. Did anyone else notice, that on engine start and runup/slowdown the airframe rocks cw, while the rotor turns ccw ? ! Any rocking of this kind is induced by rotor imbalances and as such the airframe should "follow" the imbalance. Yet it rocks in the opposite direction. I'd appreciate other opinions about this, be it confirmations or telling I have crooked eyes :D Test it yourself and tell me what you think/see! And btw, the rocking still is way overdone! :music_whistling: Greetings MadCat

A civilian version with higher skids, wire strike protection system and a winch would be soooo cool :thumbup: Why not make it like the checkbox for the mustang in the mission editor, to chose whether it is civilian or not ? ! That would be a workaround, so the 3d model in game would not need to switch between civilian (higher skids) and military (lower skids) when you arm or disarm the helicopter. Simply make it impossible to load weapons when it was set civilian. (OOTTOMH I don't know right now if it's possible to arm the mustang set to civilian) EDIT: Inspired by Lib's post, how about mirrors at the lower windows to see below the helicopter or maybe straight down to see attached cargo ? ! Greetings MadCat

So this tells me I can plug my DCS:W P-51 and Fw190 into DCS:WWII, good. Yet this, on the other hand, states one licence is not usable for both worlds at the same time. From this I gather, when I buy a licence for a DCS:WWII module, I cannot plug it into DCS:W without getting another one ?! Still confused about what's what now and if the free aircrafts are able to plug into world still remains unclear (to me at least). And in all honesty: There now are "Original Rewards", "DCS World Rewards" and "Alpha Access Rewards", like what the... ? ! What currently unfolds before my eyes is a rushed kickstarter without thoroughly elaborating things beforehand and that now turns into a patchwork adding more and more confusion. If it turns out that licences for World and WWII really are seperate in the future, this could possibly be a deal braker for me and I'll stay with DCS:World only, plugging everything into that world. It just is not 100% clear how all this will work once both worlds are officially distributed from the website. Note, all these are assumptions at this point but it's what I currently see. I have no ambition to attack anyone in any way, but to express my personal opinion! I gladly stand corrected in the future (by officials), but for now, this is what I think about all this. Greetings MadCat

Hope this doesn't mean what I think it does and what it sounds like. If I have to repurchase the P-51 again or purchase 1 licence for each world in the future to fly the aircrafts in both, this suddenly adds a (very) bad taste to the whole thing (for me personally that is). I'd appreciate a clarification ragarding this matter ! Greetings MadCat

The levers are there at the warthog's throttle, why leave them unmapped ? At least I am not the one reaching to the keyboard in case of an engine failure in flight :harhar: Greetings MadCat

As far as I understood, you don't need to purchase the modules again to have them in WWII too. How it will work, install them again, copy the folders, link WWII to the World folders or however, wasn't explained yet. It may very well just be too early in development to answer this. Already known is, the P-51 and Fw190 are the DCS versions, nothing will be touched there! Greetings MadCat

No offense, but I think you didn't read close enough! Question was, will the 3 free planes be "hard coded" into DCS:WWII, just like the Su-25T is in DCS:World? Or are the free planes also "modules" and you get DCS:WWII for free, and 3 seperate (also free) downloads for the planes that you then can chose whether to integrate them into World or WWII? That information is not clear from the Kickstarter's descrcription. I'd be interested in that too. Greetings MadCat

I put left engine throttle to the left hotas throttle, and right engine throttle to the friction adjustment (grey "rotary"). The right throttle with all the buttons, hats and switches works as the collective. Call it strange, but works like a charme for me. :prop: And there is no better use for them anyway. Greetings MadCat

From what I know about these clocks, it's the ACS-1M. Given that, there are some errors in the simulated clock. Concerning the big 12 hour register. The second hand does not work together with the general time display. It is associated with the stopwatch function of the lower small register. If the stopwatch is reset, it just stays at the 12 o'clock position. There is no second hand for basic time display. The single hand in the lower small 30 minute register is the stopwatch's minute hand. Currently it just stops a 30 second cycle. The top small 12 hour register works correct, except for the window that displays if the mission time is running or stopped. Reset, the window shows white as is does now. Running, the window shows full red, not red/white as it does now. Stopped, the window is supposed to show red/white (left/right). Please dont leave us with a "franken-clock", like we already have in the Ka-50. :( Smaller bug(s): The hour and minute hands of the general time and mission time, as well as the little window for the mission time (only white parts are fluorescent) are not illuminated by the red light. Greetings MadCat

The quote from the manual is just a list of things needed for an engine to properly start, less of a step by step procedure on how to do so. In the Mi-8 as well as in the Ka-50 the start cycle is fully automated once the start button is pressed (given all the prerequisits are met). If you press the start button with or without opened cut-off valve, doesn't make a difference to the general start procedure. Watch the EGT during start up, ignition happens not before ~20% gas-generator rpm. Now my assumptions: It doesn't make a difference if you initiate the start sequence with opened or closed cut-off valve, as long as you open the cut-off valve in time (~20% gas-generator rpm). That procedure could be to prevent early fuel injection before actual ignition, again preventing excess fuel in the ignition chamber in case of a malfunction of the injection system. So possibly it just is an extra layer of assurance, that fuel only enters the ignition chamber when ignition is supposed to happen. As said, just assumptions! I haven't had a single false start in the past years opening the cut-off valve at 20% GG rpm (on the Ka-50 that is). Greetings MadCat

Select any other joystick command field, no matter if assigned or not, and the press "delete category". That will add all those commands to the corresponding joystick.lua and make ALL fields in that column available. This way you have to reassign all joystick commands though. Note: only the currently displayed category (e.g. View, View Cockpit, ...) will be affected by "delete category". That way you can, to some degree, control what joystick commands will be deleted in the process. Or you can manually find the needed commands in the keyboard.lua and add them to the joystick.lua. All these files are found in the user\saved games\ dcs\config\input directory. Greetings MadCat

Ich muss mal eine Lanze für den Ka-50 brechen. Lässt man die ganzen Systemtests ausser Acht, ignoriert Warmlaufzeiten und startet nur die nötigsten Systeme, dann ist die UH-1 nicht viel schneller "hochgefahren" als der Ka-50. Gebraucht werden lediglich Funk, Nav-Computer, INS-, EKRAN- und Dämpfer-Systeme. Durch das Koaxialdesign ist er zudem sicherer, agiler und es entfällt das Spiel mit den Pedalen zum Momentenausgleich. Die Dämpfersysteme sorgen gerade am Anfang für einen weniger hektischen Flug. Was bleibt ist ein mMn sehr einfach zu erlernender Hubschrauber, der mit seinen umfangreichen Systemen das größte "Wachstumspotential" hat. So "klassisch" und "puristisch" die UH-1 auch sei, meine Empfehlung geht in Richtung des Ka-50.:thumbup: Grüße MadCat

Possible bug with the adjustment for the high altitude limit of the radar altimeter. The high altitude adjustment doesn't stop at the 0ft position. You can still turn the knob towards lowering the limit and it will be "counted". You reach the 0ft position with the high altitude limit adjustment and then turn the knob another 10 revolutions for example. In order to increase the limit again, you have to rewind the 10 extra revolutions before the flag starts to move again. If it is supposed to work like that, please correct me. It seems odd that both knobs have a stop at the 1500ft position and the low alt limit at 0ft too, but the high limit can be (infinitely) overwound on the 0ft position. Greetings MadCat