Hoirtel

Noticed this with 2.7. This wasn't the case before. No big deal but I'm pretty sure this isn't realistic as I think they tip over!

Oh right, sorry. Have a look through the user files on the website. This is where all the community skins come from you may well find something that already does what you want. If you find something that comes close and just needs a bit of tweaking. I'm sure someone will do it, I will. I'm no expert skinner but I do have PS experience and have modified some of my favourite skins to add my own name and/or markings. I only have limited time so prefer flying to skinning! The user files are great but lack some keyword searching. You can also try just a google search and look for the links to the DCS user files. You can also ask in the skinning forums too.

Best thing to do would be find a skin that has this two tone grey, I would think that would be easy, Then modify it to add your own roundels and markings. Have you any experience with photoshop or open source versions?

Difficulty depends on what you want, how much needs to be changed as adapting other skins can be fairly easy. Do you have a picture of what you want

I thought it was included in 2.7 too, but not yet. I still see perf gains with it on, but smoke, heat blur and some cockpit lights still rendered in one eye. I also do see some graphical glitches in 2.7, particularly around the Caucasus coastlines where grey lines and polygons appear in the sea. I'm not sure if that's to do with this option or not as I haven't tried it as false - I like the performance I get with true so just accepting any negatives.

Hmm. That doesn't sound great...

The jittering is the movement of the clouds relative to everything else. Few people don't seem to see it as much. Quite surprising for those of us that can see it. Have you tried lowing a layer so it is around the high ground. You should see it then. It happens in 2D too, so I'm sure it's the same for everyone.

Ooh. Exciting! Does it include a fix for the cloud movement??

I am in a similar situation, having trouble working out how to integrate Viacom and SRS, previous SP player now starting in MP... I had thought about ditching viacom altogether, I could just about do without it for everything except AAR and Carrier ops (Im a VR player), This option looks like a good solution, I will try that setup for myself! Thanks

Don't know if anyone here has tried airlink with DCS yet. I was very impressed. Few clicks to enable and it ran exactly the same as link for me using my standard ISP router. Couldn't believe it. I never tried VD as I was sure that my router wasn't good enough. Having said how good it is I don't think I will use link in the long term only due to the battery drain, which will be quicker than using the quest 2 as a standalone headset. Pretty good though, I use a wireless headset so I was totally free. I may use it again if I do heavy a BFM session. That will be amazing.

Totally +1 with this. In the presets menu next to nothing we need a random button, so that it chooses a preset each time it loads. Good for those missions where you might just want a bit of change. For others a fixed preset might be better. I hadn't thought about a selectable preset like "all scattered" or "all broken" this would allow some continuity but also variation.

View distance makes a big difference to performance.

Yes, but that's very heavy on performance. I only use 80hz at the same resolution (marked as 1.6 for me I think). I find 72hz I can see slight strobing and makes my eyes tired much quicker otherwise I would use this instead.

Yeah, I hope you are right. As I said I'm not entirely convinced of the on-purpose-reduction theory myself. I think your option B is probably a more likely scenario although my thoughts are that the difference in colour and contrast are more to do with the headsets/screens. I feel that the resolution of them is lower i.e in 2D where there are wispy edges, in VR its more rounded and lower detail, I guess giving the appearance similar to a lower 2D setting. Although this detail would be nice, I do agree they are much better than what we had before, the main thing is the cloud jitter which I'm sure we are all on the same page about, ED have this in hand so no worries. I told myself I wouldn't use them until fixed but somehow I just seem to apply them to every mission anyway!

I'm sure it's possible with any setting, but either it isn't the case, or the visual differences aren't so obvious. I'm not 100% convinced this is the case with the clouds myself, they do look different but I'm open to some other explanation. If so it could just be a temporary thing until more optimisation is completed, it is a first beta after all. Maybe we won't get full res clouds until the new engine updates. Dunno. Do you think they look the same in VR?

Well the theory would be that currently, either due to optimisation or hardware limits it would be too much for any system to render so if you are running VR they don't go any higher than medium regardless of ME setting. Some will say low, I'm not sure. I don't think they are too bad just not as detailed as what I see if I run 2D in ultra.

For performance?

True. I think it applies to everything else, but actually cloud detail might be held back in VR on purpose.

Nope. The clouds jitter is nothing to do with head movements. Nearly everything is more visible in VR. That's why everyone says the graphics are worse. They are not worse. They are the same. You just see it more because everything is actual scale and, you are in the game. Not looking at it through a small window.

Erm, you might be talking about when they takeoff you see a blurry/ghosting. This is the reprojection at work, nothing you can do about it I'm afraid. You can try lowering all your settings to the absolute minimum, as you will need the full minimum of 72fps to not see that. But then everything else will look a bit rubbish all the time.

Yeah trackfile doesn't show it as it's a graphical glitch and tracks are just re-runs. If I see it again I will try and film it, but if it's being seen by a few people I bet ED will be aware already.

Sounds like a similar problem I and others have experienced, are you in VR

Yup, this happened to me on link cable. Really crazy odd. The black squares were growing even in pause mode. I had many of them growing and fading until one engulfed my entire left eye. Just quit the mission, not had it since. I've not reported it, probably should do.

Oculus tray tool and DCS PD (or any other in game settings for other games) are different but they do affect one another. It can get quite mathematical if you want to really work it all out on a numbers scale. If you set 1.1 in DCS PD then 1.1 in oculus tray tool (or oculus debug tool - its the same control) the OTT 1.1 will be a larger increase than if you had 1.0 set in DCS PD and set the same 1.1 in oculus tray tool. This is because it is a percentage of what the game is running at. DCS PD is what resolution DCS is rendering to and then oculus tray tool is a percentage increase of that, or decrease if you set it to 0.X. Worth noting that in oculus debug tool the default values are 0. This is again confusing as this means the SS is actually 1 - i.e no increase or decrease. Its the same 0 for all the settings that can be set with numerical values. If in doubt - leave it at 0. Oculus slider is different. All VR headsets need more pixels than the native resolution of the internal screens to account for the distortion created by viewing screens through lenses. Oculus allows you to control this so that you can gain more performance, at the cost of visual quality. It should be the first slider you work on (or only) and you should get this as high as you can, yes all the way to the right if you can run this. If not, then reduce it. There isn't any point in having this set low to only increase things elsewhere (PD or SS). Sounds confusing as I write it! Apologies! As I said if you really want to understand it you will need to do some maths (excel) and research the difference between PD and SS. Jabbers did a good video on this with reference to steam VR and the valve index so not fully applicable to the Q2 but better explains the maths and PD/SS better than I have.

I've got more than 9 USBs plugged into my PC - all working on 2.7 no problems. I had this before too, no problems then either.