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

Level Output crash (development branch) #1232

Closed
John3 opened this Issue Mar 1, 2015 · 5 comments

Comments

Projects
None yet
4 participants
@John3
Contributor

John3 commented Mar 1, 2015

testing development branch.

Project Manager 2.2 (Binary)

  • Bullet
  • OpenGL Rendering
  • Template Full

Development Branch (Compiled with VS2010)
In-game:

  • Option Intel HD OpenGL
    • Quality: any
    • Filtering/Aliasing: any
    • Level Outpost

Crash in "Loading Objects"

Console.log - http://pastebin.com/THv62Puy

@John3 John3 changed the title from Level Output crash to Level Output crash (development branch) Mar 1, 2015

@crabmusket crabmusket added the Bug label Mar 1, 2015

@Azaezel

This comment has been minimized.

Show comment
Hide comment
@Azaezel

Azaezel Mar 1, 2015

Contributor

Verified there's a general crash in development head that it would at first check seems to have cropped up in the last 2-3 days worth of commits. Reproduction requires taking directory re-creation from the top (initial assumption is something gone pearshaped with .cached.dts). Attempting to further isolate the issue.

Contributor

Azaezel commented Mar 1, 2015

Verified there's a general crash in development head that it would at first check seems to have cropped up in the last 2-3 days worth of commits. Reproduction requires taking directory re-creation from the top (initial assumption is something gone pearshaped with .cached.dts). Attempting to further isolate the issue.

@LuisAntonRebollo

This comment has been minimized.

Show comment
Hide comment
@LuisAntonRebollo

LuisAntonRebollo Mar 1, 2015

Contributor

@JeffProgrammer and me can confirm the crash :(

Contributor

LuisAntonRebollo commented Mar 1, 2015

@JeffProgrammer and me can confirm the crash :(

@Azaezel

This comment has been minimized.

Show comment
Hide comment
@Azaezel

Azaezel Mar 2, 2015

Contributor

quick followup: looks like the culprit is buried someplace in 33fcc59

Contributor

Azaezel commented Mar 2, 2015

quick followup: looks like the culprit is buried someplace in 33fcc59

@crabmusket

This comment has been minimized.

Show comment
Hide comment
@crabmusket

crabmusket Mar 2, 2015

Contributor

Shoot. Check the files that conflicted - there was a conflict I fixed that looked like some code in compiledEval.cpp had been deleted upstream, so I removed it, but maybe that was the wrong idea. Actually, looking through the changes now, it seems completely fine. Hmm. I'll try to reproduce later.

Contributor

crabmusket commented Mar 2, 2015

Shoot. Check the files that conflicted - there was a conflict I fixed that looked like some code in compiledEval.cpp had been deleted upstream, so I removed it, but maybe that was the wrong idea. Actually, looking through the changes now, it seems completely fine. Hmm. I'll try to reproduce later.

@crabmusket crabmusket added this to the 3.7 milestone Mar 2, 2015

@crabmusket

This comment has been minimized.

Show comment
Hide comment
@crabmusket

crabmusket Mar 2, 2015

Contributor

Caused by #1054, fixed by #1234.

Contributor

crabmusket commented Mar 2, 2015

Caused by #1054, fixed by #1234.

@crabmusket crabmusket closed this Mar 2, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment