peachmonkey

check this topic out, it has couple of utils to clear up the calibration in the devices, maybe it could be useful for MFG's as well:

- the DCS graphics settings aren't grouped in to a Medium or High pre-set. Each graphic setting has its own Low/Med/High/Ultra setting. The devs did introduce the "VR settings" button that kind of presets all of the settings for the best VR experience, however in reality the chance of having a fluid VR gameplay using those settings is still highly tied to the hardware the Devs had when they were testing it. The point is it still means means that you will most likely spend some time balancing one graphical feature setting over the other. There are several posts where people uploaded screenshots of their settings along with the CPU/RAM/GPU specs, i.e. you either need to find those posts or just accept the fact that you'll need to figure it out on your own. There are several GPU heavy hitters like the render resolution textures, shadows, particle count in the objects... - SP vs MP performance - this is a tricky one. In SP all of the computational tasks are done on a single cpu core, i.e. the flight model, damage model, other flying units, ground objects, etc. All of that takes away the resources from the CPU, so more dynamic units you have the more framerate impact you'll get. In MP the majority of those units gets calculated on the server hosting the mission, i.e. your CPU is tasked with local stuff only. However, when you join the MP with multiple players the added compute requirement to render those other players essentially evens out the gains you get by joining the MP, and in some instances you actually can get too much compute tasks requests during a MP mission and your frame rate will bog down in to a slideshow. Some folks did run a SP mission on their own MP server (hosted on the same machine) in order to split the compute load between the cores, i.e. the 'server' was running the mission on core#1 of the CPU and your 'client' was running on core #2. The point is the smoothness of the gameplay depends on a lot of factors, be it SP or MP, and so there's no way to deterministically answer this question. - I play in VR, however I have a pretty beefy system - 32GB RAM, Ryzen 5900x, and a 3090 GPU (oc'ed a little). Everything I said above applies to my cpu/gpu combo as well, so I think you can already see that DCS graphics is a pro&con game. 3060ti vs 3070 will be on a low end of the performance. Can you get the acceptable smoothness in VR with this hardware? Sure, but be ready to lower the graphical settings in-game and the render resolution in SteamVR. Will you like it? Only you will be able to answer this question. - Also, don't forget the VR headset itself. The previous gen HMD's maxed out at 1600x1400 resolution physically (screens) and you could add about 20-30% in oversampling (i.e. final image is rendered at 1600x1400+20%=~1920x1680) to get a smoother image (less jaggies), however that again depends on the GPU you have. The latest HMD's have a much higher physical resolution (G2=2160 x 2160, VivePro2=2448x2448). To give you an idea with my 3090 pulls VivePro2 at 2448x2448 (no oversampling) with MSAAx2 and the graphics settings I use are hovering in the solid "medium" experience realm. Like @Eugel mentioned above you need to manage your VR expectations. My advice would be: "no expectations = no disappointments" Just get a rig that will give you a decent monitor experience and then you can slowly get in to VR once you learn and understand its options. The game itself has a pretty steep learning curve compared to WT.

yup, on a cold Channel map I had to run the time acceleration at Maximum (x16 ?) for about 30 or 40 seconds to get it in to the safe pressure zone. A working oil dilution would be a nice feature for sure.

gotcha.. for what it's worth I had problems with VivePro1 cables and the behavior of the HMD was that it simply turned itself off and on during the gameplay. It wasn't introducing any stuttering or jitter. But maybe it was simply a break in one of the strands delivering power...

Have you tried to do the Clean driver install through NVIDIA before DDU ? I never used this DDU thingie and the Clean Install option usually got things done just fine...

@dburne were you running it with Smoothing enabled? At 120hz? And you liked it? I tried the VP2 with ms after their recent update, and at 90hz it was still a pretty dirty experience. I'll give it a try at 120hz, maybe it's a bit better..

I've been flying the other sim in VR for 4 years, now I've switched to DCS and even though the object scale on the map is much smaller/different than in the other sim the same points still apply: - find the landmark on the ground - try to find it on the map On the Channel or Normandy maps the most obvious ones are the tree/forest grows. Obviously you need be at at 2+km altitude at least so you can see the full shape of the forest. For example: - look out of the cockpit and find the largest forest growth - note its geometrical shape, the weirder the shape the easier it is to find it on the map - try to gauge your location in regards to the forest (north/south of it, etc) - then open the map try to find the forest shape that matches what you observe from the cockpit I started on SOW server and it was extremely difficult at first, but after 4-5 missions it got to be pretty easy. I do get lost sometimes, but usually after 2-3 minutes I orient myself on the map... edit: It's actually quite fun getting lost now..

Yeah, constant weaving is key. The only thing you've got to work with is the flight time of the shell, and considering the high velocity of those 88s and their impressive splash radius you really need to work it. Makes it hard to line up for a strafing run. I had very little success with strafing runs against the AF's because of Flack. I stopped it altogether. It's frustrating because it's such an immersion killer. Bombing is the only method left, unfortunately.

here's a brief explanation to that registry setting: SvcHostSplitThresholdInKB It also has the table of values per the RAM installed. If your system is already debloated and all unnecessary services have been stopped this won't help in your pursuit of higher frames. https://www.tenforums.com/tutorials/94628-change-split-threshold-svchost-exe-windows-10-a.html

I found only 1 method that's proven to work against the flack. Constant weaving. Left right left right left right... Obviously it's only useful when diving at high speeds and when for running away. Anything in between you are 100% guaranteed to get shot.

thank you for the explanation! How much RAM do you have in your system? I'm running with 32GB RAM...

make sure you keeping the the stick pulled back while taxiing in in the FW190. The rear wheel is free spinning if the stick is in neutral position, and it will lock once you pull the stick back (and keep it there). Steering is with wheel brakes.

ah, yes, in DCS the A8 engine must be at least 25C degrees warm to fly , otherwise it'll die pretty quick.

- There's a fuel tank selection lever above the left knee. Make sure it's moved to its most top position (front tank) - make sure the fuel tank pump CB switches are pushed in (the middle/open section of buttons on the right)

oblomok/обломок in Russian means "a broken-off piece".. I've seen this behavior on A20, Mosquito, 109, P51...

thank you for the correction, I appreciate it!

hi there, ChainsawAkimbo, are you running a custom cockpit in Dora? If so, do you mind telling me how you managed to get it working? edit: I found this in the user files. That's the only location I haven't tried yet.. Hopefully it works.. ********** To install make sure the file structure looks like: X:\Users\Your Name\Saved Games\DCS\Liveries\Cockpit_FW190D9\Cockpit_FW190D9\English - Blacked If you don't have a Liveries folder there, just make one. **************

some new reports from the 2D world about Low/No Shadows causes the performance drops, i.e. it's better to set them to LOW... Haven't tested it myself yet, just FYI:

I have experienced Pimax twice. The 5k and the 8kx (native 4k). - 5k was too raw when they released it, the color palette was horrible with non-existent black colors and brightness/contrast locked without any possibility of adjustments. I purchased it from their website, wasn't a backer. I sold it the next day. The backers stuck around with this hmd for a year until it finally received the proper color/brightness calibration, but by that time I had the VivePro with Gear VR lens mod and Pimax couldn't top the OLED's. - 8KX (with Native 4K screens). The screens were awesome, very nice color calibration. However the IPD was all screwed up. My IPD is 65mm and the HMD in no way could deliver it despite advertising the support of 60mm-70mm. In reality, in HMD that I received, it was more like 70mm-80mm. It was impossible to align the lenses, i.e. if I aligned the left lens center with my left eye the right lens was 4-5mm further out and vice versa. So I sold it too.. edit: also tracking was very bad. The unit would boot up and find my two base stations, the tracking would work fine. Then mid-way in the game it'd lose tracking and the only way to get it back is to reboot the HMD + restart the software, i.e. it'd never recover. I'm sure they've improved it since then, but if it worked like that out of the box why release such raw product? In other words their QA is utter shit. So don't expect much.

hi, there, @NineLine, I'm a transplant from the Il2 sim and I fell truly in love with the fidelity of the DCS. I spend countless hours of learning the modules, trying to figure out as much as possible about their strength and weaknesses. That being said I spent about 5-6 months flying the Anton A8. It's a work of art, strength, survivability, and power. Couple of days ago I finally decided to give Dora a try. I'm still learning its quirks. Its engine sound is freaking menacing compared to the A8. But the first thing that jumps at me is the low quality of textures on it. The external "undamaged" model textures look decent enough, I think it has another couple of years left in it. However: - The DM textures are of really of low resolution. It's like comparing A8's 4K textures vs. 720p of Dora. The bullet/shrapnel holes aren't even holes, I think.. - The internal textures aren't as bad, but bumping them up would do wonders to the immersion. Is there plan to address the tiredness of this model in some near future?

@DmitriKozlowsky @Tank50us guys, are you talking about fire in the cockpit? Or somehow/somewhere you got the impression that we're asking for the gore and blody body parts in the airplane? There's already fire outside. We just want it inside as well. And also broken dials and holes in the cockpit.

yup, same here. I've got 2 x BBIx32 and they both show up under the same name in 2 different columns. Granted DCS keeps a good track of each and the bindings don't get crossed, but from the user friendliness it's a bit confusing.. I wouldn't touch the registry as Windows can change the UUID on the fly without any explanation... It's a tough one.

true, but c'mon.. this was an awesome update ! I'm sure the crests will come...

ED, @NineLine, @BIGNEWY wanted to thank you for the new water shaders. You guys knocked it out of the park. It is beautiful!

This AI issue is directly tied to the computational workload, hence it's simplified to emulate 30+ AI planes at once near your position in DCS. The other sim moved away from the simple AI physics but ended up in the CPU limitation camp where anything more than 15 AI planes brings the cpu to its knees. I hope to think the dev's will address this issue either during the Vulkan migration or shortly after it. They sort of hinted at it in the latest magazine interview. Personally, the AI fighter issue isn't as critical to me as the Flack and the AA aimbots. Those I truly hate with all my guts.