ah yeah that sounds about right
What are your Video/Connection settings in alvr desktop? I dont think I see any artifacts except the thin jagged outer line, but am still getting random app shutdowns/disconnects. Us having the same headset, i would think it was the desktop settings, i dont know.Updating my answer regarding the latest version for the Pico 4.
Full passthrough does work. I was using the older recommendation of 220, 220, 240 and the spectrum on Sally's plugin wasn't showing any passthrough area to see my mistake. After reading your updated description to use 100, 129, 100, it showed a nice big passthroughed area in the spectrum and in VaM.
It's amazing what you did with the outline, it's barely visible ? , incredible work. This bring immersion to a whole new level.
Unfortunately the artifacts are there and there's high latency effects when using the menu or Scene Browser. There's a higher latency when in passthrough mode, seeing in the ALVR server graphs, but it's something like a 25% jump, not something dramatic compared to non-passthrough. I also heard the headset fan starting earlier than usual and battery use seemed higher than normal, perhaps there's something there making the headset struggle a lot more than in non-passthrough besides the use of the front camera?
Is there something I should see and tell you that would be meaningful for debugging? How's the result in your Quest, does it also have the artifacts I mention?
There's tons of options in the settings, especially in the advanced settings. I think almost all are in the default option, and considering there's no artifacts until I do the key combination to use passthrough I don't think the settings would be the cause?What are your Video/Connection settings in alvr desktop? I dont think I see any artifacts except the thin jagged outer line, but am still getting random app shutdowns/disconnects. Us having the same headset, i would think it was the desktop settings, i dont know.
Weird. It seems to just have to do with whenever im trying to interact with the headset controls (adjusting volume, taking screenshots, etc) It will boot out of the app a few seconds after. Try that on yours. (Im on latest pico update 5.7.2 btw)There's tons of options in the settings, especially in the advanced settings. I think almost all are in the default option, and considering there's no artifacts until I do the key combination to use passthrough I don't think the settings would be the cause?
I can also uninstall everything and start fresh. Are your settings in the server changed somewhere special?
I didn't experience shutdowns yet, so that's good.
There's tons of options in the settings, especially in the advanced settings. I think almost all are in the default option, and considering there's no artifacts until I do the key combination to use passthrough I don't think the settings would be the cause?
I can also uninstall everything and start fresh. Are your settings in the server changed somewhere special?
I didn't experience shutdowns yet, so that's good.
hmm it must be some interaction with Pico OS. I'll see if I can find any info about that. I have noticed that I sometimes get a black screen and warning that ALXR is not responding, but I just hit okay and it lets me back into the app no issue. Only noticed it since I started this branch but I dont think I caused it unless its just bc I'm pushing the system harder. Anyway the shaders are decent enough that I'll focus on optimization stuff for a bit instead of just tweaking the shaders endlesslyWeird. It seems to just have to do with whenever im trying to interact with the headset controls (adjusting volume, taking screenshots, etc) It will boot out of the app a few seconds after. Try that on yours. (Im on latest pico update 5.7.2 btw)
Unfortunately the artifacts are there and there's high latency effects when using the menu or Scene Browser. There's a higher latency when in passthrough mode, seeing in the ALVR server graphs, but it's something like a 25% jump, not something dramatic compared to non-passthrough. I also heard the headset fan starting earlier than usual and battery use seemed higher than normal, perhaps there's something there making the headset struggle a lot more than in non-passthrough besides the use of the front camera?
Right, I forgot I did try to use the volume buttons and the client crashed. Yes, I confirm the same behaviour. I rarely do that so forgot about it.Weird. It seems to just have to do with whenever im trying to interact with the headset controls (adjusting volume, taking screenshots, etc) It will boot out of the app a few seconds after. Try that on yours. (Im on latest pico update 5.7.2 btw)
default settings are horrendous holy crap dude. I still dont know how to fix the lag, tbh, but if you look at my settings as a reference point you can at least make it look betterRight, I forgot I did try to use the volume buttons and the client crashed. Yes, I confirm the same behaviour. I rarely do that so forgot about it.
@animetiddyenthusiast
I kept my ALVR settings close to default assuming they were reasonable settings, guess I'll have to play with them even not understanding what most do. The extra effort on the Pico makes sense, hopefully addressing the server settings will improve the results.
But would still like to say that this is currently the best experience ever with passthrough, I'm quite excited to see what future improvements will do here, but damn, it's amazing what is available already in 2023.
The color doesnt have to be exact btw you can use the vertical HUE scrollbar and pick anywhere within green once you have it lined up in the right area. I find slightly yellow looks best in many scenes. And the transparenty mode is what I refer to as blend mode just FYI- Remove all environments and floors from a scene (usual process: edit mode, click arrow, find the relative assets and delete)
- Download this plugin to set the scene color background to R 100, G 120, B 100 (the values in the original description are wrong and I kept using them because, again, I'm retarded)
- Press the menu button on the left controller (the one with three lines) + B on right controller (I kept pressing menu + A which gives a half transparency mode)
public class cleanScene : MonoBehaviour //or whatever vam scripts inherit from
{
private List<GameObject> sceneObjects = new List<GameObject>();
public void Init()
{
//make a button with VAM API for session plugin or just have it activate immediately upon adding to scene plugins
this.sceneObjects = SceneManager.GetActiveScene().GetRootGameObjects();
//I'm guessing there's a way to do this more directly in VAM
cleanObjects();
}
public void cleanObjects()
{
//generalizable and nondestructive method but would require setting up a hidden layer in another class if VAM doesnt have one to use
int LayerHidden = LayerMask.NameToLayer("Hidden Layer");
foreach (GameObject go in this.sceneObjects) {
if (!gameObject.TryGetComponent(Atom.Type("Person") ) ) //Random shot in the dark, probably a better way to check this in vam
go.layer = LayerHidden; //if using layer method
//otherwise
foreach(Renderer re in go.GetComponentsInChildren<Renderer>()
{
r.enabled = false;
//sometimes it may be better to swap the shader or material out for a new one with alpha of 0 or change the render queue but this generally works
}
}
}
}
Tired to read/respond much but last night I discovered something in the client that was having an effect on the visual quality, don't yet know how to fix it fully without a new issue popping up but i hope I can figure it out soon. In other news, passthrough modes in latest confirmed working on Lynx R-1 (everything works just one big issue that's making it unusable I need to figure out without the device...)
vec4 when_gt(vec4 x, vec4 y) {
return max(sign(x - y), 0.0);
}
vec4 when_lt(vec4 x, vec4 y) {
return max(sign(y - x), 0.0);
}
Get this plugin right now: https://hub.virtamate.com/resources/scene-atomic-batch-operation-tool-lgatomtool.36603/
Seriously it's so good! tysm for making it if you see this! No other tool for the job is this feature complete so I was gonna make a shit tier version of this myself but saves me the work
I'm trying not to be mean but my dude read the names of the files
Quest version will work on any version of the quest. Tbh it should boot on every android device on os v12 or newer, the main reason for different platform versions is to handle separate controls and methods of involving passthrough. I did include a separate quest pro build in one upload to hopefully better cater to their color passthrough but even then it worked on any quest.I read the names of the files. Let me try again:
Does alxr-client.apk support all android devices including Quest 2? If this doesn't support Quest or Pico then what DOES it support?
Does alxr-client-quest.apk include support for Quest 2 (since there are also Quest 1, Quest Pro, and Quest 3)?
If both apk's support Quest 2 which is better?
Thanks for any info.
Version parity with my client since I'll be unable to work on this for a week or two. should be slight improvement for quest users but I'm not sure what the last upload was. not different enough to remake for pico sorry babes
Virtual Desktop posted a new beta update with chroma key passthrough. They use nearly identical formulas to my version and achieve similar results while having far better performance and quality than alxr. I'm not done developing in this space but I may be done with this project. There are some updates coming soon to alxr that would be very exciting if not for this situation, but may still be enough to keep me involved.
Haven't decided yet, but tbh I have to just recommend you go use VD for...
I really understand your point but, don't forget that VD is paid (i have it) and alxr is not so, is a point at your favor in that regard.
I still have to try the AR in VD, i only used AR with your alxr version and the result is mind blowing for me...
thank you really a lot for doing it and the best of luck with your other projects