Ironhand

YAHOO!!!!

Kill joy.

Dead stick landings are great fun from altitude, aren’t they? Establish your best glide speed and decide where to put down.

That’s why something is amiss. With the steady state wind that we currently have in the sim, no matter its speed with no turbulence or eddying, I’d might as well be flying with no wind. It only becomes a factor when orienting to the ground. But I was holding a 20* bank and, suddenly, both engines died.

@average_pilot I missed this thread the first time around, so thank you for bringing it back up. To be honest, wind/IAS isn’t something that I spent too much time thinking about. FWIW, wind speed seems to have no significant effect on IAS. Take off directly into a hurricane force wind, set your RPMs and the speed you settle into seems be the speed you stay at regardless of which direction you fly. The engine stall is another matter. While some in this thread have said that they only got it at slow speed, I’ve had both engines stall while making slow turns at speeds in the 500-600 km/hr range. Not at all sure what’s going on there. But something certainly seem amiss.

You’ve made me mildly curious. What was the original advertisement?

The only way to do it currently is with the old clouds. Select “Nothing” for the cloud pattern, then use the sliders and selections below to generate the effects you want.

The Sparrow, regardless of airframe, requires an STT lock to guide. It’s an SARH missile. TWS doesn’t provide the amount of guidance it needs.

Yes. Sparrows require an STT lock in order to guide.

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?