How to decide which Fan age is first on Moulagain

[Tweek]

How best to decide which Age gets in first: Release the source. GoW writes the plugin. First to convert their Age gets the prize.

That or a fight to the death.

Then watch as the first Age converted is something that looks fresh out of a 3d game from 10 years ago...

I'd rather we picked one of the finer Ages to be added first to be honest, or draw a list up and have Cyan pick out of them.

[Trylon]

Hear Hear

[Grogyan]

I reckon an Age that was made for one of the Rapid Age Development contests would be great.
My apologies if the spelling is off, typing this on my phone

Zephyr cove
Tre'bdival
Bimevi

[Whilyam]

How best to decide which Age gets in first: Release the source. GoW writes the plugin. First to convert their Age gets the prize.

That or a fight to the death.

Then watch as the first Age converted is something that looks fresh out of a 3d game from 10 years ago...

I'd rather we picked one of the finer Ages to be added first to be honest, or draw a list up and have Cyan pick out of them.

Well yes, but the point is the get the source out before worrying about the Ages.

[kahinj]

Ditto what Whilyam here said.

"Kahinj"

[Aloys]

At this point unfortunately it looks like what Cyan wants to do first is to put an Age online..
Releasing the source will take a lot of time according to Mark. And somehow I think that it will be faster to adapt our own tools (whether Drizzle or PyPRP) rather than to wait for them.. (Isn't that how it has always worked anyway?)
In the end it might just be what they want: from what we know it looks like Cyan wants to put one (or more) Age online before the source are released as a 'proof of concept', and probably also to keep us busy in a constructive way. And if we do most of the work ourselves it's easier for them and everybody wins..

Do we have any idea of the amount of work it would require to adapt Drizzle and PyPRP for MOUL?

[Trylon]

From what I know of when I last did some work on it, I guestimate pyprp 1.5 could be Mulligan compatible within about a month, once work starts.
Don't hold me to that though, it all depends on who works on it, and how much time they can spend on it.

[ddb174]

It wouldn't take much work at all for Drizzle to convert Pots->Moul (aside from the cooked PhysX data, which I imagine will be changed if we get the source-code anyway.)

[ZURI]

I do hope you're correct ddb174. Myself and a few others have begun working on a new age from scratch. Due to MOULagain's recent startup and words of encouragement from Cyan about the plugin binaries coming out soon - I find myself in a predicament. I really want to begin modelling for the age, but I'm leary due to the uncertainties with the plugin.

On one hand, Blender is beginning to grow on me - but on the other hand, I have an opportunity to aquire a legal copy of Max V7. I'd really like to begin work on the geometry - but if the Max tools are really good, it may persuade me to jump the fence and start learning that instead.

In the meantime, I guess we'll keep working on ironing out the storyline and creating concept art.

[Ashtar]

It wouldn't take much work at all for Drizzle to convert Pots->Moul (aside from the cooked PhysX data, which I imagine will be changed if we get the source-code anyway.)

So I can look forward to that in Drizzle 24 then?