We used the Tool that was linked as the solution to my Original Post.
It generated the Interiorproxies by its self, and we have been using that and everything has been working perfectly fine since then. at least regarding my original problem.
… I didn’t mean making a video, I meant a server that experiences the issue which a project contributor could join to diagnose why the ‘order-independent’ sync code is not working.
i’m having the same issue and i’m just wondering when you used the tool did you upload the mlos into them or did you just create a blank interiorproxies.meta?
I was having issues of audio being scuffed and people flickering when having more than one person in majority of my servers MLO’s, I set up the proxies using
after including the interproxies file and restarting my server the issues of flickering and audio scuffs has disappeared while being inside of MLO’s with multiple people at the same time. I am not sure where I read it but I believe it has to do with poorly made interiors with interproxy numbers lower than the base gta mlos conflicting in some way, not entirely sure though I am not the most advanced yet but adding the interproxies file and then a restart is what personally has fixed it for me running an esx base that was deployed through txadmin
that’s a good point that I didn’t think of, looking back majority of the interiors didn’t have interior proxy ordering files, the ones that did I ended up deleting and including them into the one interproxy meta file I have created for all 3rd party map additions on my server.
Do NOT use any interiorproxies creator. Delete any interiorproxies you have. This issue seems to be resolved now. For the time being, you just have to use experimental (unstable) FiveM client version till this fix is pushed to standard one.
I understand exactly what you mean. That’s why I joined this specific topic recently to clarify the situation as it is now.
d-bubble fixed the issue. I tested his solution myself and no addon proxies are needed anymore. If used, they can actually break things. Just for the time being, everyone needs to use experimental client branch, before the fix will be implemented to the standard client FiveM.
More on the the issue and the whole process of finally fixing it here