seikdel

Thanks so much, JG14_Smil!

Not to revive a weeks-old thread, but I'm now having troubles with ARK.lua. Where exactly in the .miz file is it supposed to go? I've tried in the root and in \ARK, but nothing seems to work! Anyone?

Title says it all. I have my TM Warthog in the mail, but now I need some newer pedals that aren't on a gameport =) Anyone have any equipment you're looking to sell?

Holy cow is that an awesome video! Thanks Phantom! For the record, I love WWII gun cam footage. I'm always amazed by the caliber of piloting those aircraft required. I visited the Richard Bong museum and they had a phenomenal video with plenty of gun cam footage from attacks on Japan. Wow.

You can install JSGME elsewhere and use a shortcut that runs the program in the DCS world directory. Whichever. It's worth noting that DCSW already has a "mods" folder, so you'll have to store your mods in a differently-named folder (i.e. "_MODS" or "my mods").

Isn't IFF typically a separate transceiver, at least in US military aircraft? My understanding is this: The IFF transceiver in the F-15 interrogates (i.e. asks) the IFF transceiver in the A-10. The A-10, if it's turned on and configured properly, responds back to the F-15 with some sort of code that indicates it's friendly. The F-15 then knows it's a friendly target. Am I correct or am I off base? Also, is aircraft type ever transmitted over IFF? Does the A-10 ever squawk that it's an A-10, or just that it's friendly? While I'm at it, "squawk" refers to IFF, correct? The NCTR is just a nifty radar trick that looks at the return from a target and then compares it to other known returns to figure out what type of aircraft the target is, right? Isn't it largely based off the doppler return from the turbine blades? One final question: I've heard comments about DCS "not having a proper radar simulation", and how it probably won't, at least for a long time. Why is that? What about radar is so difficult or computationally-intense to simulate?

Why does my engine temp climb until the engine dies when I'm idling on the ground? I'm in a winter mission (-2C) and if I let it idle at 2300RPM (propeller set to full increase) until the oil temp hits 40C, the coolant temp just keeps climbing. It does the same if the propeller is set to full decrease. Manually opening the radiators doesn't do anything. Am I just supposed to get her off the ground and gulping air ASAP? Can the plane really not idle for 5 minutes without overheating? Am I missing something or is this a bug? edit: here's a track overheating.zip Edit again: Found my answer, so how about another question: When I'm flying in cold conditions, I open the hot air and close the ram air. Shouldn't the carb temp increase when I do this?

I'm brand new to the Mustang and I keep killing my engine. I assume it's something I'm doing wrong with engine management. Anyone willing to take a look at the track (it's probably 20 minutes long) and tell me why I lose my engine? Thanks! why does my engine die.zip

I just started flying the Mustang yesterday. One thing that helped me was looking at the carburetor temp before starting. The colder it is, the longer you have to prime for. Speaking of which, can I use the oil dilute switch to help in cold temps?

First, if you want the autopilot to do anything about your altitude, make sure you have the altitude channel engaged (the lower-right AP button). Also, select which altimeter the AP will be referencing: barometric or radar. The left-hand switch under the flight director button controls this. When you engage that button, the Shark will automatically try to hold your altitude at whatever it was when you pressed that button. To change the set point that the helicopter will try to stay at, either hold the trimmer or the collective brake, achieve your new altitude, and then release the trimmer/collective brake. Now the helicopter will try to hold you at this new altitude. The collective brake only sets a new altitude, not a new pitch/bank/yaw. Use it when you want to only adjust your altitude. The trimmer, of course, sets a completely new attitude and altitude. Use it like you normally would. To use auto-hover, you first have to bring the Shark into a somewhat-stable hover (the manual says "near-zero"; I usually try for <5km/h). I find that I have to have the Shark trimmed with her nose roughly 5 degrees pitch-up for this. Then, engage the auto-hover and gently release the stick. The auto-hover should bring you into a fairly stable hover and hold you there. If you want to descend while auto-hovering, hold the descent switch. The AP will slowly descend at ~2m/s. The descent switch does nothing if auto-hover isn't engaged and holding you in a hover. I hope this clears things up a bit. Please ask if you need any clarification or if I was unclear about something =) P.S. One thing I've learned while flying is that you don't always want every AP channel on. Use your altitude channel when you want to hold a specific altitude, but then disengage it if you're doing aerobatics that require constantly-changing altitudes. Doing a slow hover taxi around base? Turn the heading AP off so that you can turn without having to re-trim every time. Play with these and see what gives you the best results. Good luck!

Nope, no issues for me.

Tacview is great. Just be advised that it'll cause you to fail the export.lua check on some servers. If you install it and try to connect to the 104th, for example, you'll just get the all-ambiguous "connection interrupted" error. Same goes for TARS, another extremely nifty utility.

FWIW, I'd rather shut off EEG and RTB with one dead engine and one charred engine than dump the whole chopper at the FEBA. Another tip: If you've got too much fuel and only one engine to burn it with, fire up the APU. It doesn't burn fuel too quickly, but every little bit helps. Other than that, the other tips mentioned hold true: Keep up air speed and rotor RPM. Ideally, stay far enough back so that you'll have minimal evading to do if you get hit. You don't want to be dodging SAMs and AAA at the same time. The more I fly the Shark, the more I like to sit at standoff distance with a nice altitude, rifle off all of my munitions and then RTB. Oh well, I suppose this isn't too feasible in CAS and other missions.

Yeah, I was in the server with you and saw the issues you were having. It'd be nice to have this addressed.

I just got locked up by 3 different ship-based radars in the Toad. It never gave me any launch authorization or range. Overriding and launching results in missile self-destruct. Has this been reported yet?

I used a couple of different ramdisk programs with mixed results. While the loadtimes were goregous (not perfect, but goregous), the programs themselves were a pain to use. I haven't found a cheap/free program that will take care of the disk on startup/shutdown. If you have an afternoon of gaming/simming ahead of you, it's worth the time to set it up. If you're just hopping in for a half-hour break, not so much.

I'm confused on what we're talking about. atsmith6 says "rotor overspeed" and also talks about the zebra button. Correct me if I'm wrong, but these are two completely different things. The zebra button flashes to warn you of low rotor RPM, right? That does not correlate with the overspeed warning. The overspeed warning refers to the turbine speed, and happens when a) you demand too much of the engines with the EEGs turned off and b) when you dice your blades and the rotor RPM jumps up. So is atsmith6 talking about the zebra button/rotor RPM warning, or the turbine overspeed warning that Betty alerts us to?

I guess I didn't think it took that long to get the Shark up and moving, especially in game mode. When you factor in the autostart, the hardest part about working the Shark (i.e. actually flying it) doesn't seem like it'd be that much easier if you took out the details that make DCS what it is. The only way it'd get that much easier is if you put a Novalogic Comanche 4-style chopper in the game.

Hey guys, I have a question. I sense that this may be a dangerously-heated topic, but when did we decide that tap-and-release trimming was "correct" and holding the trimmer was "incorrect"? I guess I didn't see that discussion...

Reminds me of my single playthrough of HAWX. Didn't realize that voice commands defaulted to on or that I had a hot mic. I kept wondering why my plane would randomly dump flares at loud noises =/

Do they perhaps require both AC and DC power?

Yeah, last night when I was flying, I was shot and lost my left hydraulics. I lost a little bit of pressure on my right hydraulics, but then they held steady until I was coming in on final. I dropped the gear and they made it about 80% of the way down before they bled out the hydraulic fluid that was left. ...does that count?

It is not implemented. That being said, it's the same missile type being loaded on both aircraft, isn't it? Couldn't you theoretically have a Su-25T loaded up with a missile configured for Shark guidance? pp.311 in the Ka-50 manual uses the terminology "control zone", which is created by scanning 2 lasers along the horizontal and vertical axes. This zone is 7m in radius 100m in front of the helicopter and narrows as the missile travels further.

I was teaching a buddy how to fly recently and he had questions about how exactly beam riding works. I threw these together. They are correct to the best of my knowledge. Anything I got wrong? P.S. ED please add buddy lasing for Su-25T and other birds! Please!

If you lose your radio, you can't communicate with the AI. That could be it. OTOH, the AI is pretty frightfully ignorant sometimes, so it could just be that.