Jump to content

Recommended Posts

TheAmazinGreat
Posted

I have spent more time tweaking settings than flying it seems but at least it appears to be going in the right direction. I wanted to get some feedback from others to see if I am missing something major though. Visually the plane and environment look great, contacts at a distance, however, leave much to be desired. Spotting is decent for me but ID is near impossible(though I am inexperienced). I thought maybe I just have too high expectations for VR and my hardware but they way you guys talk about it, it makes me think I am missing something.

 

My startup.cfg is set as if for Rift S in the sticky. I had to drop shadows to 0 and to FXAA for frames though. Currently at 4x, considering dropping to 2x for a bit more frames online 

 

Using opencomposite and Oculus tray tool. In tray tool, I have set for 970+ Oculus link settings even though I have a 1070, and set SS at 1.0 with ASW off. Do the default graphics setting options in the oculus home app matter when using tray tool or does it override these defaults? 

 

My rig is pretty old and wasn’t designed with VR in mind, I won the quest in a raffle so I thought I would try it out. 

I5-6500

gtx1070

16gb Ram

oculus quest/usb3.0/oculus link

no mods installed, mostly have been playing online

 

Is my rig my limitation? Am I expecting too much? Does the quest have a lower resolution than the S and this is causing the clarity/ID problems? I know the quest has 1440x1600 per eye, is this cumulative for 2880x1600 compared to the S’s 2560x1440? I can game pretty consistently at 2k on a monitor but I realize that is over a display port and not a usb connection so maybe it’s a bit much to expect my rig to handle.

 

I am able to fly and having fun at current settings so if this is the best it gets I can live with it. Thanks for the help! 

Posted

Actually Quest has slightly higher resolution than Rift S.

I disabled AA in the Oculus Home software, and seems like I maybe gained a little with my Rift S, but could be my imagination.

 

You might try MSAA x2 rather than FXAA, might look better but not sure how well your rig would handle it performance wise.

Shadows, Clouds, and MSAA are the real killers on performance.

 

ID'ing targets is difficult in VR currently, that is a weakness of it.

 

 

 

TheAmazinGreat
Posted
3 hours ago, dburne said:

Actually Quest has slightly higher resolution than Rift S.

I disabled AA in the Oculus Home software, and seems like I maybe gained a little with my Rift S, but could be my imagination.

 

You might try MSAA x2 rather than FXAA, might look better but not sure how well your rig would handle it performance wise.

Shadows, Clouds, and MSAA are the real killers on performance.

 

ID'ing targets is difficult in VR currently, that is a weakness of it.

 

 

 

Thanks for the info, good to know the ID is a problem so sounds like I am on the right track. 

 

When testing in quick mission I had no clouds so that makes a lot of sense. When in MP I figured it was just all the additional happenings causing my issues so maybe turning the cloud quality down will help significantly. 

Posted

@TheAmazinGreat I have a Quest, too, and as dburne posted, spotting and iding planes is a challenge for this VR headset as it is for other headsets.  The Quest is great for seeing if you like flying in VR enough to upgrade your system and headset. I thoroughly enjoy flying VR in my Quest, but like many here, I am hoping spotting will improve with the HP Reverb G2 that I and many others here have preordered. 

 

Here are settings I use that help me enjoy my Quest:

 

Shadows Off

Mirrors Off

Canopy reflections Off (I find them incredible but also incredibly distracting, causing me to think I spotted something out of the corners of my eyes all the time)

Landscape Filter Blurred

Grass Quality Off

Clouds quality High (I love my clouds and am willing to sacrifice for them, but lower quality can perhaps help you)

Antialiasing Type MSAA, but I also have  my Antialiasing below that set to Off since I instead set my antialiasing in my NVIDIA control panel, as shown in the image below.

 

In Oculus Tray Tool for my profile tied to the IL-2 launcher.exe I have set Default Super Sampling 1.1, ASW Mode Auto (some folk recommend Off), Adaptive GPU Scaling On, everything else below that 0, Disabled, or None.  For my IL-2 Profile I also make CPU Priority High, Detection Method Timer, ASW Delay 5, CPU Delay 5, Screen Mirror "Default".

 

I'm posting all of these here to both help you out and to open my settings up for advice from others who may know more and can offer improvements. 

 

If you want to fly and talk together in MP so we can compare what we are seeing by trying to fly in formation, just let me know - I'm lately found dying in Combatbox several times a week, and you can PM me if you want to arrange a time (I'm in Los Angeles) that we can join on an MP server and use SRS or Discord to talk as we experiment ? 

 

Nvidia Control Panel probably best for spotting.jpg

  • Like 1
TheAmazinGreat
Posted (edited)

@Charlo-VR Thanks for the reply, it was very helpful! I added you on discord and am looking forward to some CombatBox Quest quality comparisons. I tried some new things tonight and wanted to share my startup.cfg and settings because I think this is what I will be using as a baseline. 

 

NVIDIA Settings as above set to default

 

OTT Game Settings tab (do not use a profile):

Default SS: 1.0

Default ASW: OFF

Adaptive GPU: On

FOV Multiplier 0/0

Rest of the options are Disabled

 

Quest Link section of OTT:

GTX1070+ default values (I have a 1070)

 

startup.cfg

[KEY = graphics]
    3dhud = 0
    adapter = 0
    bloom_enable = 0
    canopy_ref = 0
    desktop_center = 1
    detail_rt_res = 1024
    draw_distance = 0.54500
    far_blocks = 1
    fps_counter = 0
    fps_limit = 0
    full_height = 1080
    full_width = 1920
    fullscreen = 0
    gamma = 0.70000
    grass_distance = 0.00000
    hdr_enable = 1
    land_anisotropy = 2
    land_tex_lods = 3
    max_cache_res = 1
    max_clouds_quality = 2
    mgpu_compatible = 0
    mirrors = 2
    msaa = 1
    multisampling = 1
    or_ca = 0.00000
    or_dummy = 0
    or_enable = 1
    or_height = 2179
    or_hud_rad = 0.85000
    or_hud_size = 1.00000
    or_ipd = 0.06763
    or_sipdc = 0.00000
    or_width = 1748
    post_sharpen = 1
    preset = 2
    prop_blur_max_rpm_for_vr = 155
    rescale_target = 1.00000
    shadows_quality = 0
    ssao_enable = 0
    stereo_dof = 5.00000
    vsync = 0
    win_height = 1080
    win_width = 1920
[END]

Edited by TheAmazinGreat
Posted (edited)

Very nice, @TheAmazinGreat ! Here are the only meaningful differences between our startup.cfg settings. In mine I have:

 

bloom_enable = 1
draw_distance = 1.00000
full_height = 2160 (matches my monitor since I often will look at the screen as I click through choices with my Quest off my face)
full_width = 3840 (matches my monitor since I often will look at the screen as I click through choices with my Quest off my face)
fullscreen = 1 (I thought I've seen folk recommend full screen, maybe doesn;t make much difference)
gamma = 0.80000 (I find anything less too dark for my tastes)
mirrors = 0
msaa = 1 (since I also have multisampling = 0 I don't think msaa =1 or =0 makes any difference)
win_height = 2160 (matches my monitor since I often will look at the screen as I click through choices with my Quest off my face)
win_width = 3840 (matches my monitor since I often will look at the screen as I click through choices with my Quest off my face)

 

In OTT I have vacillated between 1.1 and 1.0 SS. I know I can trade some eye candy for possibly better spotting, but I need to enjoy what I am looking at even if I miss out on some combat. Plus, I'm pretty confident I get shot down because of my lack of situational awareness and not any disadvantages in my settings ?

 

Perhaps others will chime in on their recommendations of what we have posted, though I'm pretty much done with trying to fiddle since a) I just leave turned off the fps counter and fly what looks good, and b) within 6 weeks I hope to be consumed with tuning my pre-ordered HP Reverb G2, and I know there will be A TON of great advice on best settings for that headset as soon as it arrives in our homes.

 

I hope to "see" you on Discord! :salute:

Edited by Charlo-VR
typos and spacing
TheAmazinGreat
Posted
17 minutes ago, Charlo-VR said:

In OTT I have vacillated between 1.1 and 1.0 SS. I know I can trade some eye candy for possibly better spotting, but I need to enjoy what I am looking at even if I miss out on some combat. Plus, I'm pretty confident I get shot down because of my lack of situational awareness and not any disadvantages in my settings ?

 

This is probably the truest statement ever but it’s better for my ego to blame my settings ?

 

Fullscreen/height/width would be good to test as I also have a 4K monitor. For now it has been nice to use the small window to have other programs visible on the desktop in the background (discord/OTT)

For draw distance and bloom, I’ve seen some various opinions on them so might be a good test also.

 

We might diverge a bit on graphics theory here too. Based on the attached photo from the visualization thread in the general discussion, planes can be anywhere from 1-6 pixels in size at distance. I would think that you want max FPS in order to hopefully pick up on it when it is 6 pixels and not 1. Else you might drop the frame that has the 6 and see the frame with the 1 and miss the spot. This is obviously worse case scenario but the point is the same. I will note that the game does look less visually appealing at lower settings so I understand the want for a sharper image. I think I would like to dial mine up a bit of I can do it without sacrificing frames. 

 

I wonder if this could be counteracted by more AA rather than SS?

 

Then of course comes the complete whirlwind of MP that will throw a wrench in the optimized offline settings I’m sure. 

 

 

C3D57250-4C73-445E-925E-981EC22B27D5.jpeg

TheAmazinGreat
Posted (edited)

Quick update: I am back to default Nvidia settings after reading this in the tweak guide regarding FXAA settings in Nvidia Control Panel: "If Enhance the Application Setting is selected, firstly it will only work for a game if that game has a traditional Antialiasing setting of its own and it is enabled,..." 

Therefore, if MSAA=0 and multisampling = 0 in startup.cfg then it will do nothing to put FXAA on in Nvidia. I have returned to MSAA 2x per the Rift S sticky settings for now. 

Reference:https://tweakguides.pcgamingwiki.com/NVFORCE_6.html

 

Also I discovered:

SS at 0.8 set in OTT gives a pixel density close to native resolution of Oculus Quest. The default at the Oculus home screen is SS 0.9 (1628x1800) and did not change with changes in OTT. SS of 1.0 gives 1808x2000 resolution per eye (125% of native resolution).  Rift S steamVR recommendations in the sticky say to use 130% not sure how these match up but I think much higher than that it is going to start blurring pixels and 

 

It occurred to me that maybe one issue we deal with using the quest is data going over USB 3.0 rather than display port. Beginning to wonder if that is more of a limitation than anything else. 

 

Edited my post above with current settings. I am going to keep that one up to date in case someone else wants to reference it. I think I am abandoning my max FPS theory above also. Game looks great with ASW in auto 1.0 SS and 2x MSAA even if it doesnt run at max FPS. 

 

I thought I bought a flight sim, but turns out it is a VR settings sim. Going to try this for a while and work less on graphics settings and more on flight skills...

Edited by TheAmazinGreat
Posted

Huh... it looks like I will want to try changing my NVIDIA settings from "Enhance the Application Setting" to "Override any Application Setting" if I also want to keep not using the in-game MSAA or FXAA.  I should also try out lowering my SS in OTT from 1.1 to 0.8 (or 1.0 per what I write further below).  

 

Dang, back to fiddling with my settings again instead of just flying and dying ?

 

FYI, here's one last thing I do that may not help with spotting, since it increases the resolution on my Quest, but does help my visual enjoyment of the game on my Quest. I first followed the directions and downloaded the necessary software at "INCREASE the Resolution on your Oculus Quest from INSIDE the Oculus Quest" at

 

 

Then, with SideQuest running I connect Oculus Quest Link.  SideQuest should recognize it, can then use the Run ADB Commands -> Custom Commands option in the upper right of SideQuest on my computer to send the above command, "adb tcpip 5555". This should then allow me to look at all my apps on the Quest and locate the Unknown Sources apps.  That's where I can run the higher resolution options I installed.  I found 2048 was the best choice for IL-2 back with the 4.006 version, and I haven't changed that since. In Oculus Tray Tool I can then use the Visual HUD Pixel Density option to see that the Left and Right Viewports went from the stock 1628 to 1800. If necessary, I reboot Oculus Quest to go back to native resolution. 

TheAmazinGreat
Posted

Per the tweak guide above it suggests trying first the built in FXAA suggesting it may work better having been designed for the game. Another option to try haha. I wonder if the settings came from people using MSAA in game and having NVidia add some extra FXAA. 

 

Either way way I am going to fly at the above for a while and maybe change to 0.9 SS in OTT if I feel I need more frames for MP. It’s all starting to blur at this point but I want to say it didn’t make much of a difference between 0.8-1.0 at these settings maybe a 3-5 FPS per step. So I think I can live with 1.0 and 6-10 FPS less than what I would have at native resolution because of the clarity. 

Posted

Typically most of these Nvidia settings have no affect on a VR device.

I set mine for power management to " prefer maximum performance" for IL-2 and leave the VR Pre-rendered frames at the default of 1.

I use in game graphics settings for the rest.

 

Well I take that back, I do have MFAA enabled in Nvidia Control Panel, just seems like it makes the image a little better but could

be my imagination lol.

  • Thanks 1
ktriggerk0ld
Posted

First post here, so bear with me :)

 

I am not a young fella and have been working in IT fr 20 years. I thought what could be so hard to tune my hardware to run my Quest in an optimal configuration? Well, it seems there is no shortage of "Tips" on how to optimize VR settings to run IL-2 but many of those appear to be conflicting.

I just bought Stalingrad, Moscow, Kuban and Bodenplatte and figured I'd get right into it.

 

I ran IL-2 in all default settings and everything looked fine (I don't expect the same image quality in VR as on a flat panel) except I wasn't happy the guages appeared to be blurry and were hard to read.

So I went on this forum and watched a bunch of youtube videos and now spent more time "tweaking" my settings than actually flying and getting shot down by AA guns.

 

I installed Open Composite just to realize that I when launching the game by running il2.exe I now have to log in and it won't accept my username and password despite I am logged in right now and posting this message.

 

Played with NVidia settings (following recommendations on this forum). Nada.

 

Installed OTT and played with the settings. Not a single change resulted in any noticeable improvement at all, and the guages are as blurry as they were on all default settings.

 

In-game Graphics settings appear to have no noticeable effect on my ageing eyes.

 

I know it sounds like a rant but it really isn't. I can still kinda see them but it takes mental effort and I lose focus on the task at hand so that's kinda distracting.

 

IL-2 is a great game and I am going to continue enjoying it.

 

I just wish there was a sticky of sorts that would be relatively easy for a "dummy" like me to follow. So I'll go back to all defaults, and just enjoy the game. I have plenty to learn before I can score a dog fight victory.

 

And all I wanted was to be able to see and read my guages more clearly :)

TheAmazinGreat
Posted

@ktriggerkoldako which planes are you flying? I usually compare everything using bf109 because I can focus on looking around rather than engine management. I flew allies online for the first time the other day and noticed P51 gauges did seem more blurry to me. Try bf109 if you haven’t already and I will try your plane. 

 

How does your startup.cfg compare with the one I posted above? One thing in all my reading I never came across was make sure you are setting the file manually to “read-only” so the game doesn’t change settings back to default that you can only change from the .cfg file. 

Posted
2 hours ago, ktriggerkoldako said:

First post here, so bear with me :)

 

I am not a young fella and have been working in IT fr 20 years. I thought what could be so hard to tune my hardware to run my Quest in an optimal configuration? Well, it seems there is no shortage of "Tips" on how to optimize VR settings to run IL-2 but many of those appear to be conflicting.

I just bought Stalingrad, Moscow, Kuban and Bodenplatte and figured I'd get right into it.

 

I ran IL-2 in all default settings and everything looked fine (I don't expect the same image quality in VR as on a flat panel) except I wasn't happy the guages appeared to be blurry and were hard to read.

So I went on this forum and watched a bunch of youtube videos and now spent more time "tweaking" my settings than actually flying and getting shot down by AA guns.

 

I installed Open Composite just to realize that I when launching the game by running il2.exe I now have to log in and it won't accept my username and password despite I am logged in right now and posting this message.

 

Played with NVidia settings (following recommendations on this forum). Nada.

 

Installed OTT and played with the settings. Not a single change resulted in any noticeable improvement at all, and the guages are as blurry as they were on all default settings.

 

In-game Graphics settings appear to have no noticeable effect on my ageing eyes.

 

I know it sounds like a rant but it really isn't. I can still kinda see them but it takes mental effort and I lose focus on the task at hand so that's kinda distracting.

 

IL-2 is a great game and I am going to continue enjoying it.

 

I just wish there was a sticky of sorts that would be relatively easy for a "dummy" like me to follow. So I'll go back to all defaults, and just enjoy the game. I have plenty to learn before I can score a dog fight victory.

 

And all I wanted was to be able to see and read my guages more clearly :)

 

Logging in the game has nothing to do with logging into these forums or the website. 

You should be able to put a check in remember password on the game login screen.

 

What are your system specs?

Are you running any Mods?

ktriggerk0ld
Posted (edited)
4 hours ago, TheAmazinGreat said:

@ktriggerkoldako which planes are you flying? I usually compare everything using bf109 because I can focus on looking around rather than engine management. I flew allies online for the first time the other day and noticed P51 gauges did seem more blurry to me. Try bf109 if you haven’t already and I will try your plane. 

 

How does your startup.cfg compare with the one I posted above? One thing in all my reading I never came across was make sure you are setting the file manually to “read-only” so the game doesn’t change settings back to default that you can only change from the .cfg file. 

I just started playing (never played before) and figured I would go along with the timeline so I started with BoM. Tried I-16 and Mig-3 so far, the instrument cluster looks the same hard-to-read quality wise.

 

I will try bf109 as you suggested

 

I copied everything in the startup.cfg and set it to read-only. Didn't notice any difference.

What would be helpful is seeing before and after shots of how the image is rendered in the headset. I've seen some youtubers do that wen they compared color and pixelation of different headsets. That's how I settled on the Quest because I didn't see dramatic difference in image quality from other more expensive headsets.

 

Not having a reference point may be a exercise in futility. Maybe what I complain about is what others are trying to get to :)

3 hours ago, dburne said:

 

Logging in the game has nothing to do with logging into these forums or the website. 

You should be able to put a check in remember password on the game login screen.

 

What are your system specs?

Are you running any Mods?

Thanks for replying.

 

I figured that I have to register before I can run the game without Steam.

 

My specs are:

i7

16Gb RAM

SSD

RTX 2060.

 

I installed Open Composite and OTT but couldn't get past the logon screen so I can't confirm anything yet.

 

I just hoped that there would be a "simpler" solution to the blurry guages as I am not targeting high FPS or multi player (I am a noob and suck as a pilot). Just wanted to get it easir on my ageing eyes to read the guages instead of looking at the HUD.

 

What's also strange is that there is a long list of possible tweaks, each with a potential to either "make it or break it" but when I switch from Balanced to Ultra I barely notice any difference in quality at all. FPS rate probably takes a hit but I don't really care about it at this stage of my pilot "career" :)

 

UPDATE:

SO I launched the game using Open Composite, and it started in my VR headset just fine. Now it wants me to log in but my login information is not being accepted.

I found an article on Steam that one could gran the license jey from Steam and punch it in IL-2 activation page.

 

However, I cannot fin the license key in my Steam library.

 

And that's what I am talking about. People say "Forget SteamVR and run the game through Open Composite". But the big question that remains unanswered is HOW? If I can't get past the Game login screen. Quick search n this forum yielded nothing. Isn't there a simple to follow "how to" for beginners? It's like learning Linux in the 90's using man pages written by Unix geeks for other Unix geeks :)

 

So I am back to square one. All default settings (Sigh)

Edited by ktriggerkoldako
TheAmazinGreat
Posted

Did you create IL2 account and link it to your steam account? If the email/password is different than steam account I would imagine you are supposed to use the IL2 account info to sign in with OpenComposite. 

 

 

I checked out I-16 and MiG-3 and yes I see what you mean by blurry gauges. My question though is are the numbers on the big gauges blurry too? I can read the numbers just fine, but the gauge labels are blurry. If I use the VR zoom and zoom in the labels are clear as day. However as long as you can see the numbers it serves its purpose as you only need to glance to know indicated gauge readings. If you need to read the gauge label to know what it indicates, then I hope you can read Russian also otherwise no matter how clear it is you would not know what the gauge is for. But given a little flight testing I think you can figure which is which and fly by glance. If the big numbers are blurry then we still have some work to do. Note: my small gauge (oil temp/pressure) numbers were just on the edge of visible so they might help serve as a baseline. Also, make sure quest is adjusted properly on your head up and down and IPD set correctly for maximum base clarity. 

 

I dialed my settings back a bit and am flying pretty smooth in multiplayer and almost without frame drop in SP. Updated above. 

ktriggerk0ld
Posted (edited)

I bought the game on Steam. Then I created an IL2 account but it is not linked to Steam.

The link you provided does not contain the instructions on how to link the Steam account to IL2 account.

 

I had a bit of a break-through this morning. I switched all Graphics settings to balanced then switched from FXAA to MSAA with AA set to 4. Wow! Night ad Day!

 

The FXAA did nothing regardless whether it was on or off and at what levels. The way I figured it, I was tilting my head right and left at the game start where you see the menu and the aircraft in the hangar. I was specifically looking at straight lines both close-by and farther away and they were constantly breaking up changing shape from line to dotted line of various lengths. Epileptic nightmare.

 

MSAA at 4 almost completely got rid of all moire and flickering. The lines are no longer breaking up and remain straight. The landscape became way more pleasant to look at. Literally Night and Day difference. Then I dialed it down to 2. It kept the lines straight but the overall image quality degraded. So I left it at 4.

 

I also cranked down Gamma to 0.8 which rendered the image a bit darker but added contrast and was much easier on the eyes and the guages much easier to read. At 1.0 the whites get washed out easily.

 

With these 2 changes, I could see the runway from miles away and I was able to read the Altitude and Airspeed indicators during take-off no problem.

 

Forgot to mention that I also installed VR_Enhancer_4.0 Mod (primarily for the gun sight which improved dramatically and made it way easier to aim)

 

All in all, I am happy now.

 

With the MSAA on, I took a serious FPS hit. "Backspace" shows 36/90 FPS in the upper right corner but the game is very playable at this stage when I am still learning to fly the different aircraft.

 

Now I can't wait for the new HOTAS (Thrustmaster T16000M) that is n backorder so I can ditch the Logitech 3D force feedback which is atrocious on center and not precise.

 

I tried the BF109 cockpit, and it does appear cleaner and a bit easier to read. So you were right about that.

 

Thanks for all your replies.

 

And BTW, I am Russian (living in Canada) so Russian labels and comm radio messages come to me naturally, but when I ventured into the Russian part of the forum, I figured it's easier for me in English. 20+ years in Canada and the Russian IT lingo is like Mandarin to me :)

Edited by ktriggerkoldako
TheAmazinGreat
Posted

Glad to hear it is working better! Sorry the link I provided didn’t help. Truth be told I didn’t read through it all but only saw the title and figured it was the answer. I am not using IL2 through steam so I haven’t had to deal with this. But if you can figure out how to link them that may be the issue and allow you to use opencomposite. I am one to say “if it ain’t broke, don’t fix it” though so up to you at this point.

 

 The 36/90 indicates FPS/FOV. Quest maxes out at 72 FPS. It is likely stuck at 36 by ASW (asynchronous space warp), if you disable this in OTT you may see more frames but it will be a personal preference thing for you. I like it off but Charlo above reported preferring it on. 

 

Awesome. Just wanted to make sure you would be able to read them because I imagine it would be beyond frustrating to spend all that time to increase gauge clarity only to find out they were in another language! I am somewhat of the opposite. I took Russian language classes in school and at one time could hold a decent conversation but not so much anymore. But now I read the gauge text and learn the words based on what the gauges are for. ?

Posted

It turns out I also leave  the ASW in Oculus Tray Tool to Off for IL-2 (I had forgotten I had specific OTT settings for IL-2 that are different from the Global OTT settings).  I guess I'm lucky that 35 fps looks acceptable to me anyway, since my 5-year-old rig rarely pushes it above 35 fps with the eye candy I like.

 

I also confirm that spotting is improved for me based on TheAmazingGreat's advice and what he found at https://tweakguides.pcgamingwiki.com/NVFORCE_6.html . After changing my NVIDIA settings (see earlier in this topic) from "Enhance the Application Setting" to "Override any Application Setting" and setting in NVIDIA to 4x FXAA (with no AA in-game), the spotting improved. But then after changing my NVIDIA settings from "Override any Application Setting" to "Application-controlled" and also changing the in-game FXAA to 4x, I think the spotting improved even a little bit more than that.

 

I haven't yet tried lowering my SS in OTT from 1.1 to 0.8 (or 1.0), since I only try to play for a little while with one change at a time.  Thanks for the advice,

@TheAmazinGreat :salute:

 

  • 1 year later...
scranscranny123
Posted

Hello my name is John. I have il2 sturmovik for years now I bought the CD poped into my computer and  really haven't stopped playing since    I have most of the DLCs and a few planes All was good I even got the trackir 5 even better. But last year I finally got a VR headset   yes the quest 2 and stupid me though all I had to do was plug it in and away you go    but of course NO   .so then I went down the rabbit hole of link cable/ virtual desktop/ opencomposite/ steamvr/oculus tray tool and oculus debug tool.  Learnt all the tricks delete this install that and so on it never ends   Now at this stage I can play the sim no probs  the cockpit instruments are fine the cockpit is fine     outside is ok aswell even when I have settings on high/ by the way the graphics card i have is a 1070 8gb overclocked vr ready/ and my computer has 32 gb memory.  So I can fly the sim and things are ok   until I get another plane passing by then it all goes belly up. This goisting starts and its terrible ?  Have seen a lot of posts here on the subject  but has anyone here with a 1070 8gb and  the quest got it to run as good as it can get with just a setup. And if so could you please help me     even a few screenshots of your setup more be much appreciated                 sorry for the long post   I tried to get to the point as quickly as I could     ?      yours hopefully john 

 

 

 

 

Hello my name is John. I have il2 sturmovik for years now I bought the CD poped into my computer and  really haven't stopped playing since    I have most of the DLCs and a few planes All was good I even got the trackir 5 even better. But last year I finally got a VR headset   yes the quest 2 and stupid me though all I had to do was plug it in and away you go    but of course NO   .so then I went down the rabbit hole of link cable/ virtual desktop/ opencomposite/ steamvr/oculus tray tool and oculus debug tool.  Learnt all the tricks delete this install that and so on it never ends   Now at this stage I can play the sim no probs  the cockpit instruments are fine the cockpit is fine     outside is ok aswell even when I have settings on high/ by the way the graphics card i have is a 1070 8gb overclocked vr ready/ and my computer has 32 gb memory.  So I can fly the sim and things are ok   until I get another plane passing by then it all goes belly up. This goisting starts and its terrible ?  Have seen a lot of posts here on the subject  but has anyone here with a 1070 8gb and  the quest got it to run as good as it can get with just a setup. And if so could you please help me     even a few screenshots of your setup more be much appreciated                 sorry for the long post   I tried to get to the point as quickly as I could     ?      yours hopefully john 

 

 

 

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...