Jon Fenton

Now Sold

Bump ....this is sat here doing nothing! Really needs to go to a good home. If interested then just contact me with a sensible offer - if it is sensible, I'm not likely to refuse it! Thanks Jon

Just bumping this up. If anyone needs further details or wants to make a sensible offer, then it is still available and still unopened!

Virpil WARBRD base untouched, unused and unopened. Selling purely as surplus to requirements. Currently out of stock at VIRPIL stores and in your hands in 24 hours (UK) if you need it! Pictures available if you require, just message me, but as stated, it is brand new and unopened, so really just thought it better to keep it that way for now. Save yourself the looong wait! ★ Compact Design for Desktop Use ★ Dual-Cam Per Axis ★ Aircraft-Grade Duralumin Gimbal ★ Swappable Springs and Cams ★ Compatible With All VIRPIL Grips and Thrustmaster Grips Looking for £180. (Also have Monstertech mounting plate by seperate negotiation if required. Again unopened.) Message if interested or require any further info. Many thanks, Jon

thank you! That seems to have done the trick. I tried activating MSAA again too, but on my 2080 Ti its just too much for things like Apacher, even with the Open XR. Help very much appreciated! Thanks again.

Thank you so much for the quick response! Half the prob seems to have been actually working out what my problem was! As far as I can tell, what would be ideal is to have a black mask colour when using no MSAA, but this does not seem to be an option implemented for some reason? I will try adjusting to your suggested values and see if that does the trick. Thank you so much for the steer.

Hey @speed-of-heat and @BIGNEWY, I was wondering if you ever got a solution to this problem as I have recently started to experience it after revisiting VR with OpenXR etc. Everything working great, but I use no MSAA and the outside of the mask is blue/white (not black) and am getting annoying white breakthrough on bottom edge of image in headset. I've looked about removing the mask entirely, but I thought it was there to give performance, and so it seems illogical to do that? Did you solve this? Many thanks in advance.

Thanks guys. I was more after if anyone could confirm that this was indeed the cause of what I seem to be experiencing before I started fiddling with files and values therein, but I have indeed found the videos explaining how to remove the mask completely. I will try this and see if it makes a difference. edit: It was indeed the cause - Speed of Heat had confirmed it in another thread that, when not using MSAA, the mask is not black in colour and so any mismatch in the periphery shows up. Solution is to either use MSAA or reduce mask size slightly. Thanks SoH! Perhaps ED can change mask colour to black when also not using MSAA in the future.

Thanks. Burt, but this is not the problem. I understand the foveated rendering. This is not a resolution issue or artifacting, but rather as if the mask that sizes the image to the lenses is the wrong size and so a tiny bit of an alternative image is peeking through on the very bottom edge of the in-headset view on each eye. It is most obvious when flying above a brightly lit cloud layer and when I lift the headset to look at the 2d mirror, I note that ouside of the mask shapes is indeed bright white cloud image.....I think this is what is showing on the lenses and therefore suspect that there is a measurement wrong somewhere.

Has anyone got any steer towards getting the mask edited and how to go about it? (if indeed that is what is causing my problem?). Ive got everything else set up and tweaked to optimum, but just this breakthrough around the very extreme periphery of my headset image is annoying the hell out of me that I can't seem to find how to eliminate it. I'm just using the fixed presets for foveated rendering (not customised them), and so hence why I am more inclined to think it is a VR mask issue rather than that - but open to all/any advice. Many thanks

Hi, could someone more intelligent than me please help me with a small problem? I have installed evryything without a hitch and it is all working wonderfully - thanks to all who developed this. Incredible work. The only issue I have is that I constantly get a thin bright white breakthrough of image on the bottom edge of the display. It seems to appear when on top of a cloud layer etc and so I suspect it is something to do with the VR mask not being big enough? I've looked everywhere to try and find out how to fix this and seen suggestions about "making own mask", but no joy in discovering how! I have created an opencomposite.ini file in the game bin directory and applied the MeshFix line, but no difference. Using a Reverb G2. Can someone steer me how to fix this please? Many thanks in advance.

The solution is to reset the DCS path and fix registry option in the Viacom config. I have to do this after every DCS update.

Remember that the actual resolution is a product of the two. ie : final resolution = global setting x per app (DCS) setting. Then..... FSR downscales the render first to the factor you place in the FSR settings file, does its algorithm stuff, and then the image is upscaled BACK UP to whatever you set to be the final resolution using the product of the two Steam VR resolution settings. The frame rate increase is a result of the FSR algorithms but comes at a cost of a degredation in quality of image DESPITE being at the produced at the desired resolution. That is where the sharpness filter is used if desired. Alternatively, you can experiment with increasing the final desired resolution - but obviously there comes a point of zero return as the benefit of increased frametime of the FSR algorithm gets cancelled out by the cost of setting increased resolution (and thus more pixels to move) to combat the induced blur of the image due to the downscale/upscale process. ....At least that is how I have understood the process.

...oh, and clear environment data in the environment settings tab in Mixed reality section of windows settings.

Yep, reset your room boundary in windows mixed reality portal settings (mine is the seated option where you just hold the headset infront of you centrally). I had this issue myself last week.