baking broken in 8.0.0
See original GitHub issueAfter upgrading to 8.0.0
baking seems to be broken. I get No reflection baking info found...
warnings for everything, my own classes and Unity’s.
Eventhough I am using All Generated Assemblies
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5
Top Results From Across the Web
displacement map (height) baking problem in Toolbag
The only problem is the height baking, it just doesn't work at all. It outputs a map, but it doesn't have any (different)...
Read more >Texture baking selective to active seems to be broken. ...
Texture baking selective to active seems to be broken. This isn't just the file either, this happens whenever I try it in blender....
Read more >Lightmapping issues on Android with LWRP
Hello folks, we are currently experimenting with baking lights onto prefabs in Unity using the script provided in this thread. https://forum.
Read more >Applied Energetics 2 1.16.1 8.0.0 Crash · Issue #4571
Applied Energetics 2 8.0.0. I wanted minecraft to start and start tinkering with the configs but instead it gave a crash.
Read more >Upgrading to version 8.0.0 of the Universal Render Pipeline
This page describes how to upgrade from an older version of the Universal Render Pipeline (URP) to version 8.0.0.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Tried to update for this feature, did not work out as well(tested in editor). Using assembly definitions I have around a hundred of libraries and reflection baking throws around 700 warnings. I’m not sure if it was able to bake anything in the first place. Sorry for not being able to provide an example to show the issue. Are there any requirements in placement of baking settings? I put it under “resources” of the main project, next to project context which handles a bunch of mono installers. EDIT: In log I see Added reflection baking to ‘411’ types in assembly ‘Zenject.dll’, took 0.55 seconds Added reflection baking to ‘11’ types in assembly ‘Zenject-Editor.dll’, took 0.05 seconds Added reflection baking to ‘5’ types in assembly ‘Zenject-PoolMonitor-Editor.dll’, took 0.03 seconds Added reflection baking to ‘15’ types in assembly ‘Zenject-ReflectionBaking-Editor.dll’, took 0.05 seconds
If I turn off “All Generated Assemblies” I am able to see the giant list of dlls under “Include Assemblies”, but adding them manually does not help either.
I had what seems like a similar issue. After some debugging, I found that I needed to add my own namespace pattern “^” to match all namespaces within the given assemblies. By default, Zenject adds “^Zenject” as the only namespace pattern which causes other namespaces to fail the match when searching the assemblies. See the “Run” method in ReflectionBakingModuleEditor.cs.