ricktoberfest

What about oculus runtime? Is it still not default for oculus headsets? Currently running a registry hack to disable openxr but I’d like to not have to do that.

I’d hoped when the community team took over that there’d be a resurgence of interest, but I guess that was short lived. As far as discord- no thanks. Too much social media in my life already.

I’ve been regularly checking for updates on GitHub but there hasn’t seemed to be any activity now for months. The last patch was end of December and even the commits seem to have dried up. I was really hoping at least for fixing the modules that don’t seem to work with VAICOM. Apache and Mi8 are 2 that really bother me but also WW2 aircraft. is anyone still working on this or am I holding out hope for nothing?

I speak bad texting: I think he’s saying “But when will the super carrier be complete” either that or he’s asking where the bathroom is.

Or do what the Tomcat does and start the cockpit shaking like an SOB above 8-9G

I just found that if you disable openxr in the registry then you gain (or at least I did) 10-15 fps and it’s way more stable on oculus runtime. There’sa thread here about it. Here’s the thread.

I’ve also had this happen several times with a Rift S using the openxr runtime. The openxr just seems so much less stable for me than the oculus runtime, including many uncommanded head re-centers.

On another note: now that we are being “forced” to use openxr, has anyone compared in ST mode if there’s an improvement or change compared to oculus runtime? I’ve been on exclusively MT since the patch and did note an increase in FPS, but I’m now wondering how much of that might be a different runtime and how much is the MT. Just did a quick test myself now that I'm home again, seems like very little difference in FPS either way. The OpenXR has more settings for scaling, the Oculus runtime is less "buggy" and doesn't seem to require the scaling even at the same 1.3 Pixel Density. These were of course just quick tests using the F16 instant action dogfight and an underwhelming GPU

I have found that having the pixel density in DCS at 1.3, leaving the SS in openxr at default, and applying FSR scaling of 125% seems to give a good balance of frame rate and resolution, at least compared to previous oculus default settings of DCS at 1.4. I’ve stopped using Tray tool for now as it seemed to be conflicting a bit and will just turn off ASW with the Ctrl-1 hotkey

I very much like the A10, was my 2nd purchase after the Blackshark2. I still go back to it every couple months even after “flying” it for over a decade.

I still don’t understand what’s so amazing about a new radio for the a10 and why it’s taken so long. Even watching the video by Wags just has me thinking “so what”

Is this VR or pancake mode? I run ryzen 5600x, 32Gb 3600 ram, and a Vega64 and get 30-40 fps in VR, which translates to 90-120 in pancake. This is single player so not the cpu intensive load that multiplayer puts on it but I usually still get over 35-45 fps in various servers. 35-40 FPS is very playable in VR. It only gets choppy below 25

It’s on the throttle - part of the hotas

Just recently tried msfs. I was so surprised by the ability to turn on and off VR so quickly and easily. Why don’t more games do that? Makes it so easy to set up a flight on pancake and then pop into VR for the actual flight.

I hate discord so won't be doing that, thanks for the info though

Any news on the Apache issues?

You can through VAICOM so there must be some way of doing it. (Except of course the Apache doesn’t really work in VAICOM) but it works for other aircraft.

Since voice attack is basically using keyboard macros, I just adjust my keyboard controls to be similar between modules. For example, gear is “G” in every module and so when I say “gear” it’s always actuating the gear. Same can be done for “lock target” or whatever commands you want to use. Another example is engine start. I have all my aircraft engine start/fuel cutoff mapped to the same keyboard command.

Make sure to wait a couple seconds after rpm hit 20%. Maybe you’re moving the throttle to idle a second too soon.

Bailey's doesnt require a plugin. Its entirely VoiceAttack

You should be careful about what you hear on the internet. Some “player saying” does not make it true.

It’s not their static nature that bothers me, rather the line of sight issues with the AI. reminds me of when trees were invisible to them.

I wasn’t aiming for helicopters specifically, just an all around setup. It works well with the helicopters because now I need to use more pressure on the pedals and that actually makes it better than using a higher curve.

I bought the t1600 Hoyas package a few years back but have always had issues with the rudders. Even after I loosened all the screws and replaced the springs with elastics I couldn’t be precise with the pedals as sticktion was always there. Recently, one of the springs on the toe brakes broke and so I use a rubber band to replace that spring. While I was doing this, I decided to replace the rubber band in the rudder axis at the same time, but only had the old thick rubber bands that are hard to use in a tight spot. Let me tell you how much difference it made though! Instead of trying to go with the lightest movement, now I have a much “heavier” axis that is actually really easy to be precise with. Since you have to use more force to press the rudder, sticktion isn’t an issue anymore! It has made flying with rudders much easier and the Apache is controllable now. I highly recommend to anyone struggling as I was to use a thick, tight rubber band instead of trying to go for a lighter feel. (they’re still cheap plastic pedals that aren’t good build quality but I don’t feel like they need to be immediately replaced anymore)

This is a great idea! You can also use axis curves to fine tune individual aircraft AB positioning.