is a Chaos issue that was fixed in 4.26-chaos-2 and then reappeared in ue5 EA chaos and 4.27-chaos branches.
I am not going to add an automated waking work around because I specifically want to test chaos in its native state for issues and chaos isn’t entirely useable as is anyway yet in order to go in and fully tweak everything.
ATM there is very little reason to use ue5 for VR, its a strict downgrade, the 4.27-chaos branch is a more updated version of chaos even and none of the ue5 rendering improvements work with VR yet.
The plugins chaos and ue5 branches generally just exist to work out issues and report them so that chaos and ue5 in general are ready for VR on launch.