"Maetes" <nomail@nomail> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > in an earlier post you (Gio) mentioned your own CAD parser & exporter.  attached
> > is a per mesh sequence of images, same order as file; I modified the
> > 'FURGONE.inc' to have an array of meshes and rendered "an animation" of the
> > elements.  looks like we'll need a re-export, one which gives "us" :-) separate
> > doors etc.  cheers.
>
> Poor Gio. Actually, he just wanted to quickly revive his old code maybe in some
> free-hours, and now he keeps us (and himself) busy for days :)
>
> A re-export would be a great thing. The person's hair and shoes were in a mesh
> that I could easily separate because of the different Y values.
>
> With the car, however, it was much too complicated for me. I would love to
> separate the complete wheels or even doors to teach the car (or another) to
> drive and steer.
>
> Gio's Exporter combines all triangles in one mesh that have the same color (hair
> and shoes). If you could give different parts a slightly different color, they
> would be stored in separate meshes.
>
> I'll wait and see what you're up to and won't change anything about my
> programming.
> Unless new cars or people appear, then I probably can't stop myself ... :(
>
> Ma

Ok, thank!
well, the 2nd car is incoming soon, I have a bit of work to combine some *.inc
to make management easier.
And I noticed that over time my headlight on/off switch no longer works
perfectly (changed environment...)
About hair and shoes you are right! I will do it, I am updating the file with
smooth triangle. Soon it will be ready.
Tomorrow the second car and a bicycle that was in the same file inc.
Then we immediately arrange the "facchino"

About the parts, a solution should be found. For me it is easy because I have
done and continue an importer export tool working on pov - inc - STL - DXF -
SkUp
but there are two problems.
Sometimes bugs happen (rarely) where I know how to fix it immediately, but for
others it becomes frustrating.
Also I would not like to publish executable files, the web is a bad environment,
and I care about my good name, and I hate false positives.
Impossible also to publish the source code. By now it is very complicated and it
would take a lot of experience in the language I use which is not very
widespread (RapidQ).

I could think of small separated routines that could be easily compiled, but
everything relies on an internal my 3D system that receives the various types of
3D files, and then can return them in the required formats.
And this internal format construction is indispensable and a bit complex. So I
can't make small agile tools... I have to think about it...

BR
G.
oops we are a bit off topic lol

Post a reply to this message