04-02-2019, 08:50 AM
(03-02-2019, 09:33 PM)Bilic Wrote: I have tested a bunch of other plugins that work without any issues, and the problem seemed to get a little better after you suggested replacing those files for the CPU. Fact is I purchased your plugin and it's not working. It is also not random crashes, its specific to when I do specific things in obi. So unless you have any other suggestions or let me try a version previous to 4.0 i'l unfortunately have to ask for a refund.
Hi there,
We're open to refunds, but fact is the stack trace you provided does not contain a single reference to Obi. So I'm 100% positive Obi is not causing the crash.
The stack trace looks like this, bottom to top:
- UnityEngine.GUIUtilityProcessEvent() (Unity starts processing UI events)
- UnityEngine.Experimental.UIElements.IMGUIContainer:HandleIMGUIEvent (Handles an immediate mode UI event)
- UnityEditor.GameView:OnGUI (Performs OnGUI() for the game view)
- UnityEditor.GameViewDoToolbarGUI (Does the game view toolbar)
- UnityEditor.GameViewDoZoomSlider (Does the slider)
- single:ToString (converts a single-precision floating point number to a string)
- System.BitConverterDoubleToInt64Bits (converts a double to a 64 bit integer)
- System.BitConverter:GetBytes (converts something to a byte representation)
- mono_array_new_specific (creates a new array)
- GC_malloc_atomic (tries to atomically allocate memory)
- crash.
As you can see Obi is not involved in any of these steps, this all happens inside of Unity. If you can describe the specific things you need to do in Obi in order to trigger the crash we'd be more than glad to try and hunt down any potential issues. Judging from what other users say the Unity bug report page, this seems to be somehow related to using NET 4.6 in the build settings, can you check which version you're using?
Also, the replacement files I sent you were simply the physics lib, but compiled with a different SIMD instruction set since your CPU didn't support the ones used by the retail version: Core i5 2400 only supports SSE and AVX, not AVX2. (I mean, the original library is not defective in any way, we just adapted it to your specific CPU).
kind regards,