TheSkipjack95

Thanks. Personally I think that the downward visibility is rather great as is, but by default the right side, with its waypoint info etc, is clipped by the HUD frame, which is rather bizarre, and the horizon line, backup pipper and often the TVV (on takeoff for instance) is fully hidden. I guess it's not an issue for the VR/TIr folks, but might prove reaaaaally annoying for the others, and it doesn't match the behaviour of any HUD I can think of, besides perhaps the Viggen. All others display all the info on the glass at a glance. I think it might be cause the HUD is rendered too close to the glass ? Font also looks huge, so maybe it's just the HUD not collimating to infinity like the others. Vague and subjective feedback FTW, but if that could be looked into, that'd be grand.

Is that HUD rendering gonna stay like that ? Liking the new pit so far (text is finally easily legible), but I feel I need to stuff my face in the HUD glass to see all the info on there, seems very odd to me. Can't think of another plane where that is an issue, so to speak. Can the SMEs confirm the HUD is rendered right ?

Just a tiny niggle, but the message from the ground crew acknowledging your request to update the DTC feels a tiny bit off. I fixed it myself in my install, but if the message could be changed to something like "Copy! Updating the DTC now" or something similar it would feel a little bit less awkward and engrish. Cheers.

I figured it out : 1 : Record your custom files in wav format and name them like the stock ones. 2 : Place them in a "CE" folder next to the other voice pack folders (DCS\Mods\aircraft\JF-17\Sounds\Effects) 3 : Go into DCS\Mods\aircraft\JF-17\Sounds\sdef\Cockpit 4 : Copy the sdef files from the "EN1" folder into the normally empty "CE" folder. 5 : Open all the sdef files (with notepad++ or similar) and change the "wave = "/Effects/EN1/[FileName]" to "wave = "/Effects/CE/[FileName]" 6 : Select "CUSTOMIZED" as the voice pack in the special options. 7 : Enjoy

Done that, still don't hear it. Is there a specific format it needs, are my titles wrong ? I've tried with an instant action too, triggering the warning message by switching FCS modes, can't hear anything with my file, works with the default ones.

Is there anything else we need to do to have custom voices ? I recorded wav files and named them like the original ones, and they're placed into a CE folder next to the others and I still can't hear them. What am I missing ?

Tacan has no channels, but has channals instead.

Finally ! https://razbamsimulations.com/index.php/paint-kits/dcs/mig-19-paint-kit?fbclid=IwAR3ThI6xGgoSAHQfkXqweLAFFntdQrDgt_Ur_ZqeAKlqpok4bGye2oaeEls

Could anyone please make a livery of this Sabre ? It's the only one flying in Europe, and should be fun with those shiny accents on a matte livery. https://www.aerobuzz.fr/aviation-generale/un-f-86e-sabre-dans-le-ciel-de-france/

I would love it if someone made G.91 liveries for the Sabre (or if a G91 module came out, 91Y pls)

Can someone make this one ? D-FWAA from Hangar10

Filing the AB detent of the WH is the easiest way to have a push-through detent. Just need to file it by small amounts and test until you can push it through without too much of a hassle. I did it months ago and it's still fine.

Trim will almost never make the plane fly perfectly hands off, it's there to reduce stick forces, mainly. So it's normal that you can never quite get it to fly straight. Same thing in the F-5

It depends on personal preference and hardware, so we can only really give you guidelines. Generally what I do is have the stick in non-linear, take it up for a flight, and play with the curves until I reach a setting where it is heavy enough to provide stability and not feel "on edge" all the time, but not so heavy as to hamper maneuverability. I generally have more pitch curve than roll (I think I must be at 10 on roll and closer to 20 in pitch), and I set a deadzone big enough to feel like it is there, but not so big as to require significant movement of the controls to register input.

Thanks for the fix. It has cured the rudder offset, but it doesn't seem to do anything with regards to the takeoff assist or reduced yaw moment. I have tried setting the values relating to autotrim and takeoff assist to 0, but that didn't change anything, and I can't use the keyboard to use the rudder, despite no controller being bound in the controls. I'm impressed ED somehow managed to break a plane with nothing more than wings and an engine.

Acro, Do you also have that frankly bizarre rudder behaviour introduced a few patches ago ? The rudder now stays left of center when flying, and seems to try and correct yaw on takeoff, which is now somehow much reduced. Every assist imaginable is off and the non-functioning trim tabs are all centered. Best answer I could get from ED people is that it is indeed a bug, but nothing else.

All I'm trying to prove is that my Yak 52 has an essentially broken rudder for me when the only sin I committed is updating my game.

To my knowledge, trim tabs still have no effect in DCS, and even if they did, I had very bizarre behaviour even with the engine off.

Yep, autotrimmer, autorudder are both OFF, takeoff assistance to 0, trims centered, and I even disconnected my pedals. I even reinstalled DCS a few days ago (unrelated to this though), and the problem persists.

Yep, on release and up until a few weeks ago, the Yak needed what seemed like a normal bootful of rudder to counter the right turning tendencies, and the rudder behaviour generally made sense. After the last couple updates though, the rudder seems to have a mind of its own, somewhat attempting to counter the torque on takeoff, and then staying just left of centre for the rest of the flight. I know the trim tab system (the one for the ground adjustable trim tabs) is still WIP, so I thought it might be that, but I don't know, hence this thread.

During a takeoff roll with slow power application it seems to try to correct the yaw by increasing the rudder input, but it's not really effective and accurate. After taking off it does stay slightly left and doesn't coordinate yeah, so I'm not 100% sure that it's the autorudder, but as far as I know the trim tabs do not work on any of the aircraft that support them. Just seems really bizarre that I was able to takeoff through teamviewer on my laptop with the keyboard and no real difficulty, when a couple patches ago it initially required a healthy bootful of rudder. PS : you can enforce realism settings in the mission options in the ME (if you tick ENFORCE it'll override any user settings for that parameter, and ticking the box right of that sets whether the parameter is on or off).

Thanks for this, makes the plane look even better than before !

See the other forum thread for further discussion. Since a patch or two, the rudder required to takeoff in the Yak 52 has drastically reduced, from about half deflection at the start of the roll, to almost no rudder required on the entire roll. Upon closer inspection, it looks as if the rudder axis has the autorudder feature activated, despite the setting being OFF in the options, and even enforced to OFF in the ME (Rudder input moves on its own during the start of the roll, seems to try to correct any deviation, and then stays slightly to the left afterwards). Bug ? Or modelling of forces alà 109 ?

I thought that might be the case, but on take-off it starts centered and acts like autorudder. I'll double check for game mode, but shouldn't there be the radar screen thing on the screen as well?