What is Latest PIMAX Beta and Installation Procedure???

[fiddlinjim]

I use the PIMAX 5K+ with a 1080Ti GPU.

My current Pitool Beta Version is V1.0.1.180 and Firmware V2.1.255.212 and whenever I check for the latest versions

Pitool always states no updates are available and I am sure this is not the case.

I have Win 10 and Nvidea up to date with their latest versions.

My question is what is the latest Pitool Beta and Firmware versions and exactly how do I install them??

[SCG_Fenris_Wolf]

PiTool is half a dozen versions newer, and the Firmware as well.

 

Latest PiTool is .258 https://community.openmr.ai/t/pitool-1-0-1-258-mar-14-2020/26390

 

and Firmware https://community.openmr.ai/t/5k-serial-203-204-beta-firmwareu/26430  for SN 203 and 204.

 

If your serial number begins with 202 this is not for your 5k+.

Edited March 27, 2020 by SCG_Fenris_Wolf

[Blitzen]

I've got a 203 serial & have downloaded both the new Pitool exe & the Firmware exe .My question is what is the difference & is there any particular order in which they must be installed"

BTW Thanks for the latest info!

[SCG_Fenris_Wolf]

Update to my previous post: The .258 FW I do not recommend, as I'm getting low gpu utilization using an RTX2080ti, as I cannot use the catalyst setting with it. I've heard GTX1080ti users were fine, you need to see for yourself.

 

For RTX2080ti users I recommend .253, which has good performance: 254(a) has a memory leak, and .258 bad performance (15-20fps less).?

 

 

Just follow my sticky thread, the update process to the current latest stable and best performing combination is described in there, in the first spoiler - always:

 

Edited March 27, 2020 by SCG_Fenris_Wolf

[Blitzen]

3 hours ago, SCG_Fenris_Wolf said:

Update to my previous post: The .258 FW I do not recommend, as I'm getting low gpu utilization using an RTX2080ti, as I cannot use the catalyst setting with it. I've heard GTX1080ti users were fine, you need to see for yourself.

 

For RTX2080ti users I recommend .253, which has good performance: 254(a) has a memory leak, and .258 bad performance (15-20fps less).?

 

 

Just follow my sticky thread, the update process to the current latest stable and best performing combination is described in there, in the first spoiler - always:

 

What about for us ancients still stuck with 1080 cards...which Ptool would you recommend & if its an older one where to find it?I'm ready for a completely fresh install of Ptool after removing the older one from my PC..

( Again I am curious about the Firmware download.Is it any use while re-installing the recommended version of the Ptool? Thanks again.)

[TCW_Brzi_Joe]

I am on 1080ti with Pitool 253. The latest 258 was bad for me. Search in pimax/openMR forum, you can find them all. 

But one thing, if you want to update, you must be skilled with computers. At least to be able to understand all steps, and reproduce without mistakes. Also I had unexpected problem when upgrading HMD firmware (yes, you need pitool and firmware), in my case HMD was bricked and I had to unplug hdmi cable on HMD side, and replug it again. That was not easy. Fenris_Wolf helped me, but in one moment I was lost. 

Just be aware that anything is possible.

 

And if you are not pc skilled, or you never root your phone, and your Pimax works on pitool 180, then better do not start. 

 

Ps: firmware upgrade is similar like phone root-ing, if you are familiar with that

[SCG_Fenris_Wolf]

8 hours ago, Blitzen said:

What about for us ancients still stuck with 1080 cards...which Ptool would you recommend & if its an older one where to find it?I'm ready for a completely fresh install of Ptool after removing the older one from my PC..

( Again I am curious about the Firmware download.Is it any use while re-installing the recommended version of the Ptool? Thanks again.)

As Brzi_Joe also said, same PiTool I recommended: 253.

 

But I don't recommend you to upgrade the Firmware, as you need to be very experienced for that. No offence intended, just protection from bricking your own headset. Better just stick to the PiTools and use the auto-upgrade of the Firmware, if any. 

 

P.S. Well you can do it, but you need to follow the instructions very carefully. Everything is linked to in my spoiler. For Firmware upgrade you need all three things mentioned: The DFUupgrade software, the Firmware itself, and the video by SweViver that explains the process in detail, with the timestamp where it starts. If you brick your headset, you repeat the process from the start (but correctly the next time) and it'll get to life again. But you must be very precise, no mistakes, or need to repeat the process until it gets right.

 

Edit: Removed some German bluntness and made it friendlier to the English recipient ?

Edited March 28, 2020 by SCG_Fenris_Wolf

[Blitzen]

On 3/27/2020 at 1:43 PM, SCG_Fenris_Wolf said:

As Brzi_Joe also said, same PiTool I recommended: 253.

 

But I don't recommend you to upgrade the Firmware, as you need to be very experienced for that. No offence intended, just protection from bricking your own headset. Better just stick to the PiTools and use the auto-upgrade of the Firmware, if any. 

 

P.S. Well you can do it, but you need to follow the instructions very carefully. Everything is linked to in my spoiler. For Firmware upgrade you need all three things mentioned: The DFUupgrade software, the Firmware itself, and the video by SweViver that explains the process in detail, with the timestamp where it starts. If you brick your headset, you repeat the process from the start (but correctly the next time) and it'll get to life again. But you must be very precise, no mistakes, or need to repeat the process until it gets right.

 

Edit: Removed some German bluntness and made it friendlier to the English recipient ?

Thanks ..Have done as you suggest & still quite happy with my Pimax 5K thanks to you. Will wait on upgrading to the next VR improvement from Pimax until you recommend it & when I can afford it!

[Madov]

Hello Pimax fans

 

I thought I would add some findings on the recent PiTool #258 with Firmware #255. After some tweaking and testing I now run IL-2 with render quality of 2 and with a massive 7642 x 4708 resolution per eye as recorded within SteamVR settings. I run Large FOV at 64 Hz with Smart Smoothing enabled and FFR closed. I have graphics at Ultra with everything maxed out in the sim which runs at 32 fps solid, meaning that 64 Hz is maintained. The result is a smooth flying experience with incredible cockpit visuals, all dials and instruments clearly legible as is the smallest writing.

Users are struggling with PiTool #258 but it's the best of class for me personally. I have the GPU Catalyst set to O, also Contrast at +2 and brightness at -2.

 

PiTool #253 gave good performance but I found that it wouldn't maintain Large FOV and always defaulted to Normal. Never has IL-2 looked so good in VR, now I just wish I could shoot  straight in the La-5, those ShVAK seem powerful but so difficult to get on target.

Edited March 31, 2020 by MADOV_VR

[SCG_Fenris_Wolf]

Hi Madov, 

 

if the sun flashes through the clouds with Smart Smoothing (ASW), or along the cockpit bars, I get artifacts in the picture. Often aircrafts also get to some kind of double vision.

 

I also experience latency in movement at 65Hz (5K+ SN204, so 65Hz not 64Hz for me). If I wobble around the headset, the world wobbles with it, at these low frequencies.

 

I'm also worrying about spotting aircraft at range like this. Effectively, such a high Supersampling value may cut your bubble of rendering aircrafts at range down. Instead of spotting something at 20km distance, it might just be much less than 10km before anything starts rendering this way. 

 

For the love of graphical quality, I'll check it out however. Personally for a competitive environment on servers like TAW though, I believe the trade-off due to the rendering distance may be too much.

[TCW_Brzi_Joe]

@MADOV_VR If you play single player that is ok.
But for multiplayer set asw off, and vertical resolution about 2304 (large fov is 3732*2304, Pitool 1.75, steam ss 0.25).

[Madov]

Hello Gents

 

I reckon that I am spotting at about the same distances as I was before to be honest and this is partially what started me tweaking and meddling. I use Smart Smoothing, always have with the Pimax, and I don't get any negative effects from it such as artifacts or the double vision that you mention. If I had those then I would disable that function for sure but enabling it gives me a great deal of headroom to play with as I find I fly very smooth, butter smooth as Sweviver would say, with the 64 Hz setting. I have SN 2036. I don't get the wobbling that you mention either at this low frequency.

 

I can see that if you're prioritising the competitive environment then the way you tweak is governed by that. I do fly on TAW but point scoring, stats etc is of no interest to me personally. This is all about the love  of flying these aircraft for  me, happy to have a one hour flight in the heavens without seeing an enemy aircraft. I do love formation and aerobatics though. I have this sim platform just where I want it, gorgeous cockpit and superb terrain detail, everything looks amazing and I find that I can discern much more detail on other aircraft as I approach them. As I only fly VR this was a problem, being more concerned with identification than strategical manoeuvreing, but I do find that recently I can decide what that thing is from greater distance. Which is nice.

 

What I love about the Pimax headsets is that they are so configurable and now that PiTool has gone open source we should see great things from it. I will definitely be getting the 8KX as my next gen HMD. Good times ahead I think.

 

Blue skies to you all !

[SCG_Fenris_Wolf]

They went open source? Today?

 

 

What's your pre-rendered framesetting in Nvidia's Settings?

Edited April 2, 2020 by SCG_Fenris_Wolf

[Madov]

Hello mate

 

Yes, it was some time  ago that it was announced that Pimax were releasing the SDK for PiTool. It was seen as a major step forward for a small company to allow their user base to improve the software and to develop it for their own purposes.

 

My memory is that I have pre-rendered frame setting at 3, this followed the advice of Sweviver who clarified a lot of things for the early Pimax users and helped the community to discover the hidden nuggets to improve the overall experience.

[blitze]

Finding the recent SteamVR Beta with PiTool .258 on the 8K at 64Hz = nice clarity and at distance too.

 

Can't wait for the 8K-X - running 1.25 Large FOV with SteamVR Vid 50% and App 50% which is the magic 25% people have recommended.

 

Nothing like being in the middle of a fight and you just want to pause and take in the image of the plane you're fighting as it looks so good.?

[Madov]

Sounds like you've nailed it blitze, everyone's system is different and different systems react differently to different HMDs but it is so  gratifying when you find the sweetspot.

[SCG_Fenris_Wolf]

7 hours ago, MADOV_VR said:

Hello mate

 

Yes, it was some time  ago that it was announced that Pimax were releasing the SDK for PiTool. It was seen as a major step forward for a small company to allow their user base to improve the software and to develop it for their own purposes.

 

My memory is that I have pre-rendered frame setting at 3, this followed the advice of Sweviver who clarified a lot of things for the early Pimax users and helped the community to discover the hidden nuggets to improve the overall experience.

They never went opensource though

 

What's your PiTool version, Firmware, and serial number? 

3 hours ago, blitze said:

Finding the recent SteamVR Beta with PiTool .258 on the 8K at 64Hz = nice clarity and at distance too.

 

Can't wait for the 8K-X - running 1.25 Large FOV with SteamVR Vid 50% and App 50% which is the magic 25% people have recommended.

 

Nothing like being in the middle of a fight and you just want to pause and take in the image of the plane you're fighting as it looks so good.?

Have you checked GPU utilization and compared FPS of 258 to 253? Most users report a loss of 10-15fps, me included

Edited April 2, 2020 by SCG_Fenris_Wolf

[SCG_Fenris_Wolf]

10 hours ago, Brzi_Joe said:

@MADOV_VR If you play single player that is ok.
But for multiplayer set asw off, and vertical resolution about 2304 (large fov is 3732*2304, Pitool 1.75, steam ss 0.25).

SN203? I get 3172x2104 with large FOV, PiTool 2.00 , steam ss 0.25 , using a 5K+ SN204

 

?

Edited April 2, 2020 by SCG_Fenris_Wolf

[TCW_Brzi_Joe]

lol @SCG_Fenris_Wolf , I tried to get your results, but no way with your settings I tried exactly the same, but I have more pixels, booth with and without hidden area mask.

 

Yes, my pimax is SN203. 

without hidden area mask:

pimax ss1.50 = 3200*1972

pimax ss1.75 = 3732*2304

pimax ss2.00 = 4264*2632

[SCG_Fenris_Wolf]

I use Hidden Area Mask. I have not found a reason as to why to disable it - it just nerfs your performance (?). Anyway, I believe this difference is due to our headset having different screens. The SN204 has tighter screens with less hidden area. On the downside, they cannot show anything less than 90Hz, as that'll create input latency of the headset. World moves with you.

[TCW_Brzi_Joe]

Area mask take some of my view. After months without it, once I got it checked with new pitool; the difference was pretty visible, I had to go without it. 

Second reason is Lefuneste's turn view, I think glitching is less when hidden mask is disabled.

Edited April 3, 2020 by Brzi_Joe