-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
UPBGE 0.2.1 crashes when trying to add an overlay scene that doesn't exist #615
Comments
Please provide example files. |
panzergame
added a commit
that referenced
this issue
Oct 17, 2017
The call to ConvertScene wasn't taking care if the scene existed because it's name was valid. This function call is moved down in a if block. Fix issue: #615.
Fixed in master, please close issue if confirmed. |
http://pasteall.org/blend/index.php?id=48066 It's just one line of code so i thought that you don't need a file, sorry |
Unfortunately I can't compile UPBGE myself (tried it a bunch of times and always get a long list of errors), so can another one confirm that the bug its fixed or make a build? Thanks :) |
panzergame
added a commit
to simedis/blender
that referenced
this issue
Oct 19, 2017
The call to ConvertScene wasn't taking care if the scene existed because it's name was valid. This function call is moved down in a if block. Fix issue: UPBGE#615.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bge.logic.addScene("hud", True)
The scene doesn't exist in the file (it is supposed to be in a linked group, so in the file it is linked to it works). Just put it in a script, if you comment out the line everything works, if not -> hit "p" and UPBGE 0.2.1 crashes immediately, console says: Error: EXCEPTION_ACCESS_VIOLATION.
After i found the bug, I copied the msvcp120.dll and msvcr120.dll into the upbge 0.2.1 folder because there was a bug in 0.2.0 with crashing blender connected to that problem (#598 ), but it didn't solve the bug
In 0.2.0 everything works fine
The text was updated successfully, but these errors were encountered: