Infinite Import loop in vrchat base SDK OculusSpatializer problem.
complete
Darketernal
I don't even own a oculus, i have an index, but in Unity there seems to be something wrong in the
"packages/com.vrchat.base/integrations/oculusspatializer/audiopluginoculusspatializer.bundle" It's doing an infinite import loop. I would appreciate if this would be looked into.
Log In
White Lotuz
complete
Darketernal
White Lotuz Was this problem fixed? What did you do against it?
White Lotuz
Darketernal: Hello hoping I didn't jump the gun too quickly but see comment below this seemed to be solved since previous SDK 3.6.0 version. We're now in 3.7.0 but maybe you can double check it looks resolved on your end or you have a fresh repro we can take a look?
kb10uy
I confirmed this error is solved with SDK 3.6.0 (stable).
みみー／Mimy
This still reproduces with SDK 3.6.0-beta.1.
StormRel
tracked
kb10uy
Reproduced with SDK 3.5.3-beta.2.
Edit: maybe few people are aware of this error as it does not matter in practice.
Darketernal
Yeehoo , no one knows i guess
Hackebein
Darketernal you should at least share your used SDK/Unity version. This is a bug tracker not a support forum. You come here to report a bugs not to get support or start discussions. Forum can be found at ask.vrchat.com
Also I don't think that this is a bug VRChat can solve. This looks like something on your end which constantly updates the file. Maybe AV? or a different component which updates this file? Have you tried reproducing in a new project?
Darketernal
Hackebein I mean, i get your point, but i never saw a message that said , share your SDK/UNITY version, so i don't want to be blamed for not sharing it if no one asked for it but yes i understand that it would be helpful in hindsight, but i'm just new here so ya, lesson learned i guess. i don't really agree on this being just a bug tracker place, i mean when you post a bug, you want the support to get it resolved right? Why would it be wrong to ask support for it to be solved? And the bug itself, well i don't know if others suffered from it, but it didn't seem to be caused on my side by something i did 'wrong' , i was just importing things and this was a native SDK bug from what i saw, hence i made a bug report. I also did manage to try to reproduce it in the past in a new project, it gave the same error, i got a message today saying this post was complete, so i wonder if they fixed it.
Hackebein
Darketernal Seems like i had a bad day when i wrote it. I'm sorry. Idk what i wanted from you anymore.
Darketernal
Anyone? If you open up the images in web, you can see a close up of the problem.