Oculus Quest Crash after I call "Print String" node

More than one year later after the last post and this critical issue is still a thing. Happens on my Quest 2 (using with Oculus Link, platform Windows). I can’t believe this didn’t get fixed yet. It’s impossible to run any debug/screen dump content as it sits now.

Also, why tf is this thread set to “solved”? It’s clearly just full of devs complaining about the bug, asking for a fix…

1 Like