All Activity

It's better to take out the spring in your pedals, but there's nothing stopping you from just adding another instance of this Plugin

No not today, I will let everyone know once we have a date. Keep an eye on the patch status forum post. thanks

the q3 hand tracking is pretty noisy and they've used a lot of averaging to try and stabilise it, resulting in lag. I think you'd be pretty disappointed if you could try it with the crosshair or pointer attached to the finger the leapmotion device is about as good as I've seen for finger tip control, but even that has it's own caveats due to problems with reflections, shadows and any nearby cockpit objects affecting it's performance The HTCC app and Q3 is a reasonable compromise once it's setup well

No need for a button. Even with MSL selected, if you put a WP on ground and type its altitude as 0, it will automatically adjust to MSL altitude corresponding to 0 AGL.

Nope, I just know that @Actium has his head screwed on regarding DCS on Linux.

patch today?

Wow, this bug is nasty in the Hornet and Tomcat. I can be clearly seen in any light texture. After an upgrade on my computer I finally can enable SSAO, but both on Low and High settings they look the same, with that fixed pattern on the screen that does not move with the view. Too bad, because otherwise SSAO looks great in DCS. I see that this was reported over two and a half years ago... anyone has found a workaround other than disabling SSAO?

FM is still strange, shape needs adjustment, but works for eye candy.

Being relieved

I have seen something similar happen before the latest patch (can't remember the conditions), but at least it didn't CTD or freeze the game. The IDN and Boule were all messed up, but at least the pointer showed the correct position in RNAV mode. Was on CWG IIRC.

can you use it for the yaw axis too?

I just compared the coordinates you get from the JTAC during the 9-line against a real MSGR map of the area and they're correct. (It does have it's advantages, working as civilian in the army)

Do you have the same problem Max? For me the old 2.5.6 version is working, so it is definitely because of the patch.

LOL always something. But yeah, Viacom does create problems for missions for some reason.

Hey.. I really don't have any control over what the taxi directors are doing so not sure if I'll be able to troubleshoot this one but will also ask my testers to have a look. Will keep you posted.

Sure, First lets clarify what is exactly stated in the flight manual about the aileron limiter. The flight manual states that full Aileron travel is 35 Degrees Up 25 Degrees Down. The manual also states that the spring stop limits AILERON TRAVEL to 1/2. The Flight manual does not state that the control stick is limited to half of its travel when the spring stop is engaged. The description of the aileron flight controls from the Northrop F-5/E Technical Description proves that the aileron limiter is physically located at 80% of the control sticks travel. This document contains the Stick Travel Limits, and the aileron travel limits. When the Landing Gear is down: The aileron limiter is turned off. And Full Aileron Travel is available, (35 up / 25 down), and Full Stick Travel to 4 inch is available. When The Landing Gear is UP, The aileron limiter is on. Aileron Travel is Limited to 18.5 Up / 14 Down, Stick Travel is Limited to 3.2 Inches. Thus when the Aileron limiter is active. The Stick travel is limited to 80% as (3.2 / 4) = 0.8 And Aileron travel is limited to 50 % as (18.5 / 35) = 0.52 Thus, the Aileron Limiter / Spring Stop is physically located at 80% of the sticks travel (3.2 inches) and limits aileron travel to 50%. As described in the pilots manual. If the stick is limited to 3.2 inches and the aileron 18.5 degrees, than limiter can only be located at 80% of the stick travel.

Your picture of the APP HUD with a misplace ILS Localiser Line and Synthetic Runway is typical when using a PCN "Landing" waypoint that has an incorrect Runway direction i.e. the runway heading entered should be it's TRUE heading. I'm currently reinstalling the Sinai Map to view your posted track before providing further feedback. Additional Info Here is an example of what happens when the runway heading is set incorrectly

Thank you now I can see it !

And I love the P-47 and I'm still waiting for the hydraulics simulation. I don't think it will ever be done. What a shame! The P-47, for me, is the most fun WWII aircraft.

Check your MFD resolution under graphics. Near the top left of options. I was having same issue and finally figured out somewhere along the line mine got set to 256. Put it back to 1024. -Cal

Well, that's exactly what I am doing. If you read the original post..

Oof, wait ill upload it directly to the forum... try again

Unfortunately, your link list is more of a commendable exception. I also wasn't referring to you directly, nor did I mean to sound accusatory. It's more of a general appeal and should allow more users to enjoy your work. However, TANGO and IX514 are missing in your list too

I've seen that smearing, but only if I had the settings up way too high or using DLSS without Preset K. Normally the display is very fluid, especially at 120Hz.

Ooooo, that's brilliant! It can be a real pain to deal with in a non-FFB stick while flying the Hokum, for example. Have found workarounds, but it's not all that great. Must test.