NeMoGas

Yeah I have had this happen also. Things like the observe switch will not work using my keybinds. However I can click the observe switch and it works. There are multiple other desync issues like this if you spawn immediately into a new Hind as the gunner when the pilot clicks refly. One such desync is that NVGs won't work until you go back to spectators and jump back into your friends Hind, sometimes even having to do this twice. My work around is basically what you already found, except many times I have to do it twice to become fully synced. I go to spectators after we die, then wait until his engine is running so the rotors are synced. Then I join as the gunner and usually everything works fine, except NVGs which then require me to jump back to spectators again and rejoin for a second time. Once I do that dance everything seems to work ok, usually.

I have an issue where first joining the CPG seat in another players Hind usually means NVGs won't work. If you go back to spectators and then join the CPG seat again the NVGs work. This is basically part of the dance I do when playing CPG with another human player online.

I would like to ask for a special option to disable the red "steering helper" arrow by default. I always have to manually disable it when I jump into the gunners seat because I use my stick and not a mouse for aiming. This would free up a button on my HOTAS and remove one more step when aiming down the sight. Thanks

So wondering if anything had changed with the UH-1H I went and tested it, and it appears to also have a functional WSPS. You can see near the end of the video that I got a little to low and the wires did break off a piece of the main rotor. I also tested the Mi-8 and even though it has no visible WSPS it is also capable of cutting the wires. I guess this must have been a global change to DCS helicopters? I will have to try the Mi-24 and Ka-50 next. Edit: So after testing the Mi-24 and Ka-50 it appears that all helicopters have this ability in DCS now, at least when testing in the ME.

I have not tested the UH-1 in a long time but the last time I did the only helicopter that could do that was the Gazelle. I hope it gets added to every helicopter in DCS with a WSPS.

lol yeah that would be pretty crazy IRL. It is kinda fun in DCS though . I tested the WSPS of the Gazelle again in the mission editor, and it still seems to work. I can't say I've had the same luck in MP though lol. Maybe my aim was off, or maybe it was desync. If the wires get to high they seem to miss the cutter and get into the rotor, and then it's all over. Here is a video of it in action.

The Marianas map has pretty detailed terrain. It also has lots of scenery objects for such a small map. This all comes at a price of lower performance across the board, for a map that is 90% water. IF they could optimize it further that would be great. I would be okay with a smaller map for helicopters, although 80x80km is still to small IMO.

Unless ED fixed it the option to remove threat circles (hidden on MFD) does not work. Making them invisible on map does, but then they can't been seen or controlled on map by a tac com.

Back when the Gazelle first came out the cutters actually worked. I used to go around and try to cut all the wires I came across for giggles. The wires would just disappear but the helicopter was totally fine. If you lined it up wrong, then the wires would take you down. Since we moved to 1.5 or 2.7 (can't remember) they no longer seem to function. It would be cool to see this modelled again.

That's probably a fair assumption. I wonder why ED never seems to add this capability to any aircraft since the SU25t?

Will our Apache have the IR jammer?

Yeah lol, that was a strange bug.

Definitely some kinks to be ironed out during EA. She is also extremely hazardous to M-113s apparently.

If you are playing MP and the unit is spawned in after you spawn in it won't show until you respawn. This might also be the same in SP with dynamically spawned in units, but I don't play much SP so I'm not sure. The hidden on MFD option in the ME last I checked didn't work. Only hidden on map will remove the rings from aircraft, but also makes the unit invisible to players who want to use CA to control them. I posted a bug report last year about this and to my knowledge it hasn't been fixed yet. I would be happy to be wrong though.

I agree

I always have civi traffic turned off, and the server I play in does too. I still get this glitch.

Love this server, keep up the great work!

It used to be TMS right short twice to select the IR pointer. It seems however that it was removed a few updates ago.

Are you on open beta or stable? Are they on open beta or stable? Make sure you both have the same version.

You sure can't but perhaps they could make the LOD for a unit at that range be invisible/clear/alpha whatever you want to call it to the naked eye, but make it appear the way it does now when viewed through a sensor. I'm not a game dev so I don't know if or how this would be possible, but if it is then that could help to alleviate the issue.

Sure, but they could start by making something as small as a Linebacker not visible at those extreme ranges without a sensor. Perhaps make the unit visibility distance match the visibility of terrain LOD? You can even see units that would otherwise be on the backside of a ridge and not visible to you because of this. It makes hunting all those player slung and nicely hidden convoys a breeze.

I can spot a Linebacker at beyond 40 miles with the naked eye if it is on a ridgeline. It appears floating in the air above the LOD of the ridge until you zoom in and the LOD loads. After that it becomes harder to see but is still visible. Here is a short video of what I see. It is actually way easier to see than this, but YouTube just murders the quality.

Yes I know that altitude was about 7-8nm which is why I did it that high. I was trying to demonstrate how far the actual laser designator extends from the TGP. The laser rangefinder has the same range limit in DCS as well. The easy way to see this is to point the TGP at that tall building on PG. Then observe the distance displayed in the TGP. If beyond 8.2nm it will give you the distance of where the TGP reticle intersects the ground beyond the building. However once you enter that 8.2nm threshold you will see the range reading snap from where the INS thinks the TGP is pointing, to where it is actually pointing (the building). Now in the F16 it may be a bug, I'm not sure but when you laser range beyond 8nm it will give you an accurate measurement to where the reticle meets the ground. However it will still have an L next to that number indicating the data is from the laser when it is actually from the INS. Perhaps that is true to life I don't know, but the laser rangefinder can only see objects out to around 8nm in every mod I have tested in DCS. I realized it could be difficult to understand what I mean so I made a video demonstrating it. You can watch the lower left corner of the TGP and see the range change from 29nm to 8.1nm once I'm within the range limits of the rangefinder.

So I just went and tested it again in the F16 and it appears to be around 8.2nm slant range according to the TGP range reading. Here is a video of a GBU12 being dropped from about 45k feet. The bomb goes dumb right before impact with a slant range of about 8.2nm. Here is a second attempt from about 40k feet and the bomb tracks all the way down to the target. The laser was reading right at 7nm at impact. Unfortunately I have not been able to test buddy lasing in a while so those results might vary depending on other factors. Also the bombs and other laser guided weapons don't actually look for a reflection of the laser in DCS per se. They seem to be able to track the end of the laser beam if the target is beyond that 8ish nautical mile limit, but once they pass it they go dumb. Hope this helps a little.

When I tested it last the maximum range of both the rangefinder and designator was about 8.5nm