The issue with this is that many other planes use the same mfd model
Example the j10
first two fixed, third not yet
1 Like
this is incorrect unless you are using vr heatset. Those camera controls get disabled once wt detects: “NPClient64.dll”, which is used by opentrack etc, to make the headtracking possible, making it impossible to adjust.
In fact, there was this one funny issue i came around, where a twitch streamer i watched had problems with setting up zoom axis on his tanks, because he long time ago used Opentrack and didnt tick the “Clear location when tracking is stopped” in opentrack settings
but why zoom of all things you might ask? Its because there is this funny setting in the wt (enabled by default) which says “control zoom with head tracking”, Which disables the camera axis keybinds once the “NPClient64.dll” is detected in the war thunder game files.
So basically war thunder disabled his zooming capabilities in tanks because he had both the “control zoom with headtracking” enabled and “clear location when tracking is stopped” disabled :^)
to add to the confusion, NPClient disables manual binding of zoom axis, but doesnt disable automatic binding via “scroll wheel action” option.
(sorry for the late reply lmao, havent visit forums in a while)
J10 and J11B both have the wrong hud in cockpit…
When the J10 and Jf17 were released, their hud in cockpit didn’t even show what had you locked with the radar, meaning that you had to use your eyes to guess who and where you had locked…
It took them several months, but at least this issue is now fixed though now there are several more.
Now, in the latest patch a lot of new vehicles were added, including the J11B that unfortunately come with quite a few problems (placeholder radar for example) but also it has the same hud as the J10 and the canopy tint from the inside of the plane is pretty much non existent, even though it’s clearly visible from the outside.
I hope this issues get fixed fairly soon.
The GR4 missile naming on the HUD should be fixed now
1 Like