Skip to content

D
deprecated-irrlicht-mac
Switch branch/tag
  1. 08 Aug, 2015 1 commit
  3. 31 Jul, 2015 1 commit
  5. 29 Jul, 2015 1 commit
  7. 13 Jul, 2015 2 commits
  9. 05 Jun, 2015 1 commit
  11. 04 Jun, 2015 1 commit
  13. 28 May, 2015 1 commit
  15. 11 May, 2015 1 commit
  17. 06 May, 2015 1 commit
  19. 05 May, 2015 2 commits
  21. 29 Apr, 2015 1 commit
  23. 27 Apr, 2015 1 commit
    • cutealien's avatar
      CAnimatedMeshSceneNode::setMesh does now set the animation speed again to that of the mesh. · e138121a
      cutealien authored 
      .x meshloader regards now AnimTicksPerSecond (thx @qian for a test-model and bugreport).
CAnimatedMeshSceneNode::setMesh had commented-out the setAnimationSpeed line in version r3526 which was about a joint-cache fix for skinned meshes. But there was no comment about why that line had to be removed or commented out, so my guess is that this was only a test (I hope). And it caused animation-speed values for the meshes to be ignored unless user specified it explicitly while animation range was still changed in setMesh.

git-svn-id: svn://svn.code.sf.net/p/irrlicht/code/trunk@5097 dfc29bdd-3216-0410-991c-e03cc46cb475
      e138121a
  25. 25 Apr, 2015 1 commit
  27. 24 Apr, 2015 1 commit
  29. 20 Apr, 2015 1 commit
    • cutealien's avatar
      Cameras return again an empty boundingbox (at 0,0,0) instead of returning the... · c6eec21c
      cutealien authored 
      Cameras return again an empty boundingbox (at 0,0,0) instead of returning the frustum boundingbox. Thx @robmar for reporting this.
You can still access the frustum boundingbox through the frustum itself.
Also CSceneCollisionManager collision functions ignore now empty collision boxes.
This means cameras no longer show up in the node-collision of the SceneCollisionManager.
Tests have been adapted correspondingly.
Note that this behavior was once before changed in Irrlicht (rev. 345). But it was one of many changes and there was no documentation or log-message about why anyone would like
the cameras to show up in node-collisions based on their frustum boundingbox. Without any hints about the why I decided to change it back as it's just confusing.



git-svn-id: svn://svn.code.sf.net/p/irrlicht/code/trunk@5094 dfc29bdd-3216-0410-991c-e03cc46cb475
      c6eec21c
  31. 17 Apr, 2015 1 commit
  33. 16 Apr, 2015 1 commit
  35. 15 Apr, 2015 1 commit
    • cutealien's avatar
      Fix a problem in IrrlichtDevice::setResizable that caused window titlebars to... · 3ef49054
      cutealien authored 
      Fix a problem in IrrlichtDevice::setResizable that caused window titlebars to hide occasionally under the taskbar in some systems (Ubuntu, Mint).
This was caused by quick calls to XUnmapWindow followed by XMapWindow which some WM's can't handle. 
Adding a long sleep call (~200ms) in between would have been a workaround, but looked ugly as the window is hidden in the meantime.
I found no reference in X11 documentation that unmapping is necessary for this, so I removed those calls now.
Changing the resize flags still works in my tests on Debian and Ubuntu. If it causes problems we have to switch to the ugly hack 
or get certain systems to repair their window managers.



git-svn-id: svn://svn.code.sf.net/p/irrlicht/code/trunk@5091 dfc29bdd-3216-0410-991c-e03cc46cb475
      3ef49054
  37. 12 Apr, 2015 1 commit
    • cutealien's avatar
      Update test drawVertexPrimitives · ce863d10
      cutealien authored 
      - new media for OpenGL-drawVPL_h. This test is about finding out if things changed, and this result has been like it is now at least since 1.8
- required match can be reduce for this test, as minor aliasing artifacts always are different between cards and don't matter here.

git-svn-id: svn://svn.code.sf.net/p/irrlicht/code/trunk@5090 dfc29bdd-3216-0410-991c-e03cc46cb475
      ce863d10
  39. 11 Apr, 2015 3 commits
  41. 10 Apr, 2015 2 commits
  43. 09 Apr, 2015 4 commits
  45. 08 Apr, 2015 3 commits
  47. 07 Apr, 2015 1 commit
  49. 06 Apr, 2015 2 commits
    • cutealien's avatar
      Add a new flag for controlling zbuffer writing to SMaterial. · d2169fc4
      cutealien authored 
      In 4774 we tried fixing zwriting for shader materials as those are ignored in SMaterial::isTransparent.
This affected too many existing projects and made it hard to still write to zbuffer in some situations where it was necessary. So trying now another approach which brings back old functionality mostly, but allows users to have more fine-control with a new flag. Using an enum instead of bool for the new flag as it's foreseeable that more options might be necessary for this in the future.
Note: Several tests are currently failing, but they did that before, so that has to be debugged on it's own.


git-svn-id: svn://svn.code.sf.net/p/irrlicht/code/trunk@5076 dfc29bdd-3216-0410-991c-e03cc46cb475
      d2169fc4
    • cutealien's avatar
      Update test-media for a test where the result is fine. · a1cf2945
      cutealien authored 
      This is only about position of image elements and it failed because elements are now a little brighter. Probably due to some fix in the driver at some point, but not related to this test.

git-svn-id: svn://svn.code.sf.net/p/irrlicht/code/trunk@5075 dfc29bdd-3216-0410-991c-e03cc46cb475
      a1cf2945
  51. 02 Apr, 2015 1 commit
  53. 01 Apr, 2015 2 commits
  55. 31 Mar, 2015 1 commit