Moonlight|3D 0.5.5 Released

oxygene2k2 writes "I just finished the release preparations for Moonlight|3D 0.5.5. "Moonlight?" you might think, taking a look at slashdot's nice search function and see that there are two articles from 2000 claiming that it's dead. It's alive again and this release was made to show this. We hope to attract both users and developers with this. Take a look at the Release Announcement for the Mailinglist, our development site and the press releases in english, german, french, italian and spanish."

Comments

Alive after two years

[jbarket]

And here in two seconds, the slashdot effect will make sure nobody on the internet can tell the difference.

Ow, I bruised my bandwidth!

Re:KDE and Gnome all over again

[John_Booty]

We got Blender3d now. Why revive old corpses and divide the community again?

Yeah! Who needs choice? Screw that shit!

What. Is. It.

[rschwa]

, taking a look at slashdot's nice search function

You're joking, right?

How hard is it to say "Moonlight, the window manager", or "Moonlight, the animated series", or "Moonlight, the new journalling file system" in these posts?

I don't even bother clicking these links because the server is going to be buried anyway.

..another waste of posting space

Yes

[ekrout]

I wanted live-action, photo-realistic rendering of my friend during his football game.

So, rather than using a digital camera, I made the smart (and obvious) choice to have an art student draw some scenes onto a 3'x6' cow carcass with a palette of 16 different paints.

In hindsight, seeing how she intuitively grasped the essential elements and pared the decision tree makes me glad that I left my Canon at home!

EricKrout.com

Re:KDE and Gnome all over again

[Sabbath.sCm]

But the real point is, would KDE be so feature-rich and stable if GNOME wasn't there? Competition speeds up evolution, I think.

Re:Is this better than Blender?

[oxygene2k2]

well, in terms of features, Moonlight isn't as complete yet

why does it exist?
- because some stupid guy did not take the sources of blender in 1996 or so when he started moonlight
- because some other stupid guys liked moonlight and used it
- because it's easier to cope with without learning yet-another-GUI-paradigm
- because it's fun hacking it (blender doesn't even build yet afaik)
- because blender sources weren't free in january, when I started
- and finally, because I guess that the blender sources are much bigger and less understandable than source that was once meant to be open instead of some corporate beast that wasn't supposed to see the light

maybe some stuff like choice could be brought in to the discussion as well...

Re:Description?

[Azghoul]

Just curious, aside from branding, what the hell does "Excel" have to do with anything?

Or "Mozilla"? Or "350Z" :-D

Don't whine about a lack of descriptive names in OSS. They're everywhere.

Re:I don't get people sometimes...

[TitusC3v5]

Because Confucius say "Choice is good."

Seriously, though, why not? Yes, we have Blender, but we also have over a dozen window managers. Open source is about choice - if you like something stick with it. People tend to get all up in arms about KDE and Gnome, but it's easy to see that without each other, neither would have pressed to reach the level of functionality that both have attained at this point.

because...

[Patoski]

Moonlight 3D is a ray tracer and Blender is a scan line renderer. Blender will likely never have/be a raytracer natively (although export scripts to a few ray tracers exist). These are two *very* different approaches to rendering so by no means would I say that Blender and Moonlight are cut from the same cloth.

Best of luck to the Moonlight 3d team! Its a spiffy little app with a nice interface and plenty of potential!

Re:because...

[Patoski]

Yeah, I don't understand. In the end they both produce pretty
pictures of modelled objects, right?

Well, not necessarily (game modelers for instance don't make pretty pictures) but I'll see if I can explain myself a bit better about why these two approaches are so very different (and somewhat developmentally incompatible).

In the end that is the idea but there are many ways to skin a cat (or even a mesh). ;-) Scanline and Ray tracers are two approaches. Each of these approaches have their advantages and disadvantages. A scan line renderer for example is a fast renderer which generally produces nice looking results (by using shortcuts and certain assumptions). As a result of these shortcuts it is difficult or even impossible to implement some features well such as caustics or radiosity. A raytracer uses a highly accurate (but expensive CPUwise and render time) algorithm that calculates the paths of millions of beams of light and uses these paths to piece together a pretty picture. Using ray tracing you can implement the fancy stuff I mentioned earlier (caustics, radiosity, etc.) more accurately and generally more easily than you can in a scan line renderer. So basically raytracers are very slow but highly accurate but scanline renderers are fast and (at times) don't output highly accurate renders.

Also some other differences between Blender and Moonlight.

Moonlight 3D is more geared towards ease of use and to help newbies ease themselves into 3D w/a nice UI and basic modeling funtions.

Blender is currently geared towards the more experienced 3D artist with an ultra efficient UI (with a steeper learning curve) and a professional workflow that enables you to output tons of work easily (sometimes at the price of user friendliness).

These are two very different crowds that Moonlight and Blender are catering to. I think there's room enough in Free Software for them both. :-)

Re:because...

[FreeUser]

Moonlight 3D is a ray tracer and Blender is a scan line renderer. Blender will likely never have/be a raytracer natively (although export scripts to a few ray tracers exist). These are two *very* different approaches to rendering so by no means would I say that Blender and Moonlight are cut from the same cloth.

Best of luck to the Moonlight 3d team! Its a spiffy little app with a nice interface and plenty of potential!

As a Blender fan (who has purchased books from NaN in the past and donated some money toward freeing the source) I can only agree.

My hope is that any and all of the free 3d modelling and rendering projects will get together on the data side, either using standards (e.g. renderman format) or agreeing on a common format to use as a lingua franca. Ideally one should be able to do portions of their project in Blender, portions in povray, portions in Moonlight 3D, and so on. If history is any guide, each of these projects will have its strengths and weaknesses, and allowing them all to interact (at least at the data level) smoothly would be a huge boon to all of the projects in question.

Of course, having them all be able to provide 'expert components' for their areas of strength to some kind of a meta (or ueber) 3d authoring suite is probably too much to ask at this stage, but not too much to dream of and perhaps work toward down the road.

This is SWEET!!!

[cnelzie]

I played about with Moonlight 3D some time ago and found it far easier to use then Blender 3D.

To me, the user interface was quite simply far more user friendly then Blender is. (Of course, that is a matter of opinion and that is my opinion.)

Re:3D modelers

[aridhol]

This is somewhat simplified.

O(n) describes how the processing time of a problem increases when more elements are put into the input set. For example, O(n) means that when you add 1 to the input set, you add 1 to the number of loops at runtime.

O(2^n) means that for each element you put into the input set, the number of loops doubles. Thus, while an input set with 3 elements in it would loop 8 times, an input set with 4 elements would loop 16, etc. The number gets unmanageable fast - 10 elements = 1024 loops, 20 elements = 1048576 loops, 100 elements = 1267650600228229401496703205376 loops. Basically, it means that for any significant amount of data, don't expect it to be finished in your lifetime.

Documentation

[Screaming Lunatic]

For some constructive criticism. We can bitch and complain about Blender vs Moonlight and how it's KDE vs. Gnome (pick your favorite religous battle) all over again. The bottom line is that Linux needs an OpenSource 3D modelling package.

I have downloaded the source to both Blender and Moonlight. And I'm still banging my head to figure out how to compile and run the darn things. What these projects need is some good documentation and developers jumping on board working out features.

So who's with me? Here I go to join the dev maillist

checkerboards, curved mirrors

[helix_r]

If I see one more checkboard or curved mirror surface on "art" generated by a raytracing program I _will_ kill someone.