and there is also an OpenVR Benchmark, it also shows how much the screen area is available for viewing, as I understand this figure is relevant for one screen, and only risa2000 tools can read everything together, taking into account the overlap.
5k+ normal possibly parallel projections
samsung O+
Definitely seems need more cross testing. But so far verdict is it’s not 140 wide.
The Openvr Bench is cool showing rendered ppd
Index gives that perfect window. For InDeath when going for a high score i think i prefer small mode on the Artisan or using the Index. Other games the Artisan gives me more or a “wow” factor. I used ROV steam environment where you stand in a spot and move the paddles. It didn’t feel very exact at all but a little above 120 FoV. I’ll use Risa’s tool tonight. Is there a quick link for it?
I live in EU and I’ve been waiting nearly 4 months and they keep telling me it’ll arrive soon with no tracking number or any other information…
From my observations, made on Oculus Quest, and CV1, the geometry data reported by the native Oculus runtime and SteamVR are basically the same. The only difference is that with Oculus runtime, the tool reports also the hidden area mask (HAM) correctly (compared to SteamVR which currently does not show HAM for Oculus headsets in the tool). Oculus runtime also reports some additional data as the display resolution and pixel density at the view center.
I believe there might be different firmware revs. (or hardware revs.) in circulation. From the preliminary data @16BIT recorded some time ago, it seems that Pimax changes the FOV depending on the refresh rate. So it might as well be true that “Normal” means 120° @120Hz and it means 130, 140 or whatever Pimax set it for 90Hz. The same happens on Pimax 5k+ already.
So far I was not able to get consistent data from one Artisan headset (which is at the same time working without any problem), to make any definitive conclusion about the rendered geometry.
so to end conclusion @Djonko Pimax did it and we should all have a party to celebrate right?
@16BIT wow that’s very weird. I’m starting to think you’re then either on a different FW or that there already exist different hardware revisions of the Artisan. On ‘normal’ I always get 121 degrees horizontal, no matter what refresh rate I choose. I always restart steamvr after changes. Render resolution I have set to 1.0x and left it there. I tried PP on/off, didnt change anything neither in terms of FOV.
Here’s the output from Risa’s tool:
72hz, normal:
hmdq version 2.0.1 - collecting VR headsets characteristics in no time
Time stamp: 2020-05-17 08:32:25
hmdq version: 2.0.1
Output version: 5
OS version: 10.0.18362.778
... Subsystem: OpenVR ...
OpenVR runtime path: C:\Program Files (x86)\Steam\steamapps\common\SteamVR
OpenVR runtime version: 1.11.12
Device enumeration:
Found dev: id=0, class=1, name=HMD
Found dev: id=1, class=4, name=TrackingReference
Found dev: id=2, class=4, name=TrackingReference
Found dev: id=3, class=4, name=TrackingReference
[0:HMD]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Pimax Artisan"
1002 : SerialNumber = "36000121edit"
1003 : RenderModelName = "generic_hmd"
1005 : ManufacturerName = "Pimax VR, Inc."
2002 : DisplayFrequency = 71.99986267089844
[1:TrackingReference]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Valve SR Imp"
1002 : SerialNumber = "LHB-4B2D84D2"
1003 : RenderModelName = "lh_basestation_valve_gen2"
1005 : ManufacturerName = "Valve Corporation"
1006 : TrackingFirmwareVersion = "3008"
1007 : HardwareRevision = "0x0900000f"
4006 : ModeLabel = "3"
[2:TrackingReference]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Valve SR Imp"
1002 : SerialNumber = "LHB-8C84CA09"
1003 : RenderModelName = "lh_basestation_valve_gen2"
1005 : ManufacturerName = "Valve Corporation"
1006 : TrackingFirmwareVersion = "3008"
1007 : HardwareRevision = "0x0900000f"
4006 : ModeLabel = "2"
[3:TrackingReference]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Valve SR"
1002 : SerialNumber = "LHB-2E7C6500"
1003 : RenderModelName = "lh_basestation_valve_gen2"
1005 : ManufacturerName = "Valve Corporation"
1006 : TrackingFirmwareVersion = "3008"
1007 : HardwareRevision = "0x0900000e"
4006 : ModeLabel = "1"
Recommended render target size: {3496, 4056}
Left eye HAM mesh:
optimized vertices: 48, n-gons: 4
mesh area: 19.11 %
Left eye head FOV:
left: -60.80 deg
right: 43.39 deg
bottom: -52.65 deg
top: 52.65 deg
horiz.: 104.19 deg
vert.: 105.29 deg
Right eye HAM mesh:
optimized vertices: 48, n-gons: 4
mesh area: 19.11 %
Right eye head FOV:
left: -43.39 deg
right: 60.80 deg
bottom: -52.65 deg
top: 52.65 deg
horiz.: 104.19 deg
vert.: 105.29 deg
Total FOV:
horizontal: 121.60 deg
vertical: 105.29 deg
diagonal: 124.47 deg
overlap: 86.79 deg
View geometry:
left view rotation: 0.0 deg
right view rotation: 0.0 deg
reported IPD: 69.2 mm90 normal:
hmdq version 2.0.1 - collecting VR headsets characteristics in no time
Time stamp: 2020-05-17 08:35:29
hmdq version: 2.0.1
Output version: 5
OS version: 10.0.18362.778
... Subsystem: OpenVR ...
OpenVR runtime path: C:\Program Files (x86)\Steam\steamapps\common\SteamVR
OpenVR runtime version: 1.11.12
Device enumeration:
Found dev: id=0, class=1, name=HMD
Found dev: id=1, class=4, name=TrackingReference
Found dev: id=2, class=4, name=TrackingReference
Found dev: id=3, class=4, name=TrackingReference
[0:HMD]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Pimax Artisan"
1002 : SerialNumber = "36000121edit"
1003 : RenderModelName = "generic_hmd"
1005 : ManufacturerName = "Pimax VR, Inc."
2002 : DisplayFrequency = 89.99810028076172
[1:TrackingReference]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Valve SR Imp"
1002 : SerialNumber = "LHB-4B2D84D2"
1003 : RenderModelName = "lh_basestation_valve_gen2"
1005 : ManufacturerName = "Valve Corporation"
1006 : TrackingFirmwareVersion = "3008"
1007 : HardwareRevision = "0x0900000f"
4006 : ModeLabel = "3"
[2:TrackingReference]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Valve SR Imp"
1002 : SerialNumber = "LHB-8C84CA09"
1003 : RenderModelName = "lh_basestation_valve_gen2"
1005 : ManufacturerName = "Valve Corporation"
1006 : TrackingFirmwareVersion = "3008"
1007 : HardwareRevision = "0x0900000f"
4006 : ModeLabel = "2"
[3:TrackingReference]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Valve SR"
1002 : SerialNumber = "LHB-2E7C6500"
1003 : RenderModelName = "lh_basestation_valve_gen2"
1005 : ManufacturerName = "Valve Corporation"
1006 : TrackingFirmwareVersion = "3008"
1007 : HardwareRevision = "0x0900000e"
4006 : ModeLabel = "1"
Recommended render target size: {3496, 4056}
Left eye HAM mesh:
optimized vertices: 48, n-gons: 4
mesh area: 19.11 %
Left eye head FOV:
left: -60.80 deg
right: 43.39 deg
bottom: -52.65 deg
top: 52.65 deg
horiz.: 104.19 deg
vert.: 105.29 deg
Right eye HAM mesh:
optimized vertices: 48, n-gons: 4
mesh area: 19.11 %
Right eye head FOV:
left: -43.39 deg
right: 60.80 deg
bottom: -52.65 deg
top: 52.65 deg
horiz.: 104.19 deg
vert.: 105.29 deg
Total FOV:
horizontal: 121.60 deg
vertical: 105.29 deg
diagonal: 124.47 deg
overlap: 86.79 deg
View geometry:
left view rotation: 0.0 deg
right view rotation: 0.0 deg
reported IPD: 69.2 mm
120 normal:
hmdq version 2.0.1 - collecting VR headsets characteristics in no time
Time stamp: 2020-05-17 08:37:37
hmdq version: 2.0.1
Output version: 5
OS version: 10.0.18362.778
... Subsystem: OpenVR ...
OpenVR runtime path: C:\Program Files (x86)\Steam\steamapps\common\SteamVR
OpenVR runtime version: 1.11.12
Device enumeration:
Found dev: id=0, class=1, name=HMD
Found dev: id=1, class=4, name=TrackingReference
Found dev: id=2, class=4, name=TrackingReference
Found dev: id=3, class=4, name=TrackingReference
[0:HMD]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Pimax Artisan"
1002 : SerialNumber = "36000121edit"
1003 : RenderModelName = "generic_hmd"
1005 : ManufacturerName = "Pimax VR, Inc."
2002 : DisplayFrequency = 119.9999008178711
[1:TrackingReference]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Valve SR"
1002 : SerialNumber = "LHB-2E7C6500"
1003 : RenderModelName = "lh_basestation_valve_gen2"
1005 : ManufacturerName = "Valve Corporation"
1006 : TrackingFirmwareVersion = ""
1007 : HardwareRevision = "0x0900000e"
4006 : ModeLabel = "1"
[2:TrackingReference]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Valve SR Imp"
1002 : SerialNumber = "LHB-4B2D84D2"
1003 : RenderModelName = "lh_basestation_valve_gen2"
1005 : ManufacturerName = "Valve Corporation"
1006 : TrackingFirmwareVersion = ""
1007 : HardwareRevision = "0x0900000f"
4006 : ModeLabel = "3"
[3:TrackingReference]
1000 : TrackingSystemName = "aapvr"
1001 : ModelNumber = "Valve SR Imp"
1002 : SerialNumber = "LHB-8C84CA09"
1003 : RenderModelName = "lh_basestation_valve_gen2"
1005 : ManufacturerName = "Valve Corporation"
1006 : TrackingFirmwareVersion = ""
1007 : HardwareRevision = "0x0900000f"
4006 : ModeLabel = "2"
Recommended render target size: {3496, 4056}
Left eye HAM mesh:
optimized vertices: 48, n-gons: 4
mesh area: 19.11 %
Left eye head FOV:
left: -60.80 deg
right: 43.39 deg
bottom: -52.65 deg
top: 52.65 deg
horiz.: 104.19 deg
vert.: 105.29 deg
Right eye HAM mesh:
optimized vertices: 48, n-gons: 4
mesh area: 19.11 %
Right eye head FOV:
left: -43.39 deg
right: 60.80 deg
bottom: -52.65 deg
top: 52.65 deg
horiz.: 104.19 deg
vert.: 105.29 deg
Total FOV:
horizontal: 121.60 deg
vertical: 105.29 deg
diagonal: 124.47 deg
overlap: 86.79 deg
View geometry:
left view rotation: 0.0 deg
right view rotation: 0.0 deg
reported IPD: 69.2 mmOn ‘small’ it reports 101 degrees horizontal. These FoV’s were confirmed in ROV’s tool to be correct.
My FW:
Either way this amount of deviation imho is not good on what is suppose to be core specs. With differences in FoV based on Refresh they should specify the Accurate Horizontal sizing as this will create a huge mess now that there are enough tools out there to obtain FoV data.
I agree it is confusing, especially if the name of the FOV setting remains the same (Normal@90 vs Normal@120). The best way to avoid all those issues would be if Pimax simply show the rendered FOV in PiTool and how it eventually changes according to the set refresh rate.
@16BIT can you post your FW version and the first numbers of your serial ?
Well keep in mind. I believe you said you have the blue housing opposed to black; so should be a different hw rev for sure.
Unfortunately this suggests there either still adjusting the Hardware or maybe the canting might vary a bit and they used the incorrect lens/panel module.
Yeah IF there are different hardware revisions, then I surely have the latest. So that means they’re now selling Artisan’s with 120 degrees FoV horizontally while they advertise 140 degrees horizontally. That’s just really really bad.
I think some 8k+ have different panels as well, otherwise why did the 110hz fist alpha firmware only work on some 8k+ devices but not others? Also depending on serial number …
It wouldn’t surprise me if Pimax just frankenstein different parts and call it the same sku at this point, but for artisan the fov differentiation could be caused by software. Id love to know too, at least they’re making artisans with the blue housing now.
For sure there are different panels in the 5k+, the 202 FW version has an older panel with black dots, the 203 version solved that black dot issue
There is also a reddit topic where the fellow is just using I think a VD thing to test and he gets around 125 if I recall. It could be pimax is doing what gpu vendors often do and is speccing the theoretical max if everything is within specs ideally. However they should at least disclaim theoretical max. As the mech ipd adjustment seems to have a variance of typically +/- 1.0mm.
When you say firmware version you mean product model number at the bottom of headset, or the actual firmware read on the inside of pitool? I think they are different.
Whats the product revision number of your artisan @djonko? I just saw you post pitool and firmware version
first part of the serial is in the output from risa’s tool above. Pimax seems to lock important HW revisions like panel versions, to that first part of the serial. So “360” in my case. I wonder if that’s the same for @16bit
Manufactures typically do this anyways with hw revisions. Ie first xbox 360 had custom gpu which was ditched due to red rings for a custom nvidia.
Asus has 2 versions of the sabertooth 990fx board. You have look up to know which is which. The first release was an attempt to “frankenstein” PciX v3.0 x16 in. It failed horribly and had really terribke performance. A later revision quietly changed it to 2.0