Draken35

I've been using the "feel right" method since I configured my Quest 2 back in January... After much experimentation I settle in 63, which, coincidentally is my pupil distance. But, I guess, that wasn't enough to satisfy my OCD and I've been looking for a "yardstick" to get an accurate as possible value. For some reason I focused my attempts around the stick and they weren't really working. Last night, I realize that we do have a yardstick that we can compare in our VR and RL cockpits: the seat width, and, we can compare it with our fingers... The Quest2 touch controllers can be grabbed in way where the position of your index finger matches (close enough at least) the position of your real index finder...So, if you grab the controllers that way and use your virtual finger to touch the side of your virtual seat and your real index finger touches the side of your real seat, then, your IPD value is correct. To make it more accurate, we could find the width of the ejection seat of the plane we are flying and use it to create tactile marks in our real seat. I haven't done this yet...But I suspect my OCD will make me to. I use an OpenWheeler seat and try this method and came with a value of 55 ... What method do you use?

Bought the A10C II a few days ago and installed it today. Found duplicated keybinds and the ones with keyboard assignments do not accept controller assigments. I'm running Open Beta 2.7. I'm using a TM Warthog Throttle and Stick and TM Rudder. Also I have other USB controllers connected. I read in another thread that this might happen if there are multiple game controllers, so I disconnected everything, uninstalled the A10C and A10C II modules, did a DCS repair and reinstalled the modules and try with only the TM Warthog throttle connected.... Same issue . (Screen shoots where taken while I had everything connected). Also, I cannot map the HOTAS Boat switch Center or the HOTAS Pinky Switch Center to anything. Any ideas of what is going on and how to fix?

I stopped playing flight simulators in the early 2000's. One of the reasons was that that I felt "something" was missing. "View Mechanics" with keyboard, mouse and joystick wasn't cutting it for me... I totally missied the boat with TrackIR too.... Last year, we were picking up my daughter from a friend's house, and I was able to try VR for the the fist in a Oculus Quest. My first thought was "a FS sim with this tech would be amassing!" . Got home and google it... Well, here I am... Mostly a Harrier pilot, but got the Hog bug a couple of days ago and took advantage of the sale. Bad timing though, since I had to send my head set back for replacement because of dead pixels... Doing a lot of reading while I wait since I'm not even setup to flight in pancake mode! VR graphics catching up with 2D quality is just a matter of time (and money). And it will be rather sooner than later.

Funny...the release notes don't mention any Razbam module... Perhaps it was not broken... Nothing was broken... Perhaps Oceania was at war with Eastasia. Oceania had always been at war with Eastasia. Hope I do get sent to room 101 ...

I do, but I don't think it is a factor in this scenario. The "switchology" of the TPOD/IRMV was the one that gave me more grief too..

You got me curious so just did a quick test. Fired 2 IRMAV using the tpod with TDC Action/No Action ... Same process as before, no issues... The only difference (and I didn't think about it in my prior post) between using DMT and TPOD is that if you are using the TPOD, you have to take it out of HOTAS mode (SSS Depress twice) before SSS Forward to box the IRMV in the HUD... (I just noticed that toy said TDC Fwd in your step 1, btw) So: 1. Identify & track you target with the TPOD 2. SSS Depress twice (since you will most likely be in HOTAS mode) 3. SSS Fwd 4. Cage/Uncage (LEFT MCPD must be on the stores page) IRMV Seeker will be slaved to TPOD at this point 5. TDC down as necessary until IRMV lock Hope this helps!

Fired a couple of IRMAV last night (TDC Action/No Action enabled in Special Settings) , but identified/locked the target with the DMT, I know, not the same thing but the procedure was exactly as you described... I don't think it would be different with the TPOD

Just be aware on which side you mount it so you can plan your orbits and be comfortable flying with asymmetric load outs.

Yup.... Very important. Also, if you box the "TONE" option of the Stores page, you will hear a beep every time a weapon is released. I use it a lot.

quantity = total number of bombs you want to drop multiplier = number of bomber per pulse interval= how much space in between those pulses.... i.e: Quantity 6, multi 2 , interval 010 = 6 bombs in 3 groups of 2 , 100 feet in between groups Quantity 6, multi 6 interval 000 = 6 bombs at once For CCRP you need a target designation with the DESG boxed in the EHSD (multiple ways to do this) or, do a point blank designation if you are running 2.7

Quest 2 / RTX 2060 / Drivers up to date. Intense flickering in left eye, right seems normal. Mostly noticed in smoke and canopies but I've observed it in the seeker head of my sidewinders...

What I am doing as of late, is to turn anti skid off for taxing. That wait I can taxi with my rudder pedals without pressing anything and if I need Hi Gain, I press and hold NWS. I do not acknowledge the master caution just to remind me of turning anti-skid on before taking off.

Thanks! Glad you are enjoying it!.... It is what I use for my own training... I would love to add formation flying with AI (other than flying a race track, that can be do with the tanker) but haven't found a way for the flight leader (AI) to warn about the coming turn or maneuver... Also thinking on either adding to this one or creating a new mission to practice missile evasion

No, but disabling from the cockpit is just a couple of clicks.... That's what I doing to have a readable EHSDI ... The alternative is a bunch of clicks (like 50!) to reduce GAIN and play with contrast settings. How much depends on the map you are flying on.

Just uploaded an update fixing an issue with the rearming and refueling from the FARP.

I love working with JTACs that mark targets with white phosphorus and, obviously, our shiny, brand new yard stick in the TPOD is a fantastic tool for that... Center TPOD on the mark, call contact and set the YS for the distance the JTAC tells you and voila, target should be there ... Shouldn't it? I just flew (silly me, didn't think on saving the track) a mission were, twice, the JTAC marked a target with WP and the target was nowhere to be found near the distance it reported (measured by the YS) in any direction... This could be either an issue with the yard stick, the JTAC and/or the stick/ejection seat interface... I will setup a test mission to see if I can reproduce this but was just wondering if anybody else has seen this situation? Edit. Never mind... Must have been an issue with the rookie pilot not seeing the target... Tested in Area 51 (NTTR map) with active pause, the 2DY nad the JTAC works... Mission Attached in case you wanna try it Test JTAC-WP.miz

Good luck and enjoy!

I just add Joystick Switch Abstractions key binds to the [Your DCS Folder]\Mods\aircraft\AV8BNA\Input\AV8BNA\joystick\default.lua For the course switch: {down = inst_commands.Knob_Course, down = inst_commands.Knob_Course, up= inst_commands.Knob_Course, cockpit_device_id = devices.NAV_INS, value_down = -0.5, value_up = 0, name = _('COURSE SELECTOR CCW else STOP'), category = _('Joystick Switch Abstractions')}, {down = inst_commands.Knob_Course, down = inst_commands.Knob_Course, up= inst_commands.Knob_Course, cockpit_device_id = devices.NAV_INS, value_down = 0.5, value_up = 0, name = _('COURSE SELECTOR CW else STOP'), category = _('Joystick Switch Abstractions')}, Attached is file with the one I use Mods to AV8 default.lua

New version up. Requires 2.7 so, I decided to leave the old one untouched: https://www.digitalcombatsimulator.com/en/files/3316143/ Much simpler than the old one but provides the same opportunities.

Thanks! I'll give it try Edit: That actually works very well... Can't recall what my settings where before, but these works very well!

Same issue. Quest 2

The worst thing is that I lost the backup of my values.... So, I have to redo that work, plus, re tweak my graphic settings ...

Quest 2 user here. Same issue

@RecluseDo you feel any difference with 2.7? The FM was touched: Improved FM Corrected insufficient drag at negative angles of attack. Corrected incorrect thrust being generated when engine is windmilling but no combustion. Improved negative angle of attack dynamics. I stated to use more trim while hovering/low speed , like in the video that @Jackjack171 posted above... So, I'm not sure if it that, or my imagination , but the Harrier feels more stable during approach to the Tarawa and in hovering... BTW, the new Tarawa looks great!

Sad to report that there are no noticeable improvement in 2.7 regarding the quality of the MFDs