Jump to content

Recommended Posts

Posted

Ok, tried the settings that worked fine with all the other modules and it was absolute slide show with the Apache. STUTTER, STUTTER, STUTTER. Unplayable.

Read on the forum that suggested turn down the TEXTURE to medium and PRELOAD RADIUS down to 100. Now butter smooth.

RTX 3070
11th gen intel i7 11700k
RAM 64
SSD
Oculus Quest 2 120hz-1.7x

OOT SS 1.3
45Hz forced
Adaptive GPU scaling ON
Disortion curvature LOW
Encode Res 3648
Bitrate 300
Sharpening ENABLE

Texture MEDIUM
Texture terrain MEDIUM
Water MEDIUM
Visb MEDIUM
Shadow MEDIUM
Heat Blur OFF
Res of cockpit display 512
Depth of field OFF
Cloud MEDIUM
Lens DIRT+FLARE
MSAA OFF
SSAA, SSLR, SSAO OFF

CLUTTR  GRASS 800
Forrest vis 100%
Forrest / Scenery 1
Preload rad 100
Anisotropic 16x
Terrain obj shadow OFF

[sIGPIC][/sIGPIC]

Laptop Alienware m17x

Intel Core 2 extreme CPU Q3000 @2.53GHz 2.53 GHz

8 GB RAM

2 x NVIDIA 280M

TM HOTAS COUGAR,

24'' Samsung screen,

TIR5

Posted (edited)
Quote

Oculus Quest 2 120hz-1.7x

WOW!! 🤯 I don't even go that high with other modules. For Apache, I settled on 80 Hz/1.0 (90 Hz/1.4 for other modules)

But my specs aren't as good as yours:

RTX 3070

i7-10700K

32 GB RAM

SSD

 

Indeed, I found that the Textures Medium was the key.  (Have it at HIGH for the other modules)

Edited by Recluse
Posted
16 minutes ago, Recluse said:

WOW!! 🤯 I don't even go that high with other modules. For Apache, I settled on 80 Hz/1.0 (90 Hz/1.4 for other modules)

But my specs aren't as good as yours:

RTX 3070

i7-10700K

32 GB RAM

SSD

 

Indeed, I found that the Textures Medium was the key.  (Have it at HIGH for the other modules)

 

Yayayaya fantastic!!! Its crisp and its so fing awsome in VR. NOW

[sIGPIC][/sIGPIC]

Laptop Alienware m17x

Intel Core 2 extreme CPU Q3000 @2.53GHz 2.53 GHz

8 GB RAM

2 x NVIDIA 280M

TM HOTAS COUGAR,

24'' Samsung screen,

TIR5

Posted
7 minutes ago, zyph3r said:

Yayayaya fantastic!!! Its crisp and its so fing awsome in VR. NOW

How is your IHADSS?  Even when running well, I find it seems overly large/far away and I have trouble seeing the Altitude/VVI unless I look to the side or up

 

Posted
7 minutes ago, Recluse said:

How is your IHADSS?  Even when running well, I find it seems overly large/far away and I have trouble seeing the Altitude/VVI unless I look to the side or up

 

Its perfect for me now. Very crisp. Make sure you have it set for your right eye...

[sIGPIC][/sIGPIC]

Laptop Alienware m17x

Intel Core 2 extreme CPU Q3000 @2.53GHz 2.53 GHz

8 GB RAM

2 x NVIDIA 280M

TM HOTAS COUGAR,

24'' Samsung screen,

TIR5

Posted
1 hour ago, zyph3r said:

Its perfect for me now. Very crisp. Make sure you have it set for your right eye...

I don't think the eye setting has any impact on how crisp the ihadss is

  • Like 1
Posted

Following on from my previous post.


Reverb G2

9900KF 5GHZ

3080TI

64GB RAM

M.2 SSD's

 

Before Apache using mostly F16 and FA18

In most single player scenarios I ran 150% in Steam VR (FA18 Super carrier the lot) with the below graphics settings, except with textures on HIGH

image.png

In multiplayer 4YA servers when they're busy I have to drop to 120%

image.png
 

 

After Apache 


I have dropped to 120% even in basic home made test missions in single player with the below settings, otherwise I start to lose frames with the below settings

Untitled.png

Online with a handful of friends in other apaches I'm down to 110%

image.png


As for 4YA, I dare not try.

Hope this serves as good reference for you guys.




What we really need is the 40 series GPU's  ;)))



Posted

Curious how people are doing with the IHADS at night with the FLIR or Camera in one eye? It’s really difficult with it in one eye. Very hard on the eyes at least for me. Also the camera position is a bit off or low. The horizon shows a lot lower than it actually is. I think that might be from the camera position being lower than where your eyes are. I kept having to turn it off though or close my left eye & only look out of my right eye. Not sure if this is something I just need to get used to or what but it is different. I haven’t tried the setting in both eyes but I will try that tonight and see if it helps. I was just curious how other people find this.

Thanks…

Posted
4 hours ago, BeerNfrites said:

I don't think the eye setting has any impact on how crisp the ihadss is

He wrote -"I find it seems overly large/far away and I have trouble seeing the Altitude/VVI unless I look to the side or up"
Mine is just in front of the right eye, dont need to look up or anything therefore i suggested to check that.

[sIGPIC][/sIGPIC]

Laptop Alienware m17x

Intel Core 2 extreme CPU Q3000 @2.53GHz 2.53 GHz

8 GB RAM

2 x NVIDIA 280M

TM HOTAS COUGAR,

24'' Samsung screen,

TIR5

Posted
40 minutes ago, zyph3r said:

He wrote -"I find it seems overly large/far away and I have trouble seeing the Altitude/VVI unless I look to the side or up"
Mine is just in front of the right eye, dont need to look up or anything therefore i suggested to check that.

I have mine set to the Right Eye as well, but it seems overly large compared to the way it sits in front of the cockpit frame in 2D.  I will try to capture some images to explain what I mean. Others have complained about this, so it seems to plague a number of VR users. I found it got a little better when I DECREASED resolution...but, obviously, I want the highest resolution possible that allows good performance. 

  • Like 1
Posted
3 hours ago, Sl1ck said:

Following on from my previous post.


Reverb G2

9900KF 5GHZ

3080TI

64GB RAM

M.2 SSD's

 

Before Apache using mostly F16 and FA18

In most single player scenarios I ran 150% in Steam VR (FA18 Super carrier the lot) with the below graphics settings, except with textures on HIGH

image.png

In multiplayer 4YA servers when they're busy I have to drop to 120%

image.png
 

 

After Apache 


I have dropped to 120% even in basic home made test missions in single player with the below settings, otherwise I start to lose frames with the below settings

Untitled.png

Online with a handful of friends in other apaches I'm down to 110%

image.png


As for 4YA, I dare not try.

Hope this serves as good reference for you guys.




What we really need is the 40 series GPU's  ;)))


 

Try to drop the preload radius down to 100, huge difference for me.

[sIGPIC][/sIGPIC]

Laptop Alienware m17x

Intel Core 2 extreme CPU Q3000 @2.53GHz 2.53 GHz

8 GB RAM

2 x NVIDIA 280M

TM HOTAS COUGAR,

24'' Samsung screen,

TIR5

Posted
8 hours ago, zyph3r said:

Ok, tried the settings that worked fine with all the other modules and it was absolute slide show with the Apache. STUTTER, STUTTER, STUTTER. Unplayable.

Read on the forum that suggested turn down the TEXTURE to medium and PRELOAD RADIUS down to 100. Now butter smooth.

RTX 3070
11th gen intel i7 11700k
RAM 64
SSD
Oculus Quest 2 120hz-1.7x

OOT SS 1.3
45Hz forced
Adaptive GPU scaling ON
Disortion curvature LOW
Encode Res 3648
Bitrate 300
Sharpening ENABLE

Texture MEDIUM
Texture terrain MEDIUM
Water MEDIUM
Visb MEDIUM
Shadow MEDIUM
Heat Blur OFF
Res of cockpit display 512
Depth of field OFF
Cloud MEDIUM
Lens DIRT+FLARE
MSAA OFF
SSAA, SSLR, SSAO OFF

CLUTTR  GRASS 800
Forrest vis 100%
Forrest / Scenery 1
Preload rad 100
Anisotropic 16x
Terrain obj shadow OFF

I just tried the 120hz settings you had along with the graphics settings. Man is it smooth!! I was scared to try this but man does it work well for me. Thanks! I am using the vrperfkit also.

  • Like 1
Posted

I'm having issues using my oculus quest 2 hand controllers to manipulate the power levers and collective. The power levers won't go to idle or fly, and the collective goes full up when I grab it. Any fixes?

Posted
11 minutes ago, tubbysnoutCJ said:

I'm having issues using my oculus quest 2 hand controllers to manipulate the power levers and collective. The power levers won't go to idle or fly, and the collective goes full up when I grab it. Any fixes?

The power levers are linked to the finger-lift detents that have to be manipulated in order to get from off to idle.  This prevents accidently moving the levers to off during flight.  You can disable this under the control settings "special"  AH-64D.  The downside is they will now go past flight idle which disengages the governor, and then you have to constantly manipulate the levers to keep the rotor rpm in the safe zone.

Posted (edited)

Gotcha, the detents are the issue.. I'll map the detents

 

What about the collective going full up as soon as I touch it?

Edited by tubbysnoutCJ
Posted
2 minutes ago, tubbysnoutCJ said:

Gotcha, the detents are the issue.. I'll map the detents

 

What about the collective going full up as soon as I touch it?

 

Perhaps you need to invert the throttle axis?

"Muß ich denn jedes Mal, wenn ich sauge oder saugblase den Schlauchstecker in die Schlauchnut schieben?"

Posted
On 3/20/2022 at 8:27 PM, atledreier said:

 

Edit:
I also occasionally get the lower third of the display very overexposed at times. I've seen at least one other user report the same issue. Never seen that before in any game or module. Not sure if it's Apache or latest beta, haven't tried any other module than the Apache after the beta.

I don't get what could cause this, any ideas?
 

Hi, not sure we are talking about the same issue here, but I used to have the kind of problem you are describing with my Quest2.

I think it's related to the way the video is encoded and streamed to your headset.

For me, It's been resolved for good by lowering the bandwith of the oculus link in Oculus Debug Tool, I think the setting is on "auto" by default. You can try a lower value like 300 and see if it happens again. I suppose somehow the video stream can get clogged with too much bandwith.

Hope this helps

Posted
1 hour ago, pixie said:

Hi, not sure we are talking about the same issue here, but I used to have the kind of problem you are describing with my Quest2.

I think it's related to the way the video is encoded and streamed to your headset.

For me, It's been resolved for good by lowering the bandwith of the oculus link in Oculus Debug Tool, I think the setting is on "auto" by default. You can try a lower value like 300 and see if it happens again. I suppose somehow the video stream can get clogged with too much bandwith.

Hope this helps

Me too, like a white rectangular lower third. No idea what it is. Also sometimes during flights something happens with the pictures it becomes like zoomed in but it aint... or best described to have suddenly very strong glasses everything is a bit zoomed in and blurry. Needs a restart.

[sIGPIC][/sIGPIC]

Laptop Alienware m17x

Intel Core 2 extreme CPU Q3000 @2.53GHz 2.53 GHz

8 GB RAM

2 x NVIDIA 280M

TM HOTAS COUGAR,

24'' Samsung screen,

TIR5

Posted

The problem of white or pink lines in quest2 also occurred in MSFS.
In MSFS, the problem was solved by reducing the bitrate, and in DCS, we did the same, and if the problem was still not solved, we tried to reduce the bitrate by using the graphics

Posted (edited)
On 3/22/2022 at 9:33 AM, Sl1ck said:

Following on from my previous post.


Reverb G2

9900KF 5GHZ

3080TI

64GB RAM

M.2 SSD's

 

Before Apache using mostly F16 and FA18

In most single player scenarios I ran 150% in Steam VR (FA18 Super carrier the lot) with the below graphics settings, except with textures on HIGH

image.png

In multiplayer 4YA servers when they're busy I have to drop to 120%

image.png
 

 

After Apache 


I have dropped to 120% even in basic home made test missions in single player with the below settings, otherwise I start to lose frames with the below settings

Untitled.png

Online with a handful of friends in other apaches I'm down to 110%

image.png


As for 4YA, I dare not try.

Hope this serves as good reference for you guys.




What we really need is the 40 series GPU's  ;)))


 

Question, but why are you running at anything above 2160 x 2160 per eye resolution when that is the max for the HP Reverb G2?  I didn't think doing so would result in any improved clarity....?

Here is a link to a post I made with my global settings fwiw (scroll down to post #13):

 

Edited by RLSinCO
Posted (edited)
8 minutes ago, RLSinCO said:

Question, but why are you running at anything above 2160 x 2160 per eye resolution when that is the max for the HP Reverb G2?

The panel is 2160x2160 but the lenses are optimised to run at something like 3176x3096 to allow for barrel distortion around the centre. This is what SteamVR will set it to at 100%. This contrasts with the original Reverb G1 which had different lenses and a lower default 100% resolution with same panel resolution (2160x2160). Ruining above 100% can yield further improvements in image quality at the expense of performance of course.

Edited by Baldrick33

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Posted (edited)
16 minutes ago, Baldrick33 said:

The panel is 2160x2160 but the lenses are optimised to run at something like 3176x3096 to allow for barrel distortion around the centre. This is what SteamVR will set it to at 100%. This contrasts with the original Reverb G1 which had different lenses and a lower default 100% resolution with same panel resolution (2160x2160). Ruining above 100% can yield further improvements in image quality at the expense of performance of course.

 

Thanks Baldrick33, do you mean the lenses are optimized for the Reverb G2 ver 2?  I will try the higher settings later tonight, but as of right now I don't see how they can get any better than what I have set to currently - I mean, I can see everything in super crisp resolution....but hey - I'm always learning something new every day.

Edited by RLSinCO
Posted
1 hour ago, RLSinCO said:

Question, but why are you running at anything above 2160 x 2160 per eye resolution when that is the max for the HP Reverb G2?  I didn't think doing so would result in any improved clarity....?

Here is a link to a post I made with my global settings fwiw (scroll down to post #13):

 

 

This is a very good question.

VR doesn't work quite like monitor's do.

At 100% in steamVR, the resolution is already about 40% more than native to counteract a certain distortion present in the lenses / way its projected.

The higher and higher you go the better.

At 150% at roughly 3900x3900 per eye. It's like you're inside a spherical monitor. Unbelievable clarity and immersion.

 

Posted

So changing to medium absolutely fixed my performance problems with the 64. No more bottlenecking and dropped frames. Still having micro stutter though. Is that just something I'll have to deal with? 

Posted (edited)
7 hours ago, COQQ said:

The problem of white or pink lines in quest2 also occurred in MSFS.
In MSFS, the problem was solved by reducing the bitrate, and in DCS, we did the same, and if the problem was still not solved, we tried to reduce the bitrate by using the graphics

Personally I find that the Q2 is basically at a stage where no modifications are needed in ODT or OTT at all. I really wouldn't bother with OTT now.  Set the distortion curve once, this is saved for future. Everything else at default. This wasn't always the case but the software has come on so much that it's fine as it is. Resolution and refresh rate can be adjusted in main software.

Edited by Hoirtel
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...