jaylw314

Hard way - there are DCS updater command line options you can look up Easy way - SkateZilla's Updater/Launcher GUI Just to clarify, it sounds like the only people seeing this problem are using a black HUD font mod? That would have been good to clarify from the outset

It seems like multiple people have seen no change, including myself. Have you tried the standard troubleshooting of doing a repair and clearing shaders?

Nope, you're right, I read incorrectly, JP3-09 just says using cardinal directions is "not recommended"

Maybe the way to think of this is that while type 1 is inherently safer, you end up using it in hairier situations than type 2

My understanding is that this is technically only true if the JTAC passes it as a 'restriction', and that requires specifying a final attack heading or heading range. AFAIK reading the JP3, using the cardinal directions is not specific enough and implies it's a request. I suspect, though, that if he specifically says "restriction - south to north attack" then that would count.

If that's all you want J2K makes more sense

Whenever you connect a new peripheral, including a vJoy, it's a good idea to clear ALL the bindings from it. DCS tends to have a default set of bindings that don't always make sense. It's a good idea to clear all the button bindings from your physical joystick that you intend on using with JG Using JG to trigger keyboard presses is generally a terrible idea, because they're problematic to emulate, since timing, duration, and combinations could all affect what the result will be. JG was intended to be tightly used with a vJoy device. That way it pressing Button 10 on your physical joystick would trigger both Button 1 & Button 2 on vJoy. Then you go into your DCS control settings and bind vJoy button #1 to the same function that 'f' is bound to, and vJoy button #2 to the function that 'g' is bound to. Now when you press button 10 on your physical joystick, it triggers both functions.

I'm hoping friendlies were actually NE or NW of the target. 'All friendlies are to the north' would still be technically correct if he was telling Hawg to keep his fires south of the target

There shouldn't be. vJoy installs virtual controllers, but JG only controls them when it's running. If you don't run JG, J2K should work fine. I'm not 100% sure if the other way around is true, though. In general, vJoy is ridiculously powerful and the stuff you can do will blow your mind, but it takes reading the docs. J2K is simpler but still useful for most tasks.

I don't know J2K, but with Joystick Gremlin that is a trivial task. In JG, you do not need to 'hide' your physical controllers except in rare instances. In DCS, you select a binding under the "vjoy" device, and it will only look for buttons that JG sends, not the buttons on your physical joystick. For other apps that look across multiple devices at once when you're setting them up (like Voice Attack), you would use the "Input Repeater" tool in JG, which repeats your vjoy input multiple times after you press the physical button. That way, your physical joystick won't interfere. If you don't need to do fancy JG stuff with your axes or buttons, you would simply bind your physical joystick to them, not the vjoy device. In that case, you could just create a vjoy device with a few buttons only for simplicity, and use them for the fancy functions you need (which is what I do). Yes, you could set up HID Guardian to hide your original hardware, but, in general, it's really not necessary and can be inconvenient in other circumstances

In public MP, it's problematic--you're slow, so by the time you get somewhere, the situation may be different, and AI air threats can be really annoying. In squadron MP, it's fantastic. The most powerful ability in squadron MP is not to destroy things, but to maintain SA for everyone else.

LOL, I was going to ask if it was '30 mm turbulence'

I figure it's some kind of gimbal lock effect (not gimbal limit). If it was some kind of gimbal limit, the TGP diamond would just "crash" into a barrier and not go any further. It's telling that it spins around a point right about where our TGP spins around, although our TGP seems to maintain track a little closer to that point

I just noticed something on this very well known HUD cam footage. At about 6:05, right after the pilot says "in for a dip(?) check", you'll see the TGP diamond co-located on the steerpoint as he turns in. As the steerpoint enters the HUD, you'll see the TGP diamond make a clockwise roll around the HUD and settle back on the steerpoint. The spin is a little slower than what we see in DCS, but it's the first IRL data I've seen that confirms the TGP does do something like this.

Yeah, tough to get by in DCS on anything without curves on most consumer joysticks, unless you have stick extensions of some kind

LOL, I'm okay for now, until they introduce the FCR, then my HOTAS will go into a corner a silently cry

Aside from being generally not recommended, the parking brake also disables anti-skid, so it will actually take longer to stop.

It changes to ALT, but if the LAAP is still engaged, it won't change until you disengage and reengage it.

I'm starting to think you're trolling here, and your English is too good to chalk it up to some kind of language barrier, but I'll give it one more try. The DCS function is called "Coolie Hat Left". That function can be bound to any key or button. By default, it's bound to the keyboard 'H'. So if you press and hold 'H' for more than 1 second on your initial image with the TAD on the left MFCD, you should see the TAD become SOI. You appear to have "LCtrl + POV1 left" also bound to "Coolie Hat Left." So if you press and hold LCtrl and POV1-left on your joystick together for more than 1 second, you will get the same effect. Your lack of the Thrustmaster HOTAS is irrelevant. The names of the switches refer to the functions in DCS, not the switches on your controller.

Looking at your video and reading your response, it is not clear to me that you have read any of the other responses from others. At least 4 people so far have mentioned to you that SOI is selected by pressing the keybind for Coolie Hat Left or Right long.

In thinking about how people learn, that does work, but it's not very robust. Think of it this way--you NEED to learn how to completely lose where you want to be and how to recover. If the tanker starts turning, for example, you quickly have to shift your pitch, bank and power to aggressively return to position. Keeping sight of the BIG references helps you do that, but keeping the numbers and throttle/stick position don't.

I don't think focusing on the velocity vector is a good idea. It's just not sensitive enough to show small changes in vertical motion during formation flight. Even a couple pixels up or down is a significant vertical speed. It's kind of like how in primary pilot training students tend to look at the artificial horizon to control their pitch and roll. It's just not precise enough to adjust attitude by a couple degrees. They should be looking at the REAL horizon, which is much more precise.

If you short-press 'H' or 'K' it should cycle the left and right MFCD pages, respectively. If they don't, you've borked your keybinds somehow. If you select a TAD, MAV or TGP page on the MFCD, then press the highlighted OSB on the bottom row, it should make that page SOI. In your first image, that means pressing the highlighted "TAD" OSB on the left MFCD. If it does not, you've borked your install somehow. If both the above do happen, you have some major operator error

Those can only be done by the ground crew, so there is no keybind. You have to use the comms menu. I spoke with someone who worked on A-10's, and he said the pilots should not extend the boarding ladder, the ground crew should. I suspect they're worried about the ladder getting damaged from dropping

AFAIK the canopy is on an essential electric bus that does not require the battery switch to be on. There's an external canopy switch next to the boarding ladder.