jaylw314

Looks like you have The JOY_X and JOY_Y axes bound to the TDC Slew for the Warthog throttle. I don't know if those are the correct axes for the Warthog, but if you click on JOY_X (or JOY_Y) and then 'Axis Tune' you should be able to move it around with the physical controller. If it doesn't move, then there's something wrong with the device's setup or hardware. If it does move, there may be a DCS issue or skill issue (like not assigning SOI to the TGP page before slewing).

I think you need to look under 'Assign Axis' and assign the slew control axes (not the keyboard commands) appropriately. Right-clicking on the device in the Assign Axis screen (not the buttons screen) should also allow you to reset them to default?

There is always a SPI, designated by one sensor, be it the TGP, TAD, HMD, HUD, MAV, IFFCC, STPT or MARK (I'm sure I missed something else). The sensor designating the SPI is always noted in the lower left of the HUD (and nowhere else). So when you 'set a SPI', you're only really designating which sensor's target is the SPI. That means if you move that sensor, the SPI will move around. That's not good for bookmarking stuff or setting a reminder. I'll often hear people finding something with the TGP, pressing TMS Forward-Long and then slew the TGP around to something else, thinking they set the point on the ground as the SPI. It does not, it just means that setting TGP as SPI will make whatever the TGP is looking at at that moment the SPI. So once you slew the TGP, that point on the ground is now lost. So yes, use markpoints to give yourself reminders. You have 25 of them, so knock yourself out. Some other random uses I've found for markpoints: drop them on moving vehicles every minute or two so you can see a trail of breadcrumbs. That will cue your vision to look ahead to find them and see where they're going Drop one on your position and one out in the direction of an RWR contact. Fly a bit and do it again. Look on the TAD and drop a markpoint at the intersection of those two lines, the emitter is around there Make your HMD SOI and make sure the HDC is on the center cross. Now when you fly cover for someone attacking, just look at smoke trails and AAA and rapidly mark them. Note if you want to drop a very accurate markpoint, you can look in the general area and slew the HDC until it's right on top of the target, then drop the markpoint. TMS Right-short actually drops the markpoint on the HDC. But if you just want a markpoint in the ballpark, you can just keep the HDC on the center cross If you want to figure out the elevation of terrain nearby, just drop a markpoint on it and look at its info. Draw smiley faces on the ground if you're bored

Just make sure your SPI sensor is also SOI, then press TMS Right-short. I assume both are set to the same sensor since you were 'working' it, but the distinction is important, e.g. if my TGP is SPI, but my TAD is SOI, TMS Right-short will make a mark point at the TAD cursor. So make TGP SOI first (coolie switch left/right-long), then make the markpoint. MAV seekers are pretty terrible. IRL, I've heard they were used as within visual range weapons, not really standoff weapons, so that at least correlates with being unable to lock or locking on the wrong target more than 4-5 nm away. The problem you described with losing targets is not clear to me, and it could be just spotting difficulty or a cold vehicle in IR. I have not seen a terrain issue cause that problem.

IIRC, if you have any amount of braking, the wire will not drop from the hook.

Ah, I was wondering what MUFC was

A screenshot and track would be good, since they just squashed some other entertaining instrument panel bugs (floating HSI arrow hub)

Modern Pb acid batteries have capacities at 24V of about 15-25 amp hours. The nav lights might have a current draw of 5-10 amps or so, and same with the landing light, so an hour or two of battery time wouldn't be far off. Not sure about the draw from other electrical stuff, though.

LOL, I thought I recall the training mission previously had the carrier set zero knots, which I thought was strange for Case I.

Now we just need sundogs, tangents, perizenithal arcs and other ice-associated phenomena. I'm kidding, of course! FWIW, ice halos are often seen and photographed in cold weather because they can also be caused by ice dust close to the ground, but presumably when you see it in an aircraft, it's ice crystals at high altitudes

Dang it, it happened to me also this week, but at the end of an hour flight. Had to fight to trim nose down and struggled with the go-around. Suddenly on downwind everything seemed fine again and landed normally. I won't bother with the track, just so people know it's still there occasionally whatever is causing it.

X and Y don't show up on the scratchpad, they're only denoted by the colon next to the UFC buttons I assume you misheard 'x-ray' as 'kay'?

FWIW, you can change AGM-65L codes in the DSMS->INV->INV STAT page just like all the other laser guided stuff as a workaround, but obviously this would not be the way they did it IRL...

LOL, I'd compare the A-10C to MSDOS and the F-15E to Windows 3.1

I mean, I suppose you could drop markpoints on the TAD if you weren't using them for targeting, but you'd have to copy them to waypoints to put them into a flight plan, which is clunky to say the least. That's 90's tech for you

There isn't one in the A-10C, you'd have to enter each waypoint in the CDU, then add those waypoints to a flight plan. It's not hard, but it is tedious and annoying. I'm assuming you know how to enter waypoints and add them to a flight plan? At least a couple minor shortcuts: Recall that waypoint #0 is always your initial position, so not really a need to set a departure waypoint if you started on the ground. You can add the airport waypoint #'s found on the NAV->Divert page (or scrolling through the waypoints) to the flight plan. If you already have a waypoint near your target that you want to change or copy the MGRS coordinates, if it's in the same grid zone and grid square you do NOT have to type in the grid square letters, e.g. if you want to change 38S YJ 123456 to 38S YJ 123456789, you don't need to enter the 'YJ' part

LOL, I suspect it's a bug, but I think the shadows are rendered slightly differently in each eye, so it often sticks out from the terrain more so than in flat screen

In VR, I have one word for you -- 'shadows' Unless the time of day is wrong, you can see vehicle shadows easier than any other cue, and you can scan a larger area with your Mk 1 eyeballs faster than the TGP. Especially with the spyglass zoom function, you can systematically clear out a sector by visually scanning it much faster than the TGP. And if you get shot at, you'll be able to see far quicker if your head is already out of the cockpit, and if you're fast enough you can drop markpoints on the shooters for future reference.

LOL

Looking at a point you're orbiting requires lowering the inside wing, risking masked TGP. If you increase altitude, decrease the orbit radius or decrease your airspeed, that reduces the risk of masking (in decreasing order of importance). FWIW in POINT/AREA track mode, the video tracker has an even smaller FOV than the camera itself, so you'll lose video track even while you can still see the target near the edges. In POINT track, if you're following a moving vehicle, it will change to P-INR mode, and the camera will continue to move in the direction and speed of the last tracked target, so if it's a straight road, you may very well pick up the vehicle again after unmasking the TGP. Doesn't help much on a twisty road, though

Be aware, though in DCS, most other aircraft that use VHF frequencies use VHF AM by default, and most multiplayer servers that use VHF frequencies assume AM as well, so it's still good to know how to switch AM/FM.

In case you don't realize, you can adjust your view position using the 'Cockpit Camera Move xxx' bindings, and then save that position with 'Save Cockpit Angles'. They are in each module in the 'View Cockpit' category. That way, you can tweak your position, save it, and next time you jump in you'll be in the same place, assuming you're centered in your VR environment. Since it's module specific, you can individually adjust this for each one. I actually do prefer sitting high enough that the top edge of the HUD is just on the horizon in level flight (about 5 degrees below the horizon while on the ground. I can just see the boresight circle if I lean forwards a tiny bit. That's just high enough to be able to see over the nose as far as you can. For takeoff, I just watch the AOA indexer. That's cheating, I know

Thanks, I knew it had a name but I couldn't for the life of me remember

AFAIK it does not. It only affects the Viper JDAMs, IIRC

That mission sucks. The GBU-54 sensor can't see the laser until the nose is pointing towards the ground, and the weapon's unchangeable DCS flight profile takes it on a max glide attitude until it's almost directly over the target. Only then does it nose down and only then can the sensor can finally pick up the laser. That means it won't look for the laser until as long as 30-45 seconds after dropping it. This makes it almost useless for fast moving targets, since by then the target may have moved out of the bomb's sensor or even energy range. The only way to have a chance of hitting it is to lead the ship with the SPI by a few hundred yards, then go back to point tracking and lasing and hope for the best. At least when I tried the mission again, the M151L APKWS rockets actually do significant damage to ships now, unloading all 14 at one ship does about 80% damage. At some point in the past, they would cause trivial or no damage. Edit: I've even tried diving (pointing the TVV at the target) and lasing immediately after dropping. The GBU-54 seems to either ignore the laser or sees it and records where the ship is that moment, and a couple seconds later pitches up into the max glide attitude (a great way to get hit by your own bomb if you're not careful). null null