Yeah, we pulled the trigger too early for several different purposes. People seem reasonably hair on fire about it. Weâll publish another round with fixes soonâ˘.
I obviously canât speak for everyone, but I think substantially more detailed dev logs on a much more regular basis would go a long way toward assuaging my frustration with these packages and their development. âSeems like soonâ is better than radio silence, but weâre still experiencing an infuriating cycle where we can neither work with the thing nor do we have any idea whatâs going on behind the scenes.
Unity is not just software we use, itâs the beating heart of our products, and DOTS represents a paradigm shift thatâs likely to govern the course of our careers. This particular dev hell has been so alienating that Iâm no longer sure if Iâm a Unity loyalist, or just donât like the competition. Please communicate more.
@optimise@EugenyN1 can one of you try enabling full generic sharing for your build via project settings â player â configuration section â IL2CPP Code Generation â Faster (smaller) builds? We have a theory that this might be a workaround.
The setting mentioned doesnât appear under project settings for us, but rather under the classic Build Settings menu.
The workaround appears to work for us as well, thank you!
@elliotc-unity Looks like IL2CPP Code Generation not able to serialize into ProjectSettings. Can u make sure it will be serialize into ProjectSettings at next Unity 2020.3.x version? With this current limitation I canât make sure the same project able to get working build at another machine.
Eh? This is only an issue in 21.3, I thought, not 20.3? Also, all of Unity is off today, and yes we agree it was a mistake to release before a long weekend, as well as releasing without checking all these things.
Ya. Itâs 21.3 only issue. What I want to say is IL2CPP Code Generation option is actually at Build Settings instead of at ProjectSettings which make not able to save this option into ProjectSettings. I would like to see this option moves to ProjectSettings in future 21.3.x release.
Btw I also curious I need to choose Faster (smaller) builds in order to fix the issue? Is that il2cpp codegen has some bugs?
It is probably the Full Generic Sharing feature of IL2CPP. In 2021LTS itâs only active with âFaster (smaller) buildsâ. In 2022 itâs always on. Got this from a forum post some time ago that I canât find anymore.
Also, Iâm using the build configuration pipeline because it supports subscenes and I donât see that option there either.
Iâm using 0.51.1-preview.21 in unity 2021.3.7f1 and Iâm trying to fix the error: ExecutionEngineException: Attempting to call method âUnity.Entities.FastEquality+CompareImplâ1[[Unity.Physics.PhysicsWorldIndexâŚ]]:CompareFunctâ for which no ahead of time (AOT) code was generated".
It gets triggered in an async coroutine when loading prefabs via addressablesâ LoadAssetsAsync().
Ah. I actually had the scripting backend set for il2cpp already, but I had two projects open and I accidentally looked at the settings for the wrong one when I sent my last post . Anyway, thanks for the help - the error is gone!!
Iâm happy to announce that the fix for this has landed in 2021.3.9f1, which is now live! You can all set your builds back to âfaster runtimeâ if you like.
VM Region Info: 0x21b00000005 is not in any region. Bytes after previous region: 1833951035398 Bytes before following region: 103238128893947
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
commpage (reserved) 1000000000-7000000000 [384.0G] â/â SM=NUL âŚ(unallocated)
â> GAP OF 0x5f9000000000 BYTES
MALLOC_NANO 600000000000-600008000000 [128.0M] rw-/rwx SM=PRV
. Anyway, thanks for the help - the error is gone!!