escaner

Thanks a lot Timguetta, look awesome. :) While you are at it, can you make sure that the following problem is solved? From your screenshot I think it is, but better safe than sorry... https://forums.eagle.ru/showthread.php?t=201520

Thanks for your reply, BlazingTrigger. When I found the need, the rocket pods were already unselected. So there is no way to select them back for this purpose, right?

How do you jettison empty rocket canisters? The moment they get empty they disappear from the PCA and I cannot select them.

You cannot use exterior images as reference to how it looks from the inside. Coatings are not the same in both directions. It is obviously overdone and the original color is goldish instead of the green tint that we have. It is also seen in many F-16 and EA-6B and its function on those, besides shading, seems to be to work as a Faraday cage, isolating from external radiation, but I cannot see how that would be the case in the Hog.

A few screenshots with DS on and off, check the difference in FLOOD and TAXI lights https://forums.eagle.ru/showpost.php?p=3378523&postcount=10

I was testing disabling deferred shading, came back to post my findings and I read this. :lol: There you go...

Thanks for the replies. My gamma was 1.9 and raised it to 2.1 or 2.2 because I could not see at night. The whole map is pitch dark and town illumination is barely visible but that is a different bug. I guess I never tried the A-10C in V2.2 at night. Has this bug already been reported?

Anyone else tried the Hog at night in 2.5? Internal FLOOD light is not working (barely gives any light), and TAXI/LANDING lights also too dim.

Hey guys, one last thing: how do you contact Baur? I sent him a private message in this forum but he won't reply.

Now that rings a bell :)

Thanks a lot guys for your replies, they were all very helpful. I see now that both systems are parallelograms, but still the second design looks more rigid and stable to me. If someone can comment on his first hand experience on how the curved design handles wear and whether it develops some play or not after some time of usage I would be very grateful.

Hi guys. Seeing that MFG "combat" pedals never seem to arrive, I am more and more interested in the BRD Su-35 ones, despite the customs issue. I understand that there are two basic actuation systems: BRD-MS3/F3: BRD-F1/F2: I would like to know how the BRD-MS3/F3 works (see attachment, sorry for the low quality drawing :music_whistling:). When you push one pedal, the footrests rotate with the arms of the pedal as in (2) or they stay parallel as in (1)? Is there any difference in maximum longitudinal displacement between these MS3/F3 and the F1/F2? Any difference again between MS3/F3 and F1/F2 models in distance between footrests? Do the MS3/F3 models come with a CAM system? How is the default one? Are there other CAM options for the MS3/F3 models? How is the wear with the use of the MS3/F3 models? Having only one axis in the middle it looks like a weak point for durability to me, the other option looks stronger. Thanks a lot!

Never saw that word, is it an acronym?

I have always flown the Huey taking a look at the EGT and trying to keep it within parameters, and a fully loaded chopper would do about 90-95 KIAS at low level. Since this update, either the power has been increased or the EGT lowered: a few days ago I did Sukhumi - Sochi with full fuel and two Miniguns at 115 KIAS. This performance was impossible before within limitations. Obviously the engine was undamaged and continued flying around for some time. What I found strange is that little adjustments in collective would spike the EGT gauge and then settle in few seconds later.

Being gentle on the throttle does not ensure proper lighting. I have suffered this both pulling G, at high AoA and at 1G on the runway going from stabilized MIL to minimum AB just after releasing brakes for takeoff. I also think that it is not a bug per se and so I stated it in other thread long ago (https://forums.eagle.ru/showthread.php?t=172526). Anyway, Skatezilla said that the developers were contacted 16 months ago, and every time that I suffer this problem, I remember his post. Therefore I am interested in knowing the official response. Further speculation adds nothing that was not already said in this and other similar threads.

Did they reply about this problem? It is a bug? Is this WAI? If WAI, how are we supposed to systematically get a good burner light?

It has also been fixed in V2.2, nice!

Not just NWS, the rudder axis in general is hypersensitive, needing insane curves. The problem is stronger with NWS because the input is amplified there. If I set the F-5 to the highest curve value for any of the other DCS modules that I have, it is impossible for me to control it safely in the takeoff and landing runs because I am incapable of doing smaller inputs with my pedals.

You want an orthographic projection, in which objects appear always the same size, not depending on their distance from the camera. DCS tries to emulate the real world, so it uses a perspective projection. That is why you cannot get a blueprint-like screenshot.

Thanks a lot! Can't wait to try it. :)

The speedbrake switch is 3 position. Fwd retract, back deploy, middle stop movement. The functionality is in the HOTAS section, and you can leave them in any position.

In the sounds area I would be happy if they just remove the doppler effect with no relative motion camera-airplane (it is very disturbing for me) and fix the above Mach 1 mute _inside_ the cockpit.

Yes Su-27 has both too.

OK, looks good then. Thanks a lot for the feedback!

That video was uploaded 5 weeks ago, so obviously not latest version. Anyway needing to do tricks to be able to hook a cargo means that the bug is still there and should be fixed, so please don't say "if you updated to the latest beta yes cargo is working" when that is false for this mission. OTOH, I just tried it again and had the same results as Nakha Sukka: it is still bugged and those tricks didn't work for me either.