Snuten

This was my problem.

Thanks @felixx75. Im tired and some what drunk. I forgot to check this. I will retry and go to the Training mission.

Not sure if I'm doing something wrong. But from carrier it is impossible but on ground I lift off about the range of the carrier. And I can't get the wing folding motor to stop whining? Not been trying long but it is a bit frustrating when just following standard procedure. (but might missing something)

Never mind. I don't know what happened but now it is back as it used to be?

I flew Viggen today after the update and when reaching a speed over 0.8-0.9 I could not pull her up from a dive and crashed into the ground. Not sure if this is accurate or not. But full pull back on the stick would not let her climb at all. Second try I extended the airbrakes and pulled and around 0.6 it started to climb and the it was back to "normal" and started to hear the "cracking" sound from the wings. Before I could snap the wings at any speed? But don't see any updates on this in the change logs.

Im surprised that so few mention this, but it do sound dull and weird. And has a very short audio loop. Im not an expert in how the F1 Mirage should sound, but with the afterburner running I get reminded of the sound when I was a kid and running downhill fast with my skateboard. The sound from the tiny wheels against the asfalt.

Yes please, someone make this! Would been awesome.

I agree, since the last update the trees at low level half my performance. And I also get a lot of random major stutter when using the new fog, it feels like the computer is loading in heavy assets as it does when spawning. But the trees is now always creating lots of stutter down low. AMD 78003DX, RTX 4090.

Thanks! And thanks for the explanation of the Turbo Mode, I think I get it now. But I did before, with Toolkit, have it at 90hz and 45fps (ASW on, Ctrl+numpad 3) and it worked as well and butter smooth. But if I was flying and I turned it off and then on again, it crashed DCS in like 5/10 times. So I guessed that was because of the ASW as the read warning text warns about in the menu. But then again I would think that DCS should not stutter if I choose to go without a third party injection. It do seem to work on some systems and some not. The trick for Intel seems to be to turn off HT, E-cores or trick with processor-lasso. But for my 7800X3D it does not help if I turn off HT or XMP (or what it is called). But I will stop whining about this, for a while and hope that Quadviews will be here for a longer period and hopefully developed more.

So then the NVMe does not solve it for everyone, so I guess that is even more uncertain where the problem is. And as you say, the solution just can't be a third party developers "hack" to make it work. And when thinking in a bigger picture, imagine new people coming to DCS and want to fly in VR and it is a stutter fest. That kills emersion completely and they are going to add them self to the growing list of people saying "VR could be cool, but not in another 10 years or so".. But it is the coolest thing you can do now, if it works as intended. I did just now tried out Quad Views. I did a lot of tweaking in the cfg file and I'm quite satisfied. Now running in 72hz/fps and no stutter thanks to the Turbo Mode. Turbo Mode, what ever it is, should be on by default in DCS.

It was the same on my Intel i9 as well. And I have not used that PCIe slot that is shared with the one for the GPU Hi, thanks. I will try this!

Hi, I have been a bit off from DCS lately but have installed the latest updates and read that the ST mode is now removed with only MT version. This scares me a bit, not that Im against MT since that is the future. Im writing this since I have read about many people with this exact problem with VR and MT version(Facebook groups, Reddit etc) that might not reach to DCS forums. When you first released the MT version I was really happy, and I could also use DLSS and increase my resolutions and quality even more to fully utilize my RTX4090. But back then I had my old but trusty i9 900k CPU and RTX4090 and could not get the MT version to run smooth. I saw that the fps was higher, but the stuttering was horrible. Something with frame timing is not syncing correct or interfering with hardware? Some reported this but the culprit was the E-cores, which I did not have. So I ordered new components like new Motherboard, RAM, AMD 7800X3D CPU, Nvme m.2 discs, new cooling and 1200W PSU. While waiting for these parts I read that someone else with this problem with the same CPU(i 9 900K) and GPU I had, and that he found a solution that worked. He re-installed the whole DCS into a SATA SSD disc instead of his Nvme m.2 disc. Then he could run DCS MT without stutter. I thought that was really strange, but I gave that a try as well since I was anyway waiting for my new components to arrive. So I just copied(moved) my complete DCS Openbeta folder from my Nvme disc to one of my SATA SSD discs. Started it, and it worked. No more stuttering. But loading times was horrible though. I then built my new system with the 7800X3D and all. Then installed everything and DCS installed into a brand new Samsung Nvme disc. And the stuttering was back with the MT version, exactly the same as on my old system. But the ST version was smooth. I did investigate and tried a lot of things except for moving the game to a SATA SSD. But then one day I tried to turn on Turbo Mode in OpenXR Toolkit. That completely removed the stuttering and the game runs smooth and stable(still doing so with this turned on) I have tried to completely uninstall OpenXR Toolkit to see if that it self is the problem. But no, the stutter was back. So re-installed OpenXR Toolkit again, tweaked it to my likings and turned on Turbo Mode again, stutter is gone. Now my biggest concern is that Mbuccia (sorry for misspelling) that was developing all these tools for us have stoped doing so, understandable since it is not his job to fix companies flaws with VR(not just DCS), but now when we only have the MT version left, and then if or when OpenXR Toolkit no longer working, I will just have a lot of $$$$ sitting in useless modules and maps locked into my DCS account. And therefore I will not buy any more modules or maps. Which is sad. I know that I might be hard to track this stutter bug down. But if moving DCS to a slower disc or running with Turbo Mode on fixes it, so perhaps someone smart knows where to look? Im currently using Quest 3 with link cable. Had the same problem with my HP Reverb 2 as well. I will try to get out my DCS log and Dxdiag log and send it later today. Thanks

Sorry for double posting an already recognized bug.

When I shoot my Hydra HEAT missiles they are going 45 or more degrees to the left? How is this possible? Is this they downside of DCS only being in Beta mode?

When I shoot my Hydra HEAT missiles they are going 45 or more degrees to the left?

I wish I could choose to have High resolution on my own module(cockpit and exterior) and then use medium or low on buildings and ground units. Since the CH-47 release it has become a real issue. When flying with the CH-47 near the super carrier it starts to reach peak Vram use, and I have a GTX4090 with 24gb Vram. But even when it reaches 19.9 gb Vram use regarding OpenXR monitor, it starts to lag as H*ell. And won't stop until you restart the sim. This I crucial for VR. At medium resolution you can't read the instruments on most modules. And the F-18 side "wings" outside the cockpit looks like there is 2 pixels stretched on the whole surface since it is already very low res at High texutre setting. Please make this possible since the texture density is so uneven between new vs old modules.

Not sure if this is known or due to EA. But I noticed that when the Missile Warning speaks out where a missile is, it says like: Misslie forward left or Missile forward right. But says "right" to a missile coming from left and vise versa. I have my sandbox mission on the Syria map where I have the Super Carrier near the land and when flying towards it from land I also have a couple of BMP's in the harbor that is firing missiles to the Super Carrier and the Super Carrier is firing missiles the opposite direction, towards the BMP missiles. But the CH-47 warning alert voice has left and right mixed up so when the BMP fires a missile, from my left, it says Missile Forward Right. And when the Carrier firing a missile from my right it says Missile Forward Left. Have no track rec for it. But could be an easy check. I know it is Early Access but thought I could help a little with this find.

I only tested with GBU10 and 12.

Yes, I also suspect this now. Perhaps this started after the "feature" to change codes in the air was removed, whenever that was.

I have loaded up the F18 with 4 GBU 12(or 10s) and finds my target area and lock on with the laser and drop the bombs one by one(and turning on the laser switch between the drops) and successfully hits the targets. But when the plane re-arms in the air with the new bombs selected, they do not explode, just a tiny "puff" where they hit. I have tried to re-set the Mode and Fuze again and the Code is 1688 on both laser and bombs. (also tried to re-enter the code again in Stores, but have read that would not work anyway) And in ME I have ticked both check boxes, left and right next to Unlimited Ammo. Only things that works is to jettison the bombs, land and re-arm through the coms menu. But that kind of removes the idea of unlimited ammo when practicing, even if it is still kinda unlimited Is this a bug, or known not to work or am I missing something? I have tried to google it and also searched in here. The maps I have tried this on is Afghan and Kola if that could be a the problem? Also running with the latest patch(hence Afghan map) Sorry for not using the correct terms like TDC and TGP and so on, Im still learning so a bit unsure about their names.

Same thing happened with the A-10 II, also from a "Create Fast Mission". But when trying to edit the mission it will not move from the helipad unless I choose option Start from ground and place it to the runway.

Hi! The strange thing is that I had my install exactly on a Samsung 970 Evo plus 1TB but had this problem. Then I moved the install to a SATA SSD. And then I moved it back to the 970 Evo plus and was working on that device since. Perhaps Microsoft issue/drivers that was messed up?

It was on Auto by default, and I changed it to PCIe4 before I moved to the Sata, with no luck. So I put it back to Auto, and now moved DCS back to it(as you know). So it should be on Auto now. But that m.2 slot is up to PCIe5 but the drive is PCIe4.

Darn it It is now even a weirder issue. I thought I was maybe something with registry(or some file in the DCS folder) that perhaps got "reseted" by executing it from different drives that fixed it, but obviously not. Im happy mine works with the nvm2 drive now. Loading times went from like 55 sec with Sata to 15 sec with nvm2.

I tried it back and forth yesterday, between only DCS PD or only OpexXR override, and I ended up with the same I already had. But by only use DCS PD I get worse performance and also much fuzzier image. I guess that's because of DLSS. But with a mix of super sample in OpenXR, before DLSS kicks in(I think), it gets much sharper and better. But one thing I wonder is if WMR (G2) renders the screen different, like concentrating more pixels in the centre or something. Because when I was using 1.5 supersampling in the WMR tool, I saw objects and trees much further away with the same View Distance radius(Medium). And the more I increased the WMR's supersampling to like 1.8 I saw even further and more trees/buildings. Like DCS was "thinking": Oooh, so big screen, now we can populate it with more stuff. But when increasing only with the Override Resolution inside OpenXR Toolkit, I see no difference regarding this, nor by increasing it via Oculus app. But I guess I would not be able to run it in 72fps with more objects in the viewport anyway. Im really pushing it now with a frame time around 10-13.2ms(Marianas excluded) I also using MT btw.