Hippo

+1.

Not sure if this is what you meant, but removing \DCS World OpenBeta\Scripts\Aircrafts\_Common\Cockpit\KNEEBOARD\device\init.lua leaves me with one blank page. (or in another mission a map with WP0?). If your method is different, please could you let me know what it is? I was tinkering with the above file, but there was no way I could stop that one page from appearing.

I reckon that when they were designing the cockpit, someone suggested it as joke, then came back a few weeks later to find he'd been taken seriously.

Well, I use the kneeboard builder utility, and if it provides this functionality, I've missed it.

Yes. But what if you want to do, say, five separate clicks, because you know you want to go up by 5 degrees? With rotaries you can left click and hold (which does not activate them), look away, then turn the mouse wheel, or drag the mouse to "move" them. Works great in VR. I only realised this was possible a few days ago (and you can see on the left that I've been around here for a while - doh!)

Clicking on the up and down arrows the N / E coordinates change and elevation change, but the WYPT numbers between the arrows and above the coordinates don't. The grid ref also doesn't change.

Looking at the NATOPS, all HSI displays shown in CH 24 use degrees, minutes, seconds, and NOT degrees, decimal minutes. Maybe it's a software version thing?

P.S. In VR, there really is a need to be able to (single) click these switches whilst not looking straight at them. Thinking about it, I'd say it's better to just have them be controlled exactly like rotaries.

(... in addition to the current mouse clicks) Realistic? probably not. Practical? oh yes.

I have a mouse with extra buttons, and I have now assigned my kneeboard commands to those, which seems to work well. Wish I'd thought of it before. I'm using an X52 Pro, so can't suggest much RE your HOTAS. Usually I try to make it as similar to the real thing as possible, but practicality always comes first. You might find very helpful RE HOTAS setup. I had a play using the Touch controllers yesterday. Shows promise, but (imho) is not ready for practical use yet.

I have tried this and confirm that I experience the same or similar issue. But it's the right LEF that stays at 12 on the FCS display, none of the reset attempts from the natops will clear it. Running the FCS initial BIT, it just stays IN TEST and never completes.

So it's possible to set up shortcuts (bookmarks) in the kneeboard after you enter a mission, but is there any way to set the shortcuts up so that they are permanent and always appear for any mission? Either for the default kneeboard (in \Saved Games\DCS.openbeta\Kneeboard\FA-18C_hornet) or for mission-specific kneeboards? Thx.

I've just tried to do this (for the first time ever - so very likely I could have done something wrong), and it did not work. Would be nice to get confirmation as to whether this is currently supposed to work or not. "version": "2.5.2.18736.400"

For me I would say there's not much difference from pre-VR (trackir) I find the VR zoom to be essential so I have that on an unshifted button. The VR centre is not so essential, so it's on the same button but with a shift.. The kneeboard has become essential for me, so I've had to map controls for that. I use VAC for voice comms (only); but then I've always used that. You might want to add which HOTAS you're using, as then people can show you their configs or post their config files, which you can adapt to something you like. There's also an option for VR hands, which I've been meaning to try out. Also, which headset are you using, as there are probably specifics to each one. P.S. Take the red pill (or is it the blue one).

Agree with previous poster. (SP, using VR, very simple mission with just the player's F-18 ) After further testing, the lights do come on if I call inbound. But, they only become visible from very near, and are not nearly bright enough (imho). My question is, why does it have to be like this? Why not just have all runway lights on all the time (at night)? Does anyone know if there's a config file somewhere that can achieve this?

Great post. I was wondering if I was imagining it. I've noticed that I'll configure the aircraft for a straight-in approach from around 5 miles out and 2,000 ft, Everything's lovely and stable all the way down, until I'm just over the runway, when RoD suddenly increases. As you say, one would, if anything, expect the opposite from ground effect.

Ah, RTFM. Thanks for clearing that up. I also notice that the LDDI - HUD - RDDI switch is sideways in the NATOPS (which makes sense).

: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?