<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/cal3d/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/cal3d/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/cal3d/feature-requests/</id><updated>2006-02-03T17:28:00Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Cal3D viewer Proposal</title><link href="https://sourceforge.net/p/cal3d/feature-requests/23/" rel="alternate"/><published>2006-02-03T17:28:00Z</published><updated>2006-02-03T17:28:00Z</updated><author><name>xrenmilay</name><uri>https://sourceforge.net/u/xrenmilay/</uri></author><id>https://sourceforge.net0fb1e877dccb38725911eb7649ba497b1c3786eb</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I have been savaging the internet for a robust Cal3d &lt;br /&gt;
viewer and found one that was attempting to address &lt;br /&gt;
this issues. The viewer is an GPL version of the cal3D &lt;br /&gt;
viewer that can be found here. &lt;a href="http://purple." rel="nofollow"&gt;http://purple.&lt;/a&gt;&lt;br /&gt;
worldforge.org/~rtsan/entityforge/. &lt;/p&gt;
&lt;p&gt;However it is extremely buggy and unfinished. It &lt;br /&gt;
doesn't do xml file and really complains for every &lt;br /&gt;
minor problem with the cfg files. But most of the time &lt;br /&gt;
doesn't even want to work. After several attempts to &lt;br /&gt;
export cally files out of blender and preview them I &lt;br /&gt;
got extremely frustrated. &lt;/p&gt;
&lt;p&gt;So am begging on my knees with a plea for the cally &lt;br /&gt;
team to create a similar app with the tools that are &lt;br /&gt;
already in the mini-viewer and the demo version.  Or &lt;br /&gt;
maybe not but I am relatively ignorant when it comes to &lt;br /&gt;
programming &lt;/p&gt;
&lt;p&gt;Please, please, please can you guys hack something up &lt;br /&gt;
like the picture that I have enclosed. Essentially, &lt;br /&gt;
what I have done is hacked up EntityForge screenshot &lt;br /&gt;
with a few minor tweaks.&lt;/p&gt;
&lt;p&gt;cheers&lt;/p&gt;
&lt;p&gt;xrenmilay&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>information on the miniview</title><link href="https://sourceforge.net/p/cal3d/feature-requests/22/" rel="alternate"/><published>2006-01-31T21:37:56Z</published><updated>2006-01-31T21:37:56Z</updated><author><name>xrenmilay</name><uri>https://sourceforge.net/u/xrenmilay/</uri></author><id>https://sourceforge.neta3118928ecd6b9cad5844bb030c2bf756b42b5fb</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;A readme file on how to use the miniviewer. It needs to&lt;br /&gt;
contain what keyboard strokes and mouse controls do what.&lt;/p&gt;
&lt;p&gt;Need to improve camera controls similar to the Cally&lt;br /&gt;
demo file. &lt;/p&gt;
&lt;p&gt;Relative paths need work. Mine do not work for some&lt;br /&gt;
reason. PNG issue?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>maya 7 exporter</title><link href="https://sourceforge.net/p/cal3d/feature-requests/21/" rel="alternate"/><published>2005-08-11T18:03:28Z</published><updated>2005-08-11T18:03:28Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net9ee942d201885fa2cf22e90cd4021bf600d67254</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I was wandering when will the maya 7 exporter &lt;br /&gt;
appeared ? ver 7 is now avaible so it'll be nice to have &lt;br /&gt;
this plugin.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Callback function by drawing</title><link href="https://sourceforge.net/p/cal3d/feature-requests/20/" rel="alternate"/><published>2005-07-14T18:15:19Z</published><updated>2005-07-14T18:15:19Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netfc726acd1089e4ddb5c7c83be4d4e0bdb5ce80c4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi, folks!&lt;/p&gt;
&lt;p&gt;I'm new to Cal3D, but I must say: Respect. Very nice,&lt;br /&gt;
fast and pretty simple to use library. &lt;br /&gt;
But I am missing one feature that might be useful. How&lt;br /&gt;
ybout callback functions to outside of Cal3D by drawing&lt;br /&gt;
of every bone/submesh. This will help, for example: to&lt;br /&gt;
get the transformation matrix of the bone directly&lt;br /&gt;
before it will be drawn. So it might be used in vertex&lt;br /&gt;
programs or somewhere else.&lt;br /&gt;
If I do not find any other possibility to get the&lt;br /&gt;
transformed matrix, I will probably write my own. So&lt;br /&gt;
let me know if you want a path containing this changes.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CVS modules that contain not everything</title><link href="https://sourceforge.net/p/cal3d/feature-requests/19/" rel="alternate"/><published>2005-01-24T18:32:32Z</published><updated>2005-01-24T18:32:32Z</updated><author><name>F Richter</name><uri>https://sourceforge.net/u/res2002/</uri></author><id>https://sourceforge.net9a78954b0506bdf41fc570802f528e73ab4585e5</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Could some CVS modules that don't include all of cal3ds&lt;br /&gt;
subdirectories, esp. not the weighty data/ (and maybe&lt;br /&gt;
one with only src) be provided, to reduce the space&lt;br /&gt;
taken up by the source tree? (An example on how to do&lt;br /&gt;
CVS modules with only part of the files can be seen at&lt;br /&gt;
&lt;a href="http://cvs.sourceforge.net/viewcvs.py/crystal/CVSROOT/modules?rev=1.7&amp;amp;view=auto\"&gt;http://cvs.sourceforge.net/viewcvs.py/crystal/CVSROOT/modules?rev=1.7&amp;amp;view=auto\&lt;/a&gt;).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>getVertices(float *buffer, int ofs, int pitch) et al</title><link href="https://sourceforge.net/p/cal3d/feature-requests/18/" rel="alternate"/><published>2004-11-23T19:21:29Z</published><updated>2004-11-23T19:21:29Z</updated><author><name>igmon</name><uri>https://sourceforge.net/u/igmon/</uri></author><id>https://sourceforge.net4d1cb52fea5956c5b8c1c0e471092ff93a022ffc</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice to have an option to give an offset &lt;br /&gt;
where each item of the buffer start.  As well as the &lt;br /&gt;
pitch to get to the next item.&lt;/p&gt;
&lt;p&gt;Ex: getVertices(float *pVertexBuffer, int ofs, int pitch); &lt;/p&gt;
&lt;p&gt;struct Vtx { &lt;br /&gt;
float pos[3]; &lt;br /&gt;
float nrm[3]; &lt;br /&gt;
float tex[2]; &lt;br /&gt;
float tangent[3]; &lt;br /&gt;
}; &lt;/p&gt;
&lt;p&gt;Vtx buffer[1000]; &lt;/p&gt;
&lt;p&gt;getVertices(buffer, 0, 8); or &lt;br /&gt;
getVerticesNormalsAndTexCoords(buffer, 3); &lt;/p&gt;
&lt;p&gt;getTangentSpaces(mapID, buffer, 8, 0);&lt;/p&gt;
&lt;p&gt;that way I don't have to have a separate buffer for &lt;br /&gt;
other data such as the tangent space. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Option to hide non-bone nodes in skeleton exporter.</title><link href="https://sourceforge.net/p/cal3d/feature-requests/17/" rel="alternate"/><published>2004-11-11T06:19:17Z</published><updated>2004-11-11T06:19:17Z</updated><author><name>Chad Austin</name><uri>https://sourceforge.net/u/aegis/</uri></author><id>https://sourceforge.netb7949717a765cdf6c81218df97be3fc92740d865</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;There was a recent change that allows all types of&lt;br /&gt;
bones to &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Runtime GPL</title><link href="https://sourceforge.net/p/cal3d/feature-requests/16/" rel="alternate"/><published>2004-10-25T21:46:25Z</published><updated>2004-10-25T21:46:25Z</updated><author><name>Markus Elfring</name><uri>https://sourceforge.net/u/elfring/</uri></author><id>https://sourceforge.netb07149576810c78c7c8eaa95ab2c49141e5f54c6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Would you like to consider the "GNU General Public License with runtime exception" (RGPL)?&lt;br /&gt;
&lt;a href="http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/license.html" rel="nofollow"&gt;http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/license.html&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Loading of static models</title><link href="https://sourceforge.net/p/cal3d/feature-requests/15/" rel="alternate"/><published>2004-06-29T10:42:02Z</published><updated>2004-06-29T10:42:02Z</updated><author><name>Milan Plzik</name><uri>https://sourceforge.net/u/mmp/</uri></author><id>https://sourceforge.netc33bd2b930b57fea1dc34b5153d0a9fcb53df604</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Maybe this is a bit off-topic for library designed for &lt;br /&gt;
loading of animated models, but anyway, it would be nice &lt;br /&gt;
to support static models - without animation or even &lt;br /&gt;
bones. I know it is possible by creating a bone which &lt;br /&gt;
doesn't have any motion associated, but it isn't good &lt;br /&gt;
solution. With this feature, Cal3D could be without &lt;br /&gt;
hesitation used as the only model format for 3D projects:&lt;br /&gt;
)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Cal3d model loading from resource</title><link href="https://sourceforge.net/p/cal3d/feature-requests/14/" rel="alternate"/><published>2004-05-04T22:18:53Z</published><updated>2004-05-04T22:18:53Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.nete36474e5b178d8517b98c90088a04451b304cc38</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Would be nice to load Cal3d models from system memory &lt;br /&gt;
to better integrate with pack file systems.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>