Hi,

 incompatible libraries will produce errors inside Unity editor to being with or unity won't see them at all. It has nothing to do with IL2CPP

Bye,

Jean

Unity supports both IL2CPP and Mono scripting backends for Windows builds. IL2CPP converts your C# code into C++ before compiling it, which can lead to performance improvements and increased security. Mono, on the other hand, uses Just-In-Time (JIT) compilation, which can result in faster build times during development. The choice between them depends on your project's needs. For final builds, IL2CPP is often recommended due to its performance benefits. However, be aware that IL2CPP may require additional configuration to handle code stripping appropriately.

Will IL2CPP become more difficult to configure if my project has a lot of code that uses incompatible external libraries, or does Unity have a simple way to solve this problem?

Here's a little script that makes an object explode upwards like toast ejecting out of a toaster with the ability to add some randomization in the direction / rotation if desired.

I am living a weird issue where when I activate an enemy and make him visible only parts of the 3d model are rendered. I am using a ready asset from asset store which had its own shaders but I also got rid of the shader and deleted the shader folder and created a default material for the enemy but still same problem. I am using Built in Render Pipeline and I am in Unity 2022. I would appreciate you feedback and support on this. The example video is below so you can see the problem.

I used the URP Tutorial project as it offered the possibility of using all of its great features, but using Playmaker and my own project.

I ran into an issue with a Playmaker action "Don't destroy on load".

A specific state uses that action along with the Singleton action. I believe that scenario should be common practice?

When the Scene is run, that object with the Playmaker Fsm should be added to the "Do not Destroy"; unfortunately, that is not the case. It seems to be destroyed as actions related to finding that Playmaker object and its fsm no longer work as expected!

I had to very carefully export my entire project and import it into the Universal core Template to resolve that issue.

The Universal core Template does not have this issue!

Possibly this issue has been reported elsewhere, please accept my apologies.