jaylw314

REMEBERING to do it is a whole other thing, though

On an ILS, turning the COURSE SET knob does not affect the localizer needle (although it changes its orientation, obviously). Haven't tested this in DCS, though. Of note, the yellow bars on the attitude indicator are NOT the localizer and glideslope indicators! They are "flight director" bars, which give roll and pitch instructions to get back on the localizer and glideslope. The glideslope indicator is the small arrow on the left edge of the attitude indicator, and the localizer indicator is the Course Deviation Indicator (the white needle) on the HSI. The difference between the traditional "needles" and the flight director is subtle, but significant. With the flight director Bank until the vertical bar is centered Add or decrease power until the horizontal bar is centered Scan the localizer and glideslope needles to ensure this is keeping you on (or correcting you towards) the proper approach

I think you are correct. There are a couple twists, though In INR-P mode, the TGP continues to track a point in 3d space PLUS it's calculated movement before it got masked. If you're in POINT tracking a moving vehicle, when it goes to INR-P, the crosshairs will remain centered on the vehicle, but if it turns or changes speed, the crosshairs will drift off. In inertial modes, there can be ambiguity due to terrain, e.g. the TGP doesn't know if you're pointing at the hillside or the valley behind it because its line of sight hits the terrain in more than one place. POINT and AREA are unambiguous, in theory, so the TGP should know you're pointing at the hillside in front. This can cause some wonkiness going from POINT/AREA to INR-P/INR-A, the TGP can start tracking the wrong terrain location

NP, you can find all sorts of things poking around the cockpit script lua's.

The TGP has a dead spot directly forwards where the lateral gimbal hits its stops. If you watch your HUD, you'll see the TGP diamond spin around that point as the longitudinal gimbal tries and fails to track. Try not to pull your TGP target through that dead zone when you roll in. I've been making a habit of rolling in with the HUD centered 5-10 degrees above the target, which is fine for Mavericks.

You are looking for the Mods/aircraft/A-10C_2/Cockpit/Scripts folder. In there is the HOTAS/HOTAS_param.lua and the Maverick/maverick_interface.lua. The default slew sensitivities can be set there.

It should be worth noting that Baltic Dragon's "The Enemy Within 3.0" has been updated to natively include the A-10C II, so no editing required and it shows up under the A-10C II campaigns. I'd also note that Baltic Dragon has stayed quite active updating his old campaigns to keep up with DCS updates, so reported bugs are usually fixed reasonably quickly. TEW 3.0 was one of the few campaigns I could finish without getting stuck.

Doesn't seem to be. If you carry APKWS rockets, make sure you switch to other weapons by changing weapons profiles rather than pressing the master mode button.

Argh, stuck on Mission 10. After the destroying the first set of vehicles, nothing happens. I've tried 3 times, but no success. Off to the ME for the next mission, I suppose...

The TGP has a blind spot directly in front. It's not at the TVV, which moves around, but it's fixed about 5 degrees below the boresight circle, which, not coincidentally, is about where you would place targets to fire the cannon at them. A buddy suggested when using the TGP and rolling into the target, to roll in with the nose ABOVE the target area rather than THROUGH the target area (which is how I learned to roll out). That way, when you roll out, the dead zone stays above the target. It seems like a dumb design decision, they could have moved the gimbals to make the dead zone off to the side or something, but oh well.

I was surprised to find out this is modelled. Various checklists and publications for AA refueling in the A-10C indicate you are supposed to press the Line Check button a few minutes prior to AAR. This pressurizes the closed refueling port over the next few seconds. Once it reaches a certain pressure, the AAR Ready light comes on and should stay on for a minute or two. This acts as a leak check--if there is a leak big enough, the light won't come on, or will turn off quickly. The manual suggests the Line Check button has no function, but it does indeed work this way. After refueling and closing the refueling port, the port is pressurized again automatically to push fuel in the refueling lines into the fuel tank. During this time, the Ready light will again turn on for a minute or two, which also acts as an indication the port has closed correctly. Both of the above are actually modelled, and if you've ever wondered why your AAR Ready light was on despite the port being closed, now you know! What an amazing module!

You don't have frustrum culling turned on in your autoexec.cfg, do you? Floodlit objects are not rendered in the right eye (IIRC)

In this track: I look to the right and set a SPI I look away and back a couple times to confirm the HDC is remaining on the SPI I look away and press TMS Up Long a few times. Since the HDC is on the previous SPI, this should not change anything, but each time it moves the SPI and HDC to the edge of the display I press TMS Down Long to reset the SPI to STPT, and the HDC remains in place as it should. When I press TMS Up Long again while the HDC is in the display, it correctly sets it to SPI again. If the HDC is out of the display, it sets a point at the edge of the display as SPI (and moves the HDC there) HDC Bug.trk

Not sure if this is a DCS bug or a real life bug, but if the HDC is off the HMCS display, and TMS Up Long is used to set SPI, the SPI is created not at the HDC location but at the point on the edge of the HMCS display towards the HDC.

I do not know if this is intended behavior, but I suspect it is not--there is no way to safe countermeasures other than turning off the CMSP now. You cannot start a CMS program while the CMSP is in STBY, as should be correct.

That's worth a +1. Most important for boom tankers

IIRC, there is an arrow next to the GIMB ROLL warning. However, when I tried rolling in that direction, I don't recall it fixing the problem.

I'd vote for that to, especially if it gets you more sleep :)

For whatever reason, I think it's much more noticeable in dim or dark environments (like night flying) than in bright environments

I have rudder pedals, and I don't need the extra axis, so I program the twist axis to be two extra buttons, like prev and next waypoint in FC3 aircraft. Edit: Hah! I didn't read your comment carefully enough, you're doing the same sort of thing!

Looks like I'm having the same problem, it's about 1 minute after checking in with Overlord at WP2 I posted the log files here: https://forums.eagle.ru/showthread.php?t=283333 Edit: Aaaaaaand, it's suddenly working after the last OB update! Now I have to figure out how to keep my wingman from being shot down...

Happens repeatedly at the same point between WP2 and IP Delta, presumably because some type of scripted event. Posted to Baltic Dragon's campaign bug reports as well dcs.log-20200817-021156.zip dcs.log-20200817-015202.zip

I ran into the same problem with the open beta 2.5.6.50979 version. I suspected something was up when my wingman called out "bandit, 10 o'clock". I wasn't sure if I should try shooting it down, but it's good to know that's a workaround. Thanks! Edit--I tried it again, and it worked fine. strange

As someone mentioned before, if you want to add extra voice commands in addition to VAICOM, make a new profile and add the commands to that. In addition, in the VAICOM profile, you need to enable an option to use commands from other profiles, and then select that other profile. That way, VAICOM will use the commands from your other profile even when it's running. Not at my computer now, so I can't remember the name of the option, but I believe from the VAICOM modify profile window, you press the "Options" button and need to enable it in that window. Also, you all know that Bailey has one of the more extensive sets of Voice Attack profiles that are pretty sophisticated, right? https://forums.eagle.ru/showthread.php?t=242416

I think it's intended for use in MP servers that script F10 menu items that stay the same, as opposed to single-player campaigns that have different F10 items every mission. FYI, you can still check the F10 menu in DCS with VAICOM active by saying "Mission, options"