UncleZam

I think it was that, although cannot check it now. Too bad, i can feel your pain. One more hint, disable all v-sync or frame rate limiters like afterburner statistics service, Steam or Nvidia fps limiters. Beyond those, I am out of ideas.

I think I had this issue of not being able to force 45fps reprojection. There is another menu besides SteamVR which can affect reprojection. I think it is SteamVR-WMR menu accessible through Steam menu in VR. Setting the reprojection there enabled it to me after having issues of 60ish fps stuttering and could not lock in 45fps. I can give more detailed instructions how to reach this hidden menu if necessary (and when I get in my PC). Hope this helps.

T This is usually the preferred way in programming. Coding conventions often restrict the max line length to 80-160 chars to make it readable in all editors (and without wrapping or scrolling).

That's a lot of reading, but useful topics you got there . I should still mention that you can think of Jupyter as a interactive CLI, UI or IDE for programming languages (I think it got all three you mentioned) as kernels. So you can use it as an application, like it is mostly used. But being modular, it can be extended with new kernels like DCS-lua.

This is true. I am coming from Python and learning Lua, and have used Zerobrane Studio and Vim+plugins. The former is quite neat lightweight editor, and I kinda liked it. Vim on the other hand is good if you know it or are really interested in learning something different. AFAIK it is not possible with Lua builtin console, but it is possible with some other tools. Glad you asked, because I am currently developing one. It is based on Jupyter framework, is this familiar to you? Jupyter allows for really cool interactive tools, ranging from console to rich media Notebooks and Lab, which is kind of IDE. The tool I am developing is still a bit rough and not public yet, but I am planning to publish it as open source soon. If you are interested, you could take a look at Jupyter framework in the mean time. I am basically developing DCS-kernel for the Jupyter. I am happy to tell more, if there's interest.

As a big fan of short feedback loop programming, I would suggest just start the lua interpreter to get into interactive console. There you can type lua code statements/expressions and see the results immediately by pressing enter. You can inspect variables and define multiline functions. Just mess around to get the feel of the language. Remember that DCS still uses lua version 5.1, so you may want to install that version for full compatibility. Edit: of course this goes only for learning the Lua language. Connecting the interactive console to DCS session is a whole different story.

You could try to clear all bindings in axis category for each controller listed. Even if they would not show any bindings. I have had this issue with Thrustmaster Cougar MFD button panels. Even though they do not have any axes, they were messing up my roll axis in multiple planes. The issue was resolved by clearing the axis category for this controller. Even though there was no binding listed to start with.

How about counter measures? I am just guessing here, maybe someone with true knowledge can confirm.

It says on "Flakpanzer Gepard" wikipedia page (Finnish language version), that Gepard was designed to counter heavy attack helicopters like Mi-24. I guess they succeeded in their design goals.

You can turn the landing light on, and then use control bindings to move it. It starts moving from retracted position, so you have to move it quite a bit before it is pointing forwards. The controls for the light are called "Pilot Headlight up/down/right/left".

Could someone explain. What should I enable in mission editor? I tried finding related settings, but could not make it work. Thanks. Found the solution: disable "Simplified AI" from helicopter instance settings (explained in manual). Also, when modifying th weapons range- missions, you have to do this for all armament configuration instances (helis are stacked in the same spot).

Wait a second. It is the same picture showing in the VR and in the screen mirror. In this case it sounds like VR resolution or refresh rate is not up to your standards.

Yes, but it is not so prominent then. It is very easy to forget, also in VR it does not bother me at all.

Agreed! Thanks again, you have been very helpful.

Thanks for checking and reporting back to me. This is cosmetic issue after all, and most likely DCSW-engine related. I will now forget about it and concentrate on carrier landings with this very cool aircraft!

True, I just wanted to know if my installation is somehow corrupted, since I recall seeing this kind of issue once earlier (I think it was F-16 early version). If others are seeing this then I guess we can assume this is DCS wide issue, not just this module.

This module seems great addition to DCS. Just started learning this aircraft, and I have curious problem of pilot reflection stuttering (to be precise: the reflection is jumpin up and down when the aircraft is turning) on MFDs. Purely cosmetic problem, but I was interested if this was a known issue or just my DCS installation problem (2.7 latest)? Thanks again for the module. Edit. Here is a link to video showing the jumpy reflection on MFDs:

Have you guys tried to create own bindings for MiG-21 in aircraft Lua files? I know this borders programming and is cumbersome, but those Lua-configs are quite flexible. There's 11 page document explaining the process somewhere. In fact I might give it a try next week, if I get a Warthog throttle by then.

Can you be more specific, which discord channel? And for me it would be sufficient just to see it done in Twitch right now. Your channel is up and I can hear you typing ;)

Yes, please, and there are others also. Or maybe we can get a video clip of the correct use of retarded level bombing?

We are waiting in the Twitch channel :)

I agree on this. Harrier is for me one of the most interesting aircrafts and maybe the best looking cockpit in high res VR. It still has many bugs remaining, but I am hopeful after today seeing long list of fixes in release pipeline. I also agree with some other posters that this project does not meet the criteria of professional software development. There may be many reasons, for example under resourcing.

I cannot open Encyclopedia. Just shows black screen.

I was also baffled why the ground track points roughly 25 degrees off of the correct course in Nevada. After some testing I found out following: 1. Ground track works correcly when EHSI is in TRUE mode (also accounts for the wind drift). 2. When EHSI is switched to magnetic, the compass rose (in EHSI and HUD) react correctly by subtracting 12 degrees (magnetic deviation in Neavada) to get new values. However the ground track value is added 12 degrees instead of subtracting! This results in ground track value, which is 2x12=24 degrees wrong (you can see this both graphically and in digitals in EHSI display). TL;DR: It is a bug: When calculating magnetic ground track direction from the true (as in true bearing) ground track direction, the magnetic deviation should be subtracted not added like it is done currently.

I echo lukeXIII: no issues for me when replicating the tasks in the video. The downhill during right turn in the video is indeed caused by slight nose down joystick movement, which can be seen in control indicator. Some key points that helped me to understand the logic behind the AP: 1. AP works by adjusting the trim. Just watch the white marker in the input indicator. 2. The current trim values persist when AP is disengaged. 3. You can use "emergency SAAHS Disconnect" to reset your trim. 4. AP has roll limit that is something around 55 degrees. If you disengage AP during roll, there is a good chance that nose is trimmed up and you will feel this when straightening the roll. If you disengage AP by doing rapid joystick movements, there may also be strong roll trimmed in.