Carcerian wrote...
Well, d20 modern (The material in question) is a very similar situation to CEP, a lot of older content made by different artists of varying skill and ways of doing things. It was proposed to run content thru CM to optimize for a future PW project.
Yeah yeah but there's a
difference: Both the models in CEP and Babylon
were "worked over" (by hand, in Max, or using CM3 or some other tool) in ASCII and then compiled. Decompiling and then mass-manipulating them is not necessarily going to be a wise or flawless process without some specific fix in mind in the first place.
Anyway, in any case where you're dealing with a rag-tag corpus of models which have, more or less, existed in ASCII and
never been worked over by something like CM3, then that's when a tool like CM3 (or any other mass manipulation process) could potentially give the
greatest benefit with the least likely harm done. And, at least in some capacity, that's what I believe Acaos did when he was cleaning up the models from CEP 2.0 in preparation for CEP 2.1, and then moving forward.
The above is why decompiling models currently in CEP or CTP Babylon and re-using CM3 on them is not necessarily a good idea but why, with something like D20 which (AFAIK) has never been cleaned up, it could be. Even then, though, CM3 is a tool to assist a competent modeler and isn't a substitute for one.
Proleric1 wrote...
From the context, am I right to assume that your objection only refers to the use of Clean Models?
Clearly, there are many other reasons for "decompilation and mass-manipulation", such as my proposed fix for Mounted Skeletons, which I trust is not a cause for alarm.
Not really specific to CM3. CM3 is just the easiest one for people to get themselves in trouble with.
CM3 is kind of like the sorcerer's hat in the
Sorcerer's Apprentice. Mickey snatches the sorcerer's hat at night and uses it to solve very
specificific issues which make his life easier. For the most part it works out well for him- though there
are unintended consequences on occasion. But the real trouble starts once he gets lazy, falls asleep wearing the wizard's hat and,
dreaming he is the wizard he is the apprentice to, waves his hands in ever grander jestures which cause all manner of havoc to occur.
+
=
I want to avoid a situation where people dump models
en mass from CEP, run them through CM3 not really understanding what they're doing, and then turn around and dump
those on The Amethyst Dragon and say "Here.
I fixed these 500 models for CEP!" and then have the burden on The Amethyst Dragon to figure out what, exactly, happened and make an evaluation about if some benefit was actually achieved.
I've already said quite a bit on
the model health of the existing CEP content and
unintentionally going down the rabbit hole with CM3 so I'll just kind of link to those instead of going on about it.
When it comes to any modification of prior CEP content, I have
no problems with
specific plans of
limited scope to fix
signifigant or glaring errors. Frankly, I don't think anyone should even mention digging back into the prior CEP content unless they can make a reasonable petition to do so which meets the criteria of the three things I bolded above. It just seems like a good, common-sense approach given the situation. One that shifts the balance of the burden more from the Amehtyst Dragon to those desiring to make changes.
Modifié par OldTimeRadio, 01 février 2014 - 05:30 .