UncleZam

I guess this might be offtopic in this thread, but could you provide reference for your claim that DCS VR IPD means something else than interpupillery distance? I have been using my eye IPD value for that setting and it seems to match quite nicely.

+1

First, make sure you have following setting in Mixed Reality Portal set to manual mode: Second, the startup procedure I use: Start Mixed Reality Portal. At this stage you are usually asked to turn your head to calibrate the inside out tracking. If you fail to do this, it may result in degraded tracking mode with only 3 degrees of freedom. Start DCS from desktop. This will automatically start SteamVR and WMR for SteamVR applications. Note: If at any stage you lose control of mouse or calibration seems stuck, just press the aforementioned Win+Y key combo to switch input between VR HMD and desktop.

You are welcome! I know how annoying the automatic input switching can be, but can be worked around easily. Spread the tip and have fun flying :thumbup::pilotfly:

Sounds like you have the WMR setting "Input Switching" on automatic. It tries to automatically switch between HMD and desktop, but does not work most of the time. That's why you should change "Input Switching" setting to manual. Then you can control the input selection by pressing Win+Y.

Is the "Seat Handler" "vibration level" supposed to affect DCS effects, as I had the feeling that there was no difference between min and max setting? I am using SSA with Jetseat in USB mode. I can change the strength of individual effects, but should it also be possible to control gain for all effects? Edit: now that I read user guide, I suspect the gain control is to be used in Jetseat control panel application. Haven't tested yet though.

That is a good question. I am just reporting what I have been experiencing. This has been the case with Odyssey+ WMR and most likely also Reverb (I will double check this).

This is not my experience with WMR. If I have VSYNC setting enabled in DCS, it will break 45fps motionvector ASW. Therefore I must always disable it when playing in VR.

This might be obvious, but do you have Vsync enabled in DCS settings? It causes weird stuttering and issues in VR at least for me.

Which command do you use to update? Below is copy paste from my "update" shortcut: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" update

Sorry to hear you cannot get satisfactory results. I am not sure if this is configuration issue or too high expectations. Can you be more specific which plane and which instruments you use as a benchmark. WMR has rough edges, which you just have to learn and adapt (mouse focus, flickering loading screens, etc). Some planes have small text labels which is going to be difficult to see without VR-zoom (I think F-14 has worn out labels which makes it extra difficult in VR). Definitely you cannot expect 2D-display (even FullHD) clarity from Odyssey+.

I have had doubts about color reproduction in Reverb compared to Odyssey+. I am a bit of OLED fan, and I guess it is hard to beat that with LCD. Can you give your opinions, how would you compare the color reproduction of Reverb and Odyssey+ ? Edit: I am asking this because I am interested in buying Reverb, but was afraid to pull the trigger.

I also have O+ and recently I have found out empirically that you have to use really high resolution in SteamVR in order to get sharper picture. Try using something in range 400 to 500%. Of course this is really demanding for your GPU, so you have to give up some of the eye candy. Currently I am using DCS in game SS 0.8 and SteamVR resolution 400% ( 2902x3638 ). It could be that there is some regression in SteamVR rendering pipeline causing extra blurriness, you can read about it in SteamVR discussion forum. And there is only so much you can do with the current resolution of VR headsets, maybe Reverb would improve sharpness considerably from O+. Otherwise we just have to wait for higher resolution HMDs. Edit: Breaking news from WMR for SteamVR discussion: https://steamcommunity.com/app/719950/discussions/0/1629665087691809087/?ctp=4#c1736632644636612773

This is too vague information to regain lost confidence. First, why not send this information to customers directly through email or official Realteus web site? Second, please give exact dates instead vague statements of production being completed. Does this mean that it is currently in production? When is the production estimated to finish, how long is the shipment going to take? Why the web page still states: --- We're at 85% of our goal! That’s 393 pledged of our 460 target! Estimated delivery: November 2019 --- In my opinion, the single biggest mistake with Realteus is utter disrespect for customer: rare official updates, no answers to emails, vague schedule, multiple broken promises of production/delivery. For me it is very difficult to trust anything but cold, hard deadlines and full transparency of the production/shipment progress from now on.

I filed reclamation today, hopefully I will get my money back someday.

I had high hopes when Realteus web site stated November delivery estimate. November passed and once again we are left empty handed with no update of progress. Regrettably my patience is wearing thin :(. I sent one last email communication attempt to Realteus, and will initiate credit card investigation if my email remains unanswered.

Thanks for the quick hotfix, it seems to work as intended on english cockpit (i.e. fixes the radar display). :thumbup:

I did not have issue with HSI needle, but instead I had missing texture in radar display. It had kind of camouflage pattern which read "Missing Texture". I tried restarting and changing settings, which none of worked. Then I disabled Mig-21 module from manager, restart, enable Mig-21 module, restart, and radar was working correctly. Maybe you can try similar "fix". EDIT: Further investigation proved that the radar display texture issue is only present in english labeled cockpit. It seems that disabling and enabling Mig-21 module switched to default russian cockpit (which is working ok), but as soon as labels are changed to english, radar display texture is broken.

I ordered in May, no word on delivery so far. Having waited so long, I am fine waiting until the end of the year. If not delivered before January, then I will start looking ordering from somewhere else.

Working replays would be the most welcome news in this update. Of course the Viper is also nice. :thumbup:

When I was placing my order in April/May, Realteus was advertising faster delivery than Andre's 8-motor model that was in in pre-order at that time. Silly me, I believed I was going to get the Forcefeel from May batch.

I investigated this issue, and found out following about the altitude hold: When used over sea level it seems to function correctly (no false warnings). When used over elevated land: As the hold is engaged the reference altitude seems to become the altitude over sea level (pole heights reflect this). I think the reference should come from main altimeter. The altitude warning light is activated if the altitude in main altimeter is below 80% of the engaged reference altitude. The fix could be as simple as taking the altitude hold reference altitude from main altimeter instead of using altitude over sea level.

This review from Jabbers gives some hope that things are progressing. I myself ordered in May and hope to see my Forcefeel seat soon.

Supersampling is nice technology, but cannot substitute real pixels. That's why I would always use high resolution display with lower PD over low res display with higher PD.

I guess that would be me in the photo. I did nothing wrong, just asked ground crew to arm only available rockets. Also I could not myself see what had been loaded. Instead I witnessed another plane with these silly looking rockets. My take on this: could be problem with the module and/or the server.