IzeHouze

Using a Rift-S. It APPEARS to be launching in Steam VR mode by default. No way to do Oculus VR. Based on visible loading screens and hourglass symbol in headset. As with most Oculus users Steam VR performance is lower than Oculus VR mode. Overall it seems that the game performance improvements have offset the poor Steam VR performance for the most part, so it is a Net-0 change. I would imagine that running MT with Oculus Mode should be even better.

I believe that I have been seeing problems too. But since my CP/G and I are kind of new, wasn't sure if it was operator error or not. I need to do some additional research as well.

From my perception of the process, boresight doesn't seem to be required for Hot Start. (already completed) Does need it for Cold Start. It is inaccurate without it from Cold Start. I have Cold Started, skipped B/S, had George hold a hover for me and I used the gun from GHS mode, not TADS. I then did the B/S process and the gun improved greatly.

That seems to correlate pretty well from my observations also. I was thinking that it was a lower frame rate than the non PNVS area, but applying that star/stop logic would totally look like it was slower frames. Most likely due to simulating the limited Slew Rate of the PNVS. Probably a real bear to code.

Quick note. Possible unreliable or inconsistent bug... ...Saved Games\DCS\Scripts\Twitch2DCS.lua"]:236: loop in gettable I see this error upon starting DCS and it appears in the log. I exit and restart DCS and I may not get the error the next time. So completely random and I don't know of any way to create it on demand. Just a heads up, or perhaps you know why this might appear?

A little late to the show, but you say that the wiring is wider than the RJ45 connector? Wire specifications? Should be written on the wire insulation. CAT6 CAT6e UTP STP Flat Round

I believe that I had heard the New FLIR 'paint/skin' has not yet been added to all vehicle types yet? Hopefully corrected soon?

Only because I did it once... After the last patch, you have to manually power up the RDR ALT in the FLT - SET page. I flew out, got to altitude, then came back, only then to notice that I never turned the RDR ALT on at all. And when the RDR ALT isn't working, i.e. not turned on or above 1500 Auto-Ranging quits working. I don't know if you were using Auto-Range at all to confirm. That would be a new bug, if true, I believe. And of course, ED would like a track file recording of it happening, to attach to this to verify.

For me, it is not new. No changes have occurred in the patch that changed my view. This has been persistent since release. I was saying that someone else had perhaps called it double images in a comment they had made. For 'different places on the left and right eye' Yes, that is how our vision creates or perceives depth, distance of an object from our nose forward. The greater the difference from left to right, the further away an object appears. In the case of double vision, your eyes are not correctly capturing the 'depth' of the image, so they are not merged into a single image, by your eyes. With the George Menu, in BOTH Pilot AND CPG, the lower menu is at a depth (z-distance) further/deeper than the instruments or TEDAC. Your eyes get confused and lock at a distance of the instruments or the TEDAC, causing double vision on the George menu, until you push your focus PAST those front images. when they will become a single image again. You can test this by looking at the TEDAC, when you see a double image of the George menu, look out the left or right window into the distance. The double vision will go away and you will see a single menu again. Then while you have the menu in focus as one image, bring your gaze back into the cockpit. It should remain a single image, unless you get distracted by the interior and it will go double again. You are not making 'a bug' go away, you are simply correcting your perception of the images you see. Vision is a complicated thing.

Big shot in the dark, but I did this yesterday. When you shut down the engines to get the repairs, did you use the Rotor Brake switch? I did. And I found that the PCLs would not move from idle after the repair, UNTIL I turned OFF the Rotor Brake switch. Not sure if that should be the case, but double check the Rotor Brake next time. (actually just thinking about this, in the Gazelle, the Rotor brake physically blocks the PCL preventing you from moving it up to fly)

There is also a quirk where the Master Volume appears to already be turned up, but in fact it isn't. So just dial the Master Volume Down/Up to verify and as mentioned above ensure you have turned on. With the squelch switches in the down position you can verify if sound is coming out.

Including Z (depth), not just X,Y ? Position is fine for me, it's the Z plane that makes it difficult.

Same thing if you run Oculus brands, but use the 'Oculus Tray Tool' instead of Steam VR, and run DCS in Oculus VR Mode. Set in the Game to 1.0 and set the Super Sampling in the Oculus Tray Tool from 1.2 - 1.5 depending on your system. (recommend that you put it into a 'Profile' just for DCS) For me this runs better than Steam VR option. Note: You need to keep the tool running. Either Start with Windows or start it before launching DCS. Also I don't believe that you can make on the fly changes, but must exit DCS, make the adjustment in the tool, then restart DCS.

Can confirm Flare count incorrect. 90-75-60-59-58-57

This may have come up before or may have been reported as "Menu Doubled" but I believe this is what may be happening. I think that the George Menu is currently at a focal point/distance further away than the instruments panel in the aircraft. It isn't quite so bad when looking at the upper menu as most of the time, this is above the instruments line of sight, often out into the airspace in front of the aircraft, and you are able to focus on the menu at that distance. The issue becomes prominent, when looking at the lower George Menu, such as target selection. This appears in the same line of sight as the instruments console. Your eyes tend to focus onto the instruments depth plane, instead of the further distanced George plane. To focus correctly, you are having to force yourself to look through the instruments to a further plane, where the George menu lives. The current work around is often to tilt you head upward so that the lower George menu projects outside the cockpit. I believe this could be resolved by projecting the lower George menu onto a plane that is AT or slightly nearer the instrument plane, from a normal seated position. Images and track files would be useless in this issue when being viewed by a 2D or single eye projection. You can easily verify this is in VR, just by having George try to target something and take note of the plane depth at which the lower menu currently appears. It will at first appear in double vision, until you can force yourself to focus at a point through the instruments panel further away.