frostycab

Try to remember to include a track. Without being able to see specifics nobody is going to be able to help or see what the problem is.

Bear with me on this. When in the CPG position in FLT mode selecting George right-short commands him to turn to a new heading that matches your LOS. In CBT mode the same command tells him to fly DIR/RTE. My thinking is that these 2 commands are the wrong way around. FLT mode seems more directed at getting to a waypoint or following a route. In CBT mode you're more likely to want that quick turn to a specific heading either to point your nose at a target of opportunity or to quickly evade behind a hill. Yes, I know we have the Left/Right 90 degrees and the 180 turn available, but this would be more precise and flexible I think. Just curious if this was a deliberate decision and if so what the reasoning was behind it.

I think you need to use the cyclic keybind. I'm sure I heard somebody from ED say that the "/" command only works on the ground.

I've noticed this problem too. Flight members will respond to commands to change formation, but I haven't seen them fire a single shot yet.

After flying for quite a while the CLOS on the PLT HMD with TADS as ACQ moves to the right spot, but the TADS video feed does take an extraordinarily long time to slew onto the target, and the delay before getting the solid launch box seems to increase with time too. This means that George takes a very long time between assigning a target to him and actually being willing to fire. Quite often if the TADS video is on the target and George is falling behind I'll just WAS the missiles myself and fire.

I had my right stub-wing blown off by enemy fire today. Whole wing and weapons were visibly missing. As has been already mentioned the WPN page does not reflect this, and the weapons still appear as available. Sadly, the next Hellfire that was cued up for launch was on the right wing, and I couldn't find a way of stepping to a missile on the intact left wing. The "new" bug that I've found is related to rearming. I headed off to a nearby FARP, forgetting that I couldn't repair there, so after landing I just opted to rearm to see if I could still use a full load on my left wing, and also to see how the WPN updated. Surprisingly, I was able to load a full set of Hellfires onto both wings. The missiles and launchers were visible from the cockpit and external views even though the right wing itself was still absent. Even more surprisingly, when I ventured back into the target area the Hellfires on the right side were fully functional. I did save a track, but it was very long (over 20 minutes before reaching the target area). Sadly it seems to be of little use, as the aircraft flips over and rolls into a mountainside shortly before the wing gets blown off.

They might well do exactly this, but things take time. Right now I imagine they’re 100% focussed on squashing bugs that detract from being peoples’ ability to fly and fight effectively. After all, it’s not like one dev is going to get all that set up and running in an afternoon.

I’ve developed a habit of setting my gun range to 800 when I fly in VR. That’s about the point where targets are close enough that I can see them and hold my head steady enough to get a good burst off at them.

I think Wags spoke about this in one of his videos. The ASE sensors are unable to distinguish between a friendly missile launch and an enemy one, which I believe is accurate. How could the system possibly tell the difference? AFAIK the system merely looks for the bloom from the missile as it launches. It’s down to you to decide if it’s a threat. This is why he recommends keeping the CMWS in BYPASS when there are other missile-equipped friendlies in the area.

You need to deslave and then reslave every time you switch target points. The TADS doesn't automatically slew from one to the next when you select them. No idea if this is correct behaviour or not though.

Range display on the WPN page always shows your last commanded MAN RNG. This is because this is what the gun will default back to if you deselect and subsequently reselect it. To check that you are in auto you need to look at the range display on the left of the field of regard box on your IHADSS. If it reads “Ax.x” then you’re in auto.

Try POINT - IDENT - Txx - DEL - YES. Not at PC right now but I think that’s the sequence

Have a look at the first post in this thread. Hopefully it can point you in a useful direction:

DISCLAIMER: I am an uneducated technical idiot, but I'm going to try and offer a suggestion. Do the luas that are used for the Streamdeck plugin not contain the required information? I've managed to use them successfully with my Streamdeck but have no idea if any of that would be relevant to other exports to other devices.

It's not really a "bug" as such, just a planned/WIP feature that isn't ready for implementation yet according to ED. Unless things have changed since I last flew the Hind dear old Petrovich suffers from the same limitations when searching for targets (which is much more serious as you have no video image to help you ID for yourself.) I'm sure that once it's all ready it will work very nicely indeed.

Following up on the reference to civilian aviation it is common practice when given a change to a new frequency it will be tuned on the standby frequency, not the active, and then swapped over. This way if there is no response on the new frequency or you've set the wrong one you will still have the last frequency available to swap back to in order to confirm or get new instructions. Its a sort of failsafe procedure so you don't forget the channel you just came from. I don't think you can do this in most of the DCS aircraft though.

I want to zig-a-zig-ahhhh!

Just because nobody asked for it doesn't mean nobody will want it. Well done you!

Which software is driving your VR? If it's SteamVR then you can go the menu and enable "Display VR View" to get it to open on your monitor. From there you can select which eye you'd like rendered to the screen and then screenshot that.

Hmm, not sure. Have you updated again since last Friday's April Fools patch? (I'm joking, ok?)

It does a bit. It only starts to get bad at 135ish. Perhaps RBS was the wrong term. What I was trying to suggest is that at higher speeds my limited knowledge of physics suggests to me that there will at some point be a perceivable lift imbalance, evidenced by OP saying that the roll always seems to begin towards the retreating blade side.

I don't notice it until I'm pushing 120, but given the direction of rotation of the main rotor I assumed it could be down to retreating blade stall. Calling all knowledgeable people! Enlighten me!!!

You should see them in VR! Jokes aside, I've had a problem with horizon lines in all of the HMDs on different aircraft. Really noticed it on the Hornet, and no matter how many times I'd run the alignment it never improved. I just thought it was me doing something wrong.

I'd be happy if he could just tell the difference between the ring of identical SAM launchers and the big-ass radar sat in the middle of them all!

This is one of those things that sounds like either way could be right. If the ASE always showed radar signals such that they correspond to your map settings then for some people I can see how they might find that a good way to maintain situational awareness on the map. However, from a personal perspective having the ASE show signals that correspond to the verbal warnings by referencing the your own 12 o'clock perspective it could cut recognition and reaction time down slightly. To my mind the behaviour seen in your track makes sense if audio warnings use the clock-type of callout. Had they opted to call out a bearing or even a cardinal direction then perhaps the other way might make more sense to me. Sounds like this is one for the SME's to weigh in on.