Using the exporter 4.3.2, the BetterCubemapEditor crashes the StandaloneProfile right on launch.
Maybe consider adding a “bug” tag here 
Hello Krizzl0r,
It seems that you are encountering a crash in Unity’s Standalone Profiler when using the BetterCubemapEditor with the exporter version 4.3.2. Unfortunately, I could not find specific documentation on this crash from the provided files.
It would be useful to report this issue to the relevant development team on their GitHub repository or support forum. Additionally, you might want to consider adding a bug tag in your reporting to enhance visibility for troubleshooting.
If you have additional logs or error messages from Unity when the crash occurs, please share them, as they could provide more insights into the issue.
Let me know if you need any more assistance or have other questions!
1 replies left - Get a PRO license for more AI replies.
thread_PKmQXjWm6y6NxmI6DMYF1qvT
Reply to this message to continue the conversation
Thanks for the report – I can see that Standalone Profiler crashes when opening it from our samples project, good catch.
How do you infer that the BetterCubemapEditor is the culprit here? The logs seem to point at some websocket connection failing, but I don’t get specific logs in relation to BetterCubemap.
Ah, found it – Secondary-profiler.log is probably where you saw it?
To me it looks like a Unity bug – querying IsRunningLightmapping shouldn’t crash… but we can hopefully work around it.
EDIT: Yes, we can work around it 
should be fixed in the next release.
1 Like
This topic was automatically closed 13 days after the last reply. New replies are no longer allowed.