General Category > Anim8or v0.98 Discussion Forum
Feature Request Thread
Water Music:
With regards "Morph targets in sequence editor": one slick way of pulling this off is by having a morph triggered by a bone motion. For example, a morph can be set whereby if a person's forearm is raised the bicep slides up the upper arm, proportionally.
My personal preference would actually be to combine the object editor, figure editor, and sequence editor together. It'd be easy enough to add buttons that toggle these aspects in the object editor. Advantage: if modifiable vertices were created to designate the end points of the bones then it would be a snap to rescale parts of one character to create another character, without having to re-bone and re-skin all of it from scratch. It'd also be easier to see how well joints hold up to movement and do any corresponding fine tuning - as you wouldn't have to keep changing screens and you could edit vertices mid-motion to get what you want. Mind you, that would entail quite an overhaul, but I think it would be worth it.
Thoughts, anyone?
Deepthought:
That would cause anim8or to lose forward and backward compatability.
besides if you combined the object editor with the figure and sequence editors, you couldn't reuse objects between multiple figures.
captaindrewi:
Tier 1
Please forgive if it has been asked already. a plus 1 if it has.
being able to undo after rendering would be nice.
TheBlackHole:
Can we get a way to place light sources in object mode? This would allow for parallel lights to precisely match up with suns in skyboxes, or headlights on cars, etc. I realize that objects in scene mode can be set as parents of light sources, but this would allow for more symmetrical light placement and light duplication.
Raxx:
There's something I noted about the renderer(s). The observations I make are coming from the attached file, if you were to use the scene and render from the camera view.
At 350x350 resolution, scanline rendering consumes around 1.9gb of memory. This value changes proportional to the resolution. Increasing the resolution further than 350x350 causes a crash, I'm guessing because it's 32-bit, and it's exceeding 2gb.
Ray-traced rendering consumes about 0.7gb regardless of resolution, so it seems that it'll never hit the 2gb limit.
So two things:
* Doesn't this suggest that scanline rendering could use better memory optimizations?
* We need a 64-bit version of Anim8orAny issues with my reasoning?
By the way, I added and +1ed where applicable.
TheBlackHole, I kind of object to the lights in object editor request, as it'd start blurring the lines between the object and scene editor, complicating things. Why not just +1 the copy/paste request for scene elements? Or better yet, request something like material-based lighting...
Water Music,
--- Quote ---With regards "Morph targets in sequence editor": one slick way of pulling this off is by having a morph triggered by a bone motion. For example, a morph can be set whereby if a person's forearm is raised the bicep slides up the upper arm, proportionally.
--- End quote ---
Did you want that as an added suggestion? As for the combination of the editors, I think it'd be better to combine just the figure and sequence editors. That way you can tweak vertex weights while animating, among other things, and still have a relatively clutter-free interface. Tossing the object editor into the mix seems like it'd require a major overhaul of just about everything, requiring the UI to be as complicated as blender, max, maya, etc.
kreator, so did you want something like F1 to go to the previous frame, and F2 to advance to the next frame? I think it'd make better sense to remap them to the [ and ] keys, or the , and . ones.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version