Sandman1330

Good point! I’d have been dead then ;) That being said, I would imagine he had capable AWACS and wingmen / other assets to help. We have DCS AI... :megalol:

Yeah, tried that. He misses then carries on to the target, my sparrow misses, then I end up in a turning fight with 2 migs while carrying 4 Mk84s. I manage to kill those 2 alone, then another one always sneaks up on me. Gotta love DCS AI! ;)

I can't even get to the target. MiGs get me every time, wingmen are useless, MiGs dodge my sparrows like they don't exist. I end up taking on 4 migs by myself while my wingmen do nothing to help.

Thanks for the mission Wags, love the concept! One suggestion: It would be nice to start a bit further back. I don't even have time to set up the cockpit (like turning on countermeasures) and build at least a base level of SA before I'm already in a turning fight. Otherwise, looks interesting (if I can ever get past the getting killed stage)

Mini joysticks work for me, you have to bind them in the axis commands, horizontal and vertical separately. So you’ll see slew vertical and slew horizontal in the axis commands, you can bind those. The one on the stick I set up in the Logitech software to do button presses so it can be used for hornet wpn select and A10 CMS

Haha, so true

Same, slightly off. My X55 was aligned nicely. A bit annoying when walking the throttles, I always end up with one engine higher and the associated yaw

Looking good! Single core performance on par with the 9900K in an early sample, with much lower power consumption. Release versions could even be higher... https://www.tomshardware.com/news/amd-ryzen-7nm-cpu-radeon,38399.html

Glad you fixed it!

I had a similar issue, does it look like this? https://forums.eagle.ru/showthread.php?t=227481

I am soooo waiting... got my AM4 board and first gen Ryzen just waiting for a new 3000 series chip! I recommended AM4 just because it’s the best bang for buck right now, if money is the issue for him.

Throttles should be x and y axis, just ensure they are bound to left and right throttle in axis commands. There’s a separate column for stick and throttle, so select the box for left throttle in the throttle column and bind the left one, same with right, and it should all work. Toe brakes are same, just ensure you are in the pedals column. Also note they probably work as an axis (not sure which ones you have), so bind them to left/right toe brake axis. You may need to reverse the axis in the tune option if you find they stick on with no pressure on the pedals.

Little is known about what ED is developing, but I wouldn’t be surprised if it encompasses all or most modules in one campaign. I would hope it offers a variety of missions for different platforms within the overall campaign to choose from. Pure conjecture on my part though. Most user made DCs can only use one, but they are limited by the ME and LUA scripting that ED isn’t.

Highest clock speed you can get within the rated TDP of your motherboard. FX9590 if your board can power it, FX8370 or FX8350 if it can’t. Either way, performance will be limited. Probably better off buying a cheap B450 mobo and Ryzen 2600 and overclock, for around the same price as that FX9590... and the electricity savings will pay for itself! :lol:

What it sounds like you are asking for is a dynamic campaign, like that other F16 sim. ED are actively developing it and are quoting some time in 2019 for its release, though I think it will be late this year if we get it in 2019 at all.

Super weird. Sorry, got nothing to suggest :dunno:

Your copilot and door gunners in the Huey can be killed. They slump over in the seats and don’t shoot / aim their guns. Jester would be infinitely more complicated but I think the mechanics of it are there.

Not really... Rift spec says 110 degree FOV. For NVG, I think it’s 40 per eye, but due to overlap I don’t think that equates to 80 degrees. From a subjective point of view, with hundreds of hours flying helicopters on NVG, I can tell you the rift FOV is significantly more than NVGs.

One thing I have noticed is that stick is not necessarily the first column in the DCS control setup. In fact, the order of mine from left to right is throttle, pedals then stick. As the column titles usually cut off the full name of the controller, mouse over the heading to get the full name and verify that you are trying to bind the correct controller. Remember to click the cell in the correct column when you are binding the axis. It sounds to me like the columns are reversed.

Didn’t know that! But it makes perfect sense, I am hoping we will get them in the helicopter community, peripheral vision is so important for us. The weight will still be an issue though...

I used 2 X55s and loved them. If you spend a half hour and crack open the throttle to tape up the wiring (before it becomes a problem), they last. I used each one for over 2 years. They do have some well documented issues, but there are fixes for all of them. Aside from this there are obviously one off problems, as with any other product. The warthog has issues too (just look at all the frustration about the TDC controller for the Hornet), and it costs twice as much. For what you get in terms of button selection and software control, the X55/X56 is a great setup for the price. Try one out before you bash it. But back to the point of my post, my X55s did not have this slop in the middle. Everything else about my new X56 (it’s the new grey Logitech model) has been great.

The FOV for standard binocular NVGs is only 40 degrees. 4 tube panoramic NVG expand this to around 90, but are only in use by a very small subset of the community. The rest of us fly behind binocular NVG.

Tell Meg I love her! So I wasn’t the only one who thought this might be an Easter egg??

Nope, they don’t all click. Just pressure on the two thumb hats is usually enough, they move but don’t click.

Noticed it in the A10, though I never thought to shut down the engines to see if it’s still there. I just thought it was the sound of a pump or something that they added... it sounds like a fuel pump to me.