Chump

@leonardo_c, I noticed that you are initializing the FACs as BLUE_FAC_POINTER=1651 and BLUE_FAC_AXEMAN=1652 in Caucasus_Pendulum.lua, but the mission briefing has the laser codes the other way around (POINTER=1652, AXEMAN=1651). BTW, love this mission! :)

I use the "single directory" method for all custom liveries, explained here: https://forums.eagle.ru/showthread.php?t=174462

I had this thought for a while. I put a script together that allows the use of mark panels @ https://github.com/chump29/DCS_Mod/blob/master/seaEagle.lua To use it, include the MiST script before this one in your mission. In game, create a marker with the word SEAEAGLE in it (case does not matter) and it will detect and target a random ship group within 1NM of the marker. Feel free to use it how you want, or make suggestions.

x52 (non pro) to WH here. I spent too much time clicking with the mouse or fumbling with the keyboard instead of flying. Having the additional inputs greatly increased my HOTAS time. It's not perfect, as many will say. But, it's a giant step in the right direction for me. </2¢>

AFAIK, ships do not have the capability for a homing beacon (not even in LUA). I am sitting here wondering if maybe you can put a HMMWV/etc. aboard a ship and have that transmit something that an aircraft can pick up and home in on?

I came from a X52 (non-Pro) and love it! I bought the green spring for less resistance. Simple to install, makes a heck of a difference if you don't have an extension and aren't used to how stiff the WH is out-of-the-box. I have a decent slew setting figured out. Who knows if I'll upgrade that later on. If you are flying a newer airframe, you need more inputs than the lower-tier joysticks provide (for me, to make it truly HOTAS and get the mouse out of my hand). I bit the bullet when things weren't on any kind of sale, and I still don't regret it! Jump on it while it's on sale and your significant other will be easier to woo over on the purchase price. I can always replace the stick, gimbal, or both if I'm not satisfied and want to make the leap to Virpil or something even more top-shelf. My options were limited with the x52. The WH opened up the world to me. The value I get now when flying was worth every penny. </2¢>

Bah Humbug! lol The breaking of lights is a tradition around here. Pissing people off is a tradition around here when referring to the breakable Christmas lights. The only unity we have between the Christmas-light-breaking-people and the Others is that there are Christmas lights to break! <chant>Bring them back!</chant>

You will need to look into other springs if you want the stick to be less pressure. https://warthog-extensions-by-sahaj.com sells a green spring if you want less tension and do not have an extension.

I find that the newer ReShade causes only a few FPS to be lost, as opposed to the older versions where it was noticable. The newer DLL is optimized much more for DX11/12, even rewriting most of the plugins. Give it a try and see. If it hinders you too much, let him know. I would recommend ReShade vs. oppose it.

Chuck usually specifies what the curves should be set at per airframe in his guides @ https://forums.eagle.ru/showthread.php?t=135765

By the default config, the switch is in the center (lights off) position when you get in the plane. Try to bind a keyboard key to HOTAS Pinky Switch Aft and, when on, the switch will be in the "Lights according to Panel" position (p.160 of flight manual) and you'll be able to configure your light settings on the Light Control Panel as-desired.

It does not sync the flaps and throttle in the A-10C when using a WH.

The stupid flaps and idle detent do not register when you cold start the A-10C. We've all known this for a while, and it has to do with how the buttons are set up by default. I got tired of constantly flipping my flaps switch up and throttles to the stop position each time I cold-started a mission. I searched a bit and didn't come up with an answer. If it's been covered before, I apologize. I am currently using a custom script to handle events (missile trainer, etc. since I mostly solo). I made a new handler for S_EVENT_TOOK_CONTROL: if event.id == world.event.S_EVENT_TOOK_CONTROL thenInside of that, I simply checked to ensure that you are actually in an A-10C: if string.upper(event.initiator:getDesc().typeName) == "A-10C" thenI have a function as follows that will handle the needed click event: function click(dev, cmd, arg) GetDevice(dev):performClickableAction(cmd, arg) endAnd now the click commands that I want to execute in the cockpit when I join: click(39, 3002, 0) -- flaps up click(1, 3017, 0) -- l eng start off click(1, 3018, 0) -- r eng start offThis simulates the flaps key being put into the upper/raised position, as well as each throttle being pulled back over the idle detent. It seems to work great. When I now join a cold start mission, my WH throttle is actually in sync with the cockpit. Thoughts/comments welcome. :pilotfly:

I recently got a WH (and would never go back). I upgraded from an X52 (non pro), along with Saitek rudders which have been serving me fine for over a decade. I don't have the largest monitor. I immerse myself into DCS using TIR (4 even). I would probably love VR, and my PC would probably appreciate the usage it was made for. Unfortunately, I have hesitations. I wear glasses. I sweat. I don't have the ability to stand long periods. How is VR for those of us that have everything going on that VR doesn't address yet? I heard that you can get prescription lenses, and mod fans into the headsets (not talking about any VR in particular, just listening). I want something that is flushed out for everyone. I just figured that it would be a few more years before it got anywhere near usable for me. Am I right on that, or am I buying into rumors and scare tactics from the TIR guys (joke)?

T&S 97713 Kansas USA

I have not noticed that OVGME cares what type of storage device it uses. It would be much faster on SSD or RAID drives.

Try this one (see attached). I put it in OVGME format so that the directory structure would be retained. NOTE: This is will not pass IC Colored MFDs.zip

Someone has a case of the Monday's...

If you have bonus points that are about to expire, this is the perfect thing to pick up (got $15 off this way).

Learn to use the mission editor and make your own missions that suit your playing style. That's what some of us do. Remember, this is not a polished off-the-shelf game. It is more of a sandbox of what-ifs. If you can't find a map that has/does what you want, you can make that happen in a short time and be flying before dinner. Personally, I had some problems with the Gazelle at first, but after months of practice, it's now like mowing the lawn (but with armament).

DonH, I'm curious as to what settings you found most effective?

Is it possible to add C-101CC to your missions?

I tried using BEACON_TYPE_VOR_DME and distance was not picked up by the CC. Is this a known ED thing? Maybe not fully implemented?

I cannot set my altimeter/encoder in the CC to 28.82 inHg via mouse wheel scrolling. Just kind of skips over the 28.xx range. Is anyone else seeing this issue?

There is no setter for mission time as far as I'm aware. It is stored inside the .miz file, and read upon mission load. You would need to manually edit the mission file each time before you started it up.