It has been a little over a month since we’ve released Panda3D 1.10.0 along with the new website, and we’re excited to see the positive reactions. We’re glad to see that people are enjoying the new changes!
Of course, any major new release is expected to contain bugs, and we have to admit, there were a couple of pretty significant ones in the last release. We’ve been working really hard at fixing those bugs and this culminated in the release of Panda3D 1.10.1 last weekend. Thanks to all who have diligently filed bug reports!
We recommend that you upgrade to 1.10.1 as soon as possible. If you installed Panda3D using pip, this can be done using pip install -U panda3d, otherwise you can head on over to our download page and check out the latest downloads.
If you find more bugs, please don’t hesitate to report them on our issue tracker at GitHub! You can expect us to address them in additional 1.10.x releases in the future. Minor releases like this one are guaranteed not to break functionality and only address bugs and minor shortcomings. In the meantime, we have begun working on the new features of the upcoming Panda3D 1.11 on the master branch in the GitHub repository.
Below is the full list of changes:
- Fix crashes when gamepad is plugged in on 32-bit Windows
- Fix deploy-ng error regarding
exist_okon Python 2 - Fix Linux install from pip not working with some mesa drivers
- Fix compatibility issues with upcoming Python 3.8
- Fix regression with
Audio3DManager.setSoundVelocityAuto() - Fix issues when awaiting
loader.loadModelin Python 3.7 - Audio3DManager accepts tuple in
setSoundVelocity/setListenerVelocity - Fix lighting being disabled when only an AmbientLight is active
- Fix an error saving from Particle Panel in Python 3
- Depth buffer now defaults to 24-bit on macOS (fixes flickering)
- Fix no devices being detected on Windows with
threading-model - Implement collision tests from Capsule and Box into InvSphere
- Fix odd behavior and occasional crash in QuatInterval
- Fix SpriteAnim error in particle system
- Fix ShaderGenerator error when using too many shadowing lights
- Fix interrogate crash in Python 3 with optional wstring args
- Fix compilation errors for x86 Android platform
- Fix permissions of directories created by installpanda
- Improvements to API reference documentation
- Fix incorrect features printed out when printing an InputDevice
- Support cross-compiling for Android platforms in makepanda
- Work around various bugs when compiling with OS X 10.7’s libc++
- Fix wrong error sometimes being reported when loading plug-in
- Allow getting NodePath from CullTraverserData object
- Add config options to Assimp loader for generating normals
- Fix multisampling in floating-point framebuffers on OpenGL
- Parse egg files with 4-component tangents (must be 1 or -1)
StencilAttrib.make()write_mask argument is now optional
Any news on the timeline for the development of 1.11? A PBR shading system would be wonderful, and would bring Panda3D more up-to-date in terms of rendering and graphics. I realise that implementing this in a performant/flexible is not the simplest of tasks, but when can I anticipate a development build containing these features?
We’re still sorting out the details of the planning for 1.11 (I would personally expect it to be somewhere near the end of 2019 or otherwise in 2020), but since this is such a top-priority feature, I would be surprised if we didn’t already have a PBR material model in development builds sometime before autumn. No promises at this point, though; we want to make sure we do this right. We’ll keep you updated.