Gun Jam

Lets try this again... seems my reply got lost as they shuffled this thread around. First thanks for placing this back in the main topic. In my case its a two axis problem. First I feel like ive been cut off at the waist and then place at the front of the seat. The front panel including the UFC and MFCDs are too close making gauges hard to read. Also im too low in the seat my head is below the headrest section of the ejection seat. It doesnt appear to be a hud issue its a default XYZ location issue if this XYZ location needs to be different for monitors then the simple solution is to build a VR XYZ location that users could select. This seems quite simple if not it would be great to get a explanation why. Im pretty sure if I held my body in a weird position and gave it a few tries I could create a new temporary XYZ location using VR center and when sitting back in the seat normally by butt would be on the seat cushion, my back against the backrest and my head in the headrest in VR space. Having to do this each time I want to recenter seems pretty unattractive. its an expensive module a lot of work has gone into it. The a10 is why i started with DCS before DCS world why cant we spend a few hrs to fix a basic requirement? VR is going to become quite popular now that resolutions are approaching that of a monitor and the immersion is a game changer. New comers are going to be put off by this immediately its very very obvious and quite distracting. is there really no workaround? I cant enter a new default head position for a particular aircraft?

I noticed two CTD events with a10c II as well. DCS has maybe 1 before CTD in my entire time using it...very stable. After installing a10C II I got two CTD events within an hr of each other both on the home screen on DCS 1st was right after installing a10cII I clicked on the little icon at the bottom that shows the a10C II module as being installed to see if it would do anything if I clicked on it... Instant CTD in VR. 2nd was clicking instant action during another play session (unrelated to 1st event) clicked on instant action CTD in VR. seems most unstable during first launch of dcs world then stable after the crash during 2nd launch. Dont have enough data for a pattern yet.. But yes issue.

When I position myself comfortably and press the "center" view button for VR the position it gives me feels quite disproportionate to reality. when I look down the seat and the left/right consoles look very close. I feel like Im the wheelchair guy from the movie "wild wild west" with will smith. In addition to this I also feel like I'm sitting far forward in the seat and the front panel is too close to my face when I look back my real body is nice and firm against the seat back rest but I am separated from the aces II ejection seat backrest by quite a noticeable amount and when looking directly back my head position is below the what I would consider the correct headrest position on the ejection seat. Looking outside the plane and in real life photos the pilots head is much higher up into the headrest section. This was the very first thing I noticed when loading for the first time... "woah this is all goofy looking" I didn't recall it looking that way with the old a10c module is it just me?

I was able to get my old reverb to run long enough to test and at 500% render res with dcs PD at 1.0 I get the same results so there is little to no difference between headsets. With DCS PD at 2.5 and steam Render Res at about 150 to 175 appears to be the maximum resolution going beyond that shows no real improvement but at the same time FPS is now so low that its very hard tell if things look better or not. so I my case that is the maximum theoretical resolution which provides about 25 FPS in f14 instant action mission DACT vs f16. Spotting the f16 is much more difficult at this resolution and is easiest near a PD of 1.0 and a render res of about 30% he's a big dot at that point if you are below him just a bit as in the start of that mission. With PD at 2.5 and RR at about 150+ to perhaps 170 provides an image that is likley as good or better than my monitor now a direct comparison is difficult because things are much larger in VR making them easier to read in VR now so you may argue that it is better VR because its just as sharp but also about 2x as large. So the change here has to be software. Not sure if windows or steam. but I suspect this change MAY have occurred within the last month because I notice that FPSVR window is now in focus...It was not when my old headset failed. OR this may have been at whatever update they got rid of the "super sampling" and replaced it with "render res" or its totally something else

The thing they are calling "render resolution" is still Super Sampling just a simpler name for it? and render res still functions as before with DCS PD the same way? Thanks

Okay first of all I was simply impressed by the theoretical quality and wondered what had changed I figured others might be unaware too OR I was the last to find out and could get an answer as to why things are so different now. Is it software or my new headset? (will try to find out more later) with f14 at 500% res playing instant action Nevada DACT vs Viper I get an avg of 38fps I dont feel sick afterwards and it takes me just about as long to shoot him down as it does at 90fps. yes I can tell the FPS could be better but it is playable I dont get stutters that are distracting I can seem him more clearly and it appears that the hud glass is less likley to get that green reflection / tint at certain sun angles the clarity of text and the world do offest this reduction in FPS so its just as playable as it is at 100% res at 90fps. With that in mind I would not consider pushing it this hard as this is quite a simple mission and im sure fps would fall on its face with anything more complex I have great eyesight and dont use corrective stuff I have an intel 8086k pushing 5.1ghz with a 2080ti Again in the past yes about 6 months ago at the time the reverb was re-released with the cable clip I played a lot with many setting particularly what was then called "super sampling" My DCS PD has always been set to 1.0 1) I found that pushing DCS PD up past 1 made only very tiny improvements so I just set it to 1.0 2) pushing ss past 188% or near native res made little to no noticeable improvement 3) I had updated win patches and was running steamvr beta. Nothing made significant improvements past a PD of 1 and a SS setting of 180ish. Without first hand experience observing someone else's setup I drew the conclusion that it was working well (which it always has) and that i see no gains because its hardware limited. Think of it like a full glass you add 10 more gallons of water to it and pick the glass up and observe it...still looks about the same. 4) several hundred pages back I made the decision to abandon steam beta at the time. I felt that things ran better in stable release and others agreed. The main reason for revisiting this was the the absolutely stunning quality that can be displayed (what this headset is actually capable of and others unware should at least get to observe this) AND the huge discrepancy of individuals and their reported findings which is apparently still occurring since this thing was released. The range of discrepancy is from "Its absolutely rubbish I sent it back you are all idiots for using this crap and should be ashamed of yourselves for supporting this product" which was got replies like "bother to set it up right" AND "its because you are blind and have an 80mm IPD" TO "its as good as my 30" 2k monitor or "its as good as a monitor the best quality you will be able to find for a long time at this price point. Now despite doing everything suggested (say 4 to 6 months ago) I never got to the "its as good as a monitor" no it left quite a bit desired compared to a monitor BUT it was so much better than my SO+ that I could see how at initial shock and awe of putting it on that you would go "dang this is like a monitor" but after a few weeks and more careful observation you would see that it was really only about 50% to 65% of what a monitor could do but still WAAAY better than anything else so why were some people so bent out of shape? Well lazy, blind and/or incorrect IPD right??? hummmm..... NOW as of yesterday this has changed I now find myself in the "Its as good as a monitor camp" well no its not but its about 85 to 90% of what my Acer predator 32" 1440 monitor will do. That's pretty amazing I spent sometime getting those bitmap images I posted to fairly accurately simulate the difference in quality if at 500% res. If it doesn't look as good as the 500% image that would be an interesting observation. It should look like that with your head in normal upright position no leaning in, no zoom and you should be able to break out the number as easy as it is in the image. The one thing not simulated is the slightly bluish tone of the image vs my monitor likley due to the LCD displays in the reverb. The color is a bit more vibrant in the bitmap vs real life in the reverb but clarity and sharpness are well simulated. also hold your head still or motion will cause blur. yes I see an improvement in 300vs 500 to the point that I can be sure that its not a placebo I still have my old headset Im going to try to get it to run long enough to see if I can get equal results out of it. -Gun

Which vr menu? I dont even see "supersampling" anymore. Im working in the "setting / General" menu. That's where I remember the SS setting being before. Im trying to figure out what has changed. I figured a boost in SS had no noticeable impact because the HMD was hardware limited the displays max resolution was the best it could do. I see that is not the case and the displays are capable of 2 or 3x the resolution I thought they were in terms of clarity.

Totally new observations with steam super sampling. Im running steam vr 1.11.11. This looks like a recent update and I notice a few new things about it one of which is a new looking "settings" menu. I got a replacement reverb unit last week and ended up revisiting the super sampling menu. In the past I think I had to set it near 188% or something like that to get 2160x2160 native res. Now I noticed that its apparently called "render resolution" Or is this a new setting I dont recall that before I though it was always just "super sampling" I do notice that 100% is now equal to native resolution. In the past using SS above native resolution didn't give any noticeable results but would sometimes lead to people arguing that it did make a difference others would claim that it did not. In my case I saw little to no improvement going beyond native resolution. I wanted to check this again this time I moved what is now "render resolution" to 200% and saw a noticeable improvement... Each time I moved this up I saw an equal improvement. At 500% im kicking down the door to resolution about equal to that of a 2k 30" monitor not quite as good but well beyond what I though this headset could do and much better than anything I have seen before in person VR wise. I also saw a steady drop in FPS as well at 100% I was getting a pretty solid 90 flying f14 instant action DAC Nevada with the f16. At 500% this was now to an avg of about 38ish there isn't a way to really show you the improvement but I can simulate it. F-14 just below the hud, right side there is a small red stripe.. this is actually text but until today was just a red stripe. Here is a simulation of how it looked before at 188%ss or more vs 500% render res. At 500% I can see that it reads something like "AM or FM" 23445. The first two characters aren't easy to see but I can see the number reads 23445...the 5 is hard to break out too but its a 5. I can read this without vrzoom with head in normal upright position. When did this change? Did I totally miss the discussion about this? It seems that even though it beats up frame rate that the quality currently available is still impressive. I do notice blurring during even slow head movement at above 200% it always occurs but becomes really noticeable above 200 I suspect. Thoughts on this? 100%.bmp 500%.bmp

Question after receiving replacement reverb. I had a cable issue with my reverb and HP sent a whole new unit. I use the long cable over headphones too (which I dont use) So the issue was apparently on the HMD side and not the PC cable side. It took several weeks to get the replacement unit. There is one thing that I noticed right away as being quite different. I used FPSVR to show frame rate and temps. I have the floating panel on the left side low it moves a bit with my head movements. Previously despite being about the same distance away as the airspeed indicator on the f14 it looked blurry and was a bit difficult to focus on as if it were much closer to my face than the air speed indicator. Now with the new headset its very easy to focus on and is not blurry. its focus distance is about that of the airspeed indicator. Is this because of the new headset or the new updates? Anyone else notice this? Thanks!

Hey guys. Ive been having a good time with my reverb I use it a 3 to 4 times a week for dcs maybe an hr at a time usually. its been flawless until today. I was in the middle of flying around and the VR screens went black. on my PC screen everything looked fine. I get "check your display cable" on mixed reality portal. I tried plugging things in and out that didnt help. If I moved the connector in the right place on the headset it will light up and stay running if i hold real still as soon as I let go or move it will go blank. It does not appear to be the video card or the internal USB hub that is powered off the PC's PSU. This was a 2nd batch headset with the clip to hold the cables together it was purchased about 9/3/19 from HP. Is this cable thing still an issue and are current failures consistent with my description? Thanks -Gun

Im having issues getting the MIC on my reverb to work. Ive never used it before. I have it turned on in WMR settings "when WMR portal is running switch to headset mic" The other two options are off I have the ear phones removed. In sound settings input is set to "head set microphone" I get nothing in sound settings test mic Noting in discord which im also new to EDIT: It was disabled in windows privacy settings :Settings > Privacy > Microphone. I had to allow app access Any ideas?

Thanks for your help with this! Now that I've asked the question I do now recall going through this before doing google research. The result was similar. "HDMI cant run 1440" display" "yes it can" Or "yes it can but the Hardware might not support it" I think the answer is "yes it can but the hardware wont support it" which I suppose it how I got the initial replay to the first answer. I found my HDMI cable that appears to be rated for "high speed" or HDMI 2 In display setup the max res I can apply is 1080. Now the HDMI to DV converter is a suggestion that had not occurred to me as a thing due to the "HDMI can push 1440" argument which I believe is inaccurate as far as the 2080ti is concerned. So if i can take an HDMI signal and dump it into the DP on the monitor do you suppose it would push 1440? Thanks again for all the help with this! -Gun

I dont think the dell u2711 will support HDMI at native resolution.

I have two monitors that use display port and the Reverb which also uses display port. The 2080Ti only has 2 available DPs I would not use the 2nd monitor and the reverb together. But I do like my 2nd monitor from time to time for work related stuff having dual monitors can be a huge time saver. Right now i have to unplug the reverb and plug in the monitor if I want to use it. I would like to not have to keep swapping plugs in and out. Is there a suitable splitter that can let me easly pick between monitor output and reverb output that wont cause issues with the reverb? Thanks

If you have the f-14 can you read the warning lights on the right side console? With the reverb they cant be read but are almost legible.

Is anyone with the reverb able to read the warning panel lights on the right side console in the F14?? No cheating methods just simply looking at the panel and maybe leaning in a bit. and by read I mean actually read it and not simply recognize a word by the approximate lenght of the characters and its location. PS In regards to my previous post about DCS constantly fading to steam grid it was indeed caused by malwarebytes. I simply went to exclusions and excluded the DCS folder and its great again. Thanks! Gun

Thats interesting I do. It never caused an issue before... I'll look into this now. Thanks!

Question. My reverb has been working well but yesterday I started to get momentary kicked back to the steam grid page with the stars and hills. It had never done this more than once for an instant with both my O+ and the reverb. Then out of the blue its constantly dropping back the grid every 30 seconds or so for maybe 2 to 5 seconds. Its pretty much not playable. What causes this menu to appear? I dont recall making any setting changes since it last worked well. I dont see FPS dropping below 45 often (no more that it did before and it never went to grid) any ideas? Thanks

My thoughts and observations on the reverb: My IPD might be 62 to 64ish...maybe ill remeasure it sometime and post. My eyesight is good I can see better than all my friends and dominate in RC aircombat. I dont use corrective nothing. My first Vr headset was the SO+ I was never that happy with it and thought that originally it must be partly defective because it didnt seem as clear as people made it out to sound. When I found that it probably wasn't defective I kept it as there was likley no better option. I got the reverb and was partly expecting to go "welp here we go again these people must all be blind..." Actually not this time I'm impressed. My initial reaction was it actually does look as good as a monitor. Thats actually not true but its such a huge improvement over the SO+ that at first glance it does look as good as a monitor. The sweet spot: is much improved so much so that I was unaware of the sweet spot until I took the time to look for it. Once you look for it its noticeable but it transitions from the sweet spot to the "not sweet spot" pretty smoothly and the sweet spot and usable area is large enough that by the time you get to the area of major degradation its so far off to the edge that its hidden by the frame or black edge that cuts off your natural FOV. FOV: I cant tell a noticeable difference in horizontal or vertical FOV vs the SO+ SDE: SDE is more noticeable vs the SO+ BUT appears conditional (I would like your thoughts on this phenomenon) A way of describing this might be the SO+ hid SDE by smearing grease over the lens well sure you cant see the SDE but the whole image is also blurred by the grease. The Reverb removes the grease and the image is very clear especially at longer ranges but because the image is now clear you can also make out the pixels even if you aren't looking for them its noticeable. The trade off is quite acceptable. NOW here is the conditional part that Im curious if you guys also notice. If you hold your head totally still while looking at a fixed object like the WRM cliff house wall or that green turtle thing in the steamvr house the SDE is 100% eliminated. No matter how hard I look I cant see a single pixel and its nearly as good as a monitor. but the moment I move my head at all I see very noticeable SDE and I can almost make out the individual colors (like green and red) making up that color group and can see the very clear square outline of each pixel or pixel group if you will. Does anyone else notice this?? LED color: First impression was black was a bit more grey but everything else was fine. After actually taking the time to look yep its a bit more washed out vs my color calibrated monitor or SO+. Not enough to worry about until I remind my self about it. Would like to have the color reproduction of the SO+ which was quite nice but can move past this after about 27 seconds its all but forgotten again and unlike SDE im not forced to be reminded about it accidentally during game play. Mura: Yep its slightly noticeable people want to blame the panels. Im not convinced it isn't the lens. Just like with the SO+ I blame a lot of the shortfalls on the use of the fresnel lens. I still feel this lens choice has no right being used in anything attempting precision...which is why we get banding, chromatic and spherical aberration, a "sweet spot" and probably "mura" and overall degradation in quality. But yeah at the end of the day they need to sell units and a decent piece of apochromatic proper ground glass is going to cost probably over a 1000 USD then the argument could be made that the hardware isnt good enough to justify the lens so we get stuck with plastic BS that is actually ok for now. I would like to think that in 2 years or so a true 3rd gen system will actually be using a glass lens...maybe not an apochromat but at least not some crappy plastic and "sweet spot" will be a legacy issue. Comfort: much improved over the SO+ I dont get red marks on my face. Does take some effort to adjust initially it was putting excessive pressure on cheek bones near nose but was able to adjust out. Steam VR VS Steam VR beta Steam VR seemed to run smoother. Despite what ive read on here I got full resolution at 188% using either Beta or non beta. With beta I was unable to achieve native resolution at 106% it took 188% same with regular. Not sure if this recently changed. Tracking: Better than SO+ it appears that it finds my space faster and has slightly less tendency to lose tracking when looking down. I found both systems to be quite acceptable and I am happy to not have to install lighthouses. Inside out tracking will likley replace lighthouses in future revisions. The last thing I need to more crap to bolt to my walls. Image distortion: Possibly and issue related to IPD In DCS main menu when I move my head slow across the image from L to R or R to L I can see a fish eye type distortion near the center of the image like someone were pushing a softball through the back of the panel causing it to curve. Anyone else notice this? Not obvious during game play -Gun

so Steam Vr beta vs regular steam Vr. should I opt back out and use steam VR...it seemed smoother to me.

My Reverb arrived today I had the SO+ previously and the SO+ was my first vr system. I'm attempting to get things setup...Ive actually read all 342 pages of this thread over the last few months as I watched the reverb go through its "launch" phase. I learned that its not helpful because stuff changes so quick that it becomes not too relevant. Let me know if this seems reasonable. 1) I believe im running steam beta but Im having to push it to 188% to get the stated resolution see photo. 2) In DCS I have PD to 1.0 and I am running 2xMSAA (I need to try with msaa off as well) I thought there was a 3rd place where I had to mess with stuff too Now the clarity is way improved over the SO+ but as odd as it sounds the SDE is a bit more obvious. Im not sure yet if this is because I have a setting off some place. please advise on what I need to check settings wise. Thanks -Gun

Is there a reason not to purchase it from HP direct? I was waiting for amazon but that seems to be taking a while they still dont have any. The ones on the Hp site should be as good as any right?

I have switched to steam vr beta as well as it appears it was initially recommended. One thing I noticed instantly was it acts as if motion re projection (or smoothing) is disabled. It very jittery and I was assuming it had to be re-activated due to the switch to beta. I was running it initially but I haven't checked yet if its still active because I forgot how and haven't looked it up yet.

I got the 1903 update to work. The issue was attempting to run try and decide during the update. now because I just installed this are the mentioned patches included like the july 26th build? Looking at these builds mentioned in this thread it says yes they will be automatically installed using windows update. I dont see them in my update history and win update says it "good to go" I have no idea if im running these patches or not. winver shows Build 18362.267 Can we Identify if a system would require a patch like KB4505903 (july 26th build) based on the build id?? If I look at July 26th build it shows the same build number I have now in its title "July 26, 2019—KB4505903 (OS Build 18362.267)" Thanks

If I keep running into issues with 1903 update ill remove the geforce driver and try again. Im hoping that try and decide isnt causing the issue. Thats a great piece of software..."oh damn I just bricked by PC here let me discard those changes" and back to normal