Talonx1

Thanks boss, like I said wasnt sure it had always been that way or not. No complaints, just wanted to be sure. o7

I've been flying the tomcat mostly for the last couple months and havent flown the hornet in ages. So i hop in and do some refueling and landing practice and notice that I get no audio indication of deploying the refueling probe or from lowering the gear. I've become really used to it in the cat and not sure if this is a bug I'm having in the hornet or if its always been this way.

What about the way it seems to work opposite to whats expected? As I move my head forward my head in the mirror gets smaller and vice versa. Its a really strange effect.

Dont know if it was due to over g but after playing around a bit around the carrier I noticed my compass was off by 10 deg. Only fix I could come up w was setting compass to DG mode and turning the knob to match my heading up to the carriers brc. (Also used info bar to confirm it was set properly as it will show you actual that you can compare to your instruments)

Still room? Flew with one of the virtual squads here for a bit but ended up departing for "dad" reasons. Have been looking around a bit for a more casual group since.

Was always there for me as alt ent. Had trouble assigning it to button press though.

35 is way too high. 15 is plenty for even the finest of small inputs during a2a refueling and if youre flying the plane properly on landing youre going to be using very little flight stick input as all your pitch control is made via the throttle once gear and flaps are down. At a setting of 35 youre gonna get almost no input then input is suddenly going to increase very rapidly resulting in constant over correcting. Ppl often dont realize that when you decrease sensitivity near the center of stick movement you are creating a sharp curve increasing sensitivity at the outer edges of movement. The less curves you use the more steady and predictable your movements are going to be. My guess is that most of your problem though isnt curves but that youre not trimming to on speed aoa and are instead trying to man handle the plane down with the stick. (Just saw DavidOC’s post earlier, basically just mirrored what he said)

This has always been the case. Assumed it was intentional as the heading indicator is replaced by the alignment offset indicators.

We’ve seen this since day one w the hornet. Any ship that takes off from or traps on the carrier bounces if you try to land on an airfield. Its so consistant it was assumed to be a known issue. (The player in the bouncing plane doesnt notice anything, just others that observe it)

Make sure anistrophic filtering hasnt been turned down. No reason it shouldnt be set to 16x its not a major performance hit. I see no difference now in textures opposed to previous versions.

There are some undocumented shortcut keys in oculus home. Perhaps the latest update added one thats causing the issue.

:book: (Mouse not working on lower parts of screen) Issue already fixed internally and due out with next beta patch. Till then try setting windows desktop resolution to 1080p before you load dcs. Works for most ppl.

Did you have the vr mod installed prior to problems? After hotfix reinstalling newest version of vr mod gave me about 10-15 fps over hotfix alone.

Dont care for the test channel but the desktop abilities of beta are pretty essential imo. The ability to interact with desktops without taking off the headset and pin windows and position them so that I can see them while in dcs or other games. Turning ot off makes zero difference in my experience.

Didnt this used to only work in external views? I dont recall it doing anything in cockpit.

If anything latest hotfix made it worse. Used to get 90fps on carrier deck in optimal conditions. Now I’m lucky to 45 and spend most time around 30. A single hornet on deck with me last night pushed me into the 20’s just taxiing by me. Fps combined w black box around peripheral vision has turned dcs into complete no-go for me till it geys sorted. Not complaining really, its beta. Beta is beta for a reason. Just hope it gets sorted soon.

Windows desktop. The setting within dcs makes no difference

Have tried with scale ui on and off and with pd between 1.0 and 1.6. Setting windows desktop resolution to 1080p is the only thing thats worked.

Mine works well enough in most situations but the black box borders are pretty annoying and I’ve had to turn down a lot of options to make up for worse frame rates.

I assure you it isnt 2hz. :) 2khz maybe. Just sayin.

Did not help at all. In fact making it run with steam makes it worse because the oculus still needs oculus home running to work so it wastes even more resources and frame rates get worse.

Finding that I have to be set to pixel density of 1.6 or lower or the black border shows up again and things get sluggish. Used to use 1.7. Maybe its my imagination but text seems much more blurry now aswell.

Theres an additional issue with selecting things in vr today after the hotfix. Buttons on the bottom of windows arent selectable unless your desktop is set to 1080p or lower. Assumed this is what you were referring to but perhaps not.

Other than the bottom of menus being inaccessible now it seems mostly fixed. I still have a slight black border around the edges that I can see in the edges of my vision but not nearly as bad as before.

Ditto, was just logging onto the forum to report the same thing. I wasnt aware it could be helped by setting desktop resolution down to 1080 though. For every step forward, a step back.