Floyd1212

Sounds like a control bind issue. Maybe your trigger button is setup as a modifier in conjunction with some other axis? Or double-bound with Force Trim Release? Does this happen when you give George permission to fire, or only when you fire the weapon yourself? Like MAXsenna said, capture the event in a short track file and post it here.

Two things to consider here. 1) Selecting MSL on the WPN page is not the same as Was'ing missiles with the Weapon Action Switch. You may have done so during your engagement, but didn't explicitly mention it in your description above. 2) More importantly, it doesn't appear that you have any RF missiles left to shoot. It looks like you have fired 4 missiles, and the 4 remaining on the rail are SAL laser-guided missiles.

This has always been the case. I just checked it again now, and when I swapped to the front seat the "Boresight IHADSS" message is not there. That's not to say that there isn't a problem with alignment when using the IHADSS in the left eye. I could see George boresighting for the right eye, then when you swap seats and use your left eye, things are off. I use TrackIR in 2D myself. If you use the right eye, does everything work properly?

Yes, if you start the aircraft from the back seat, and let George get through his startup routine up front, you don’t need to boresight again when switching between seats.

In my experience, trees in DCS are mostly just cosmetic. FCR can see through them George can see through them You can IAT a target, and then continue to track a moving vehicle through them You can lase through them SAMs can track you through them And in some cases, missiles can pass through them and kill you

I don't think anyone has been complaining about that type of issue. Maybe some sort of hardware issue? Where are you taking off from in those screenshots?

Select HMD as your Sight.

Next time you go to fly one of those missions, grab a screenshot of the PERF page before you lift, and then post it here.

I'm not familiar with the campaign, but what is your altitude and temperature at the airfield?

Not yet. You can see it is still on the ToDo list here: https://forum.dcs.world/topic/318054-dcs-ah-64d-roadmap/

I know there was something mentioned in the recent patch notes about "optimized build of ground unit routes" but I am still seeing a lot of issues with pathing for on-road routes. For example, along this one section of highway I am seeing three segments that it won't route vehicles through: At 32 U NB 48231 33379 At 32 U NB 50013 33743 At 32 U NB 61160 29189

Yes, that is a temporary workaround while working in the ME, but the issues needs to be resolved by Ugra. If a better solution is going to take a while, I would suggest removing them altogether until they are ready to be implemented properly.

I just checked for myself and also see the issue. Rocker down works fine. Rocker up slowly and it seems to be reliable, but click it too fast, and it jumps to Preset 1.

Do you mean when clicking the rocker button with the mouse in the cockpit, or when using a bind on your HOTAS for those functions?

I'm going to be honest, I did not read all 248 pages of this thread, but I did do a quick search for "S350" and didn't see anyone discussing the issue I am having... Some of the people that fly in my helo squadron are experiencing FPS issues when looking in the direction of an S350 site. The site is still 100km away, but frames drop to 10-15 fps when looking toward it, and come back to 60 fps when looking away from it. More than one squad-mate have described this to me. I don't see the same issue on my machine, but I have experienced issues after launching a Hellfire at the SR or STR from an Apache. I can spot the radars in the TADS and lase them, and everything is fine. But as soon as I rifle, my FPS drops to single digits for as long as the missile is in flight. Then when it destroys the target, my frames are back to normal. Anyone else experiencing FPS issues related to the S350 assets? EDIT: The next post from SizzlepopBACON is from one of my squadron-mates having the issue...

To check if your boresight has been performed accurately, set your ACQ to TADS and tell George to slave to your LOS and see how far off the cued reticle is from where you are looking. If you have boresighted correctly, the dotted cross should alight with the solid cross exactly.

It has done this for me since day one. You request repair and you get the 170 second countdown. At the end of the countdown when the actual repair starts, the helo levitates 3 feet off the ground and the access panels open up. When the repair is complete, the helo drops (literally) to the ground looking brand new. I assume it does this so that in the event you got repairs with any of the gear missing or damaged, the wheels are properly setting on the ground surface when the repair is complete.

The laser on/off bug, and Geroge not ready to slave to PLT LOS, have both been fixed in the last patch for me. Try it in an Instant Action mission and post the track?

Yes, if there is a way to reduce the saturation in the Moza software, that might work, but DCS needs to be configured for 100% saturation.

Can you post a screenshot of your binds for the power levers, to and from Idle?

We’ve seen this issue in missions on other maps when GPS is not available. I’m not entirely sure how this results in the symptoms you experienced, but forcing “Unrestricted SATNAV” in the ME solves it. I think there is a way you can save/edit the instant action missions to fix it yourself, but sounds like ED needs to address it in a future patch.

Forgive me if I get my acronyms wrong, but what we are discussing (complaining about) here is the way the Yaw Channel of the SCAS is behaving when it is trying to help control the yaw of the aircraft. When you hold FTR for significant maneuvering, you are disabling (or at least reducing) the assist the SCAS system is providing, so of course you won't see the problem while you are holding FTR. What we are seeing (feeling) is overcompensation in the yaw channel when making small adjustments with the pedals while not holding FTR. For example, while rotating the aircraft to a new heading while in a hover, with ATT Hold enabled. Thanks!

I like how the early results of the poll show 50% of users (4 out of 8 votes) are running a FFB setup. Sounds like a bunch of FFB elitists rushing in to make sure everyone knows how awesome their setup is. And yes, I am also running a VPForce.

This may be related to the other bug of not being able to get the laser turned on from a cold start. If you switch to the front seat after letting George get his crewstation setup from a cold start, you see that he has the "grayscale" color bars up on the IHADSS. These color bars are turned on with the L6 button on the WPN page. If you turn this off, George will resume slaving to your LOS again. However, you can't get the laser turned on using L6 on the WPN > UTIL page. George says he is lasing, but the laser is not activated. Is it coincidence that he manages to get the color bars on from L6 on the WPN page during his startup routine, but can't get the laser turned on from the L6 button on the WPN > UTIL page? We have seen other bugs in the past where button presses on one page impact functions in the same spot on other pages.

I totally get that there are a ton of variables and aircraft to test to make sure things are still working for each patch release, but there has got to be some sort checklist of the bare essentials that need to be tested before signing off on a patch. And you would think having George be able to rifle a Hellfire at a target would be on that checklist.