Captain Orso

I can say for certainty, that MVCS FWD/AFT do adjust the HMD brightness, albeit it starts dim at 100% -- IMHO -- and can only go dimmer. The changes are in 10% steps, which is actually displayed in the HMD. The rest of the discrepancies I can neither confirm nor deny, but i would not be surprised in the least. When the "Tank Killer" appeared it changed some things from the older version and has since changed additional thing, like switching left and right HFCD's -- which was pure fantasy from ED apparently -- was removed to free up the DMS AFT Short to make HMCS SOI. This makes me question, how many other things in the "Tank Killer" are pure fantasy, let alone other modules. In the light of that, not creating, for example, true SEAD (Growler) aircraft, 'because the technology is classified' , and 'ED only creates simulations of publicly accessible, documented technology' seem to be less than honest statements IMHO of course.

But that would mean, at as soon as the Mav were no longer bore-sighted, you could never adjust it again, because being bore-sighted is the base requirement. If feels very off to me, like it's supposed to trick you into thinking it's WHOT or BHOT when it's not.

Both the Early Access Guide and Chuck's A-10C Guide say that you control the IR-MAV reticle (no TGP mounted) using short inputs For/Aft/Right/Left of the DMS. Even without the TGP loaded, these do nothing that I can see. Using the TDC does however work the same as with the TGP. Am I missing something here? Also, using the Boat Switch is weird. It seems to only change the color of the reticle, and when set to black, as soon as you fire a Mav, the reticle reverst to white again, and when you return the Boat Switch to center, it says something about boresighting

KBB was built before the current DCS kneeboard. Whatever settings KBB makes are not used by DCS anymore. Further, if you are using VR KBB has never understood to properly create a profile for a VR environment. Just ignore that KBB was ever able to create a profile, way-back-when. Move the kneeboard with your mouse to where you want it when you first enter your aircraft and the issue is solved.

Nope, unfortunately not. I'm always sorted by mod-name. Changing to Status and back to Name changes nothing. The list still jumps to the top when installing or uninstalling a mod. Kewl, that will be nice I just tried this. Works well, so I guess that's fixed I was kind of wondering back then if that might work, but at the time I was trying to avoid messing things up any more that they already were. I guess it would be nice if there were a button to "reset after update", but I'm not shy about laying hands on if I'm sure I won't make things worse, so if I ever screw up again I now know what I can do to help myself out. Thanks!

I've been using this for a while now and am mostly satisfied. There are some things that could be improved though; some with very little work, I believe, but not all. -- When installing a mod from my fairly long list, the list always jumps to the top. This ia a real PITA, because for example if I'm installing mods for a specific module, they are all named like "DCS UH-1H...". After installing the first, I have to scroll all the way back down to find the next, install it and scroll all the way back down to find the next, etc. If the list stayed put, it would be very helpful. -- Batches: Allow for updating a batch. It would be user very friendlier if instead of having to recreate a new batch, because I've added a single new mod, to simply update the current batch to contain all the currently installed mods. Also, renaming batches from the front page... no need to search for it somewhere else. -- Was the context pull-down menu on the first page not supposed to work before the first context has been loaded? It has never worked for me. Not sure if this is WAD. It would be user friendly to have the last context loaded automatically load on startup, or at least have it in the pull-down, instead of having to go through File -> Recent contexts -> list. -- Emergency Reset: Here's the situation. I inadvertently updated DCS once, before uninstalling mods. I wasn't sure if an update was available, and expected to have a download of the updater binary as the first step, which would have allowed for me to open OMM and uninstall all my installed mods before the update ran, because there is always a dialog before it runs. This time there was no new updater binary, so the updated blew through, first overwriting all the installed mods and "fixing" them, and then installing the update. So now OMM thinks the mods are installed, when they are not, and that it has a bunch of files it has to put back into the DCS installation, to remove the not-actually-installed mods. So when I "uninstall" the mods, OMM copies the it had backed up from DCS, overwriting the update (possibly), which means after "uninstalling" all mods to get to a defined situation in OMM, I then had to do a repair in DCS to get that back to a defined situation as well. Lots of time wasted that might have been avoided... yes I know, if preemptively uninstalled all mods before starting the update process. And yet, if there were a way to simply tell OMM to drop the status of all installed mods and delete the backed-up files from their repository, it would have saved a lot of time and effort. I hope this isn't too overwhelming and many thanks for all your time and efforts.

Thanks for replying, but ... Yes, exactly.

In the Early Access Guide, in page 363 it states, "use the WPDSG pushbutton on the HSD to designate a target waypoint". "HSD" should be HSI.

In advanced waypoint actions, S-3 set in racetrack orbit, TACAN set to 21X, and "Tanker" set. AR works normally, but TACAN does not work at all. The S-3 started from the Super Carrier. Doing the same thing with a KC-135 airstarting works perfectly. TACAN set to 20X and while flying the Hornet I can find the KC-135 TACAN signal (direction and distance) without issue.

Two suggestions to make SRS better: 1. On the Settings tab, in GLOBAL SETTINGS you can set 'Auto Select Profile For Aircraft', but you have to guess how the profile for an aircraft is named . In the PROFILE section, in the pulldown for selecting the profile, if 'Auto Select Profile For Aircraft' is ON, add all the valid profile names for Aircraft. That would make that option about 99.995% easier to use. 2. Once control inputs are defined on the Controls tab, there is not way to determine if they are properly set and working. You can only go back and set them again. It would be very helpful if you could assert a control to get a response on the Controls tab -- like having the corresponding line highlight while the control is asserted -- demonstrating that the control is set and working.

This QRH has helped me so many times while learning the FA-18C, and it's still being updated All the awesome-sauce is all yours, sir. If ever there were an A-10C version of the QRH, I'd not be disinclined to downloading it too

Many thanks. Didn't look for "stuttering", which is why I couldn't find it. Report actually happened here: Guess we'll have to wait and see a bit longer

I'm still having this issue. It seems far worse in my system than in the video above. It's been nearly five months already, so I thought I might check to see if this might have gotten forgotten?

ED! Please finally make this minor fix a reality. It would be sooooo useful

Hi bn880, Could you give me a tip. How do you unscrew the retaining nut from the Autopilot Engage/Disengage button? The space between the flat edges of the retaining nut and the side of the well is so narrow that I can even fit a needle-nose plier in to unscrew the retaining nut. Do you have a tip for me?

Yup, the title say it all.... okay, not really. Every time and in every aircraft that I'm in at an airfield, whether just spawning in, or having landed there, when I call the crew chief and ask for Rearm & Refuel, in the graphic for setting what to load, when I move my mouse pointer to the hardpoints-boxes under the wings and fuselage DCS suddenly lags immensely -- mouse lags (absolutely no mouse pointer movement) for about 1 second and then I can move it for about 0.5 seconds and then lag again for 1 second again, this for the entire time the mouse pointer is over one of the rearming boxes. Am I the only one in the entire world with this issue? Any tips on how to fix it?

You can copy text, not graphics. Text from the chat window can be copied. Text rendered and displayed somewhere in the cockpit are only graphics at that point and can therefore not be copied. It would require OCR (Optical Character Recognition) software to do that, which is far from trivial with even professional system not being perfect. Read text you want to record off the cockpit and type it into the scratch-pad. It's as simple as that. Don't know how to use the 10-finger system of typing so you cannot use a keyboard without staring at it? It seems that you "lack". There are hundreds of free courses and videos on how to learn the 10-finger writing method. Bone up, issue sovled. The virtual keyboard is a mod of the mod. It's somewhere in one of the older posts. You'll have to actually look for it.

Yes, you just sit normally in your seat and press the re-center VR camera button again, and everything will be back to normal.

The "Flashlight" in the Hornet is a hand-held-lamp, mounted on the rear, right cockpit wall. I don't recall that you needed to turn the battery on for it to work, but maybe. I the A-10C the flashlight was only just added due to popular request. Even though it is in the category "Right Console" there is nothing else in the category and I'm guessing it was simply copied from a different module and left as it is. I just tried it, and starting in an A-10C II Tank Killer cold and dark at 2am local time, no moon, no nothing, pitch black out there, it works as the very first game button I press. Dim controls don't seem to work, but better than nothing. No idea what your issue is Ziptie. Maybe check your controls again. Also try <LAlt><L> on the keyboard. That should always work, unless you've changed it.

If you are flying in VR, the re-center VR button is your best friend. Lean forward until your head is above the control stick and press re-center and then sit back again. Your view is now emitting from close to your headrest and you can easily look down at all the radios to make all the adjustments to your heart's content without having to do acrobatics -- works on the other console as well

RFI I fly in VR, but am often outside VR for mission editing etc. Not seldom while not in VR while using Scratch Pad I move it off to the side. Then when I'm back in VR the scratch pad is still way off to the side, but now it's outside my VR viewing window, and since it's outside the window and locked outside my ability to reach it with my mouse to move it back to where I can see it again. My RFI is to have a re-center hotkey. It would do nother other than have the scratch pad window move to the center of which ever display I'm currenting using so that I can see it again, without having to quit DCS completely and then manually change the window position in the config file.

After adding new waypoints in the normal fashion and going to create a new Flight Plan, I've noted that none of the new waypoints appear in the TAD until after they have been added to the new Flight Plan. Is there anyway to make then appear on the TAD before implementing them into a Flight Plan, to addid in setting up the new Flight Plan?

OMG this is actually they way it is supposed to work?!? In the AV-8B-NA Harrier the throttle is even more complex and RAZBAM has made it work logically without forcing the virtual pilot to the keyboard to move the throttle, when I already have it mapped to a throttle-lever axis. Harrier: You cannot move the (in-cockpit) throttle from 'Stop' to 'Idle' without operating the sim's throttle-finger-lift. In RL the throttle-finger-lift is spring loaded holding it in the downward position. The finger-lift has a cutout in its stem. The finger-lift is mounted with a rail inside the cutout so that the finger-lift cutout slides along the rail. Toward the 'Idle' position of the throttle, the rail has a wedge shape which causes a resistance (sloped side of the rail-detent) while advancing which indicates to the pilot that he is nearing the 'Idle' position, but conversely stops him from decreasing the throttle to 'Stop' once the throttle as been advanced to 'Idle' (detent side of the rail-detent) without lifting the throttle-finger-lift over the detent. In-Game you must operate your mapped throttle-finger-lift to advance the throttle to 'Idle' or decrease it to 'Stop'. - In-Game-Throttle is at 'Stop': [operate throttle-finger-lift] ->In-Cockpit-Throttle advances to 'Idle'. - In-Game-Throttle is at 'Idle': [operate throttle-finger-lift] ->In-Cockpit-Throttle regresses to 'Stop'. Additionally, in RL to advance the throttle past 'Idle', you must release the parking brake first. The parking brake lever has a physical stop preventing the throttle from advancing past it. In-Game if you haven't release the parking brake, you can push your controller throttle-lever anywhere you want, but the In-Cockpit lever will not move. Once the parking brake lever is released your controller-throttle-lever and the In-Cockpit-Throttle-Lever are synchronized again, and advancing an decreasing the controller lever will mirror the same motion in-cockpit. So if RAZBAM can do all that in the Harrier, Belsimtek can certainly do half the same thing (Idle/Stop side) in the Huey. I'm sure you don't want to let RAZBAM make you look bad, right?

I've always had the 'save view' option checked. I'm also very aware to save the view with <RAlt><NUM-0>. It seems to me DCS is saying, "you are using an HMD, so we will ignore what you have saved and let you reset your camera view again, just because". That's the way it acts anyway.

Hmmm... I'll have to try un-ticking it to see what happens.