DCS and Pimax

[darkman222]

Seated position is very easy. Just put one in the top right corner of your room and the second one at a lower position in the left corner behind you.But at all time at least one light house needs to have clear sight on you. You should not be able to get into a position where both lighthouses lose sight on you.

EDIT: DId you just say you have only 1 lighthouse? Then you should just put it at position where it can always see you. But I am not sure as I own two lighthouses for my Pimax

[ariyaner]

so the lighthouse must see me or the hmd all the time ?

because i wouldt like it to place the basestation on the upper right (45° from my pos.)

 

so when i check my 7-8 clock the basestation will maybe dont see the hmd - or just a part from it

 

how the communication works between hmd , basestation and pc ?

[darkman222]

It is a laser beam ( cone) which is shot in a wide angle out of the lighthouse. Very wide angle. I think, if the HMD loses sight it is not too bad for a quick amount of time as it compensates with the gyros, and starts tracking again, if the HMD sees the lighthouse again. For the controlers ( in case you have them too) I think if they arent seen, they lose tracking instantly

[Bouli306]

So are al you guys starting DCS through Pitool and wait for the annoying popups? If so what setting do Pitool and Steam VR have?

 

I am running a 2080Ti and I7-8700 but do not seem to be getting more FPS than 32 in Nevada.

[ariyaner]

if i launch dcs over pitool dcs is bugged and some moduls didnt work (fc3 for example)

 

your frames are limeted via ffr i think

 

i wouldt recomment to use parallel projetions only

all the other options didnt work very well in dcs i mean

fov has a big impact not only in fov also in a much higher resolution - thats why i use large fov

you can even see missles very good

[Bouli306]

Thanks, will try this tomorrow.

[Phantom88]

[Phantom88]

New Pitool Beta

https://forum.pimaxvr.com/t/new-pitool-1-0-1-197-is-available-now/23003

[gorzasty]

Does anyone have better performance with it? My P5k+ is RMA at the moment so I can't test it.

 

Wysłane z mojego SM-G960F przy użyciu Tapatalka

[Rosebud47]

Does anyone have better performance with it? My P5k+ is RMA at the moment so I can't test it.

 

Wysłane z mojego SM-G960F przy użyciu Tapatalka

 

Yeah, it´s fine, SteamVR shows a more appropiate resolution in normal FOV, but the 120Hz mode doesn´t work for me at the moment - doesn´t want to reduce the FOV anyway.

[Phantom88]

[dburne]

Ok that was a little difficult to watch...

[SneakyBastd]

Hi guys, quick question...

I just updated to latest piTool 1.0.1.1.97, it updated my firmware to 2.1.255.244. It's working.

Smart smoothing is on, which is good, but I can't see how to turn it off anymore (to check actual fps). There used to be a checkbox - but that's gone now.

I see a Motion Compensation option, but it only has "None". Any ideas?

Thanks.

[gorzasty]

Try different tabs? They offen change stuff between them in different versions.

 

Wysłane z mojego SM-G960F przy użyciu Tapatalka

[Rosebud47]

The Motion Compensation option in Pitool is only meant for Simpits with a motion system.

 

Try reinstalling Pitool, if problems appears. A good advise is to deactivate Windows AnitVirus protection for the Pitool reinstalling process.

[Shack]

can someone link me to the latest pitool update ?

[kreidel]

This is the link for the beta... use with caution.

https://forum.pimaxvr.com/t/new-pitool-1-0-1-197-beta-is-available-now/23003

[Shack]

 

I cant help to think of the Hanz and Franz SNL skit when hearing this guy's voice :megalol:

 

[Phantom88]

I cant help to think of the Hanz and Franz SNL skit when hearing this guy's voice :megalol:

 

:megalol::megalol::megalol:

[moespeeds]

I'm struggling to get the prescribed settings by -voight- on page 135 of this thread. What am I missing?

 

Pimax 5k Plus

 

Latest beta of PiTool installed as linked a few pages back. 1.0.1.197

Firmware v2.1.255.244

Steam VR 1.8.20

 

Render set at 1.0

Everything else off

Apply/save

 

Open Steam VR, close PiTool

Under tab Applications/DCS (DCS running) I see 1432x1176 at 100%

Under tab Video I see 1920x1580 at 36%, 3200x2632 at 100%

 

I used to use the profile.json file mod, but now when I open it there's just this in there:

(I did read that editing this is no longer needed with the latest Steam VR.)

 

{

"Pimax P2 5K Formal" : {

"color_brightness_0_rgb" : {

"x" : 0.01999999955296516,

"y" : 0.01999999955296516,

"z" : 0.01999999955296516

},

"color_brightness_1_rgb" : {

"x" : 0.01999999955296516,

"y" : 0.01999999955296516,

"z" : 0.01999999955296516

},

"lens_separation" : 0.085736483335495

},

"dbg_asw_enable" : 0,

"dbg_hidden_area_enable" : 0,

"enable_pvr_home" : 0,

"ipd" : 0.05995561182498932,

"pixels_per_display_pixel_rate" : 1

}

 

 

Any ideas?

Edited November 12, 2019 by moespeeds

[Rosebud47]

Hi moespeed,

 

didn´t look for long time into this. Things change, like SteamVR and Pitool by newer version more compatible to each other.

 

If you like to test with the settings, try adding the line:

 

"FOV_outer_adjust_degree" : -2.32

 

to the last section in the above noted profile.json and observe how it influences the given resolution in SteamVR under "Video". After editing, both, SteamVR and Pitool, should be restarted completely ( reboot the system ).

[moespeeds]

Ok thanks I'll try tonight. My goal here is to get steam vr to the native resolution, which is 2550x1440, then use dcs pd to increase clarity, right?

[Rosebud47]

Yes, that was my goal too, but not sure if it does counteract visual quality. Meanwhile not sure in the way, if the rendered pixel overhead could be reduced for the benefit of performance, but then the visual quality need to be balanced by supersampling for the cost of performance.

 

With the new Pitool version and firmware, they have also managed to reduce the rendered pixel overhead for the headset, which should result in a performance gain of approx 10%.

 

I, for me, decided to not touch the configuration files anymore and wait for Vulkan implementation in DCS to get better performance. It´s better to let the professionals do what is good for us.

[moespeeds]

I tried it, but no effect. Moving pitool render to 1.25 did give me less shimmer, but with what I think is "tearing"? If I move my head quickly, I get some stutter, and black artifacts on the edges of my vision.

 

I use the same scene to test, takeoff from Al Dhafra and fly over the city doing a lot of rolls and such to see how it feels. Frame rate in fraps is high 20s to low 30s, GPU frame times in the low 30s.

 

I did try cranking the brightness up in pitool, then running the gamma in DCS down, and that looks to help with the shimmering effect.

[Rosebud47]

Just had a quick look and it´s still working.

 

I´m sorry, moespeeds, but forgot to mention, that the profile.json file should be set to write protected after editing, so it won´t load the default settings after reboot.

 

So here some quick results:

In regular, I´ve set the resolution to 48% = 2668 x 2276 in SteamVR/Video override

Pitool normal FOV / render quality 1 ( or maybe 1.25, I have to look again, not sure atm :-) )

 

After editing the "FOV_outer_adjust_degree" : from default 10 to -2.32 ... setting write protection to the profile.json ... rebooting the system

SteamVr now shows a render resolution of 6108 x 2276 @ 48%, 3944 x 1468 @ 12%

 

I think with the new Pitool version some values changed and -2.32 is no longer the right value to get exactly the native display resolution. I´ll try later some more values, but would suggest to increase this value in small steps and observe the result in SteamVR ( need to be rebooted or shut down completely by windows application manager to have effect with fresh loading ).

 

Jesus, I want to leave this stuff, until my 8KX arrives in February next year :-)))

 

 

 

Edit:

 

with "FOV_outer_adjust_degree" : set to 1 resulted in a resolution of 28xx X 1468 @20% in SteamVR, which increased the performance a lot, but decreased the visual quality as well a lot

 

with "FOV_outer_adjust_degree" : set to 5 resulted in a resolution of 2588 x 1740 @28% ... very close to native 2560 x 1440 .. I guess some value between 3 and 4.5 will match the native resolution.

 

render quality in Pitool is set to 1 in my config.

 

Also it should be considered if it does make sense, if setting to native panel resolution, while having set the P5k+ to small or normal FOV instead of wide FOV.

Edited November 14, 2019 by - Voight -
some more testing results