rdb
January 26, 2010, 10:13am
1
This major release introduces tons of cool new features. As it
is highly experimental, it is not recommended for production use.
Support for running Panda3D apps in a browser via web plugin
Fully automatic shadow mapping
Easy to use distribution and packaging framework
Integrated support for NVIDIA PhysX
Support for GLSL shaders
Geometry shaders, both in Cg and GLSL
Improved Cg support
Hardware geometry instancing support
Runtime fullscreen toggle
Unix/X11 resolution querying/switching support
Experimental Unix/X11 support for relative mouse mode (via xf86dga)
New, cleaner import conventions, replacing PandaModules
Parallax mapping
Support for OpenGL ES 1 and 2
Experimental Screen Space Ambient Occlusion
New collision solid: box
Working FreeBSD support
Blur / Sharpen postprocessing filter
Many improvements to the Shader Generator
Fixes and improvements to DistributedObject network system
New AI libraries
Added MeshDrawer2D
Most Panda objects now work with the pickle/cPickle and copy modules.
Windows build now compiled for Python 2.6
Tons of new features and bugfixes
Praios
January 26, 2010, 10:34am
3
Cool! …downloading…
Looks like the manual is not available packed for download anymore - is it still in developement?
rdb
January 26, 2010, 10:44am
4
Oh, forgot the manual and reference. I’ll do that tomorrow.
YAY! 1.7.0 *me let the update manager run" great job!
Congratulations on getting this out at long last
lethe
January 26, 2010, 12:56pm
8
Congratulations to all of you involved in getting this release out, and also for the new website. Between the two of them Panda is now giving a much better impression than it was as recently as a month ago. With a bit of luck panda will now attract an even larger user base, with all the advantages that brings:-D
b1g4l
January 26, 2010, 1:57pm
9
Yes indeed - thanks to everyone’s hard work in getting this release completed.
Anon
January 26, 2010, 2:14pm
10
Is it the one from “Snapshot builds”?
I don’t need that but looks cool.
Lazy me can use shadows now, thanks.
Window$?
Cool
Is it removed completely?
Interesting
Wow, how much time did you spend on this one?
great
Thanks to everyone involved into this release, seems very yummy
Good work!
ambyra
January 26, 2010, 3:22pm
13
I’m having problems with the ubuntu 32 bit build. First I was getting libcg.so problems so I had to download the nvidia toolkit. I’m surprised the deb didn’t require nvidia-toolkit as a dependency when I installed panda 1.7. Will this be a problem for other people trying to run my game online?
After I got the toolkit, I still get
Known pipe types:
glxGraphicsPipe
(all display modules loaded.)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
I have ffmpeg installed, and all the examples run now, but what are these errors?
I am also getting those exact errors. They are related to openAL. You can use fmod for now.
rdb
January 26, 2010, 5:20pm
15
Ah, sorry about that. Usually the dpkg system automatically adds dependencies. I’ll manually add this one then.
Nope, it does not affect the runtime.
These are errors in the audio implementation, not from Panda. I get these too, but I think you can safely ignore them. They are from pulseaudio or something like that.
big thanks. there are some VERY interesting new features in this release.
ambyra
January 26, 2010, 5:53pm
17
Great! I guess everything is okay then, but why are audio errors coming up when the audio isn’t even initialized, like in most of the demos?
rdb, sorry for picking at the problems before thanking you for the great new release. Thanks a lot!
rdb
January 26, 2010, 8:31pm
19
I’ve just fixed the Ubuntu debs - the nvidia-cg-toolkit dependency is added.
Anon:
Window$?
No, the PhysX integration is functional on 32-bits Linux as well. Even in the web plugin environment.
Thanks go to enn0x for writing the PhysX integration.
No, read the blog post. We do care about backward compatibility. We’re not Apple.
Because the audio library is always loaded, unless you specify this in Config.prc:
audio-library-name null