Bugs & Issues Reporting

[BNP]

I don’t have that many installed and it just rode past 22gb memory showing no sign of stopping

[SweViver]

By the way guys, when new bugs are found ,could you please create new threads in the Bugs category instead of replying to other topics? It will be easier to backtrack everything this way

Thanks

[SweViver]

@NoamLoop

setting quality to 2 (Overkill) and then clicking the 8kX render mode immediately applies the settings without any dialog or auto-reset countdown. The UI cannot be controlled anymore after that, per-eye images aren’t rendered correctly anymore, tracking is just jumping around. Had to reset quality and toggle render mode in PiTool to get it back to normal. Imho for all changes that might lead to an inoperable UI it would be better to have a dialog with an acknowledge button. And to revert back to the last safe settings automatically after a few seconds in case the button isn’t pressed.

Hmm, I havent been able to replicate this issue. It sounds like some error happened right before. The idea is that whenever any settings are supposed to be changed that requires a HMD reboot, the popup should warn about it, and ask for confirmation. If you press cancel, no changes are made.

Could you please try with version 0.20 and send the debug log? (the log is way more detailed now in the new version).

@NoamLoop

When setting a custom FoV in a profile (e.g.small) and then one saves, clicks on “apply” (so the default gets overwritten with the settings of that profile), then changes the defaults again and then goes into the profile, then the settings in the profile also changed to the values of the defaults. This is unexpected, I would have expected the profile to stay as it was.

I think I have to clarify this, as the profile management works slightly different from PiTool after all:
Profiles are loaded as-is upon start. You can load them, save and apply:

• Load Profile: simply loads the profile settings to the UI, so you see what settings the profile contains
• Save Profile: Saves the settings to the *.json profile, without applying anything to the HMD
• Apply Profile: Applies the profile settings to the HMD. Also, the settings, whenever changed or not from default, are set as active values for the current session. Which means these values are sent to the headset to be used. Meanwhile, the settings are also temporary “added” to the profile, but not saved to the file until you press Save. Which means, the active profile will show the new settings for that profile everywhere (Settings/Advanced Settings Image Adjustments/Profiles), unless you press “Load” on the same profile again, or unless you load another profile. This is simply to show that the current profile and its settings are currently used.
  There are no real “default” settings provided yet as the Default buttons are not active (and I temporary removed them in this version), unless you create a new profile, which has default values (same as PiTool generates when new profile is created).

I hope you get the point hehe, it might sound a little complex and confusing at first…

@NoamLoop

Two important options are currently missing in profiles: setting the render mode and quality (supersampling). E.g. for table tennis I want upscale, for most other things native. And e.g. for Redout upscale and additionally some level of subsampling (SS < 1), which helps with frame rates.

The problem is that, currently PiTool doesnt allow changing more than 1 HMD setting at a time, and HMD Settings (refresh rate, render mode, backlight) cannot be fixed with the other settings (fov, render quality etc). This is the reason why refreshrate/backlight and render mode isnt added to the profiles. As they simply cant be executed at once, and especially not upon starting a game. Ive asked the PiTool engineers to fix this, and hopefully they will soon…

Regarding SS; the supersampling values (for any SteamVR game) are available in the SteamVR Optimization profile, which each imported SteamVR game already has at first startup. So simply load the SteamVR profile for table tennis, adjust the supersampling etc and save profile (under Advanced->Manual SteamVR Optimization). Next time you start the game, the supersampling will be automatically applied to SteamVR, right before game launches.

@NoamLoop

When quitting SteamVR games I end up in the “empty coordinate system room” now. I have to click the system button and then go to “leave VR” to go back to the Pimax Experience. It would be better to return to the launcher the game was started from after exiting the game (either Pimax Experience or Steam Home)

Yes, this is because there is no way to automatically exit SteamVR when a game is quitted. Its simply out of our control. When you have played your game and feel to go back to VR Experience, you need to Quit SteamVR (which you can do with one click in the SteamVR Dashboard, all in VR).

@NoamLoop

when changing render mode, the frequencies listed are still the ones from the previously active mode (so if I switch from native to upscaling then it still offers 75 Hz as frequency. This only changes after pressing apply)

Thats because the render mode or refreshrate isnt applied until you click OK on the popup and the HMD reboots. As I said, only one parameter of the HMD settings can be applied at one reboot, so there is no way you can with one click go from native->upscale and in advance chose the refreshrate for that mode. You need to first enter upscale mode, and then change refreshrate. Its basically the same way when using PiTool, but the difference is that PiTool doesnt give you any prompt, but instantly does the refreshrate change. Its really not optimal as it is right now, but Im trying to adopt to the current limitations of PiTool

@NoamLoop

The circle line around the question mark is too thin and flimmers from aliasing

I fixed these icons in 0.19 and 0.20 already Should be better and less aliasing now!

@NoamLoop

It might be better to position the UI relative to the view the user has when entering the application instead of relative to the configured roomscale position. Or at least a prominent “reposition” button that moves the UI so one can see it optimally from the current position and orientation.

FIxed that in 0.20, but its working so-so, because the SteamVR SDK doesnt let me do it instantly on boot without a delay. So currently there is a 2 second delay before recenter is done. Also, when tracking is not found, the recenter never gets executed upon start or VR Exprience.

The only solution for now is to press Thumbstick/Touchpad down and recenter. I will see if I can tweak this somehow…

@NoamLoop

Most buttons at the bottom (IPD wizard etc.) don’t do anything yet, it might be better not to show these (or a “coming soon” hover text instead of just not reacting)

Yeah, these buttons are not active yet. Will try to add some information about it in the UI.

@NoamLoop

In the per-game screen where one can start the game, set the profile to use etc. it would be handy to have a shortcut button that jumps to editing that profile with one click (and optimally it could jump back to the game screen once the settings were saved). In case of SteamVR games a shortcut to the SteamVR per-game settings might also be convenient, if technically possible (these are still applied, right?)

Yep, I will add this to some of the next versions!

@NoamLoop

Not sure, are the gpuSpeed settings overwritten each time Pimax Experience starts? Or only when clicking the “Apply Optimizations” button? At least having an option to automatically run this at each start might be handy, as it’s the first thing that starts when switching on the headset anyways.

Yes if you have chosen to have SteamVR profiles to automatically apply upon game start (in Profiles->Settings), then yes all 10 gpuSpeed values are always overwritten to the values set in your SteamVR Optimization profile that is assigned to the game.
Check the Profiles->Settings for more options if you want to have it automated or not. On default, its all automated on each game start.

@NoamLoop

Probably just beta artifacts:

• 261 is recognized as newer version
• pi_server is giving an “unknown manufacturer” warning (still works when acknowledged)

Yep, its because this PiTool version is not official. Its still the latest available, so just ignore the update.
Regarding the unknown manufacturer, that sounds weird… lemme look into this!

[Tharg]

I had a small issue with the scroll bars in the interface. If you click / drag and move the pointer from them to the left, away from the scroll bar itself, slightly weird stuff happens.

With most menus everything goes back to normal after releasing the trigger. But the menu to the right stays ‘messed up’ when the trigger is released.

[SweViver]

@Tharg Yep, Im still waiting for a coder I talked to, to help me with this. The input event handler-system is basically built from scratch by two scripts… my own and one individual coder who is willing to help me out to solve this. I have spent too many days o that haha, better wait until he fixes this. But I fully agree its an annoying bug!

[DrWilken]

Did You notice this guy on the request thread?

https://community.openmr.ai/t/pimax-vr-experience-weekend-private-beta-testers-request/30099/39?u=drwilken

[SweViver]

Yes, I will add more people tonight when I have solved the code here and released a 0.22 Beta which should be more stable for everyone, without memory leaks and stuff.

[DrWilken]

I mentioned it because he’s apparently a Unity developer

It’s always nice to have someone to spar with

[SweViver]

Thats awesome! Added now

[NoamLoop]

Have retested stuff with 0.22 now. Quite an improvement, particularly speed wise!

@SweViver

@NoamLoop

setting quality to 2 (Overkill) and then clicking the 8kX render mode immediately applies the settings without any dialog or auto-reset countdown. The UI cannot be controlled anymore after that, per-eye images aren’t rendered correctly anymore, tracking is just jumping around. Had to reset quality and toggle render mode in PiTool to get it back to normal. Imho for all changes that might lead to an inoperable UI it would be better to have a dialog with an acknowledge button. And to revert back to the last safe settings automatically after a few seconds in case the button isn’t pressed.

Hmm, I havent been able to replicate this issue. It sounds like some error happened right before. The idea is that whenever any settings are supposed to be changed that requires a HMD reboot, the popup should warn about it, and ask for confirmation. If you press cancel, no changes are made.

Could you please try with version 0.20 and send the debug log? (the log is way more detailed now in the new version).

Couldn’t reproduce the issue with 0.22. Good!

@SweViver

@NoamLoop

when changing render mode, the frequencies listed are still the ones from the previously active mode (so if I switch from native to upscaling then it still offers 75 Hz as frequency. This only changes after pressing apply)

Thats because the render mode or refreshrate isnt applied until you click OK on the popup and the HMD reboots. As I said, only one parameter of the HMD settings can be applied at one reboot, so there is no way you can with one click go from native->upscale and in advance chose the refreshrate for that mode. You need to first enter upscale mode, and then change refreshrate. Its basically the same way when using PiTool, but the difference is that PiTool doesnt give you any prompt, but instantly does the refreshrate change. Its really not optimal as it is right now, but Im trying to adopt to the current limitations of PiTool

What the PiTool does imho better is that it shows the frequencies for upscale/native as soon as one clicks on upscale/native (before applying it). So one can click to upscale, then select the desired frequency, then click apply. In PE one first has to click to upscale, then apply (+ reboot), then go to advanced settings again and set the frequency.
Currently not a problem because the 8kX firmware only offers one frequency for native and upscale each anyways - but this will likely/hopefully change.

@SweViver

@NoamLoop

The circle line around the question mark is too thin and flimmers from aliasing

I fixed these icons in 0.19 and 0.20 already Should be better and less aliasing now!

Thanks, looks good now!

@SweViver

@NoamLoop

It might be better to position the UI relative to the view the user has when entering the application instead of relative to the configured roomscale position. Or at least a prominent “reposition” button that moves the UI so one can see it optimally from the current position and orientation.

FIxed that in 0.20, but its working so-so, because the SteamVR SDK doesnt let me do it instantly on boot without a delay. So currently there is a 2 second delay before recenter is done. Also, when tracking is not found, the recenter never gets executed upon start or VR Exprience.

The only solution for now is to press Thumbstick/Touchpad down and recenter. I will see if I can tweak this somehow…

For some reason the first time the UI is visible after an HMD restart it looks good regarding position in small UI mode. After switching to upscale and back to native the UI is too high and close for my taste in sitting position though. Pressing the thumbstick doesn’t help here, this only changes view direction, not distance. To get it more comfortable, I can switch to large UI, where the distance is a little higher - or switch the HMD off and on again, then the small UI is shown in comfortable distance again. Would be great if we would have the option to change height and distance of the UI!