Ironhand

I’ve used it in the past as a plug-in for Photoshop. So I’d generate what I wanted in Photoshop and save it in DDS format. I imagine the stand-alone would require you to first generate what you need in some sort of paint or photo program. Save the file in BMP or some other format. Then run that file thru the standalone.

Eagle Dynamics does not offer mod support. So, until the mod creator adjusts their mod to work with the current OB, the problem will persist.

Last update to it (on Github) was 8 months ago, if that suggests anything.

Another person with the same issue but in the Su-27:

Someone else with the same issue, different aircraft. Perhaps the two of you can compare notes. Usually, this type of thing is mod related. The mod does not necessarily need to be one for the specific aircraft.

https://developer.nvidia.com/nvidia-texture-tools-exporter

OP “original post” or “original poster” (as in the person who opened the thread). And a warm welcome to you.

I believe it was a few updates ago but I’m also not sure that it was formally acknowledged. EDIT: Here’s a thread from November. The actual switch that created the bug noted by the OP was from the switch made a bit earlier.

At the time the tutorial was created, the Mercury pod was being modeled (incorrectly) as being infrared, hence the tutorial description of what to look for. The pod is now being modeled more correctly as a low tech light amplification pod. So things no longer show up in high contrast as they once did. The target is on the runway centerline just above the white runway markers. The tutorial needs to be remade. in your second set of screens, your seeing what you should see with the pod amplifying daylight—a bright, washed out screen.

If you revert back to a single monitor, does it reappear? My guess is that, with a two monitor setup, it’s being “displayed” outside the viewable area.

Unfortunately, the result would be a missile that “should” have hit in a given situation but didn’t for no apparent reason. For instance, the target notched it and it didn’t hit. Or the target barrel rolled and it didn’t hit. And players would be complaining about the bug because of a mistaken cause and effect.

This “teaser” constitutes cruel and unusual punishment…

Don’t know anything about it but here’s one of them https://www.digitalcombatsimulator.com/en/files/2829090/ And here’s the one from cookiemonster: https://mega.nz/file/E3pwjIKK#z-wxf7GqY_a_wjXxDoZ8CXaukytr_MHe0VZ8_31TKJM

I notice that the aircraft in the video are all F-16s which is an incredibly small aircraft. Even a MiG-29 is bigger. I wonder if that has something to do with what you’re seeing, especially in the presence of countermeasures. It’d be interesting to test against other aircraft with and without countermeasures.

Unless there is a problem with the joystick itself, there is normally only one reason for this to happen—a duplication of the rudder command somewhere that is being activated. If he unplugs his joystick, are the rudders still hard left?

Evidently, it only works properly with the MT version of DCS Open Beta:

Not exactly new to the sim myself but thank you for the time and effort you put into this.

I wasn’t when I tried the mission. It only works on MT? EDIT: Problem solved. It evidently only works properly with the MT exe.

Or, perhaps, he did slew the reticle to the ground. I have the same issue as the OP. The display remains dark. I can see more with the Shkval than the Mercury pod. Obviously something is wrong on my end. I’ll need to double check for mods. This is supposed to be my clean copy but who knows?

Su-25 Clean, No shaking beyond high speed shake at around TAS 900 k/hr, M 0.76. Su-25 Dirty, Shakes right down to TAS 360 km/hr (probably further but that's where I stopped) (TRK of this attached) Su-25-Dirty_Shake with Air Brakes Extended.trk

After the first fight devolves into a two-circle fight, you’ll get an excellent idea of what the Su-27 pilot would be seeing…

If you simply want to practice, you can do what you're looking to do on the right map. Nevada, for instance, because of the higher elevations involved. I tried Groom Lake with Overcast 6, 1300 meters. That worked pretty well. Use a lower base and It'll be right down to the ground, though there might be clearer holes here and there depending on cloud structure. You can also use the old clouds for a more uniform effect, if you prefer. There's something odd going on with the cloud bases because, once in the sim, you either have the cloud bases far enough above the ground not to suit your needs or right down to the ground on airfields with runways below 900 meters altitude with nothing in between.

Excellent. Wish I had realized that there were three steps, not two, sooner. But at least you and your team have that squared away. Enjoy. And thanks for letting me know.

No, there's not. Just to make sure we're on the same page, do the following. Do your startup procedure and take off. Once established in flight, select EAC Arm (LAlt+4). Next select LAAP Altitude/Heading Hold (LAlt+2). Finally, LAAP Engage/Disengage (A). Did it work? EDIT: It's been a long time since I've been in the A-10A pit. I realized this evening that there are three steps, not two as suggested in my previous post. EDIT 2: Forgot to mention. Make sure you’re in fairly level flight before steps 2 & 3. Not sure how finicky the AP is.

I assume the instant action is an air start? If so, that's why. The EAC is already on in an air start. If you're starting dark and cold, you need to turn it on (keyboard "A" toggles it on/off). But another question is what AP function are you attempting to engage? There are only two: Altitude/Heading Hold and Path Hold. A third option, Altitude/Bank Hold, is listed in the controls listing but doesn't exist in the sim. Not sure why it's there because the A-10A sim manual only refers to those first two.