Nancy sent us a cd of chess pieces and garden elements
I put them on svn.
They seem to be v11.1
I moved their image and materials into folders so they will have to be browsed for.

Wasn't sure where on dot project to put them so I put them in preproduction modeling

Garden
http://www.hash.com/dotproject/index.php?m...iew&task_id=608
Chess
http://www.hash.com/dotproject/index.php?m...iew&task_id=609

Thanks Nancy!

Noel

ps also sent her voice tracks she included to Charles

Excellent! Thanks Nancy and Noel.

I started updating the chess pieces to v13 but A:M won't update the material shortcuts in the models' groups. They continue to point at Nancy's v11 materials. Should I edit the models by hand to fix the links before committing the v13 versions?

Rhett

I'll play with it tomorrow and see what is going on. You are welcome to hand edit the files.

What specific file did you have this problem with?

I think you should just overwrite the v11.1 files with v13.0 files as we can always rewind to the original commit if we need the v11.1 files. Save won't let you overwrite the v11.1 files but I think save as will let you overwrite them.

Thanks

I was saving the v13 Models and Materials with "v13" appended to their filenames.

In SirCelerifer.MDL, for example, I saved it as "SirCeleriferv13.MDL" and the material it uses as "TinHorseHairV13.mat." The trouble was that SirCeleriferv13.MDL was still linked to TinHorseHair.mat which is the v11 version (It may be best that A:M work that way...). If I save over the v11 files (which I'll go do now) the problem should go away.

Hi Noel ,
Where ,exactly in SVN , have you uploaded Nancy's files ?

I've found nothing into:

TWO_project\data\Shared Data......???

I'm not following the dot project at all...so have I miss something or ??

Maybe you would make us a report status about nancy's stuff here ?:

http://www.hash.com/forums/index.php?showt...=0&#entry174444

thanks for your light

Al

Nancy's files are in data/Act 1/Shared Data/Models

Why are they located there ?
it doesn't seem to be at the right place isn't it ?

Why not in : prop/Nancy_stuff ....or something similar?

... just to know the logic of the thing


Al

"Nancy_stuff" is too specific, and they're only used in Act I, but in Sequences 3 & 5, so they go in "Act I/shared data".

...Well it's cause , I use to update my local SVN from the root shared data dir only and keep the Act area for later... it look faster...

If all Nancy's files are use in different set like in the throne room or in the garden ...those set are not located in the Act1/shared data ? so... I was under impression that we should keep model into modeling area ?
But I think modeler can just pick up what they need from there and include it to their different castle set...
So seen that way, Nancy models location is not very important after all ...but huh hep ho..
..anyway hehehe !


BTW I'm asking, is the final-set will be relocated into their respective "Act" directory once finished ? or?
this idea seem a bit odd to me at first tought but...I'll appreciate some light about this ?

....eh! oh! eeh! he he hee shoooot ...HE SCOOOOOOOOORE!!!!
...sorry ...watching TV...NHL

Thanks
Al

Good point about only having to update a single directory on SVN... Also, you're right, the other sets have not maintained the directory structure I'm talking about... Hmmmm... I think, given this, you should move Nancy's pieces to the main "Shared Data" directory before anyone uses them in their scene!

Does everyone see what Alain's talking about? TWO is so HUGE, that people only want to update what they are currently working on. Modelers just want to update the models, not all of Act I. If you agree, I'll change the directory layout guidelines in the Wiki.

p.s. Alain, don't forget to move Nancy's stuff to where you want it.

I completely agree. In fact, as an animator, I wish there was a way I could do without the materials and the images--and the non-proxy models, for that matter!

I don't think there's a solution for that, though.

It looks like animators need to update from two directories: the sequence they're working in, and occassionally the "Shared Models" directory.

Anymore comments or suggestions?

Hi

From the final set modeling point of view,
We work only on model in the root shared data...it's already complex enough that way.

We assume that animators will pick up their need from there
and update their project as we update set and related files there.

After that, if they want to copy their set files to a specific animation directory,
it's free to them...I don't see the purpose but we'll not update those directory...
the animator should be the one responsible for updating the files they use.

Martin,
I'll try to move those Nancy files into shared data /prop/nancy stuff.

Do I have to ok to do this ?

Thanks
Al

edit:

Ok Nancy's files are now moved to :

...data\Shared Data\Models\Props\Miscellaneous\Nancy_models

Thanks
Al

I see from a modelers point of view why you wouldn't want to have to get all of act1 for just its models.

But moving models only in act1 to shared data means that an animator who only wants models that are in all acts and the ones specific to act1 would get all of act2 and act3's models.

So what we could do is, make it like this:
[-]data
---[+] shared data (data in more than one act)
---[+] act1 shared data
---[+] act2 shared data
---[+] act3 shared data
---[+] act1 (chors etc)
---[+] act2 (chors etc)
---[+] act3 (chors etc)

That way modelers for act1 could just get act one models and animators for act1 would need act1 and act1 shared data.

I'll leave it up to you guys to talk it over and choose what to do. Remember to keep the data management part of the wiki up to data with what you decide. Also remember svn looses its history if you move or rename things locally so ask for my help if you need to rename or move a file or folder that is already on svn.

Thanks
Noel

I think animators only need to update the "Shared Data" folder occassionally when they really need something in it, and so a long download time getting a bunch of stuff they don't need is not too bad, but modelers never want animation stuff (huge), and they certainly don't want to go rooting around trying to find which local directory to update, so I'm not convinced by Noel's argument.

I see your point Noel ,

I'm not sure how animators procede actually but I would presume something like this :
... let say a modeler need the throne room set...
he import the action assembly .act of the set to his project... all related models should be mounted in the same time. he work with it , save his project...bingo

In the modeling area we update the related files of the action assembly, like pillars, wall, add new props to the action assembly etc etc.

So when the animator open his project he got all updated files since they are all linked.
Same thing for the characters...and free props

--------------------

I don't think there're models used in all Act ?
if a model repeat in many Act , no need to duplicate it but if an animator want to modify a props or something , he just have to work on a copy
...this copy can be store in the Act/shared data since it's the animator who initiate the change and he's aware of it.

IMHO no really need to duplicate every sets or props into Act/shared data...since they are classified into the root shared data dir.
We(modeler, texture) should work safely on the root shared data ...the animator should use their Act/shared data for their own use and search for update into root shared data...



well, we already have this kind of classification here :

\data\Shared Data\Models\Set_chors

It look the same but organized by Act... presently we organise things by sets: castle-throne-room, castle-outside, winkee village etc.

IMO those Act dir should be exclusive to animator ...when they want to extract a complete set or some specific part from the main modeling pipe...Or if they want to work on copy not on the originals sets...they still can get their update from the main pipe

So..this is how I see this, I'll comply with the procedure you go with anyway.
be sure to make it clear ....

hope what I' saying have sense ?

Thanks
Al

Just an idea, only would be usefull to reduce the amout an animator needs to update if there ends up being a lot of models that are specific to a single act.

EDIT: Was this resolved already? Oh well, here I go...

I think organizing props and sets by act would only create more places for contributors to overlook. One of the first things I made was the warning sign for Act2 Seq 2 and I put it in the Act 2 Seq 2 Models folder. Even though it was there a second version appeared in the main Props folder.

Since we don't have a master props/sets list for contributors to refer to, they look in the Shared Data folder on SVN as the authoritative resource.

I think props and sets ought to go in the root-level Shared Data folder. That way all the pre-production work (in this case the props and sets) are in one place.

I think that puts me in agreement with Alain

I just got to look at the fountain today that Nancy did on SVN.

WOW!

two thumbs up! Excellent work Nancy... I only wish to reach 25% of your talent.