LorenLuke

I think what's happening here is that you have a relatively hot object (rotor) entering and exiting the frame rapidly, and any logic in automatic gain/level control just is incapable of adjusting to the rapid changes. See how having more or less than 10 degrees down angle (full or no rotor in frame) helps with the flickering. It may still be there, but hopefully will be not as bad.

It does, but it's also used to to jump through targets when there are multiple boxed in the Acquire on the Move (ACQ OM) mode.

I presume this to be the 'Frame Freeze/Target Select / HOG ON/OFF' button.

It's rather difficult to notice if you're not sure what you're looking for, but the unit last designated in this mode will have a slightly thicker box. You can sequence this thick outline box through these boxed targets using the Frame Freeze/Target Select / HOG ON/OFF button. Pressing Point track will jump you to the target (and I believe if it's the first target in the series, will switch you to point track mode). From this point, you can press the Frame Freeze/Target Select / HOG ON/OFF button to select the next one (if none are selected) or the Point Track button to jump to the next in sequence. If for whatever reason there's no thick lines on any of the boxes, or if you are in point track mode (or 'Offset Acquire' mode), do the following: Return to Point Track mode if you are not in 'Offset Acquire' (OSET ACQ) mode or Area Track/'Acquire on the move' (ACQ OM) modes. Press 'Area Track' to enter 'Acquire on the move' (ACQ OM) mode. If the desired target is not boxed. designate the desired target by using the MMS slew to slew the diamond over it (the MMS will attempt to designate the moment you release the MMS slew). If necessary, press Frame Freeze/Target Select / HOG ON/OFF button, until the target is surrounded by the thicker box. Press Point Track to jump to that target. Note that any boxes/targets will be lost if: The currently point-tracked target is destroyed (bug?) The object moves behind another object that obscures it. The object ever leaves the current MMS field of view.

The Polychop Kiowa manual has bindings suggested specifically for the Warthog. (Somewhere around Pg 26, IIRC)

Because those helicopters work differently? Because the that's the physics of the aircraft in an unpowered fall. It's not a matter of axes working or not working, if you don't follow the correct steps to autorotate. We can see you move your collective up and up as you fall. Your collective works, and you're doing the opposite of what you need to do. From what I'm able to gather from what others have said in this thread, all hydraulic and electric power in the aircraft is generated from the rotors spinning. Usually that's the engines doing that, but if you lose those, if you want any hydraulic or electrical control, you have to keep the rotors spinning. It doesn't matter if it's from the engines (which you've lost), autorotation, faerie magic, or getting out and pushing them with your own hands... if you want power to the aircraft and hydraulics, YOU HAVE TO KEEP THE ROTORS SPINNING. There have been multiple updates to the systems to make them behave more realistic to the real-life aircraft since. This behavior before was likely the result of a less accurate simulation. When you lose the engines, just make sure you IMMEDIATELY put your collective to the floor as the very first step.

Engine failure doesn't care where you've studied or where you've worked, either. Other's said it can be done, and if you were doing it correctly, this thread wouldn't exist. I've watched the track, too, and the VERY FIRST THING you did was add collective, which is at the top of the 'do not do this' list. So, if you want to put your studies and work experience into play, this is what it got you. Or you could just go look up a video, and add to that education just a bit more, especially considering you're coming to others to ask their help for your problem.

Additionally, a bind for each position of the MMS rotary (one each for off, stow, preflight, prepoint, forward, and scan). And the copilot doesn't have binds for their radio channel select hat-thing (the one the pilot has on their grip).

nullSteps to reproduce: Multicrew HSD Nav Setup Waypoint List Prev Page Steps to fix Next Page MFD button Kiowa-Display-bug-pilot.trk Kiowa-Display-bug-copilot.trk

GO HOME FOLKS! THAT'S IT! THAT'S THE REVIEW!

Pack it in everyone! Go home, thread's done its job! Seriously though, I'm glad you've found it as fun as I do, and I'm glad it was just as fun, if not more fun, than I was hoping it'd be.

Title.

That said, Pg 68: I can't for the life of me get anything other than the Copilot ASE page with 2 hellfires and an MG (loaded via Mission Editor). (Nor does the LMC seem to work.) EDIT: The WPN page switch DOES work, but ONLY for the mouse. The keybind moves the switch correctly, but only accesses the ASE page.

Ignore the first 5 and subtract 5 from all the subsequent numbers.

Didn't say that. But I know that if I'm close enough to sniff the polygons, I'm probably going to get about one frame to see, process, analyse, and criticise it before I disappear in a midair collision. So I can stomach a moderately subpar tenth of a second, compared to the enjoyment of actually flying and fighting the thing. I buy modules to play, not to polish them and put them on a shelf next to a sunny window.

I mean, I like flying my modules from the cockpit, but you do you.

https://forum.dcs.world/forum/1242-bugs-and-problems/

I managed to find these binds. null

Graphics are as follows, and I generally run the multithread client. null

ODU displays outside of the monocle. The top scale seems to 'jump' from side to side and isn't culled outside the monocle. The monocle size is independent of visual zoom, the ODU is not. nullnullStrange behavior with how the bar on the right extends upwards or downwards out of the ODU.

It has been announced as being part of the patch scheduled today.

Worth noting is that if you select your acquisition source to GHS in the TADS, and then switch to your HMD as sight, it can't set the acquisition source to itself, so it defaults to 'fixed', which remains when you switch back to another sight. This is true for switching to the the FCR with the FCR as your ACQ, as well.

I mean, this is just the same for the Kiowa as for any other module. Once it has left pre-order/early access periods, it's full price.

If they were, I don't think the SCAS and FMC systes would work the way they do.