Hippo

:smartass: I am left in two minds by your post. On the one hand, I am highly impressed by your quest (and ED's) for realism and perfection.:thumbup: On the other, I am puzzled as to how ED have not provided a suitable option for a rotary analogue axis, for the remaining 99.9% of us using off the shelf controllers.:doh: However, I very much support and appreciate your request that what is in place does remain as an option.

See images.

See my post here RE a similar requirement. I haven't tried it with zoom, so can't say if it works; I think it should. By changing the delay time, it should be possible to increase the level of zoom per 'click' of the wheel.

I am using the scroll wheel for this. It's not perfect, but it does work. You may need to adjust the delay.

Actually, there is hope. With gamma at 1, and cockpit flood lighting at full, I have had with the F18 in the latest beta, the best night (imho) experience so far in DCS. mura almost gone, and no horrendous banding. Try the attached mission. Must call for landing (121.000 already set in pos 1 on comm1) for the airfield lights to come on(!). Turn landing lights on. Again, all imho, I still think the runway lights (and all ground lights) are far too dark and only become bright enough once very close to the runway. And they should be more like points than huge orbs. But once landed and on the runway, not too bad at all. Also odd things happen when banking at high g and looking straight up through the canopy (g-effects?). Straight-in Landing (Night).miz

I realise that this has been explained but just to be clear as there are some contradictory posts: FCS BIT consent switch (on right cockpit wall): key Y. autopilot/nosewheel steering disengage lever (Paddle switch) (on HOTAS): key A. 2.8.2.2.8 FCS RESET Button. The FCS RESET button on the FCS panel is used to reset the flight control computers after a transient malfunction. (there is no key assignment for this by default, at least on my system). Looking through the NATOPS one of the steps is explained clearly: 2.20.3.5.1 FCS Initiated BIT. For the FCS, the FCS BIT consent switch, on the right essential circuit breaker panel, must be held ON when initiated BIT is started. This prevents inadvertent initiation of BIT on the FCS for reasons of flight safety. However, it is not clear to me what the following action achieves: 7. FCS RESET button and paddle switch - ACTUATE SIMULTANEOUSLY All I can find is "Pressing the FCS reset button, simultaneously with the paddle switch, does not correct BIT detected flight control system failures; it simply clears the BLIN code(s) from the display." So, what is the difference between pressing FCS RESET (alone) and pressing FCS RESET with the paddle switch? Also related: 2.8.2.4 Actuator Exerciser Mode. An actuator exerciser mode is incorporated to improve cold weather start-up of the FCS. On the ground, the pilot can initiate the exerciser mode by simultaneously holding the FCS BIT consent switch ON and pressing the FCS RESET button. When initiated, the mode cycles the stabilators, flaps, ailerons, and rudders through 20% of full travel for 10 cycles in 20 seconds. The operation can be stopped before 20 seconds have elapsed by pressing the paddle switch. The mode should be used in cold weather or any time an initial FCS RESET fails.

natops:

Maybe an option to be included in the options->special?

From the NATOPS. The behaviour in bold is not replicated in-game (all the numbers come up).

Just checked again. Apologies. I could've sworn that using the finger lifts the other day I had full range (I must've been dreaming). I also get a small bit of nothing at the lower range of my throttle (x52 pro), like in your video. Sorry for the confusion.

Bumping - shouldn't this be in the bugs forum? From natops

You already have it -> GROUND idle to full AB. You have to assign a key to activate both finger lifts, and press it while moving your throttle. As this range exists on the real throttles I suppose they had to simulate it. Is it really necessary though? Maybe they should give an option to remove the ground idle to idle range and have a keystroke for this instead? What I've done is to change my curves, which helps a bit. You could make it even steeper by going to 30% on the second notch (or the first??), and smoothing out the main range even further?

I've been looking through the NATOPS, and this item is in the interior check: Can't find anything about it anywhere. Wondering if anyone knows what it is?

YES PLEASE to this. I'm using labels in VR to make up for not being able to see targets as well as I would on a monitor (or IRL for that matter). However, it's too much of a cheat when they can be seen through the cockpit instruments / frame / floor etc. They should only be visible through the canopy. Any chance of an option to disable this behaviour as suggested by OP?

I've been experimenting with these, and have attached what I've come up with so far (it's wip - esp distances). Comments and suggestions welcome. Labels.lua

From the NATOPS engine shutdown procedure: I waited (and waited) but the amber FLAPS light never illuminated when attemting this in-game.

Time for me to eat some humble pie: Er. I've just realised that it's possible to left click to "hold" rotaries and use the mouse wheel at the same time to turn them. So the functionality I've requested already exists. Not sure how I'd missed this. I suppose that just leaves switches that you'd want to click (but not hold) whilst looking elsewhere. Not sure that there are too many of those.

Er. I've just realised that it's possible to left click to "hold" rotaries and use the mouse wheel at the same time to turn them. So the functionality I've requested already exists. Not sure how I'd missed this. I suppose that just leaves switches that you'd want to click (but not hold) whilst looking elsewhere. Not sure that there are too many of those.

+1 I'm using VR, and this is a real problem for me. Real hornet drivers aren't sitting in front of a computer monitor (or using a Rift) playing a computer game. You are much more limited to begin with, why add even more limtations? Thanks for posting the mod. I'll be trying it out later. *EDIT* Works great - thanks again.

Very nicely explained - thanks.

Thx.

See post title. 2.5.2.18037

I was flying this mission in VR, not sure whether issues occur in non-VR. Issue #1. At mission start flying towards the SAM (see 185557.png), note how the flight plan path scale does not agree with the map on the MPCD, it should be going over ground but doesn't (see 184306.png). It does sort itself out at some point, though (see 184816.png). Issue #2. Flying low over ground, waves appear to come through the ground. This appears to happen depending on head position. The SAM appears to be floating in mid-air. (184119.png, 184501.png) *EDIT* P.S. What is that thick orange line in the mission editor? *EDIT2* All issues happen in non-VR as well. Should be in another forum (sorry). *EDIT3* Forgot to mention, the map was occasionally disappearing (and coming back) from the MFCD as I was flying the mission. v. 2.5.2.18307.391 FA-18C_AD01.miz

+1.

Similar to the current click and hold solution for momentary toggle switches (e.g. warning lights tests). Perhaps a new key bind "hold switch" which could be used in combination with the mouse wheel / LMB / RMB. It could be assigned to a joystick button or spare mouse button (I have eight on my mouse).