I’m having the same issue. This is a common sense “feature”.
By hard-coding this, the programmer responsible essentially created a circular dependency between the subsystem utilities and the subsystems themselves. 0/10 wouldn’t even consider hiring them.
Apologies for breaking your custom online subsystem implementations. Two features that improved UniqueId overall came together to break the code in question.
1) UniqueId compression - up until now, in the interest of simplicity, we were simplify passing a string across the network. This was grossly inefficient, but for small player counts it wasn’t on our radar. For Epic’s unique id scheme, a guid, it was 43 bytes to replicate. We found that we could pack this into nibbles and save a ton of space. The code now serializes at 18 bytes, which is significant savings in FNBR where we replicate 100 user ids to everyone (10k replications x 43 bytes). Additionally for cross play we replicate other platform unique ids (10k x 64bit number in string format). These weren’t as big a savings, but since they were straight up integers, we could pack them the same way.
2) UniqueId type - again for crossplay, we needed to better understand what type of UniqueId we were dealing with without having to cross reference other systems. Replicating the type without losing savings from 1 is the reason for the “hash/index” value that is causing you trouble. 5 bits of the packet were used to have room for 32 online subsystems. Of course this means we need to know ahead of time all the values. This is clearly not conducive to custom implementations.
We are going to fix this. We will use one of the bits to signify a custom Online Subsystem, and pack the name of your system into the packet. We thought about some way to deterministically register all known online subsystems, but this won’t work given that not all will register in all scenarios (not all platforms register all subsystems). The simplest thing to do is sacrifice a little bit of the compression savings for simplicity and convenience.
We are looking to get an implementation in ASAP and have it available with the one of the next 4.20 hotfix releases.
Apologies for the delay in a response, we do not often get a lot of visibility into specific forum issues. I hope this addresses the concerns, the online team does care about the pains of other developers.
Any updates with this? Our project uses Uworks, and we are getting the same TypeHash error on 4.20.3. Is there anything that needs to be done to get custom OSS to work on 4.20.3?
For anyone reading this, I found the problem and posted it in the thread and I’ll paste the text below as well.
Found the fix for the hash issue. Instead of adding a hash, given the “fix” implemented by Epic in 4.20.3, we now need to override the following function in FUniqueNetIdUWorks, inherited from FUniqueNetId:
So I’ve done what vlad.serbanescu11 has suggested and when the server is getting the hash for the subsystem. It’s still only checking the official 20 subsystems.
note: I am not deriving from any of the official subsystems, but mine is basically just a copy of the steam subsystem. Also I created my own OnlineSusbytemNames.h called OnlineSubsystemCustomNames.h which includes OnlineSusbytemNames.h and defines my custom OSS. So I’ve already done the GetType() thing, it seems like I need to hash my OSS name and add it to SubsystemNameToHash but I have no idea how to do that. Has anybody solved this?