Page 4 of 6

Re: Help decide what should Cyan release next

Posted: Fri Feb 19, 2010 2:37 pm
by Paradox
The plugin source would be most useful to us in trying to get PyPRP exporting all features correctly, and compatible with MOUL.

Re: Help decide what should Cyan release next

Posted: Fri Feb 19, 2010 3:02 pm
by Jishin
Seriously, I'm just wondering -- why can we *not* get both the binaries and the source for the Plasma plugin? It seems natural to me to release both at the same time, so you can compare what the code says it does to how it actually works in practice.

Please, someone 'splain, 'cause I'm confused.

Re: Help decide what should Cyan release next

Posted: Fri Feb 19, 2010 3:07 pm
by Marcello
Without hesitation: source!

The number of people who will be able to lay there hands on Max will be limited. The community will be better of with a Blender pluging that can export everything the Max plugin can.

Re: Help decide what should Cyan release next

Posted: Fri Feb 19, 2010 4:50 pm
by Trylon
If the choice is solely between plugin source or plugin binaries, my choice will be source, since source builds binaries.

Otherwise I still agree with chacal that we could use server binaries better than either plugin source or plugin binaries. (We already have the client binaries ;)

(Might want to change this in your tally Robert)

Re: Help decide what should Cyan release next

Posted: Fri Feb 19, 2010 5:02 pm
by Chacal
Robert The Rebuilder wrote:Chacal and Trylon: I hear ya. But because Mark said:
the next goal should be to get one or more of the fan created content on the MOULagain servers. To me, that would show the most promising thing about the entire project.

we gotta leave servers for later. So, I put you down for plug-in binaries.


Sorry, no. What Mark said does not mean "we gotta leave servers for later". Quite the opposite.

A test server is a required step for reaching Mark's goal cited above. Plug-in sources or binaries are not.
Even if they were, a test server will help us reach that goal quicker.

Also, I have sorted the steps according to the most important criterion: ability for Cyan to deliver.

Re: Help decide what should Cyan release next

Posted: Fri Feb 19, 2010 6:16 pm
by Robert The Rebuilder
Jishin: good question. I'll speculate that even if they were to release their 3DS Max v4 (?) plugin binaries as-is, they still have to write a EULA for it. Not nearly as much work as sticking a license declaration at the top of each source file and ripping out PhysX code, but still an effort none-the-less. But that' s just speculation.

Trylon: I updated the OP.

Chacal: Here's my line of reasoning. Since Mark said that they want to get fan created content on the MOULagain servers, I interpreted that to mean that they would be bold enough to use their servers as the test servers. Might the servers crash if we give them a poorly written/converted age? Possibly. But it seems - to me, at least - they're willing to take that risk. Reading Mark's statement that way - "we have the test servers already" - is why I said we can leave the servers for later. But I admit that's my own line of reasoning. Also, if we open this up for a debate as to servers vs. plugins, we'll fracture even more - and we can kiss the consensus goodbye.

However, I don't want to misrepresent your opinion. So, do you want me to count you as plugin binaries, plugin sources, or 'abstain' (because you'd prefer the server binaries/code instead)?

Re: Help decide what should Cyan release next

Posted: Fri Feb 19, 2010 7:31 pm
by Robert The Rebuilder
UPDATE: I had thanked Mark for his reply and told him about this thread. He sent the following reply:
Chogon wrote:I wish it was as simple as putting the binaries in my left hand and putting the source in the right hand and just let y'all choose. Releasing the source to the 3ds max plugins *is* a giant step. I know a lot of people will complain that we are not making big enough steps fast enough but it is still a trolling motor on the back of the cruise ship. We would love to just jump to the completed MOULa/MORE/OSMOUL. But we are stuck doing small steps.

We do have 3ds plugin binaries that could be released right now (or something close to now), except they are for 3ds Max version 7. We do have a requirement for a different project (MagiQuest Online) to update the plugins to the latest 3ds max. So, theoretically, the MOUL 3ds plugins could be converted at the same time with little added cost/time.

And as I said, we have not finalized what the next step will be but I think we are leaning towards this. And we realize that most of the user-created content writers will not have 3ds max but there are a number that do have 3ds max or the means to acquire it. And taking a select few user-created Ages and getting them on the MOULa servers will provide a lot of good information on what the next steps should be.
And please, don't think just because we do a particular small step that all other steps to the final goal have somehow dropped off the table. We will get there, and there will be a step that includes the source to the plugins.

Thanks,
Mark


I was going to reply, asking if they could release the 3ds Max v7 plugin binaries when they're ready. But before I send the reply, do any of you have questions for Mark/Cyan?

Re: Help decide what should Cyan release next

Posted: Fri Feb 19, 2010 8:40 pm
by Jamey
How should we, or how will Cyan, decide which fan-created age(s) would be released in MOULa first? Should we submit them to Cyan? How will that work?

Re: Help decide what should Cyan release next

Posted: Fri Feb 19, 2010 8:51 pm
by I.Brattin
I would like to know if their going to write tutorials to go with the binaries?

Also something else I would like to know is whether or not the 3DS Max v.7 binaries are compatible for 3ds Max 2009?

Re: Help decide what should Cyan release next

Posted: Fri Feb 19, 2010 8:52 pm
by Paradox
I.Brattin wrote:I would like to know if their going to write tutorials to go with the binaries?

Also something else I would like to know is whether or not the 3DS Max v.7 binaries are compatible for 3ds Max 2009?


No and no.