search

graemeniedermayer / augmented_reality_SD

Combining augmented reality and stability diffusion through api calls.
MIT License
9 stars 1 forks source link

What could be the potential issue here? #1

Open yorkewoo opened 3 months ago

yorkewoo commented 3 months ago

Hey Graen,

This is AWESOME experiment. Thanks for sharing!

I followed the instructions and have successfully setup the backend and the proxy pass I assume.... attached with screenshots. Automatic1111 is running well on the PC side.

Screenshot 2024-08-27 223819

On the frontend, I am using a Meta Quest 3 default browser as well as an iOS app XRViewer, After I keyed in the IP address, I can't seem to click the Enter AR button. I also tried my friend's Android phone...

Could you guide me through where could be a possible error?

20240827_145212000_iOS 20240827_144034059_iOS

graemeniedermayer commented 2 months ago

So Quest 3 and IPhone aren't going to work because of the camera access requirement. You should actually be able to capture

I've heard there's been issues with particular android phones. Like Samsung models s8-s21 seems to work well but I've heard mixed things outside of that. This is usually from the camera access component.

You should also be able to rewrite some of the code to make it work with Quest 3 depthmap and controlnet. 

let options = {
         requiredFeatures: ['depth-sensing']
}

But this would require rewriting the UI and capturing the depthmap. So it would be a little bit of work.