-
-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
some errors on windows 10 64bit #785
Comments
I will check it: |
The assertion in Mathutils_RegisterCallback was raised when all the callbacks were registered (freestyle and bmesh too). But this assertion introduced in 1b74ec9 is wrong. The test i + 1 < MAX suppose that the last callback is a null sentinel. But this is not the case as no one is using this to stop a loop and the loop in Mathutils_RegisterCallback must stop when it find a null slot or that the slot is already containing the callback, otherwise it's an error. It's impossible to stop the loop with all regular slots registered and and different from the one intenting to register. Fix a part of issue #785.
no , i have not compiled with debug option. Thanks |
i have recompiled upBGE with "make release x64 2017" and now all work without errors. i think the "make full" enable the debug option . |
Hi , i have compiled upBGE for windows without errors but when i use it , sometimes return me this error
Sometimes i click on ignore and the program continue to work but somtimes the program crash without reason.
using the overlap function of BVHTree without collision , the program return this error in console :
using the xml library , the program return this error in console :
Opening another test file (saved with the 0.2.3 stable of upbge), in the splash screen and when i start the blenderPlayer , the program return me this error :
I have follow the steps on wiki and the command i have used for the compilation is "make full x64 2017" because i have installed visual studio2017.
https://wiki.blender.org/wiki/Building_Blender/Windows
Thanks in advance
The text was updated successfully, but these errors were encountered: