Pimax users, new beta PiTool 1.0.1.180

[blitze]

https://forum.pimaxvr.com/t/new-pitool-1-0-1-180-is-available-now-from-pimax/21281/91

 

Close down old version, kill pitool processes in task manager and install.

 

Reboot - Enjoy.

[=ILS=_ppph]

what is your performance like for the new pitool 180

[fiddlinjim]

I updated to Pitool 180 and very latest Nvidea and have now got some very jittery/jerky movements when moving my head side to side or forward in the cockpit.

However, this does not happen in exterior view. 

Not happy with the 180 version and seriously considering reverting back to previous version.

[blitze]

Performance - seems better on initial trials but I have not had a chance to test them for a reasonable period of time.

 

fiddlinjim - did you update the Nvidia drivers to the ones linked here?  There is also a newer hotfix driver just released from Nvidia you can pull from the same site as the others.

I have not found there to be jerkiness but then I am limited to 3 axis of movement as I don't have a lighthouse yet for 6DOF.

 

Will play with it more when I have a time and it cools down a little. ?

[blitze]

Did a Stalingrad mission, bomber intercept in my La5.

 

PiTool FFR Aggressive, FOV - Wide, Render 1.25

 

SteamVR Vid 50%, App 100%

 

Il2 - Balanced preset with 4x terrain distance, high shadows, high clouds, SSOA, HDR etc.

 

Winter day, overcast - it was a pain to navigate relying on landmarks as the cloud cover was at 1200m and lots of it.  Overshot the intercept, back tracked and then caught up with the enemy as it was flying home.  109 G2's were being engaged by another 3 La5's, I called to attack Stukas (6 in all) and my wingmen call Bingo Fuel and piss off.

 

4 Stukas later and a cloud hopping flight home with leaned out fuel and reduced engine power to conserve fuel, I make it to base.  I land right on top of another and run out of fuel as I taxi off the run way.

 

Field of view - Lovely.  Fairly smooth, approx 45 above the clouds at 2000m+ and 35 in the clouds playing cat and mouse.  40ish near ground.  Not bad and I could introduce Smart Smoothing at 64Hz if I wanted it a little better.  Balanced preset does introduce view distance haze over Low and it is noticable but then with lots of cloud about - yeah, navigation was sucky.

 

Thought the combo of Wide FOV and Aggressive FFR would cancel each other out and maybe make up for Parallel Projections as the overlay would be reduced by FFR.  Seemed to give similar fps results as no FFR and Normal FOV.

 

Spose a 190 A5 Jabo run over Kuban will be my next test.?

[Blitzen]

Any improvement in SDE /clarity or FPS?

[blitze]

1 hour ago, Blitzen said:

Any improvement in SDE /clarity or FPS?

On the 8K?  I now run it with +2 Screen Vertical Offset adjustment.

 

I would need to run Low setting in Il2 as I used to up till recently to gauge differences as Balanced and above introduce haze over distance.  I like balanced though in that it blends near field trees nicely with non rendered trees on the landscape.  Not sure if this was further improved with the recent Il2 update as I seem to remember it being more obvious in the past.

 

Clarity with the Screen Vertical Offset adjustment was greatly improved as was 3D render depth perception.

[Blitzen]

1 hour ago, blitze said:

On the 8K?  I now run it with +2 Screen Vertical Offset adjustment.

 

I would need to run Low setting in Il2 as I used to up till recently to gauge differences as Balanced and above introduce haze over distance.  I like balanced though in that it blends near field trees nicely with non rendered trees on the landscape.  Not sure if this was further improved with the recent Il2 update as I seem to remember it being more obvious in the past.

 

Clarity with the Screen Vertical Offset adjustment was greatly improved as was 3D render depth perception.

Install went very smoothly replacing my old Pitool install, so thank you for the postings ! I set "Enable Program" to Il-2 BoS as well ,I assume that's correct?.Is there a settings for "Vertical offset & Render Quality" I should be programming in as well or just experiment with what might work best for my set up ??

[blitze]

Under Settings and HMD

 

 

Rest of the settings for Il2 under Games and Il2 specific.  Launch SteamVR from My games Il2 hyperlink and then Il2 after you see SteamVR launch and the grid appear in headset.

 

Just did P47 x2 vs Ju88 x4 Kuban with Low settings, yeap - vis with haze is a Balance and above thing but blur over distance is much improved with screen vertical offset adjustment.

[SCG_Fenris_Wolf]

7 hours ago, blitze said:

Did a Stalingrad mission, bomber intercept in my La5.

 

PiTool FFR Aggressive, FOV - Wide, Render 1.25

 

SteamVR Vid 50%, App 100%

 

Il2 - Balanced preset with 4x terrain distance, high shadows, high clouds, SSOA, HDR etc.

 

Winter day, overcast - it was a pain to navigate relying on landmarks as the cloud cover was at 1200m and lots of it.  Overshot the intercept, back tracked and then caught up with the enemy as it was flying home.  109 G2's were being engaged by another 3 La5's, I called to attack Stukas (6 in all) and my wingmen call Bingo Fuel and piss off.

 

4 Stukas later and a cloud hopping flight home with leaned out fuel and reduced engine power to conserve fuel, I make it to base.  I land right on top of another and run out of fuel as I taxi off the run way.

 

Field of view - Lovely.  Fairly smooth, approx 45 above the clouds at 2000m+ and 35 in the clouds playing cat and mouse.  40ish near ground.  Not bad and I could introduce Smart Smoothing at 64Hz if I wanted it a little better.  Balanced preset does introduce view distance haze over Low and it is noticable but then with lots of cloud about - yeah, navigation was sucky.

 

Thought the combo of Wide FOV and Aggressive FFR would cancel each other out and maybe make up for Parallel Projections as the overlay would be reduced by FFR.  Seemed to give similar fps results as no FFR and Normal FOV.

 

Spose a 190 A5 Jabo run over Kuban will be my next test.?

FFR has always been crashing before after several minutes. How long did it work for you, how long did you test it?

 

Must give this a try.

 

I got the best clarity with 0 vertical offset. Point is, it may depend on the shape of our faces and must be found individually.

Edited July 27, 2019 by SCG_Fenris_Wolf

[fiddlinjim]

Not sure which but either the 180 Pitool update or the IL2 Update or the very latest Nvidea update or the latest Steam VR update changed my IL2 graphical settings

causing some severe cockpit-only jerkiness when moving my HMD, however the  external view was not affected.

Returned graphical settings to their previous selections and got back to near normal.

Has anyone been able to use the new Pitool 180  "Motion Compensation" setting, my setting is unchangeable and continues to state "None"?

[E69_Luke]

Pimax 5k+ user here. I always have 29-35 fps unless I try flying with Large FOV and/or >70% SS on SteamVR and/or >1,25 SS on PiTools.  My question is: Any advantage of using 90hz instead 72hz ?  I can't see any difference. Do you?

 

Also, FYI , I´m using these drivers ripped from Windows 10 Insiders fast ring, and I'm very happy with them. Supposedly they solve the high GPU usage on some games, like DCS, but if the last version of pitools also solved that , I dont know if they worth the time. Anyway:   

Quote

Nvidia 435.27 Windows Update driver date 3.6.2019
https://www.mediafire.com/file/u4fqcklzt82b2tw/Nvidia+435.27+3.6.2019.rar

 

Maybe with help some of you, in case official drivers are not working as they should.

 

Cheers.

[SCG_Fenris_Wolf]

The last version of PiTool solved it, .180 version. I am consistently at 92-96% usage now.

[=GW=a7610783]

In version 180, FFR still crashes; the first time it is installed and the battle is completed perfectly in DOGFIGHT, but when the aircraft is selected in WOL, the screen freezes immediately after entering the cockpit (but the sound indicates that it is still operational), test condition STEAM 144 % PI 1
I have an I7-8086K (OC 5.2G) + 2080TI

Edited August 2, 2019 by IV./JG5_a7610783

[blitze]

2 hours ago, IV./JG5_a7610783 said:

In version 180, FFR still crashes; the first time it is installed and the battle is completed perfectly in DOGFIGHT, but when the aircraft is selected in WOL, the screen freezes immediately after entering the cockpit (but the sound indicates that it is still operational), test condition STEAM 144 % PI 1
I have an I7-8086K (OC 5.2G) + 2080TI

test condition STEAM 144 % PI 1

 

Try Setting SteamVR 100% and running PiTool at 1.5 Render.

Also, what Hz are you running and are you using Aggressive FFR?

 

It seems to be about load on the CPU as I find hangs and crashes are due to a CPU spike of 100%

If I run career missions with reduced activity that helps or PWCG

 

I also run Low Graphics settings in game but I have a CPU that runs at 2/3rds yours and the non ti version of the 2080 running off a Thunderbolt connection. 

 

Experiment with SteamVR settings of 50% - 100%- 150% or 200% with PiTool as inbetween SteamVR settings, like 144%, will not perform as well.  I believe it is due to the math crunching to calc Rendered Pixels at non factor of 2 ranges.  Easier to double or half the number of pixels to be displayed than obscure multipliers like 144 / 80 / 60/ 24  I put it down to the binary nature of computing aka 2/4/8/16/32/64/128.......?

 

Then again, I could be talking out of my backside but try it and see how you go.

[=GW=a7610783]

15小時前，blitze說：

測試條件STEAM 144％PI 1

 

嘗試將SteamVR設置為100％並在1.5渲染時運行PiTool。

另外，你正在使用什麼赫茲並使用激進的FFR？

 

它似乎是關於CPU的負載，因為我發現掛起和崩潰是由於CPU峰值100％

如果我執行職業任務減少活動，幫助或PWCG

 

我也在遊戲中運行低圖形設置，但我有一個以2/3的速度運行的CPU和運行霹靂連接的2080的非TI版本。 

 

使用PiTool進行SteamVR設置50％ - 100％ - 150％或200％的實驗，如同之間的SteamVR設置，如144％，將無法正常運行。我相信這是由於數學運算以非因子2範圍計算渲染像素。比144/80/60/24這樣的模糊乘法器更容易顯示的像素數量的一倍或一半，我把它歸結為計算的二元性質又稱為2/4/8/16/32/64 / 128 ...... .... ?

 

然後，我可以在背後說話，但試試看你怎麼走。

我的CPU最高速度為5.2G
測試STEAM 50％
                  PI 1.25 72HZ
寬視野
當你進入遊戲菜單時，立即凍結（連續三次）
特定的CPU使用率沒有保持在高水平，關於漂浮50~70％

 

以上圖片使用STEAM 150％
                                PI 1.25
中場視野
飛行凍結約五分鐘（但仍有聲音可以操縱）

Edited August 3, 2019 by IV./JG5_a7610783

[blitze]

@IV./JG5_a7610783

 

Are you using FFR?

Did you try Steam just at 100% with PI 1.25?

 

Sorry but also, what video card are you using with that 5.2Ghz Beast? ?

 

I have been testing it with PI 64Hz and 80Hz modes.

 

A mission I had last night - Stalingrad, Winter, La 5 Intercept of German Ground Attackers not far from home field - I was having Il2 Lock up 3 or 4 times.  I decided to disable SSOA and I was able to play through the mission with no lockups.  More testing to be done but that saved a bit of frustration and also gained a little FPS as well.

 

I do like the in cockpit effects SSOA gives and it will be interesting to see what comes of it with the Engine update in Late September given 1C are looking to extend visibility out to 100km.  They will be doing some serious behind the scenes work on the Graphics Engine I would expect to achieve this.

 

I also wonder how sensitive FFR is to Overclocking.

 

[SCG_Fenris_Wolf]

On 8/3/2019 at 10:37 AM, IV./JG5_a7610783 said:

我的CPU最高速度為5.2G
測試STEAM 50％
                  PI 1.25 72HZ
寬視野
當你進入遊戲菜單時，立即凍結（連續三次）
特定的CPU使用率沒有保持在高水平，關於漂浮50~70％

以上圖片使用STEAM 150％

 

                                PI 1.25
中場視野
飛行凍結約五分鐘（但仍有聲音可以操縱）

 

好朋友！
FFR和遊戲崩潰。
也許這就是原因？

5.2GHz閃電般快速。也許它太多了 - 撥打速度慢到5.0GHz  - 一個想法！

遊戲使用AVX訂單。這是一組特殊的訂單，它們給CPU帶來了很大的壓力。

Edited August 13, 2019 by SCG_Fenris_Wolf

[=GW=a7610783]

14 hours ago, SCG_Fenris_Wolf said:

 

CPU 5.2G HZ is generated by me in the overclocking state (the motherboard is fully overclocked). The normal working condition is 5.0 (I7-8086K)
I tried not to overclock to start FFR, the situation is still

On 2019/8/3 at PM5點52分, blitze said:

@ IV./JG5_a7610783

 

你在使用FFR嗎？

您是否使用PI 1.25以100％的速度嘗試Steam？

 

對不起，還有，你使用5.2Ghz野獸的視頻卡是什麼？?

 

我一直用PI 64Hz和80Hz模式測試它。

 

我昨晚的任務 - 斯大林格勒，冬天，La 5攔截德國地面攻擊者離主場不遠 - 我讓Il2鎖定了3到4次。我決定禁用SSOA，我能夠在沒有鎖定的情況下完成任務。更多的測試要做，但這節省了一點挫折，也獲得了一點FPS。

 

我確實喜歡SSOA給出的駕駛艙效果，看看9月下旬發動機更新的結果將會很有趣，因為1C正在尋求將能見度擴展到100公里。他們將在圖形引擎上做一些嚴肅的幕後工作，我期望實現這一點。

 

我也想知道FFR對超頻有多敏感。

 

My video card is 2080TI
The memory is 8G X2 3600MHZ

[blitze]

I have launched a Bug in the appropriate section.  Fixed Foreated Rendering with Pimax and Il2 seems to have at random a CPU Core Spike that brings Il2 executable to a freeze.   This is a problem with the game engine being single core based.  I hope for the reworking of the engine for many aspects as detailed for the next release - they will address this short coming and that of Parallel Projection compatibility.

 

For small FOV headsets and even the 5 and 8K on Small FOV (120 to 130ish) Foreated Rendering does not bring much benefit but when you go 150 and larger - it makes a huge difference especially at high render targets.

 

Pimax is also aware of the current >8192 x or y axis resolution bug in SteamVR they have with PiTool where the Left eye ends up scaled 3x the Right eye.  This should be addressed in the next update which will allow for FFR testing on Large FOV at PiTool 1.25 and 1.5 with SteamVR at 100% Video/Application.  I think performance results when not crashing will be the same as Normal FOV or not much higher due to the nature of Foreated rendering on the outer view.  My tests at lower render targets with FFR on between Normal and Large FOV in PiTool has shown similar fps output between them.  This is upto 8192 horizontal resolution where more than - the PiTool/SteamVR render bug hits.

[SCG_Fenris_Wolf]

The Fixed Foveated Rendering FFR API/whatever there exist that they use is the one published by Nvidia for RTX cards. No idea if the IL-2 devs have implemented that or if it even needs implementation. It would be great if it worked, but it rarely works on quite a few games.

 

Regarding the latter part of your post:

You don't want to put the target render above 8192 pixels horizontally anyway. That's a resolution 4 times larger of what the average eye of an Index, Rift S, or anything really renders. There's no PC that can run that fluently.... not even my RTX2080ti. I'm sure your laptop couldn't. So why even mention that? I cannot run my monitor on 8000*4000 either - it's only 4K....

 

Why would anyone put his resolution at what, 9000*5000 pixels? Maybe in 2025. Last time I looked though it was still 2019! So why mention things as "bugs" when they are impossible and irrelevant anyway...

[blitze]

@SCG_Fenris_Wolf

 

FFR is implemented for RTX cards correct.  It is supported by Pimax headsets via PiTools and can be enabled for any VR title via PiTools.  You have heard of Super Sampling right?  It is used as a form of AA and improving the quality of pixels displayed on your headset.

 

The PImax 8K headset has 2 x 4k panels but they are not true RGB subpixel matrice panels - they also have a 1440p limit in data sent to the HMD and then upscaled on the headset via a built in scaler chip.  Not very ideal but hardware limitations at the time of inception.  Both in 4K panel refresh speed which got them at around 80Hz stable per eye and the limitations of Display Port at the time for Single cable VR connection.

 

To get a quality detailed image on the 8K you can use a combination of Fixed Foreated Rendering and then bump your Render Target up to 5k+ per eye.  In Large FOV mode this means that if you go 5K vertical, you will exceed 8K horizontal.  FFR will of course only present that res at the lens sweet spot and then step the render down 2 stages.  This at the mentioned high render targets removes the obvious render step down to the eye whilst maintaining a reasonable performance on the headset.  As mentioned also, FFR is rather pointless on Low FOV headsets performance wise as there is little image room to step the render down.

 

Unless you have access to the hardware I am talking about and have experimented with it - then please, let those of us who do and are using it on a daily basis communicate with the Developers to try and improve the current day tech experience that can be possible with this sim.

 

I have flown this sim on my 8K with FFR on at 6684 x 6612 (Normal FOV) SteamVR Render Target on Il2 Low settings and the detail is gorgeous.  The detail in the landscape and overflying towns is lovely, even on Low Il2 Graphics settings.  The 8192 limitation which would apply trying to use Large FOV with PiTool at 1.25 or 1.5 is a real issue and will be dealt with by Pimax.  I am not trying to push 80fps constant or 120 or 144 - I am looking at mid 40's with high fidelity image.  It is also a proof of concept for when a real 2 x 4K headset comes to market.  It is said that it will require less to drive that due to the crispness of the image than the current Pimax 8K.

 

You could possibly try what I am suggesting on a Pimax 5K but I don't think you will see as much what I am talking about.  At least following my settings you would know from your own system that it is indeed doable even if the 5K can not deliver the same image quality.  Glad I didn't jump on the bandwagon when it was said the 5K was the HMD to go for, not that the 8K has been a jewel right from the start either.

 

My understanding is the issue with FFR is most likely a problem with Parallel Projections Compatibility required to use Il2 on Canted Headsets.  At the end of the day it is my drive to improve Il2 VR experience with what is possible on todays hardware.  This is not a case of - oh, it can't be done have to wait for RTX 5080TI and i3990KS  @ 10Ghz before one can render at such targets in 4 or 5 years time.

 

Experiment with FFR on your Pimax 5K and see what you can do.

Oh F it - come to middle Finland and I will show you.?

[Blitzen]

Very slightly OT: Now that i am up to the latest Pitool version how will I know when it is time to update to a new version? The "check Current Version" function has never told me to update even when a new version is available- I have to depend on news here in GB's.sort of inconvenient.What gives?

Also of note :recently during a reboot or mistakenly turning off & turning on Pitool I noticed it had reverted to the older originally (and this consequently caused a lower quality of images of aircraft esp in exterior views- they got very jagged....) installed version v 2.1 something ( weird numbering system they have..) Of course I changed to the newer version after I figured out what was going on.I never did figure out what this happened?

Finally I can live with lower FPS number in the 30-40 ranges as long as the quality and clarity of the aircraft in & out are high with sharp shadows & crisp objects &  line work. I've played a lot with this & found that 100 in Application & 160 in Video in SteamVR settings, while going to high or ultra settings in game and following other suggested settings in game and 'startup" suggested at the beginning of this thread, seems to work best .Lowering those settings seems to degrade the clarity while boosting FPS a little. Does anyone else have a better sugestion (s)?

 

[blitze]

@Blitzen

Whilst running 160% SteamVR Video and 100% Application, what is your PiTool Render setting?

 

Have you thought about using SteamVR Video at 100% and using the next higher setting on the PiTool Render setting?

 

Seem to find myself that SteamVR settings work well at factors of x2 so 50%, 100%, 200%, 400% be it either Video or Application or both.  Keeping things mathematically simple in relation to the resolution PiTool tells SteamVR.  When I have tried 40%, 60% or 80% - I find my performance drops considerably.  I keep SteamVR Video and Application at 100% and just use the PiTool  Render setting instead.  Have a go and see what you think.

 

I've been looking at FFR and high render targets with PITool at 1.5.  Not very stable at the moment but boy it looks nice but interesting enough, with Lefuneste 3Dmigoto Mod, latest version he has implemented a Parallel Projections fix.  It is a work in progress but - with it on and PP off in PiTool, performance is better and image clarity is much better too.  At least for my 8K.

[Blitzen]

17 hours ago, blitze said:

@Blitzen

Whilst running 160% SteamVR Video and 100% Application, what is your PiTool Render setting?

 

Have you thought about using SteamVR Video at 100% and using the next higher setting on the PiTool Render setting?

 

Seem to find myself that SteamVR settings work well at factors of x2 so 50%, 100%, 200%, 400% be it either Video or Application or both.  Keeping things mathematically simple in relation to the resolution PiTool tells SteamVR.  When I have tried 40%, 60% or 80% - I find my performance drops considerably.  I keep SteamVR Video and Application at 100% and just use the PiTool  Render setting instead.  Have a go and see what you think.

 

I've been looking at FFR and high render targets with PITool at 1.5.  Not very stable at the moment but boy it looks nice but interesting enough, with Lefuneste 3Dmigoto Mod, latest version he has implemented a Parallel Projections fix.  It is a work in progress but - with it on and PP off in PiTool, performance is better and image clarity is much better too.  At least for my 8K.

Let's see if I can answer your questions.

My setting is currently at the recommended "1".

I have tried various settings of these sliders , but not 100% and  say 1.25 on the render slider.Is it worth a try/ does it work well for you?

Are you referring to both the application & Video settings beng the same ? Of course I can try experimenting, but right now I have really pretty good clarity with 160 and 100.Of course i'd like to get as close to perfect clarity as i can, but don't want to play around too much either..

 I can try 1.50 , but to be truthful I've never got the hang of how to use Lefunste Mod.It seems pretty complex to my weak mind.

finally I have noticed that I am getting better clarity in my right eye than left.It is probably because after a cataract operation one eye ( the right) is at 20-20 whereas the left is set for better nearsighted tasks.I wonder if there is a way to compensate for this difference?

 

[blitze]

Application and Video settings the same in SteamVR - 100%

 

Try PiTool Setting at 1 / then 1.25 and then 1.5

 

See how you get on.  For the 8K I find PiTool Render Setting 1 to be worst of them.

Without FFR then 0.75 is good, with FFR then 1.25 and with PP fixed then 1.5 is nice.  3Dmigoto PP fix seems to work with Normal FOW but with Large the world scale is quite small.  It is a work in progress and who knows what 1C/777 will bring to the table with the BoBP release.

[Blitzen]

Ok - Best performance yet, with nearly all ingame settings on Ultra and most clip & paste settings in place.:

Applications 100

Video ; 100

render setting 1.5

FPS on simple mission is in the high 40's

Aircraft definition & crispness of detail very good with some break up Of single lines like radio aerials & bracing wire in outside views but not too bad.

Shadow definition very good.

No sparkle or blurred detail initially noted.

A bit of bounce or shutter from time to time but not too bad either.

From my point of view nearly all good signs.

 

BTW No one addressed my first question : how will I know when the Pitool needs to be updated if the Pitool won't tell me?

Thanks guys!

[fiddlinjim]

10 minutes ago, Blitzen said:

Ok - Best performance yet, with nearly all ingame settings on Ultra and most clip & paste settings in place.:

Applications 100

Video ; 100

render setting 1.5

FPS on simple mission is in the high 40's

Aircraft definition & crispness of detail very good with some break up Of single lines like radio aerials & bracing wire in outside views but not too bad.

Shadow definition very good.

No sparkle or blurred detail initially noted.

A bit of bounce or shutter from time to time but not too bad either.

From my point of view nearly all good signs.

 

BTW No one addressed my first question : how will I know when the Pitool needs to be updated if the Pitool won't tell me?

Thanks guys!

I have received an email notice from PIMAX each time there was a Pitool Beta update.

 

[Blitzen]

BTW: I activated "Super Smoothing" and it worked in whatever way it is supposed to work & has seemed to do away with the small but incessant 'jitters" I had previously. No loss in FPS either ( about 48 on simple game play..).I think  Pimax5K is about as perfect as I could ever hope for now ...until next Pitool upgrade that is!

[TCW_Brzi_Joe]

Hello Plimax users, I went to the dark side also  It is 5k+

 Can you tell me, what is with sun halo? With pimax I practicaly do not see anything if sun is anywhere on my screens. With a Oculus Rift before I could just turn my head a little bit, and I woud see again. Now sun halo is huuuuuge, can not turn my head away, and I don´t see a s___ .

Second, I stil do not have basestation, only HMD. If it goes to sleep there is no way to wake it again, except with pitool restart. And that kills Steam VR, and my game also. Do you have that problem?
PS: 1080Ti, 8700k, Pitool ss1.0, no reprojection, Steam VR video ss1.00, Steam VR application setting for Il-2 ss0.5 (result is almost native resolution, slightly bigger) , 3dMigoto; the game plays 45-90 fps, spotting with 3dMigoto only, I like it a lot

[blitze]

Welcome

 

 

 

 

Too the Dark Side. ?

 

Ok, Sun Halo, do you have HDR on in your Il2 Graphics Settings?  I do but in startup.cfg I turn Bloom to 0.

3Dmigoto though should help you with that.

 

What settings do you have PiTool HMD Backlight Brightness?

I use normal for the 8K but 5K+ has different panels so others with that headset might be of more help.  I do set Il2 brightness to 0.7 in startup.cfg if I use Balanced or above Il2 graphic setting.

 

Enjoy.

 

p.s. try bumping PiTool Render to 1.25 with same SteamVR settings and see how it goes.  On Normal FOV you should get good results with your setup.

Edited August 29, 2019 by blitze
additional brain fart

[SCG_Fenris_Wolf]

4 hours ago, Brzi_Joe said:

Hello Plimax users, I went to the dark side also  It is 5k+

 Can you tell me, what is with sun halo? With pimax I practicaly do not see anything if sun is anywhere on my screens. With a Oculus Rift before I could just turn my head a little bit, and I woud see again. Now sun halo is huuuuuge, can not turn my head away, and I don´t see a s___ .

Second, I stil do not have basestation, only HMD. If it goes to sleep there is no way to wake it again, except with pitool restart. And that kills Steam VR, and my game also. Do you have that problem?
PS: 1080Ti, 8700k, Pitool ss1.0, no reprojection, Steam VR video ss1.00, Steam VR application setting for Il-2 ss0.5 (result is almost native resolution, slightly bigger) , 3dMigoto; the game plays 45-90 fps, spotting with 3dMigoto only, I like it a lot

Welcome to the dark side! Check your six easily, no more neck pain, travel around the universe with your eyes and not just your neck! 170° vs the Index' puny 115°, and higher resolution harhar! Prepare for Index fanboy-hatemail ?

 

 

Various topics in this post, let's see:

 

Giant Sun halo: You can upvote the bugreport on it here

Also, as blitze said, it's good to disable bloom. This can only be done by editing the startup.cfg file in IL-2's data folder. Find Bloom and set it to 0. Putting gamma to 0.7 helps too, until there's an official fix.

Sleep mode: You have enabled "go idle when headset is not in use", it's found in the settings in SteamVR. You need to disable it. Also disable "fade to grey when idle", or something called in a similar fashion. I don't remember the precise designations but you'll find it

P.S. I have my Hz set to 64Hz and can run that 99% of the time now. As both fps and screens' Hz align, the image is butter smooth even without reprojection.

Edited August 29, 2019 by SCG_Fenris_Wolf

[TCW_Brzi_Joe]

Well thank you father, and father

 

Bloom and HDR are always disabled for my vr. Gamma is 0.7. Pitool 1.25 looks great, but kills my pc. Also I tried 64Hz, and that is no-no for my brain. I tried it on Berloga only, with many planes, but I just can't tolerate that. On 90Hz I got only sometimes downs to 45Hz, and that is for me more or less ok. 

I am happy with my low (native) resolution settings. It is easier to see plane on distance, and for identification there is 3dMigoto.

Just that sun halo,  @SCG_Fenris_Wolf you described that problem good. I upvoted that.

 

Pitool and brightnes; I use "normal" and 0 sliders, as that tool sometimes shift my brightnes sliders (usually left one sometimes goes to -5 or so, with no reason, and it goes back there if I change it. If I set it to "+0", it is constantly "0", no unexpected changes then. As I want to fly, and not to be 2 months without HMD, I just let it on default settings (0). That works.

EDIT: This is probbably connected with my Pimax does not want to wake up...

 

Stem vr disabling sleep - I just did it, thx.

 

A few days with Pimax, and I am so get used to it, as it was my old Rift. It is somehow strange with no more wooows, just flying 

Edited August 30, 2019 by Brzi_Joe

[TWHYata_PL]

mhm RMA that unit. Just checked, I dont have your issue . It's visible on screen during gameplay or expirence?