fullcoupe

+1, with accurate sounds please so I can do this all day:

AI is a big one for me since I fly mostly SP. On that same note, improved comms and ATC logic are a close second. But as we know that is in the pipeline... And the A-10C refresh. :smilewink:

Hmm...I'm on the same OB version and I still just get the initial chatter. I don't see it on the change log either. IIRC, the comm update in the last OB was somewhat unintentional to begin with...

+1 ATC has been one of the itches I couldn't scratch for quite a while. Glad to see the improvements making their way in... Thanks ED!

I just noticed the same thing. Mine just seems to extend/retract on its own until I switch the battery. A toggle for it would be nice IMO.

Very helpful tips! I will give these a try! Thanks Ironhand.

I recently started getting back into some of the FC3 jets and I'm having a blast with the Su-33. The one thing I'm struggling with is landings, or, at least landing with any sort of precision. I'm really used to the Hornet and other jets that have a velocity (flight path) vector in the HUD - which allows you to get a general idea of where you're going to touch down. In the Su-33, I can get on a good glide slope and maintain my AOA with ease, but trying to determine my landing point is a crap shoot because the HUD seems to lack any sort of flight path indication. I'm always under/overshooting - which is kinda crucial when it comes to landing on the ship... Any tips/tricks on this? Reference points maybe?

Can't speak to the nozzle behavior, but I've always felt it takes a lot of throttle to get the Hornet rolling, even with a clean loadout. The AV-8B, Mirage, A-10 all require very little input to move forward. IRL pilots have also made comments that the first half of the throttle range not being effective enough, whether it's in the air or on the ground.

Mirage. Especially from cold start. Chuck's guide usually comes out every time...

x2. Just a triangle between North Island, 29 Palms and MCAS Yuma would be more than enough to tickle my fancy, if DCS ever decided to do another training area. Vietnam and North Africa would be cool additions. Maybe Somalia too.

I'll +1 this. The AI behaviors have been a thing for a while. AI and ATC/comm improvements are both at the top of my list in terms of World itself. Just the other day I sent my #2 RTB to Creech, and it starting zig-zagging, rolling back and forth, and bringing the gear/up and down repeatedly, before eventually turning into the side of a mountain and crashing. :lol: Aside from obvious fixes, my wish list for improvements would be: Ability for lead to select a takeoff type once cleared for takeoff (section, indvididual, interval). Right now you can only perform section if you start your flight hot on the runway. Logic for AIs to follow and repeat a basic landing pattern. Useful for our new Navy toys and FCLPs. Even better if they could follow it off of a break. Ability for AIs to follow (ghost) the lead's exact flight path. This would be handy for low levels and would solve the issues around terrain following. AIs taxiing on their own once the lead has been cleared. (probably an ATC-related bug) This drives me absolutely nuts!

Not entirely. I keep mine attached to my seat via velcro so it's always in the same spot. Some people also hook/hang them, or keep them strung to their wrist. Not sure about the Vive, but the Oculus software depicts where your controller is (in the form of a hand) in the 3D space, so even if you threw it across the room you could, in theory, go find it without taking the HMD off. In my personal opinion, if you're focused on flipping switches in a dogfight you've probably already lost. This is another reason for a HOTAS system, you can toggle master mode and select your weapon in a second, and know confidently what you're pressing without having to glance down at the stick in the cockpit. :thumbup: +1 to this, with a HOTAS there's a minimal need to even pick up the controllers, except maybe for switchery during startup procedures. That's the very definition/purpose of a HOTAS.

With my Rift, I use the touch controllers to manipulate the cockpit switches and functions and they work great! I don't think you would be disappointed. It is really immersive and highly detailed. However, I don't believe they work to "grab" the throttle and stick: https://forums.oculusvr.com/community/discussion/64452/dcs-and-joystick I'm not sure why you would want that, I would throw down for even a cheap HOTAS or joystick before going that route so at least you have some degree of feeling. It's even more essential when it comes to precise flying (formations, carrier landings, attack runs). Having a few physical switches is also a benefit, for common 'back of the hand' tasks like gear, hook, flaps, trim, master modes, FCS reset, etc. That's my personal opinion though.

Not sure if this is a wish list item or if I'm just not doing something correctly. Is there a way to activate the integrated smoke with WoW? I know the Angels test it before/during taxi and again just before the takeoff roll. I can only get it to activate while airborne.

Since I've been using VR, the A-10 cockpit just doesn't feel like the -18, which is expected considering the module was designed pre-VR. Perspectives and depth just seems off. Some updates to the cockpit (which IIRC are somewhere in the pipeline) would be welcomed, and would definitely get me flying it more. That aside, the A-10 is still a blast to fly even though it's not as fast or maneuverable. It keeps you in the combat area much longer, which means more play time with targets and that's the fun part. I don't really care for the CM system on the Hornet. The A-10 has a quick and easy interface for both programming and modes and I do miss that sometimes. Not a fault of the aircraft, but I just dread tanking via the basket (also a gripe for the Harrier and M2000). The boom is so much easier to me. That's another thing I miss....

I've been eyeballing the Dell UP3216Q and UP2718Q (both 4k), personally. I've always had a great experience with Dell displays - at least the higher end ones. If I didn't use the same PC I use for work (which is mostly photo editing), I would probably go ultrawide for additional FOV in DCS. I get what you're saying about the shallow aspect ratio, but I think if you tinkered with the view settings it would be fine.

I would love to go that route but unfortunately the 2080Ti is too much of a leap in price. $600+ is already too much, even though it seems to be the new norm. Doing further research, the benchmarks between the 1080Ti and the 2080 (non-Ti) seem pretty marginal - but the bottom line is that there are still improvements even at 4k. May be answering my own post here, but I'm leaning towards the 2080 considering the prices of the remaining 1080Tis are on the rise. Why not have a newer GPU with faster/more efficient memory, rather than one that is nearly 2 years old?

Hi guys, After around 5 1/2 years, I'm planning on retiring my current rig. I used to have an upgrade cycle every 2-3 years, but that was back when this stuff was a lot cheaper. :lol: Currently I'm on an i7-4790k with 2 GTX 680s. I use a single 30" display (resolution 2560x1600) but am thinking of going to a 4k display in the near future. I used to play a lot of the latest games, but now I primarily just fly in DCS. The rest of the computer's use is photo/video editing, which I'm not concerned about as my current setup handles that just fine. I've got most of the components figured out and budgeted, I'm really just stuck on the GC at this point. My question: Considering the 1080Ti in its remaining availability is going for anywhere from $600-800 depending on luck - is it more worthwhile to seek the 1080Ti or would it be wiser to go with the newer GPU (2080 non-Ti) with 8GB for roughly the same price? I know either one will be a huge improvement, but I really don't know how much DCS leans on the graphics memory, nor how much DCS would take advantage of the new GPU. :dunno: Thoughts?

I'm on 2 GTX 680s still. No complaints here, w/ 1080p and medium-high settings all around. More than flyable. I do plan to upgrade before the end of the year, though. I'm past due, I used to upgrade every 3 years or so, but that was when this stuff was a lot cheaper :lol:

Yes, seeing the same condition here as well. Definitely not right...

Agree with the OP on this one. The strobe in the game has too slow of a pulse. IRL it blinks much faster and brighter. The nav lights on the fuselage look like they are painted red/green when on - hard to tell that it's actually a light. The white light on the Vstab seems about perfect. And yes -- the landing light is way too visible during the day. The A-10C has the same issue. May be the tradeoff to get things looking right at night when the lights are really necessary.

They do seem to be a little less effective than desired (especially if you REALLY needed to stop in a hurry), but that's only coming from comparison vs. other DCS aircraft and my own feeling. In a normal scenario, though, I find it's sufficient - I've never had trouble getting down to taxi/turnoff speed by the 2/3 or 3/4 mark. On runways, deploying the speed brake, full flaps (if not already) and pulling the stabs all the way up helps slow the jet tremendously. You can also use a little L/R deflection on the stabs to make micro-adjustments and keep the jet on center, down to a certain speed anyway. Common practice for field rollouts IRL to minimize wear and damage to the brakes.

I'll echo that...great to see the open communication and fast responses to user feedback! Keep it up ED team!

Out of curiosity, has anyone found the throttles on the Hornet to be a little ineffective in the first half of the band? I'm using the TM Warthog HOTAS and haven't messed with curves or anything yet. Saturation is 100%. I notice it most when I'm taxiing around. I have to push the throttles over half just to get the A/C to roll with no loadout and minimal fuel. In most other sim A/C it seems like just inching the throttle forward should be enough thrust to start a roll. Is this true to the Hornet IRL? Also, has anyone with the TM Warthog found the need to tweak their throttle settings, specific to the Hornet? If so, what changes have you made?

Has anyone come up with a solution to this?