Jump to content

WheelwrightPL

Members
  • Content Count

    257
  • Joined

  • Last visited

Community Reputation

178 Excellent

About WheelwrightPL

  • Rank
    Member

Recent Profile Visitors

1441 profile views
  1. I did overclock my i3-8350k to 4.6Ghz at 1.2Volt (verified by Prime95 and Intel CPU Stress tests). I run Reverb at native resolution, I also have Ultra shadows in game (sorry, the cockpits look too damn good with them), and High clouds, so I am not running at low graphics. Here is my Passmark 9.0 Results, which indicate there is nothing wrong with my system, it is the Reverb which is too demanding for IL2 if you run it at 90Hz with decent graphics settings, and do more than simple QMB missions. That's harsh reality, but I believe it is important to set realistic expectations.
  2. To me VR feels like motion platform already because I experience physical sensation of flying. It was making me dizzy initially, but not anymore.
  3. Why? IL2 already has the best damage model in the business and challenging AI. I see higher priorities like upgrading maps fidelity or adding some ground physics.
  4. I have 2080 Ti GPU, 4.6GHZ CPU, and 32GB RAM at 3200 and can only run the simplest of missions without reprojection at medium graphics settings. I have HP Reverb. Even Stalingrad career "at low density" stutters severely when my 190A-3 gets jumped by several I-16s. And this is with reprojection turned on which introduces a new set of problems such as double-images (also called: ghosting), and image distortions (obvious when looking at replays in VR). The cockpits are mesmerizing in Reverb, but the rest of the graphics is a severe downgrade. I am debating with myself if I should return the Reverb, I still have about a week left out of their "30 days free returns" policy.
  5. High resolution textures will make a huge difference in VR because everything gets enlarged in VR, including ugly textures which become super-ugly. Really the DEVS should be looking into this.
  6. I just wanted to add that limiting number of simultaneous planes in careers and scripted missions would also be a lifesaver for VR players, who did all they could to wring out a few more frames per second, only to see their effort nullified in many common career mission types like "destroy ground attackers","troops cover","escort bombers" etc.
  7. Agree about the resolution: P38's cockpit felt so real to me I once caught myself wanting to grab its yoke instead of my joystick. Regarding weight: most of the headset's reviews actually praised it for being pretty light, so I am surprised you don't share those opinions. The wiring is indeed bulky though.
  8. I am buying it tomorrow from amazon so I can return it easily. I will keep you gents posted (BTW I also overclocked my CPU from 4.2 to 4.6 today but see no difference, my 32GB RAM is at 3200).
  9. My Reverb resolution is at 100% (so it runs at native 2160 x 2160 per eye). My IL2 graphics are mixed but mostly towards the higher end. From memory I have view-distance set to: 40km (I think more is wasted in VR because the image is blurrier anyways). Shadows are High or Ultra (didn't decide yet). Grass is High. Rear mirror is Medium or High (didn't decide yet, but if it is too taxing I will just play planes without rear mirrors) My landscape filter is set to Sharp (it helps with flickering) My cockpit-instruments filter is also set to Sharp (who wouldn't want sharp, clear gauges ?) I have antialiasing set to full I have SSOA and HDR enabled, but Blur set to 0 in ...\IL-2 Sturmovik Great Battles\data\startup.cfg
  10. I also have HP Reverb (with 1080 Ti, 32GB RAM at 2600 and i3-8350k at 4.2). I had unacceptable performance, which was improved when I enabled reprojection in this file: C:\Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings by uncommenting this line (ie. removing two backslashes in front of it): "motionReprojectionMode" : "auto" More info here: https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/ I also go through all those steps to launch IL-2 and would like to know a faster way. I even have to plug HP Reverb into USB each time I turn my PC on because otherwise it is unrecognized (is it normal ?) And all those crashes you have are not normal, I didn't have a single one in VR, but on the other hand I don't have any mods and only play simple QMB battles so far.
  11. I agree that this is very disappointing performance: if I am paying $1500 for a video card, I expect extreme shadows and extreme clouds at 90Hz, not at 60Hz, with reprojection turned on. I turned on full shadows in my 1080 Ti and the cockpits look so much better I cannot go back.
  12. Average 55.5 fps with dual-pass vs Average 53.3 fps with single-pass. The difference is minor. BTW: did anybody get a big graphical boost in VR by going from 1080-Ti class GPU to RTX-2080 Ti ? I only mean less CPU-intensive missions like for example 2-versus-4-dogfight in Quick Mission Builder ? I am asking because I am not sure if I should pull the trigger on a $1500 card.
  13. I don't know about JU 52, but HS-129 has standard settings which are simplified. The reason they are simplified is because your RPM-governor has only 1 position, so when you switch to constant-speed-propeller mode you cannot change your propeller RPM up or down (like you can in for example P-38, JU-87 and many other planes) because you're stuck with one "combat setting" RPM. That being said I find that HS-129 is an amazing plane in VR. For example: with the cockpit open I can stick my head out, and observe each single rivet on the windshield frame. Plus the forward sitting position makes one feel like a bird, because there is such an unobstructed view. And it goes without saying the 3D cockpit just blows me away every time I sit in it. The gauges seem so real I feel I can literally touch them.
  14. Bought Reverb a week ago (my first and only VR set). Still cannot get over how awe-inspiring all those plane cockpits are. I thought that "being there" was just a figure of speech. Not anymore.
  15. I find this thread strange: people complain that 90fps is a must or that CPU faster than 4.6Ghz is a requirement for decent VR experience. I think that lower specs are fine too as long as you turn re-projection on. I also had unsatisfactory experience until I found this re-projection setting which made my VR experience considerably smoother (still slow in some cities though). First you need to install "Windows Mixed Reality for SteamVR" and then in this file: C:\Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings you must uncomment (ie. remove two backslashes in front of it) this line: "motionReprojectionMode" : "auto" (default.vrsettings file uses JSON format) I know doing this made the game much more playable for me (I have Reverb and 1080Ti running on i3-8350k CPU at 4.2Ghz), even though it started showing fps in the 45fps range where previously it went all the way to 90fps. I hope it helps some on this forum the way it helped me.
×
×
  • Create New...