Silver_

Thanks my friend you are right. Happy New Year, and thanks again.

In the firts points , thank you very much for the clarification. In the latter I disagree with you, since when you return to MAIN POWER and the plane is without the main engine running, it does not enter INS alignment, you can try this in a start-up and wait for the time you deem appropriate, it will never be aligned, DED doesn´t go too . I rather think that when resetting the electrical system the ADI automatically goes into autolevel mode. But I still have doubts that this is the case in the real aircraft. Thanks my friend.

When for some reason (lack of fuel, engine failure, etc) the engine shuts off, and you are turning at a certain angle, the ADI stays working but out of calibration and does not mark the horizon correctly. The solution I found was to go from MAIN POWER to BATT, the ADI automatically stops working (I don't know if this is normal too!!!) and level the plane with the SAI (this is always working, both in MAIN and in BATT) and , once the plane is leveled correctly, turn the switch to MAIN POWER again. With this I have the ADI, again, calibrated and working. Keep in mind that this flight was made in very low visibility conditions, hence the need to calibrate with the SAI. My question is whether it is normal for the ADI to go out of calibration and lose its normal position due to an engine failure where the batteries are supposed to take the control. Also if when going to BAT it is normal for it to stop working. Thanks

Did you change the release angle by chance?

It's a mode that is activated within the OpenXR toolkit, my friend.

Thank you very much friend, glad to hear from you. For me personally, Turbo mode suits me better, I tried removing it but what @speed-of-heat says, happens to me.

The funny thing is that nowhere does it appear to modify the Frame Rate Throttling parameter, a small mention of this would be nice, that's why I have done it. Things cannot be taken for granted. Anyway thanks for the correction and for you job.

I mean the Frame Rate Throttling adjustment, sorry but I still don't see it recommend it anywhere. Regarding the 55, I will not be the one to highlight it, but at least I see it strange if your system is not capable of reaching them.

I'll try without Turbo mode, Thanks. I haven't seen any post that talks about Frame rate Throtling, almost all of them talk about activating reprojection, that's why I published it. I'm glad there are more people using it for a long time. 55 frames as long as your system supports it, otherwise I don't think it will be smoother. In addition, the ideal is to always be in synchronism with the frequency of your glasses

Hello guys, I want to tell you a little about my research and the truth is that I have obtained magnificent results with DCS and HP Reverb G2. This may be applicable to other systems but I don't know. Now I have my simulator as if I had the reprojection activated but without having it and with an amazing smoothness and WITHOUT ARTIFACTS, the latter is the best. The first thing I followed the advice of my colleague ChichoWalker in this post to get the maximum number of frames possible. I also deactivated the MSAA that on top of eating many frames gives me the feeling that everything is blurrier, I prefer to raise the resolution to avoid saw teeth than to use MSAA, lower frames and lose sharpness (also DCS in its VR preset does it deactivated by default, it seems that this is not fine with VR) the latter is a matter of taste. Also activate Turbo Mode within the OpenXR Toolkit and it seems that I gained something else too, although not much (at the moment, although this option is experimental, it seems to work for me). Once I have gained all the possible frames that I can in my system, and here comes the trick, I activated the Frame rate throttling function within the toolkit and set it to exactly 45 FPS, this function basically makes DCS never exceed those frames And in highly loaded scenarios, if they have to lower the frames, they will obviously drop, but we won't have the problem of artifacts because the reprojection tries to keep the frames at 45 at any cost. Setting it to 45 is for the Reverbs whose nominal rate is 90 and you always have to use multiples of this amount (eg 1/2=45, 1/3=30, 1/4=22.5), I have set the which best suits my system but in poorer systems this rate can be lowered to achieve similar effects. In addition, the crazy frame jumps disappear. Now the truth is that I enjoy my flights until one day DCS put us a new graphic engine or improve the issue of reprojection. I hope my experience is useful to you. Thanks. Puede que esto sea aplicable a otros sistemas pero lo desconozco.

As you say and also you can update your dll every time you start opencomposite launcher.

Thank you very much friend, for my part it is clear. If you are the author of the OpenXR toolkit, I congratulate you for your marvelous application, I was a programmer of video games in machine language(assambler) for 8 bits (z80 Zilog) and I'm already a little rusty but I know how to appreciate the work that there is behind all this. My doubt mainly came from the issue that using one dll instead of another did not affect the operation of openXR in DCS, personally I have the general version installed with OpenComposite and I have not needed to replace this library that is delivered with the DCS patch. Thanks for all.

I wanted to tell you about a personal experience that surely happens to more than one. When I activate MR I can't see certain objects clearly, such as the edges of the cockpit or the tips of the wings (distortion effect such as water, blur), the FPS meter is not clearly visible either (when I use it, of course) or the MFD's (in the case of the F16 Viper). All this has forced me to have to deactivate MR even in spite of having gained FPS's thanks to the trick of my partner @chichowalker (in a post above). Thanks Chico. I noticed that if I leave MR off and on within the OpenXR toolkit in the Inputs tab, Shaking Reduction and set it to -30% (in my case) I get more smoothness when doing fast head turns inside the cockpit. I tried other smaller values like -20 or -10 but the one that fits the best, goes better in sync, with my system (CPU, GPU, etc) is -30%. For me it is a remedy for the small graphic jittering that occurs when you turn your head quickly and have MR disabled, as in my case. I hope this helps someone. All the best.

This is not entirely true, not only does it work with SteamVR but it also does great with OPenXR and can be used perfectly with OpenXR and OpenComposite. From here I urge you to try it if you haven't already. Therefore your answer, excuse me for telling you, but it is not entirely correct.

Sorry friend, but I don't know if I explained myself well, I mean that there are two exactly the same dlls but of different sizes: 1) openvr_api.dll= "Comes with openbeta 2.8 patch" and the other 2) openvr_api.dll="It is downloaded from the OpenComposite´s website" https://gitlab.com/znixian/OpenOVR What I wanted to say, I'm sorry I didn't explain myself well, is that the first one occupies a few bytes (585 Kbytes) and the second one occupies a little more (1815 Kbytes) I know exactly what Opencomposite and opervr_api.dll are. The only thing I want to know is why, being the same library, they occupy different Kbytes. (Is it more complete than the one that DCS brings? More up-to-date perhaps?). That´s my question.

I have observed that there are different dlls with the same name and I don't know which one will be more efficient for DCS and VR with OpenXr. If the latest openbeta 2.8 installed by default, I have observed that openvr_api.dll only weighs 585 Kbytes and the one I download from the official github website for openComposite weighs 1815 Kbytes (64-bit version). Of course, the latter is supposed to be installed in a configuration per game, according to the OpenComposite website explanations and not for a general configuration with OpenComposite Launcher, as I have it. My question is: why, being the same, do it´s differently? Thanks greetings.

As the title says, the radar switches/resets from GMT to GM when I switch from Air-Ground to Air-Air or NAV, then back to AG and magically the radar switches to GM without command. AG master mode does not keep the radar as I configured it.

Thanks my friend, I had the illusion that this was also possible as it happens with the skins of the airplanes and thus avoid inecely touching the main folder.

Can you somehow save the textures of a theater in the "Saved Games" folder? My intention is to have everything there and not put anything in the DCS OpenBeta root installation. I have already achieved it with some mods and skins of airplanes but I don't know how to do it with the theater. P.E. Insert this mod: Thanks.

It is not consistent when dealing with different launch systems.

I totally agree but I remind you that the HAD screen shows data from the POD HTS mounted on the side of the aircraft and not from the missile's predisposition, in fact the HAD will show a range according to the type of anti-radiation missile mounted since the on-board computer knows perfectly what type of missile has been equipped and not from the preset data in other modes. What's more, when you program the missile in WPN (POS) you are programming part of the missile's behavior based on avionics and inertial positioning data and part is managed by the missile itself, in fact, according to HANDBOOK, the mode in which it is completely independent of the avionics and managed exclusively by the missile is the HAS mode (it is the most primitive/primary way of management) the POS mode, excuse me for saying so, but many parameters do not reside in the missile and are stored so that others can represent them displays such as HAD. The HAD is based exclusively on the sensors mounted on the POD HTS (AN/ASQ-213). So it doesn't make sense for the range to go narrow when changing it in POS mode.

I do not care what it is called or should be called, what I know is that a configuration made in POS should not affect the HAD. They are two completely different forms of launch.

Sorry my friend I meant HAD mode instead of HAS. I corrected/edited my post. Thx I am familiar with the HAD mode of the AGM 88 and that is what I am referring to it when I talk about the range oval problem. RUK, PB and EOM is refered to "POS mode" in WPN page.

I have no idea if this is correct or not but since these are two different ways of launching the same missile, AGM88, this behavior has surprised me. I will explain: When I'm in HAD mode with the AGM88 normally a white oval appears indicating the missile's maximum firing range, so far everything is normal. But if I switch to WPN, POS trigger mode and select PB (Prebrief) and then switch to HAD, to my amazement, the range oval disappears!!! I think it shouldn't be like that because these are two completely different shooting modes and the options in one shouldn't affect the other. I hope you clarify this for me. PD: If I put any other mode like EOM or RUK in WPN, everything is back to normal in HAD mode. THX