Guild of Writers

Considering this site has worked heavily on teaching people to make Ages through Blender... let's just assume that sometime before the end of this year we're given tools to create our own Ages.

Now, assume that these tools AREN'T based on Blender...

Will we continue to show people how to make Ages with Blender, as well as the other tools? Should the boards be set up to divide "Unofficial" and "Official" tools, with the Unofficial ones encompassing what we've already been using?

Just wondering :S

If we are allowed to use the blender-plugin to make content and put it on the server... I'm sure it'll be more powerful than what Cyan will give us.

I'm expecting some tool that is fully integrated into Uru and that they've been working on since the dawn of time. But, I highly doubt that we'll be allowed to export ages and pop them into Uru (getting fan ages on UU was a nightmare (this is why more shards did not have them)). I think the closest thing we'll get to Blender>Uru will most likely be something like: Blender>Obj>Age-Building-Toolkit>Plasma

I doubt though that Cyan will use 3dmax anything on us.

So, the current thing to do is stick with PyPrp and Blender. Now need to too eagerly ditch them. Really, Blender--IMO--is one of the best free 3dModelers out there.

I really don't know how messing with development of Plasma while it runs on their servers will work. *runs away* I hope that true devs can get the soucecode, the server (for testing) and some other things. This is NOT to say that just anyone who claims to be a dev should get this. I don't know how Cyan will keep the non-dev code-grubbers away ('cause the devs want the code too... if not more).

~Lontahv

What kind of tools do you think Cyan has?

Their tools are very similar to our own, except that Cyan's tools are all based on the expensive 3D Studio Max program. Unless Cyan is going to encourage the pirating of 3DS Max, or spend years writing their own 3D program that will never be as complete as Max or Blender, our tools will still be the ones that most people end up using.

And our tools will always be available to the public, through an open-source license, which makes them free for use.

Mmm, I guess you have a point there. The tools Cyan may give us should be similar.

I was just wondering the opinion of the Guild on this.

If you have to hope for tools from Cyan hope for the blueprints.

A gentle nudge when pydevs hit a wall on a new toy, ect.....

MustardJeep wrote:If you have to hope for tools from Cyan hope for the blueprints.

A gentle nudge when pydevs hit a wall on a new toy, ect.....

Why? We know how the vast majority of Plasma works... It's just exporting it from blender in sane way that's the issue.

Do you think a form/similar entity to Blender is used by Cyan? I hope not in my personal opinion, as no matter how many tutorials I try I still find it cumbersome

Paradox is correct. If you read the article it says Cyan has 10 game dev employees now.

Even if they had began building a system or program to make ages for Uru it would be next to impossible for them to develop or finish them in a timely manner. I wish people would come to their senses and realize that Cyan is never going to release tools for the public to use. It is obvious that they will rely on the brilliant people we have in this community to make that happen.

I have, up to this time, never heard one viable way for Cyan to release a tool set to develop ages for Uru. Face it. It was a pipe dream of Rands that probably never got off his ideas note pad.

BTW, Almlys and the developers here have created a tool that not only works, but is free, and in constant development. The plugin has improved leaps and bounds and there isn't any sign of it slowing down.

I believe it would be better for this guild to focus on making our tools even better so that Cyan isn't burdened with the task of developing tools for us. If , by some miracle Cyan does release tools, then we have 2 avenues to take in creating ages. More the better.

BAD wrote:Paradox is correct. If you read the article it says Cyan has 10 game dev employees now.

Even if they had began building a system or program to make ages for Uru it would be next to impossible for them to develop or finish them in a timely manner. I wish people would come to their senses and realize that Cyan is never going to release tools for the public to use. It is obvious that they will rely on the brilliant people we have in this community to make that happen.

I have, up to this time, never heard one viable way for Cyan to release a tool set to develop ages for Uru. Face it. It was a pipe dream of Rands that probably never got off his ideas note pad.

BTW, Almlys and the developers here have created a tool that not only works, but is free, and in constant development. The plugin has improved leaps and bounds and there isn't any sign of it slowing down.

I believe it would be better for this guild to focus on making our tools even better so that Cyan isn't burdened with the task of developing tools for us. If , by some miracle Cyan does release tools, then we have 2 avenues to take in creating ages. More the better.

Well, that sums up an answer for me :S

*reminds self to stop making "what-if?" threads*

Though it isn't out of the question that Cyan may eventually get us tools, I guess you're right. Blender is, right now, the best thing we have and can efficiently make Ages that work. So... I guess:

*Nek'rahm crawls into corner of the room and waits for thread to die*

Tsar Hoikas wrote:

MustardJeep wrote:If you have to hope for tools from Cyan hope for the blueprints.

A gentle nudge when pydevs hit a wall on a new toy, ect.....

Why? We know how the vast majority of Plasma works... It's just exporting it from blender in sane way that's the issue.

Because it would be nice to do something like:

#define DoorWayToHell {
object(doorDescription);
anchor(x, y, z);
open(anchor, theta);
closed(anchor, theta);
curState(open, closed);
}

and then:
pushDoorButton;
morphObject(DoorWayToHell(curState));

and let the engine swing/slide the door to its open/closed state rather than

pushDoorButton;
drawObject(DoorWayToHell(anchor, theta_1));
wait....
drawObject(DoorWayToHell(anchor, theta_2));
wait....
.
.
drawObject(DoorWayToHell(anchor, theta_N));

using a python script?

I reckon that with all the time you've put in to studying the code that you're potentially aware of what form object animators need to be in and the problem is still with the export from Blender. Don't you think it could be of benefit if Cyan would publish a formal API and perhaps some examples? Some of us may miss statements like; "it goes all wonky with big numbers" if the devs knew what the bounds of such numbers should be but surely, it would have to be beneficial if one knew those bounds in advance.

Hmm... That's some crappy sentence structure. If my thoughts would be clearer in English; let me know.