On Thu, 13 Apr 2006 06:01:51 -0700
Arc Riley <[EMAIL PROTECTED]> wrote:

> On Thu, Apr 13, 2006 at 01:12:59PM +0200, Jiba wrote:
> > > You can use this function to set land materials using either a greyscale 
> > > or 
> > > indexed image.  I've tested it with several dozen materials.
> > 
> > I've included these two patches in CVS.
> 
> Thanks Jiba
> 
> Feedback on the Cal3d Morph-Target support?
> 
> I have a growing list, and unfortunetly, more cash than time at this point 
> with 
> this new business.  I'm thus defining a list of tasks which need to be done 
> in 
> short order (much of which are Soya3d enhancements or bugfixes) and assigning 
> either bounties or direct contracts to get them completed.

About bounties, my current status (French research allocation) doesn't allow me 
to have other remunerations thus i'm not currently interested myself :-(

> 3) Solid Translucent Objects (aka volumetric "fog") 
>   * for water, ground mist, nebula, glass walls, etc 
>   * there's already a section in the renderer reserved for the watercube..

SolidShape allows that, although they are still bugged.

> I know there's some things missing/broken in the ODE bindings (such as 
> ODE + Cal3d integration), Cal3d model posing (beside animations), and the
> exporters need a bit more TLC as well.  These are not issues effecting my
> immediate game-dev needs, however, but they should be defined as well.

About ODE, it seems that the ODE .c files in the release have been generated by 
an old Pyrex, that doesn't support GCC 4. However, CVS should compile.

> I believe we should adopt the standard "odd minor versions are development" 
> mode.  This means bugfixes get applied to 0.10 (prehaps for 0.10.3) and a 
> seperate tree for 0.11.x working toward a stable, well tested 0.12 release.

I'm not sure about that... The scheme would propose is not very frequent in the 
Python world, and the unstable version is just the CVS, isn't it ?


> We need better documentation (ie, a User Guide and API reference included), 
> testing on more hardware (I've recently found 2 popular cards which segfault
> under certain conditions in Soya), and some API cleanups before 1.0 release.

We also need to support 64-bits processors, but i have no such hardware... do 
someone have some ?

Jiba

_______________________________________________
Soya-user mailing list
[email protected]
https://mail.gna.org/listinfo/soya-user

Reply via email to