error after updating to Entities 0.1.0 m_systemsToUpdate does not exist

I get a list of exceptions now due to internal code

Code (CSharp):

1. Library\PackageCache\com.unity.netcode@0.1.0-preview.6\Runtime\ClientServerWorld\ClientSimulationSystemGroup.cs(148,56): error CS0103: The name 'm_systemsToUpdate' does not exist in the current context

Is this something Unity will fix? Or is this somehow triggered by my own code. A bit confused because there is no stack trace.. nothing..

 

NetCode has always been a bit behind the latest entities package. I’d wait for the next netcode release before moving to the latest minor entities release (use the second latest for now). It’s what I did after trying to move to the latest entities package. Unity is a bit behind the latest package management tools - imho the netcode package should be able to specify an upper entities package version bound.

P.S: m_SystemToUpdate missing after Entities Package Update to 0.10

 

Is there a way to hack around this?

 

@

 

Check the link I added in my PS

 

allright so ill just downgrade the entities package to the previous version then and wait for a fix.

 

Why when installing Netcode unity manager simply download all valid versions - or why in the Netcode manual there is no list of all valid versions of packages that Netcode depends on? @JoachimAnte

Can anyone list needed versions(highest level) that work?

Edit: it(package manager) shows actually what i need - on advanced click show dependencies

 

UPM should at least pop up a dialogue stating that the Entities package version is higher than is needed and offer the option to downgrade, I think. This kind of incompatibility is one of the goals UPM aimed to solve in the first place, isn't it? Allowing a 5 version gap without setting some sort of a `maxVersion` dependency property seems a bit ridiculous. Especially since you can't simply downgrade the Entities package and call it good and you have no idea which version actually broke the system

 

Use Systems instead