!ktbltgjXqfcBPmbeky:matrix.org

general

1592 Members
41 Servers

Load older messages


SenderMessageTime
26 Jul 2024
@_discord_85950865113903104:ckie.devhypevhs the alternative to corectl if you REALLLLLLLY dont want it
sudo sh -c "echo '4' > /sys/class/drm/cardSOMENUMBER/device/pp_power_profile_mode"
21:43:50
@_discord_797861611637440553:ckie.devbabblebones#0 GPU will freeze if you touch overclock settings 21:43:58
@_discord_797861611637440553:ckie.devbabblebones#0 Which is what most likely happened 21:44:08
@_discord_331951461594431489:ckie.devlord0fdragons Nah... GPU froze when I just launched CoreCtrl... rofl 21:44:28
@_discord_797861611637440553:ckie.devbabblebones#0 Oh, wow 21:44:35
@_discord_331951461594431489:ckie.devlord0fdragons Hm... I've got /sys/class/drm/card0 and /sys/class/drm/card1 and both are amd-gpu driver... russian roulet 🙄 21:47:49
@_discord_797861611637440553:ckie.devbabblebones#0 Which one drives your VR? 21:48:06
@_discord_490390320098312192:ckie.devBluedotAster changed their display name from blue.aster#0 to BluedotAster.21:48:10
@_discord_490390320098312192:ckie.devBluedotAster 21:48:11
@_discord_331951461594431489:ckie.devlord0fdragons Most probably the second one. Usually the first one is the main monitor 21:48:51
@_discord_85950865113903104:ckie.devhypevhs if anyone uses KDE and ALCOM and cares enough to want to switch off of the GTK themeing:
I have a script that replaces Unity binary that runs the actual binary but unsets GTK_THEME and others since ALCOM launches unity in its own environment which is GTK-heavy for some reason but I wanted to see if it was worth it to just raise an issue with ALCOM to get it to launch Unity with the "system default"(?) envvars if that's even possible given how AppImage handles environments with much insulation
21:51:19
@_discord_331951461594431489:ckie.devlord0fdragons Yep, it's the second card. It has 90 display rate 21:53:06
@_discord_331951461594431489:ckie.devlord0fdragons Okay... that path "pp_power_profile_mode" does not exist. Maybe it's named differently on the card I have 21:55:01
@_discord_331951461594431489:ckie.devlord0fdragons I'm totally stuck. Envision does not continue claiming I need to "build the profile first". I have no clue what it want's from me. 22:20:29
@_discord_301973641674096640:ckie.devstuin Menu button in the top right to build/install 22:24:59
@_discord_331951461594431489:ckie.devlord0fdragons Okay. Claims now I'm missing "jq" and "openxr"... how so... I'm deving with OpenXR... what does it need? magic dust? U_U 22:25:38
@_discord_331951461594431489:ckie.devlord0fdragons Also... what is "jq"? never heard of this one 22:26:37
@_discord_301973641674096640:ckie.devstuin I think it's a tool for reading json files 22:26:59
@_discord_331951461594431489:ckie.devlord0fdragons That tool is really missing documentation. It wants me to set a libsurvive path but doesn't tell at all what kind of path is expected. lib? bin? source? repo? something else? nothing I tried seems to be the one the tool looks for 22:29:37
@_discord_331951461594431489:ckie.devlord0fdragons Okay... I gave up on envision. I can't get any further than this compile-profile-blockage. I guess the only option is to somehow fix Monado to run libsurvive... or better... somebody gets hand-tracking working with lh_steamvr. that one is working here flawlessly 22:37:53
27 Jul 2024
@_discord_510621703051935744:ckie.devothello7 babblebones avpro sync is broken again 00:00:29
@_discord_797861611637440553:ckie.devbabblebones#0 https://tenor.com/view/angry-fist-arthur-%E6%86%A4%E6%80%92-gif-5794225 00:09:17
@_discord_331951461594431489:ckie.devlord0fdragons I recompiled monado now in debug mode and gdb stepped through it to see what happens. I noticed monado sort of fails the first time and after that the device is sort of "dead" which is the reason why monado never reported survive to be working. So the real problem is monado dying on the first attempt to access the device. Hence power off the VIVE, then power it on, wait a bit, then run monado results in this:

Using builder lighthouse: Lighthouse-tracked FLOSS (Vive, Index, Tundra trackers, etc.) devices builder
Result: XRT_ERROR_DEVICE_CREATION_FAILED
ERROR [init_all] Could not create system!

I don't know yet why this happens but that seems to be the actual problem. After this if i don't power off the vive all future attempts simply fall back to the simulated HMD
00:19:38
@_discord_331951461594431489:ckie.devlord0fdragons Looks like this is the main problem:

Info: Loaded drivers: GlobalSceneSolver, HTCVive
Warning: Failed to submit transfer unknown Watchman (-4)
Warning: Failed to submit transfer unknown Tracker (2018) (-4)
Warning: Failed to submit transfer unknown Watchman (-4)
ERROR [lighthouse_open_system_impl] Unable to find HMD
00:23:43
@_discord_1151988060435775598:ckie.devimrsvjon_damaestro#0 are you sure you have the needed udev rules? 00:46:47
@_discord_1151988060435775598:ckie.devimrsvjon_damaestro#0 https://gitlab.freedesktop.org/monado/utilities/xr-hardware might be of help 00:46:59
@_discord_1151988060435775598:ckie.devimrsvjon_damaestro#0 -4 looks like signaling, if it was permission denied i'd expect -13 00:50:01
@_discord_331951461594431489:ckie.devlord0fdragons No, Steam can use the device fine. Also steamvr_lh can use it fine. It seems libsurvive is broken and can't handle the vive_pro anymore. I checked the hidraw files before running monado and they are fine. after running monado (with the error) the hidraws related to the HMD are all gone. so libsurvive somehow manages to totally kill them off in a way they plain out die. 00:57:46
@_discord_331951461594431489:ckie.devlord0fdragons With other words Monado+libsurvive = broken. 00:58:01
@_discord_331951461594431489:ckie.devlord0fdragons The only solution seems to get hand_tracking working with steamvr_lh since libsurvive is a dead-end right now 00:58:42

There are no newer messages yet.


Back to Room ListRoom Version: 10