A few minutes ago we published com.unity.netcode@0.3.0-preview.3 .
This release requires Unity 2020.1.2 and entities 0.14.
NetCode 0.3.0 is a significant change to the authoring workflows for ghosts. We now automatically generate code per component and no longer do any code generation per ghost prefab. Since it is a major change any project using earlier versions of NetCode will unfortunately have to change some code to upgrade, please see the change log for details.
I’m porting my existing code base to Netcode 0.3.0 right now.
Can someone explain the usage of the new Composite field inside the GhostFieldAttribute?
On a different note i found out that multiple entity fields on the same component lead to the variable ghostEnt being declared multiple times inside the components serializer.
Is it possible that 2020.2 is behind 2020.1 in terms of DOTS support? I tried opening the sample in 2020.2 and I’m getting errors about job reflection data
Our new serialization code supports serializing structs, so if you can have patterns like this
public struct SomeData
{
public int A;
public int B;
}
public struct SomeComponent : IComponentData
{
[GhostField] SomeData Data;
}
Part of out delta compression is a change mask - 1 bit per field in the component - saying if that field has changed. If it has not changed the data is not part of the snapshot. We also delta compress those change masks to make non-changing fields zero bits (there are some side effects which make subsequent changes slightly more expensive in a few cases, but generally the cost is <1bit).
The Composite field is something you can put on the GhostField attribute for the struct (the field called Data in my example) to control if you have one change mask bit per field in the inner struct, or one change mask bit for the inner struct as a whole. In my example it’s either two bits, one for A and one for B in the non-compoiste case, or 1 bit for SomeData in the composite case.
Which is better depends on how your data is changing. If A and B usually change together it’s probably better to use composite, but if one changes frequently and one rarely it might be better to use non-composite.
Thanks, we’ll fix that. It would be great if you can file a bug for it in the Unity bug reporter so we get tracking on it
Throws up misconfigured errors as your certificate expired a month ago
Websites prove their identity via certificates, which are valid for a set time period. The certificate for oc.unity3d.com expired on 7/22/2020.
Error code: SEC_ERROR_EXPIRED_CERTIFICATE
I really like the addition of [GhostComponent] and [GhostField]. They allow me to easily make a plug-n-play NetCode integration for my package instead of having to write a big guide on which variables in my package’s components have to be networked and how to setup ghosts
In the doc’s “Getting Started”, it says whenever you add a GhostAuthoring component, it automatically adds replication fields for Translation and Rotation
But I’d also be curious to know how we can replicate other fields that weren’t maked with [GhostField], but are in packages that we don’t want to modify. I’m guessing that if NetCode can add those automatically, we might be able to do that as well
I am wondering what GhostGroups are exactly and how I could maybe use them.
GhostGroups are now supported. A ghost prefab can have a GhostGroup buffer added to it at authoring time, all ghosts listed in that buffer are guaranteed to be sent together with the main entity. In order to be in a group the child ghost must have the GhostChildEntityComponent component added to it. The GhostChildEntityComponent can be added at runtime when moving the child entity into the group.
I’m guessing it’s for adding virtual children to another ghost prefab… am I off the mark?
In the picture: Rotation is synced for the root, but not for child 0 (no fields are listed, and it is not rotating in the client, but it is on the server).
Is anyone else getting “Internal: deleting an allocation that is older than its permitted lifetime of 4 frames” warnings in the Asteroids sample?
I’m on 2020.1.3f1
because netcode runs at a fixed framerate, you need to limit your fps so it’s not 4x higher than the update rate
(they are looking into a way to fix this)
You are mostly correct, but it is important to note that the group itself is not replicated at the moment, so you can’t get the list of group members on the client side - you have to add entity references to them. The main use-case it intends to solve is if you have a player and a replaceable weapon or ability owned by the player (which is not known at authoring time) and you want to make sure those two ghosts are always sent together so you know they are in sync.
