nikoel

So what's the verdict Brochachi? I am actually about to press play on the darn thing myself. But the only thing that I don't like about it is that I learned the ways of @edmuss and have the force powers to tolerate the G2 @ 60hz. So I have been flying with pure smoothness and no artefacts in DCS ever since the new MT Beta Dropped. I see that we only have 72(4?) hz and 120 so I will be back to tearing. I think I should be able to subside this by locking 60FPS with adrenaline chill

Yay! My setup is identical to yours let me know how you get on

Hey Slug, I am thinking of biting the bullet as well, but no one with AMD graphics card that I know of has opted for the QP, what are you running nowadays hardware-wise? A supercomputer or something a little more humble?

Here is a quick demo I shot today (it's a different track) I tried to get both high and low aspect shots. Both with reticle on target and shots on target (with reticle in front). We are not talking a lot here, but just enough to miss (*Most of the shots missed because of my <profanity>ty aim and flying, but this cant be helped) It will take a little while to get to 4K quality. But I hope it will assist All the best

Hey Team When fighting smaller bandits (Mig 21) I noticed that I need to place the crosshair in front of the bandit's path for rounds to hit. Placing the pipper over the bandit directly always makes the rounds fall behind them This is not as much of an issue with a Flanker as the aircraft is much larger, but the same issue can be seen to lesser extent, ie aiming for the pilots head, hitting the engines There have been some issues with one of ED's planes too (F/A-18), but others are unaffected for me Playing in VR Only. Open Beta. MT, OpenXR Track file attached. I tried demonstrating this by firing both ways several times. (Default Gulf Map Lion and the Sun) F14.trk

Holy thread resurrection Batman! It’s not pinned because we got official DCS implementation of OpenXR It’s two weeks later; the clock has struck midnight and the future is now! With one argument inside the DCS shortcut we can now have home grown multithreading and OpenXR; no open composite needed This thread and open composite were glorious! It was so popular at one point we crashed opencomposite update/download servers. Worth the effort and may have even helped get to us to where we are today but it’s time to say goodbye (for dcs anyway, I still have it installed for Il2)

Thanks for the additional advice on how to overcome the issue. I am just sticking to hand flying for now - I much prefer the realistic feel of the cyclic than having the clutches tightened. Hopefully the SAS keeps improving In your second paragraph you may have incorrect understanding of how the real trim function works. It may have been just the way you worded it, but in case you’d like to know as a thanks for looking at my track here is a quick explanation. Now take it with a grain of salt as my real life experience is not in the Apache but other civilian built helicopters, however they all work pretty much the same The real aircraft often has a “centring point” created artificially either via mechanical servos or motors etc… which work similar to springs to apply force against your inputs back to that specific point When force trim is pressed those forces are cancelled. The pilot then can move the cyclic in whichever direction he desires without forces acting against his inputs. Upon releasing the force trim button, the forces re-activate. But that centre point has now moved to where the cyclic is now. The cyclic does not move back to center. It is then held in place by those electronic motors. The pilot can still move the cyclic by overpowering those forces. The motors will gently work against the pilot until force trim is either triggered again or the cyclic is returned back to the same point.

So Yeah, you've basically confirmed my suspicions in my original post. The ~3-5% Deadzone (or fixing the SAS) when the trim is engaged would do wonders I think In my case, not moving the stick is not an ideal fix because of these three factors 1) I have no springs but still have it set as close to flying the real helicopters (aka with least amount of stiction possible) thus reaching up to the trim button, pressing it forward and then pressing it left makes the stick move slightly sometimes. - I fixed this with the collective bindings as per a post above 2) I have to trust the system would work and half the time it still won't. The only way to tell is to let the aircraft start drifting and then take over when it doesn't. It's just frustrating. No thanks, I rather just hand fly 3) To lesser degree I have to have my hand on the stick for when the system doesn't work so I can fix the aircraft or risk having to restart again because it drifted into a nearby tree. This means that its more likely I make those minute inputs

Does this mean that you now get the same broken behavior of the trim functions as I do?

Hey Folks not sure if this belongs here or the requested feature page I am flying with a WinWing SuperLibra with extension and without springs. I have Tightened up the dampers so that the cyclic doesn't move when released but are still fairly non-sticky for small inputs. I still have pedals that have springs in them (the official DCS VKB ones) I have Cyclic Trimmer Mode set as Joystick w/o Springs I have Pedal Trimmer Mode set as Central Position Trimmer FFB is off in the Misc Options Menu In a hover as an example; I am finding that the trim in the Apache is very hit and miss. Success Rate of around 2/5 times. The Apache goes into the hold modes perfectly but gives up on the hover by starting to rapidly drift without trying to correct I believe this is due to the fact that when I reach up to the trim-hat and press the trim forwards (for the pedals) and then trim to left to hold attitude, I end up moving the cyclic ever so slightly which might be messing up SAS in it's current flaky state I believe as an stop gap solution you can give me say a 3% dead-zone when I activate the trim switch that should give enough wiggle room so that the ever so slight movements don't upset the machine In the meantime I have given up on the trimming altogether, and have been just hand flying her, but it's a bit annoying to do this whilst entering coordinates with your head down. If you have any other advice please let me know trim is so flaky it should have a tinder account.trk

Hey Team Amazing work with the multi-threading update I suspect that maybe something may have gone slightly wrong with the A2A computations with the Viper. It has been many weeks since I've played but I sat down tonight and found that in some instances with the reticle directly over the bandit none of the rounds hit It only happens sometimes, maybe 5% of dogfights. I think this happens mostly when I lock the target via HMCS off bore I have attached a track file I am using the latest Beta, with Multi Threading I fly exclusively in VR shooting blanks.trk

Not bugged, you're getting exactly the performance that you're supposed to. Your CPU is giving you a theoretical 250ish FPS (4ms), whilst your graphics card is giving you a practical 58FPS (17ms) Therefore you're limited by your graphics card and you get your 58FPS It's sometimes just easiest to use this calculator to give the FPS figures -https://fpstoms.com/

Okay so “idiot checks” - not to call anyone an idiot, I just call them that is the Capitalisation there as in XR etc… is capitalised exactly like you see above are you launching DCS via DCS Updater? It won’t work via that - only DCS.exe Do you have two dashes — instead of one (better of copy and paste anyway) is open composite highjacking your pipeline because you have been using the drag and drop method of installing it if you have OpenComposite exe file (as per my guide) go into the per app settings and right click on all DCS apps (there might be two for some) and check “use application default runtime” (paraphrasing of the top of my head) Plz provide screenshot of your properties of dcs shortcut finally are you using the Beta version of the game? Stable doesn’t support OpenXR natively

Newy I have to agree with the others on this. It makes high AOA, 1 circle fights frustrating at best, game breaking at worst It makes the F/A-18 an offbrand Viper, as it takes away from it's primary advantage I will upload an other video/track that showcases this. Please note where the bandit is, and where the target placement is. I tried making this obvious by pointing my head when it happens. Additional Screenshots of this are attached. Track file is also attached. HACQ Take Two.trk

Nope

Mbucchia for President 2024

A bit of confusion. I will try to explain If you are using the OpenComposite method of launching (aka the one outlined on the first page of this thread. AKA without --force_enable_VR --force_OpenXR) Then you can still use MR and Turbo If you are using --force_enable_VR --force_OpenXR (aka native DCS OpenXR implementation) Then you can not use MR or Turbo

Turbo Mode and Reprojection does not currently work with native implementation of OpenXR in DCS. You can not reset settings outside of safe-mode. This is what safe-mode is for To fix your issue see here: https://mbucchia.github.io/OpenXR-Toolkit/troubleshooting.html#start-in-safe-mode Then here: https://mbucchia.github.io/OpenXR-Toolkit/troubleshooting.html#reset-all-the-settings

Before anyone gets confused by this. Oldcrusty means 'OpenXR' and OpenXR Toolkit. There is no such thing as OVR Tools

Try this mate

Before this thread finally comes to rest wanted to see if anyone else had a similar result to me after upgrading to the native implementation I did not want to uninstall OpenComp because I was using it with "the other sims" [that everyone here knows about]. So, I just right clicked dcs inside OpenComposite and told DCS to use its own default runtime Looks like ED agreed with me, and thought they'd rather give you CTD than waterboard you with reprojection. Nice feature. The performance is… mixed. Slightly worse GPU frametimes. Much better CPU frametimes. Slightly worse picture at the same settings. A boatload of shimmer. Smoother even with my I-will-die-on-this-hill 55FPS locked state. How?! No double vision or ghosting at all in dog fights (wut?!) My conclusion is: つ ◕_◕༽つ whiplash with a side of meh!

Boys, has DCS integrated OpenComposite, or is it running OpenXR Natively? The title of this thread suggests it's the former, but I'm highly suspicious of this claim as this would be importing code from an Open Source project into a commercial sim

Did we get a fix, for the fix that didn't fix this bug in this latest fix (26/1/2023)?

Wut?! MSFS does not utilise 32 threads. Hell it doesn't utilise 5800X3D to it's full potential either In a properly configured and designed system 5950 will never get close to the performance of the X3D in simulation type games. Hell even 7950X doesn't get close