Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Bug / Crash  obi fluid unusable since 2021.2.17f1
#2
Hi there!

I'm developing using 2021.2.19, and had no problems of any sort with Obi Fluid (or any other Obi asset). No other reports similar to yours either, this sounds really strange. Obi does no work if there's no components in the scene, it doesn't attach itself to editor initialization callbacks or anything similar.

The stack trace in the crash log you provided doesn't contain anything related to Obi, these are the last few lines:

Quote:0x00007FFA852BD988 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\mini-runtime.c:3286] mono_jit_runtime_invoke
0x00007FFA851FE744 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\object.c:3066] do_runtime_invoke
0x00007FFA851FE8DC (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\object.c:3113] mono_runtime_invoke
0x00007FF7E0AAECF4 (Unity) scripting_method_invoke
0x00007FF7E0AA9914 (Unity) ScriptingInvocation::Invoke
0x00007FF7E0AA325A (Unity) ScriptingInvocation::Invoke<bool>
0x00007FF7E15C5988 (Unity) core::function<bool __cdecl(void)>:Gran sonrisaispatchT<<lambda_0e5811cec38eff5093b6e5836fe870c8> >:Gran sonrisaispatch
0x00007FF7E15C4F6F (Unity) Editor:Lenguarogress:LenguarogressManager::CancelOperation
0x00007FF7E15E5B38 (Unity) Editor:Lenguarogress:LenguarogressManager::Shutdown
0x00007FF7E169FB22 (Unity) Application::CoreShutdown
0x00007FF7E16B23EB (Unity) Application::Terminate

Some questions that I think could help investigate this:
- Could you share a screenshot of your profiler with editor profiling enabled? This way we can see what's dragging the editor down.
- Do you have Burst installed? (maybe there's some incompatibility between Unity/Burst versions?)
Reply


Messages In This Thread
obi fluid unusable since 2021.2.17f1 - by locque - 19-04-2022, 07:46 AM
RE: obi fluid unusable since 2021.2.17f1 - by josemendez - 19-04-2022, 08:21 AM