Advertisement
Guest User

kek

a guest
Apr 18th, 2015
217
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.64 KB | None | 0 0
  1. Okay, so. We merged 3 branches to master to get lights and all that junk in. There was a bug with mine and Albin's graphics cards that made the model matrices not function, but we fixed it. Worked on Albin's computer, and Emil's, and Johan's... but mine. Ooooooh boy. Mine.
  2.  
  3. See, all the collision worked. The models were in the "right places". Right was right, left was left, up was up and so on and so forth. Everything loaded right. Just that, uh. Every single model was slanted 45 degrees to the right, making everything look like what you might see if you took too much LSD. It was terrifying.
  4.  
  5. We tried everything. Doing the ViewProjection-multiplication CPU side, removing the geometry shader for-loop and emitting vertices one by one, clean solution, removing the view matrix (would not recommend), removing the projection matrix (would not recommend), updating my drivers (which I needed to do anyway). Nothing. Fucking worked. So, you know what? Fuck it, let's go back in gitk and see WHERE the error starts happening.
  6.  
  7. We went back to the middle of the Light branch. Worked fine. Alright, next step. Worked fine. Step by step, we went closer to the merge, and nowhere along the line did the glitch occur. Alright, so the merge to master? All fine. The small Shrine fix I put in after that? Completely fine. The, uh. The map chunk file edit, the last change before my project would be up to date again?
  8.  
  9. Completely fine. The problem never occured again and we have no idea what caused it.
  10. [2015-04-17 21:48:11] Kraetyz, God Warrior: So, when grefix break: Go back in Git, then go forward again. 10/10 tried and true solution. Don't CHANGE things, whatever you do.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement