(Build Number 1746) World version is incompatible with this instance | Voters

(Build Number 1746) World version is incompatible with this instance

tracked

＠VoicesShiature

World version is incompatible with this instance. some world is pretty rare to see this chances bug when I switch live is complete fine when I switch beta is chances will be buggy to join other worlds chances you will see this > World version is incompatible with this instance. + Joining instance blocked by master two thing it's pretty rare to find other world causing this
> 1746 beta = https://www.dropbox.com/scl/fi/6yd4s7xostkyd70vkffyr/2025-10-25-19-20-25.mp4?rlkey=fvjllonqkcd4rhvlvuqhcw49p&st=raysl6i4&dl=0
> 1727 live = https://www.dropbox.com/scl/fi/1p3uu6cjynyts36g0iosj/2025-10-25-19-28-29.mp4?rlkey=p6q5jy2noc16jjowhucwwwi7k&st=v695stax&dl=0

2 days ago

_tau_

marked this post as

tracked

Heather May

I was getting this issue as well, though slightly different circumstances and I believe I've resolved it now.
Problem: Quest users (live or beta) were unable to connect to the world if it was created by a PC user on Beta. All other cases appeared to work,
edit: Everything below here was likely wrong. Issue came back and may have had a flaw in my testing combined with just random luck, as evidence is now that I can connect successfully sometimes.

Heather May

So, I said this last night. Testing worked, I swear. I'm pretty sure I tested everything correctly.
It's not working again. If Quest live tries to connect to PC Beta it fails with a Version error.
World is https://vrchat.com/home/world/wrld_2dddec3a-f471-4c7e-ab39-00ab9ce427c7/info

Heather May

Doing a bunch more testing and seeing if I could get things to work I had a case where I was able to join the world on Quest Live when PC Beta had created it. I then attempted to rejoin on quest and was able to do so without issue. At this point, the PC user recreated the world and the quest user was no longer able to join it, getting the World version error, even though the world had not changed.
I have verbose logs from both sides of the testing I can provide if needed.
For my testing tonight, I:
Ensured all networked objects were the same in both versions
Downgraded SDK to 3.9.0 from 3.9.1b1
I had the same results when connecting from Quest live to the world. When connecting from Quest Beta it did work.
For a final test, I reenabled one (not-synced) item so the two platforms were no longer the same the same and it still worked.
Testing was done using my WIP world: wrld_5001fb52-6fbd-42a8-8f11-5b00a21c861d; there is a button on the backside of the front counter which will log (to the best of my current knowledge of UdonSharp), what it thinks its NetworkIDs are.

Vincil

This has been happening in a world of mine I updated yesterday.  With the help of a friend on live while I was on the beta (installed today, so I should have the up-to-date version), I was able to join the world when I created it on beta, but was unable to join it when my friend created it on live.
This is not an issue on the older version of my world.
An error I get in my world when I get kicked out:
Error      -  [Behaviour] Failed to collected metadata on /NetworkedPlayerManager [3]/PlayerPositionSync/PlayerReviver
Object reference not set to an instance of an object.
NetworkedPlayerManager is a manual synched PlayerObject (no persistence).  PlayerPositionSync is a NoVariableSync child of NetworkedPlayerManager.  PlayerReviver is a NoVariableSync child of PlayerPositionSync.
NetworkedPlayerManager has another child object that is manual sync that didn't appear to throw an error.
Here is a working version of my world: https://vrchat.com/home/world/wrld_32a0e2ec-cb81-4367-a93a-31f7ee7324a4/info
And this is the version of my world that has the issue: https://vrchat.com/home/world/wrld_afa6359c-0679-46d1-9ae7-9f4e648650c3/info