seikdel

I'll add one more point to this. I asked a buddy who flies the Longbow about trimming technique, and he reported that it all comes down to personal preference. Some pilots hold and maneuver, some maneuver and tap, and some trim for 120kt IAS and then do all their maneuvering from there without re-trimming. All of these are valid techniques in the Shark (you'll have to key your heading channel a fair bit for the last one), and so our argument about what method is "real" is moot. Use whatever technique you prefer to get the chopper to accomplish the mission.

Actually the Su-25T's gunpods were bugged a number of versions ago so that they appeared to be continuously firing to all other clients, and people did load up the pods as a defensive technique. Hard to engage a Toad WVR when they crash your game.

I echo the confusion.

Yes, one does change views a lot in a fighter! It's odd that the kneeboard still pops up after you cleared it. Are you sure you changed it in the correct P-51D control set? For example, if you fly in sim mode, make sure you didn't accidentally change it in the game control settings, and vice versa. If that doesn't cut it, open the kneeboard section in the controls and make sure there aren't any other kneeboard controls mapped to your controller.

I'm surprised I didn't dump this in earlier in the thread. If anyone's still having an issue mapping the TM Warthog for the P-51D, here's my pre-made profile along with a guide on customizing it. That should help as a starting point, at least.

From what I can gather (English cockpit mod + experimentation), the first 3 banks of breakers control weapon systems. You can skip them when you're starting the helo if you're not heading straight into combat.

Are you sure all your circuit breakers are on? And the GMC and Doppler systems? Beyond that, I have also lost autopilot functionality before and been unable to restore it. If it only happened once, it's possibly a bug. If it happens every time you cold start, it's probably a missed step.

Gabuzomeu: Excellent doppler guide in that link! That really helped establish what's what for me, and also confirmed my suspicion that the knob behind the copilot is for system tests. Thanks much! Foofee: A line up means you're moving forward, a line down means you're moving back, and line left or right means you're moving in the respective direction. All of those numbers are in km/h. The little crescent gauge on the left tells you your vertical velocity in m/s.

Try adding this to your keyboard.lua file: I tried switching numbers for the UV-26 around, but it doesn't fix the problem =/

Aha! Thanks much for the info! Is that modeled correctly, or is it a bug?

Set the bomb-rocket selector switch to either train (which releases one bomb per button press) or both (which releases both bombs simultaneously). Then arm the bombs wiht the bomb arming switches (set them to arm, not to chem release). Then try pickling them =)

My #1 feature is integration with AmBX, so that when I flip the fan switch, the real fan on my desk turns on, cooling my face and helping me fly! In all seriousness, a real flight manual would do so much for me right now.

Works perfectly! Thanks so much!

Riddle me this: Why do I have such drastically different engine power outputs and temperatures? Both engine condition levers are set to normal. Is there something I'm missing, or is this normal?

Yeah, I've never had a problem with your other mods. Sadly, this one just does not want to work correctly. Would you mind terribly uploading the entire cockpit zip so I can try that? Thanks =) Edit: The new zip you PMed me worked great! Thanks so much!

This exactly. Also, thanks GregP, I'll give it a shot =)

Windows explorer. 7zip refuses to add files to the textures zip; it says, "operation not supported".

Not working for me. I make a copy of MI8MTV-STND-TEXTURES.zip, set it up in JSGME, paste in the replacement textures, and boom! black cockpit with no textures. Of note, the file I'm downloading is 14.8MB, not 15.2. Am I getting the wrong file somehow?

TARS isn't, perchance, working in the Hip yet, is it?

Make sure you're setting the 4-way switch to whatever you're trying to fire (800, 622 or 624). Also, ensure that your pod variant knob (to the co-pilot's right) is set correctly (I, V, or all the way right) I'm not at my computer now, so that's all I can think of.

If you're unfamiliar with editing the input .lua files, take a look here. That's a guide I typed up for the P-51D, and most of it carries over. I'm going to try to impart what I've discovered so far about the Hip's somewhat confusing controls. First off, anything that's not in clickabledata.lua won't work using these methods! You can still map these through the config menu, but this thread will address the clickable things in the cockpit. For some odd reason, the left and right engine throttle controls are not clickable, and thus, this thread does not apply to them. I haven't figured out how to get them to work as a 3-way with the ENG OPER switches on the TM Warthog throttle. In clickabledata.lua, you'll find different control types, starting around line 20. I'm going to step through these to explain how to set each of them up. Buttons First off, we have buttons. They're simple - they're either pushed in (1) or not pushed in (0). Example: APU Start button If we look in devices.lua, we find this in the 3rd line of devices: So our cockpit device id is 3 (because it's the 3rd in the device list). Put that together and our throttle.lua file looks like: 2-position switch Next in the list is the 2-position switch. It has 2 possible values: 0 and 1. Practically speaking, it's set up in the same way as the button, so I won't clog up the page with duplicate info. 3-position switch Ah, the bread and butter of throttle.lua modification! These guys are great. They have 3 possible values: -1, 0, 1. These typically correlate to down, middle, up, but not always. Trial and error is key: if you map the switch and it's backwards, swap your -1 and +1 values. Example: Rocket series quantity (8/16/4) on the boat switch. Devices.lua indicates that WEAPONS_SYS is device #12, so our throttle.lua reads as follows: See the positive and negative values bolded there? Multi-position switch There's a few of these around. The most important one for me is the GUV mode switch (the 800/622/624 one). I have this mapped to the DMS on my TM Warthog stick. Up is up, down is middle, left and right are down-left and down-right. In clickabledata.lua, multi-position switches are declared thusly: This is important. As you can see, we have two new colors to worry about. Count is the total number of positions the switch has (4 for the GUV switch, 6 for the pod variants switch, etc.), and delta is the value that it counts in (0.1 for both of the above examples). So for our example of the GUV switch, we see this: This means that the GUV switch has 4 possible values: 0, 0.1, 0.2, 0.3. You can assign these to any controls you wish. It will take a little bit of experimentation to figure out what value correlates to what position, but here's the aforementioned DMS mapping: You can thank DCS for ordering it all screwy-like for me. Multi-position switch, limited There's only one of these so far: the static pressure system mode knob in front of the commander's left knee. I don't know how it differs from the normal multi-position switch, and I'm not too worried about it. If someone else is, I can try to figure it out. Radio wheel These little bastards had me going for quite awhile. I think I've got them cracked now. We'll reference clickabledata.lua again to see how these are declared: As you can see, we have two buttons to worry about now. But which one do we use, you might ask yourself. Fear not, for my blood/sweat/tears have led me to deduce the following: You use command_1 to decrement and comand_2 to increment. Simple, huh? These guys are only used for the R-863 frequency knobs. I have mine mapped to the 4 rockers on my right-hand TM Cougar MFD (aka F16 MFD 2). The rockers are buttons 21-28 in pairs (odd number = rocker up, even number = rocker down). Let's get to it. Okay, so we've got even-numbered buttons ((300)6, (300)8, (30)10, (30)12) that are used to decrement the knobs, and odd-numbered buttons ((300)7, (300)9, (30)11, (30)13) that are used to increment them. That means that the value_down for the even-numbered buttons is -0.1 and the value_down for the odd-numbered buttons is 0.1. Open up devices.lua and you'll find that the cockpit device ID is 38 (or, if you're me, you'll miscount twice and pull your hair out trying to find out why it's not working). This gives us the following: Important notes: The left and right engine cutoff valves (cockpit device id = 3, buttons = (300)9 and (30)10 (respectively), value_down = 1, value_up = 0) DO NOT WORK CORRECTLY for me. They switch on and off just fine, but if you click them with the mouse and then switch them again, they toggle incorrectly and then you can't click them anymore. I don't know why, and I'd appreciate if someone could please confirm this for me. I haven't delved into button-axes or axes in general yet, because they're easily mappable through the normal config screen. I think that's pretty much it for most of the common controls. Questions or comments?

Confirmed again. Is this how it's supposed to work and we just have bad control entries?

Confirmed again. Is this how it's supposed to work and we just have bad control entries?

This is the correct question. Anyone remember Jazz Jackrabbit 2? =)

I know, for I, too, was expecting the helicopter to go up in a thermonuclear blast NCC 1701-style. Does it perform a similar function to the ATGM emergency jettison arm switch in the Ka-50 or am I completely off base? While I'm asking questions, do we have an English flight manual yet? No, not the real one they borrowed, but one written for the sim that assumes we haven't already had ground school and that I need a lot of pictures?