-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
Windows x86 UPBGE crashing at start #797
Labels
Comments
@lordloki : What kind of file are you using ? |
Default cube |
Joel, can you test this build? https://mega.nz/#!cttHlRiY!NNf4b8NO9k7tFUySVdP4K39Zd6iGUmupDG8qokfNrG4 It is from branch ge_bug_fix_797. |
@lordloki I just built the branch you said, it's working for me as well. |
lordloki
added a commit
that referenced
this issue
Oct 4, 2018
Set GPU_INT to 5 avoid buffer overrun
lordloki
added a commit
that referenced
this issue
Oct 6, 2018
Introduce new array of GPUType sizes to make it extensible and adding more comments too.
lordloki
added a commit
that referenced
this issue
Oct 9, 2018
Introduce a new array of GPUType sizes to avoid a buffer overrun. The new array will allow make the system extensible easier. More comments added. P.D. It fixes the win32 crash
lordloki
added a commit
that referenced
this issue
Oct 9, 2018
lordloki
added a commit
that referenced
this issue
Oct 14, 2018
We use GPU_DATATYPE_SIZE to avoid pass info from outside of array
youle31
pushed a commit
that referenced
this issue
May 26, 2019
youle31
pushed a commit
that referenced
this issue
May 26, 2019
We use GPU_DATATYPE_SIZE to avoid pass info from outside of array
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello! Windows build process is successful at both x86 and x64, but the x86 build won't start, printing only
EXCEPTION_ACCESS_VIOLATION
on the console when Blender starts. I tried to rebuild from scratch, but the problem persists.I will try to revert some commits to see where this problem starts. In the meantime, could someone confirm the issue? Thanks.
The text was updated successfully, but these errors were encountered: