FlippingGerman

Flying in a multiplayer server in AH-64, first ~40 minutes or so went perfectly normally, controls and weapons acting as expected, mainly from CP/G seat with George flying. Landed, rearmed, went out again, and George won't slave to line of sight. I head into the front seat, and lots of controls are giving uncommanded inputs. I find a target, hit IAT and track the target - and it immediately untracks again, giving "all tracks dropped". Looking at the handgrips the button is moving itself to drop tracks, without me pressing it. Similar things seem to be happening with LMC and slave. Checking the "adjust controls" menu shows it's not my hardware giving these inputs: in the video attached, every input that happens is one I command, whereas in the cockpit the buttons are pressing (seen visually on the handgrips) uncommanded. TDC slew is extremely jerky; my mini-joystick works fine, and changes smoothly in settings, but the handgrip stick jumps back to zero even though mine hasn't. I also see the MPD "WPN" pushbutton activating itself. YouTube link attached. I have a track file, including both normal flight before these issue started, and once the bugs happen, but it's fairly long and too big to attach here; if you want me to upload to somewhere custom I can do that. https://youtu.be/jUVx-HZEPBM

I'm not that bothered how he deals with insufficient power, but crashing is not an acceptable solution.

null Steps to reproduce: Enter an ACM mode, such as "select gun" switch press A/G Master Mode button A/G radar has no movable cursor, even though it's SOI, and range cannot be changed, as though an A/G target is designated Tested coming from gun, AMRAAM ACM modes, sidewinder radar cued modes - does not happen with sidewinder seeker only mode. AG radar borked2.trk

I haven't tested this in ST, but I'm in a multiplayer server, running multithreaded. Pilot body is off by default, and I had a few infrequent flashes of bits of the pilot body, as seen from inside it. As the mission went on it got worse, right now it's showing continuously in the standard centred view. Turning body on (LShift+P) makes no difference except the kneeboards appear. If I look down with TrackIR the body disappears totally (as it should), as in the bug isn't occurring, my head would still be inside the pilot body as shown in image. I've never manually changed the default view. Looks like it's not just the body either, the Maverick sight is visually duplicated and so is some of front panel. Current Open Beta build, Nvidia driver 531.41, 1070Ti, 5600X; I can give you a track file but it'll be enormous. null

If you want more detail, watch this. This is a Hornet video, but the principles of how radar works is exactly the same, the interface just looks a little different:

Update - it's still happening. My testing yesterday after the slow fix was singleplayer; perhaps that makes a difference.

Slow fix appears to have done the job, thanks! It wasn't the first sim launch after update - I think about the third. No mods installed (apart from aircraft, eg. A-4). Log is attached anyway in case you want it. dcs.log

Found while performing gun attacks on ground targets. View becomes very distorted, but the effect disappears and returns to normal once the gees have gone below a certain level - seems to be about 4-5G. Driver is latest Nvidia 531.18, hardware: 1070 Ti, 5600X, Win10 https://youtu.be/mD_G0msXM8E

I've experienced this too. This isn't a control axis issue - the entire cockpit goes dark, and it also happened while viewing my aircraft in F2 view with the external lighting going dark too, although not completely black. I was in burner, which was lighting up the aircraft, and I think all light from the aircraft itself disappeared, with background light still showing. I do have a track file, but it's ~500MB, this happened at some random point toward the end of the (quite long) flight...Is that still useful?

Same issue; the above method seems to have solved it, thanks! I've copied over my Config (and Missions, Liberation), that seems to have carried over my controls and settings.

When you start getting frustrated, stop trying, shoot down the tanker to make yourself feel better, and try again in a few hours or the next day. Also: the Hornet's built-in refueling mission isn't very good - make your own, simply set a KC-135MPRS (I find bigger tankers much easier than the tiny S-3) going in a nice straight line, 20-25kft, 250-300kts. No wake turbulence, no turning tanker. Or make it part of a mission - go blow up some tanks, grab some fuel, and land. But mostly keep practicing - I could do it within perhaps two weeks of daily practice, albeit very badly, but after that's it's just improvement, you've cracked the hard bit.

After taking battle damage to internal fuel tanks - i.e. fuel drains out -, land, repair, refuel and restart. Indicated fuel on the IEFI is then Full Tank + whatever actual internal fuel is. After a few minutes of runtime, the engines cut out, as though they have run out of fuel - even though I just refueled. Refueling again repeats the cycle - fuel level then goes up to ~30k lb, until the engines cut out. Below fuel level is impossible, even with external tanks, and I have none. I do have a track file, but it's hours long, happened somewhere in the middle, and is nearly 200MB. I can post it if needed, though.

Boresight on the ground, with a nice taxiway signpost (those yellow things with "A" on them). Ds are normally quite happy to lock them.

Razbam's apparent total lack of documentation is very disappointing. A Wags-style video when things change or new features come out ought to be the minimum. If you can make the changes you can at least document them. This in particular, refusing to help Chuck Owl with his guides - WTF, guys? If even he can't keep up, how are the rest of us supposed to cope? For dropping bombs, there's the video above; for manipulating the TPOD, see https://www.youtube.com/watch?v=v5kk8dFcyBA&ab_channel=GrimReapers, along with a few other of their recent videos on the Harrier.

The way JDAMs fly changed a few months ago. If you spend a lot of time watching them you'll notice. They used to follow what looked more like ballistic trajectories, now they spend a lot of time at high AoA, frequently until very close to target, then suddenly remember what they're doing and start guiding, but they do it too late and miss. They also seem to waste a lot of energy. Toss bombing - launching at about 45 degrees - is not very useful, as the IN ZONE indication appears when the bombs cannot hit the target. Recently I dropped a GBU-54 from a Harrier, from M0.85, 28k, when the HUD said 100 - supposedly hit probability. It overflew the target, tried to turn back, failed and missed by a huge margin, perhaps 50m. I've just done a bit of testing, and I'm getting much better results than I do in MP -they seem to glide as they used to, rather than what I describe above. Is MP different? Perhaps there GPS jamming? Although that shouldn't alter flight profile, only accuracy. Or there's a mod on the server affecting things, or wind, or...