Recluse

So every time I get into the cockpit, my View is messed up, e.g. too far down and to one side. This seems to be worst in the HORNET but it happens in other a/c as well (AV8B, A-4, less so in the A-10C) I adjust my view using the camera controls, RCTRL-RSHF-Numpad keys and then hit RALT-Numpad 0 to save it. But it DOESN'T SAVE. Something must be saved because I get he same crazy unacceptable view EVERY TIME. In 2D view, without VR, the default view looks OK. I also crank my seat position a bit, but I don't expect that to be saved. What am I missing????

You can also use the built in DEBUG tool: C:\Program Files\Oculus\Support\oculus-diagnostics (or wherever you have your OCULUS folder) Run OculusDebugTool.exe Many of the same options as Tray Tool and no new download required Seems like most recommendations are to mess with it in the Debug or Tray tool and leave DCS Pixel Density at 1.0, but either way works. I've tried both and just ended up doing it in Oculus settings vs. DCS Note: I left Encode Bitrate at 0 which is the DEFAULT. It is probably set to about 120 at default setting. I usually crank it up to 300, but then I have to crank it down if I decide to use AIRLINK vs. the LINK CABLE, so I just leave it at the Default to have more flexibility. Haven't noticed much difference. Usually I use the CABLE for DCS since is a little more reliable and continues charging so I can fly longer before the battery runs down.

On my Quest2, the Hornet DDI's are much clearer than the Harrier (esp Harrier left DDI). Just recently started flying A-10C and it looks gorgeous in VR, though I DO have to lean in to really see the TAD page. RTX 3070 Core i7-10700K I keep changing my settings, but currently: 90 Hz 5152x2608 (1.4x) SS (Oculus Tray Tool) 1.2x (Hmmm I usually have it at 1.4.....maybe I cranked it down when I upped the resolution) DCS: Pixel Density 1.0 IPD 66 MSAA Mask 0.90

Question: I upgraded my HOTAS to a WINWING ORION, and I am trying to use some of the buttons/switches on the Throttle Base. I cannot get them to work. I suspect it is because the numbering on the buttons is above the Windows limit of 32. For example: [Buttons] BtnToggle = 3Joy7 BtnItemUp = 3Joy109 BtnItemDn = 3Joy111 BtnSelect = 3Joy85 The TOGGLE WORKS but the others do not. I guess DCS gets around this. Any way to use Menu Nav with higher numbered joystick inputs?

I am guessing the Cougar weighs pretty much the same as the Warthog...so probably a no-go.

Bit of a Thread Resurrection here... I bought the adapter just in case, though I didn't think I would ever use it. Just started messing with the A-10C and I find I want my TMS back, so was going to put on the Cougar grip. I AM leery of the Cougar weight on the ORION base. Wondering how many folks have actually done it and if it it OK despite the weight? Not sure I want to "spring" (no pun intended) for the new WinWing F-16 grip, though it looks mighty sweet! As an aside, anyone have an A-10C HOTAS mapping for the stock F/A-18 ORION that they would like to share? I was going to use the little RECCE MARK Hat as TMS, but as I fly in VR, I tend to use that for the DCS MENUS radio mod as well as paging through the Kneeboard.

LOL. Losing it on the Landing Roll in the crosswind on Mission 5 at caused me several re-tries after otherwise successful attack runs. TAKING OFF in the Crosswind on Mission 6 proved similarly difficult the first time I tried it. I realized that at the end of Mission 5, I forgot to put ANTI-SKID back on since it was off from Carrier Takeoff....but it didn't help much during Mission 6 Takeoff. Still felt like I was ice skating. Will get back in the saddle again soon...but now you have me worried about the rest of it. I have honestly NOT done many Night Ops to being with, so maybe I will do a few practice hops with NVG before I tackle the mission.

Ahhh good call. I didn't even think of it. NEXT TIME!! I might go practice strafing a bit as well on general principles! Hehe.. WAGS makes it look so easy

Good job! I made multiple passes as well, trying to conserve ammo but didn't get the hits. Seemed like the shells were gently floating down everywhere but where i aimed them... I really wished I could invoke a RELOAD cheat and just keep trying!

Thank you for not punishing me for my inability to strafe on the Egress from SAM SLAM! After emptying my cannon and hitting NOTHING I feared I would have to repeat the mission, but all proceeded, albeit with silence from the Troops in Contact. Sorry ground guys.. Maybe the F/A-18 plunging toward the bad guys spitting bullets scared them enough to leave you alone. As an aside, from everything I have read, it seems like the cannon effects in almost every flight sim (DCS included) are anemic compared to the real thing and not nearly as effective (though that doesn't excuse Pilot incompetence)

Hmmm.. Under the MISC Tab do you have PLAYER or SPECTATOR EXTERNAL VIEWS on? BTW, can you use any of the other F commands (like F2 to see your external view?)

Do you use TRACKIR? Make sure F6 isn't bound to a TRACKIR function.

Well that's odd because I have ALWAYS been able to do just that: -Desginate with WPDSG/FLIR etc.. - Move TDC to MAV page and Uncage if it doesn't happen automatically. - With TDC on MAV page, UNDESIGNATE - HOLD DOWN TDC DEPRESS and SLEW. I JUST tried it again and it worked fine as it did when I tested it to write my previous responses. (Don't think this made it into the latest Open Beta, so I doubt it was fixed just now) Ahhhh OK.. I did not go into POINT TRACK/SCENE. In that case it did not release the lock for slewing. It works fine when slaving the FLIR to a WPDSG OR Slew the LITENING POD and designate with TDC DEPRESS then follow the steps above.

Wow.. that is news!! Can you expand on what the issue is? (the inability to slew when slaved or the continued ground stabilization when undesginate.. or OTHER) and what should the "Correct" behavior be??

Thanks for the info. In the Hornet, as I mentioned, once you undesignate the target, the uncaged Maverick DOES remain ground stabilized at that point for the selected missile and you CAN now slew the seeker around (TDC HELD DOWN) and it will lock onto a target when you release TDC. Only works for THAT missile. The next one will be boresighted. Again, I have no way of knowing if this is CORRECT behavior or not, just that it works that way.

Yeah, I gave it a try, but I DO believe this is CORRECT AS IS. Once a target is designated by another sensor, the AGM-65F slaves to it. In order to slew independently, you need to either undesignate or start with no target undesignated and slew the Maverick seeker as the MAIN Sensor. I have no references to support this, but it seems to make sense to me. I haven't flown the A-10C even though I own it. Does it work differently there? ...come to think of it, in the HARRIER you CAN slew the Maverick Seeker after slaving it. I had to remap my TDC DOWN from the depress function of the TDC because it kept slewing when I didn't want it to.... HMMmmm

My understanding is that you have to UNDESIGNATE to slew the Maverick off of a target is it slaved to by another sensor. I did think that if you turn REALISTIC TDC slew OFF, you can slew without undesignating as GazAce does in this video. He does say that it doesn't work the same way with ATFLIR. I usually have REALISTIC TDC SLEW on, so if I need to slew the Maverick Seeker, I undesignate first whether using LITENING or ATFLIR. When the AG RADAR is used for the initial lock, I think the UNDESIGNATE is necessary with or without Realistic TDC slew, but you CAN hand off a radar lock to the Targeting Pod first, which, while clunky, is something I usually do to make sure of the targets. After the first UNDESIGNATE, the MAV seeker remains ground stabilized and the SLAVED position. After it fires, you need to re-slave it from BORESIGHT. Aaron Nies 2 months ago (edited) Are you using "realistic TDC slew"? If not, than for those of us that leave that on, I think you'll need to undesignate before slewing GazAce 2 months ago I always have that option unticked

I am about 99% sure this is just ME, but it seems that lately I am having trouble with Short Takeoffs (when pretty heavily loaded). In the past, I could pretty easily get airborne and transition by using the recommended Nozzle angle and Rotation speed, but LATELY unless I am really careful, I drop like a rock back to the runway while trying to climb. I know the Engines were modified from how they were originally, but I am pretty sure my STO problems started long after the Engine modifications were done. As I said, probably just me, but I wonder if there were any other changes that I need to be aware of in my STO procedure. Similar issues getting off the Deck of the Tarawa where I used to be able to manage it pretty easily. Hmmmm wondering if the STOL FLAPS are creating more drag than I am used to: OK, thanks to the folks on the RAZBAM discord: - I wasn't firewalling the throttles. I didn't realize that was the condition used for calculations on the VREST page. I always tried to stay below the advisories (Hexagon in HUD) - It does seem that STO using AUTO FLAPS does work as well for me with the configuration I had been using without firewalling.

For those who like to use the Maverick Seeker slew, if you have DESIGNATED a target with the TPOD, Fired a Maverick, uncaged a second Maverick still slaved, you can UNDESIGNATE the TPOD target and the MAVERICK seeker will remain Ground Stabilized at the last designation but is now SLEWABLE by holding down TDC DEPRESS and Slewing. Upon release of TDC depress, the Maverick will lock on the spot. (Assumes realistic slew enabled... without it, I think you can slew the Maverick WITHOUT needing to undesignate). If you have more Mavericks loaded, the NEXT Maverick will NOT be ground stabilized and will be BORESIGHTED so you would need to RE-Designate a target.

You can't. ILS is not implemented in the F/A-18C only ICLS.

Always check the calibration/center of the axis you use for TDC slew. At the times where my TPOD was OFF or not stable it was traced to a wandering axis.

For what it's worth, I setup an F/A-18 (me) and a TU-95 at 70 miles away and I picked him up IMMEDIATELY in RWS, 6 bar scan even with INTL PRF, but I kept dropping him until I went to HIGH PRF also might have been the slow updates on the 6 bar scan which probably wasn't necessary) I was at 10,000 he was at 15,000, but my Radar elevation was scanning a pretty huge volume, Then it was rock solid. He was HOT which makes a difference, but I tracked him all the way in to 40 miles and I went to TWS and locked him up for an AMRAAM shot.

Check your PRF and elevation. Since you were so close, I am betting on elevation being the issue. If you are THAT close transition to AACQ mode. This is a pretty good tutorial for BVR radar usage, RWS and TWS

The argument that is most persuasive is the presence of TOO1 and TOO2. If the presence of TOO1 and TOO2 is correct, then it makes no sense that you cannot use them independently. There is no reason to have a TOO2 is you are dropping singles with TOO designation before each drop with no way to program 2 stations.

There is an older thread linked below from when the E2 first came out (and the -F almost went away) that mentioned the E2 has a better seeker and software that allows self-laze. I remember reading that the seeker/software on the E would sometimes lose the laser spot due to its own rocket plume obscuring the own-ship fired laser, which wasn't an issue with the geometry of a buddy lase. The E2 could filter out that interference. I can't find that anywhere, so maybe I imagined it. The link below describes various characteristics of the E2 which probably aid in the Self-Laze capability. In truth, the other DCS platforms (e.g. F/A-18) should probably require the E2 vs. E for self lasing as well https://warisboring.com/the-maverick-missile-is-perfect-for-hitting-fast-moving-vehicles/