Fair enough, SkullboX
I can see why it might not be desired to be able to have multiple names for different node types.
That still doesn't explain why Maya's interface for managing Layers was spawned in hell though!
Oh, and those << | >> buttons for controlling column width ... GREAT IDEA
I'm no programming expert but I always imagined something like this would fix the problem.
//fake-code
Layer_1.rename('High Poly Helmet') would intelligently replace the spaces with underscores
or maybe add a label attribute to be the layers visible name in the layer area.
Layer_1.relabel('High Poly Helmet') and then the code would check to see where in the interface the rename call came from, and if it came from the layers area it would display the label instead of the actual object/node name. So you could still have a mesh object named "High_Poly_Helmet" while also having a layer named "Layer_High_Poly_Helmet_random1234" but the layer object's "layer_label" attribute would be displayed in the layers area as "High Poly Helmet" and renaming the layer just changes the label and if you wanted to actually rename the layer object itself you could do it with mel.
But then you could simplify that further as a function
renameLayer("High Poly Helmet", 'Low Poly Helmet', 'lph_layer');
// old label, new label, new node name
Explicit is better than implicit. The more you code, the more you realize that programming languages that 'automatically do things' such as replace spaces with underscores, or are 'smart' in other ways, make your life hell.
I heard talk of an updated UI or at least one that utilizes a new engine...not sure if it'll be in this Maya or next one though. But here's to hoping...
it would be nice if they improved the edge selection tools they mapped to the cursor keys in 2008. Why does it only expand to one edge loop if I hit right even though I selected two different edges in two different loops >:[
A raycast selection system would be a BIG one - at the moment even if you click 'pixel perfect' on an edge you can still select the one behind for some reason.
And what about a Connect tool ffs! It's not even in Maya2008!
haha I hear you on the connect, there's still no nice setup for that yet besides MJpolyTools but that's kinda slow.
True that on the selection too. I'd love a selection system like max implemented or something - where you can cycle through items based on their depth in relation to the camera.
btw, fmnoor, I'm not sure why you're having trouble with the edgeloop hotkey. It should convert every selected edge into its respective edgeloop. Are you using the "SelectEdgeLoop" hotkey in the "Polygon Select" category?
There is a dedicated "Wishlist" Forum on area.autodesk.com . But who knows if they really read it . Linky
They do, at least they did for 3dsmax. They included 1 thing I requested in 2009, Sound Trax. They went above what I was asking for and included Foley Sound. Granted its only available on subscription but will be included in the next.
It also might have helped that I talked to an autodesk presenter.
btw, fmnoor, I'm not sure why you're having trouble with the edgeloop hotkey. It should convert every selected edge into its respective edgeloop. Are you using the "SelectEdgeLoop" hotkey in the "Polygon Select" category?
Are you sure about that? Tapping right just selects the edgeloop for the last selected edge and then starts cycling between edge loops.
:thumbdown:
the default -> hotkey should be a sideways pickwalk, so I don't know what hotkey you're using.
If it's the hotkey called "SelectEdgeLoop" in the "Polygon Select" category of the window->settings/prefs->hotkey editor and it's not working correctly then I dunno what the problem is. The only time it should expand just one edgeloop is when you're using the "SelectEdgeLoopTool" as far as I know.
If reduce juggles specified resolutions by percent or vert count, preserves UV's and doesn't destroy the original model then yea, its the same...
I think (not around Maya right now) but reduce's nearest cousin is "optimize" inside of max. Multi-res is the next step up and polycruncher is the step up after that. Hopefully reduce isn't the forgoten bastard child that optimize is...
If reduce juggles specified resolutions by percent or vert count, preserves UV's and doesn't destroy the original model then yea, its the same...
I think (not around Maya right now) but reduce's nearest cousin is "optimize" inside of max. Multi-res is the next step up and polycruncher is the step up after that. Hopefully reduce isn't the forgoten bastard child that optimize is...
I am very sad to have found Maya lacking in all regards of modeling and game content creation (aside animation) to Max. How the hell for the last few years have Maya users honestly been trying to justify that this package is better than Max for modeling?
Give me all the fundamentals of edit poly and Nex/Poly boost, Pivot system and some basic history elements that will stay on top of the stack (history all Max) then they will be steering the modeling aspects of the package back on course.
You can do more with mel script sure.... but that doesn't mean the basic user should have to write everything themselves...
Spacemonkey : What I have gathered so far is the following. Most studios relying on Maya for modelling do so because some tech guys in the core team have an animation backgroud, hence obviously use Maya. Then, if you compare Maxs and Mayas modelling feature list 'on paper' they looks very similar, hence the whole studio uses Maya because it's 'just as good'.
I think this will start changing in the near future, as more and more users get familiar with hardsurface highpoly modelling done *fast* and realize that Max is way ahead of the league in that one specific are. (someone try to reproduce Per's mechs in Maya, at the same speed...)
Hardcore Maya users tend to say that it's okay, because one can script everything. But most of the time it's just way to time consuming and require skills that an efficient, dedicated artist shouldn't have to have.
As for the pivot editing thing, I totally agree. These days I FBX full meshes to Max just to edit pivots :P
I know what you mean. I set up an elaborate set of helper objects just to manage pivots when I was working in Maya last. Still wasn't a replacement, and took 3x as long, and wasn't nearly as precise. They started upgrading the pivot system in 2008 and I hope they carry over the rest in 2009.
As for animation, Maya does have some major advantages, but also some huge set backs. For every 5 great ideas they've put in, there are 1-2 real turds that have you scratching your head thinking hold on why hasn't there been an open revolt? Answer: You don't miss what you never had.
Hopefully more hardcore Maya users get their feet wet in other apps and raise holy hell for some of those features... Because they don't like listening to 3dsmax guys bitch about Maya...
i was a max user for nearly 10 years and just recently switched to maya a year ago. it really comes down to how you work, i am not saying i love everything about maya, and i had to change the way i did a number of things but i can honestly say after a year of using it i am no slower than i was in max. max is more forgiving and defiantly a less linear way of working, but after adjusting my processes and doing a bit of pre planning there is no loss of time that i can tell, i just work differently.
i wish maya would be broken up into smaller packages or modules. if i am a modeling and texturing i don't need bones, or rendering, or 90% of the shit in maya. as the program adds more and more features across the board the longer it takes to load and the more it crashes. i have been using silo a lot lately in my free time and if it can get a few more key features i will probably drop the uber 3d apps altogether when it comes to modeling. i would much prefer a specialized tool rather than a swiss army knife.
The pivot point thing Vig brought up (specifically that sweet-ass pivot location dropdown) is the last thing I miss from Max - I was going to post that here before I found out it was already mentioned. So I'd really like that little option for 'local to selection' deal.
Well, that and the modifier stack - history just doesn't cut it. Increased stability/performance and all of the other common sense things, of course.
I'd also really like a faster workflow for projection mapping - like ZAppLink is for Zbrush.
Ok, here´s one thing that all softwares are starting to have, XSI and new Mudbox will have so I think Maya 2009 could also have realtime ambient occlusion.
Well it doesn't...but here's the full feature list. Very cool release.
Assets: Assets are a new feature based on the existing container functionality. With assets, you can encapsulate a set of nodes in a container node and publish attributes from these internal nodes to the container. You can flag containers as a certain type and then use those types to limit what assets a specific artist can see using Views.
Assets promote encapsulation of data and black box design.
Once you have set up a container, you can save an XML template of its published attributes. Using these container templates, you can pre-plan all assets and their required attributes for your production.
Within a template, you can define multiple views that set up the user interface for the container. Artists can then use an assigned view as they create assets and bind their published attributes to the template.
Preselection Highlight: This feature provides a visual cue about the component that your mouse cursor is pointing to by highlighting the component in a different color.You can turn Preselection Highlight on and off by selecting Window > Settings/Preferences > Preferences and then Preselection Highlight in the Selection section.
Enhanced reflection: Reflection is now supported for the select tool. Additionally, reflection for all tools has been enhanced with additional options to give you more control of the seam.
Heat Map Display: You can now color nodes in the Hypergraph according to their performance in various metrics. This allows you to quickly identify computationally expensive nodes just by looking at the Hypergraph.
Transfer Attribute Values: You can now copy or transfer commonly named attributes between two objects using the Transfer Attribute Values option. You can also use this feature to copy incoming connections and outgoing connections which is useful for copying animation from one object to another.
Panel toolbar: You can now readily access many of the frequently used items that exist within the panel menus by using the panel toolbar. The panel toolbar rests below the panel menu in each view panel. You can toggle view the panel toolbar by pressing + + M.
Multi-component selection mode: You can now select faces, vertices and edges without having to change between selection modes. By selecting the new Multi selection mode, you can select components based on the mouse cursors proximity to them.
Camera-based selection: Camera based selection limits the components you can select to those which are unobstructed from the viewpoint of the current camera. This allows you to streamline selection so that you dont accidentally choose components that are hidden from your view, especially when viewing a scene in shaded mode.
Drag select: Drag select provides you with a new way to select groups components quickly and easily. Like the Paint Select Tool, it allows you to select components by moving mouse along a surface.
Moveable marquee select: You can now reposition a marquee select without redrawing the marquee by holding the key while dragging the marquee with the left mouse button.
Channel Box Enhancements: The Channels menu has now been divided into the Channels and Edit menus. In addition, new filtering options are now available in the Show menu to help you manage the attributes and objects that appear in the Channel Box. You can now filter by attribute types, or create your own filter types.
Transform tool marking menus: You can now access some transform tool specific features from a marking menu by holding CTRL + SHIFT + RMB.
Merge connections: You can now condense multiple connections from one node to another in the Hypergraph into a single bolded connection between the two nodes. This can greatly simplify the display.
Archive scene: You can now archive your scene and all its dependencies into a single zip file with the Archive Scene command. This is useful to ensure scenes work correctly when transferred between artists.
Customer Involvement Program: When you start Maya 2009 for the first time, the Customer Involvement Program (CIP) dialog box appears. The CIP collects information to help Autodesk learn how you use Maya. Your participation in the CIP helps design new features and helps improve existing features. You can choose to participate or stop participating at any time by opening the Customer Involvement Program dialog box in the Help menu.
Soft Selection: Soft Selection lets you include a weighted falloff area in your component selections. Its useful for sculpting a smooth object or making smoothly integrated slopes or contours to your model without having to transform each vertex manually.
You can turn on Soft Selection in the Tool Settings editor for any of the transformation tools.
Merge Vertex Tool: You can now merge vertices quickly with the Merge Vertex Tool by dragging from one vertex to another.
You can access the Merge Vertex Tool by selecting Edit Mesh > Merge Vertex Tool.
Smooth UV Tool: You can now interactively relax or unfold a selection of UVs in the UV Texture Editor with the Smooth UV tool. This allows you to perform these operations by dragging the mouse and offer instant visual feedback so you can judge exactly how much you want to relax or unfold.
Poly Count Options window: You can now choose to display a polygon count of either the objects in your scene or their cages.
Tweak mode: Tweak mode lets you quickly move components under the mouse cursor regardless of whether you are currently using the Select Tool, Move Tool, Rotate Tool or Scale Tool.
You can activate Tweak mode by holding on the keyboard and simultaneously dragging a component with .
Enhanced loop selection: You can now select edge loops by double-clicking a single edge or select face and vertex loops by selecting a face or vertex and double-clicking a face or vertex next to it.
Convert polygon edges to curve: You can now convert a path of polygon edges to a NURBS curve by selecting Modify > Convert > Polygon Edges to Curve.
Normal Average component movement: This option lets you select multiple components or objects and move them all along the average of their combined normals.
UV Texture Editor snapping improvements: You can now use snapping in the UV Texture Editor to lock your transformations to existing objects in the scene. You can also access a number of options related to pixel snapping by selecting Image > Pixel Snap > in the UV Texture Editor.
You can also use Discrete Rotate and Discrete Scale to rotate and scale UVs in specific increments.
UV Layout enhanced options: A number of new options have been added to the UV Layout Options window, which allow you to adjust multiple UV shells in a single UV space more easily. These options also allow you to offset your UV shells and scale them in the UV space.
Preserve textures during transformation: You can now transform components of a mesh without warping its texture. By turning on the Preserve UVs option in the Tool Settings editor for any of the transformation tools, Maya will automatically perform the appropriate transformations to the UV shell to maintain the overall look of the texture.
Bevel inside curves: You can now bevel within the bounds of a curve by turning on the Bevel inside curves option in the Bevel Plus Options window. Beveling inside a curve gives you more precise control over the overall size of a bevelled surface.
Animation layers: There is now a third editor in the Channel Box that lets you work with layers of animation. The Animation Layer Editor gives you all of the tools and options you need to create and manipulate animation layers.
Animation layers let you create and blend multiple levels of animation in a scene. You can create layers to organize new keyframe animation, or to keyframe on top of existing animation without overwriting the original curves.
Bake Simulation options: New options for animation layers have been added to the Bake Simulation Options. You can use these options, such as Smart Bake, to specify how you want to bake animation layers.
Maya Muscle: Maya now includes the powerful Maya Muscle skin deformer, which provides you with a complete set of tools for muscle rigging and deformation effects. To learn more, see Introducing Maya Muscle. The following sections summarize the new features provided by Maya Muscle:
Muscle creation: Maya Muscle provides you with streamlined muscle creation workflows using the Muscle Builder or Muscle Creator. These tools let you quickly and intuitively create, sculpt, and orient muscles in order to create convincing character rigs. Using the Muscle Creator window, you can create muscles by growing them out to a surface, mirror muscles from one side of a character to the other, and control the muscle shape at different phases of contraction.
Skin deformation: The main Muscle deformer lets you set up muscle and skin deformation, but it can also be used as a standalone deformer. To use the Muscle deformer as a skin solution for Sticky or Sliding weights, you can quickly apply default weights, then paint weights on the mesh when you need a higher level of detail. You can also mirror weights from one side of a symmetrical mesh to the other.
Re-use an existing skin set up: If you already have a rig set up with skin clusters, you can use Maya Muscle to add detail without re-creating your existing skin to joint weighting. Muscles Relative Sticky mode lets you use your existing skin cluster setup and focus your efforts only on areas that benefit from additional muscle and skin detail.
Along with the main muscle/skin deformation tools, Maya Muscle provides several standalone deformers that can be used for any number of deformation effects. For example:
* Simulate effects based on natural forces like wind and gravity using the Force deformer. See Force deformation.
* Create high quality, detailed displacement and sliding effects based on curves or a 2D image map using the displacement options. See Displacement deformation and rendering.
* Set up Jiggle effects directly on each point of your skin mesh. See Per-Point Jiggle deformation.
* Apply Relax and Wrinkle effects to a mesh. See Relax deformation and Smooth deformation.
Skin Collision: Several skin collision features let you simulate realistic skin collision effects. Smart Collision, Self Collision, and Multi-Collision give you options for controlling muscle and skin shapes when collisions occur. See Collision to learn more, or refer to the following topics:
Wrap deformer: Auto Weight Threshold option. A new wrap deformer option (Create Deformers > Wrap > ) automatically sets the optimal weight of the wrap influence objects shapes. See Auto Weight Threshold.
Volume Axis Curve: With Fields, you can now define an axis field region around a NURBS curve by creating a volume axis curve. Volume axis curves let you move particles and nParticles in various directions along the curve. When working with volume axis curves, you can now create a ramp to scale curve section radius along the curves axis.
Volume Trapping: Fields now include volume trapping attributes, which allow objects to be trapped inside volume fields. Volume trapping works with all volume shapes including cubes, spheres, cylinders, and volume axis curves.
Axial Magnitude: You can now create a ramp to scale field Magnitude along the axis of a volume shape field or volume axis curves.
nCaching fluids: Fluid caching is now done through nCaching, the Maya caching system used to cache nCloth simulation data. nCaching fluids improves caching performance, as well as uses a more efficient storage method for your cached files. As with the previous fluids caching, you can specify which fluid properties are saved in the cache file.
Improved fluid to polygon mesh conversions: The quality and speed of the fluid output mesh (that results from fluid to polygon conversion), as well as the interactive display of surface fluids have been greatly improved. New Output Mesh attributes allow you can control the resolution, smoothness, and speed of your fluid to polygon mesh conversions.
nCloth force fields: nCloth now includes Force Field Generation attributes. Force fields generated by nCloth can repel and attract nParticle objects and other nCloth objects. Force Fields are defined by the magnitude of the force field, as well as by the distance from the field generating object that the field is active. Passive collision objects can also generate force fields.
Stickiness: nCloth now includes a Stickiness attribute. Using Stickiness, you can adjust the tendency of your nCloth object to stick to other Nucleus objects (nCloth, nParticles, and passive objects) when they collide. Passive collision and nParticle objects also have Stickiness.
Convert nCloth output space: You can now convert the space of your nCloth output mesh to either world space or local space, depending on whether your nCloth was created for Local Space Output or World Space Output.
New particle generation system: There is a new particle generation system called Maya® nParticles in Maya 2009. nParticles use Maya® Nucleus , which is the same dynamic simulation framework that generates nCloth simulations. As part of the Nucleus system, nParticles interact and collide with nCloth and passive collision objects, as well as with other nParticle objects. You can use nParticles with Nucleus-based nConstraints to create particle effects and dynamic simulations that cannot be achieved with Maya classic particles. Like other Nucleus objects, nParticle objects are assigned to a Nucleus solver which calculates the nParticle simulation in an iterative manner.
In addition to Nucleus-based dynamics, nParticles can be used in place of Maya classic particles for particle goals, geometry instancing, and sprite effects. nParticles can also be manipulated by external non-Nucleus forces, including gravity and wind.
nParticle collisions: When nParticles objects are created, they are automatically capable of colliding with nCloth objects, passive objects, and other nParticle objects. With collisions between nParticles and nCloth, you can use the force of emitted nParticles to drive nCloth deformations. For example, you can create an nParticle rain effect with droplets that fall onto and deform the material of an nCloth umbrella. nParticles can self-collide, meaning that nParticles generated from the same nParticle object can collide and interact with each other. nParticle collisions can only occur between nParticles and nCloth or passive objects that are members of the same Maya Nucleus system.
nParticle constraints: You can use nConstraints to control the behavior of individual or emitted nParticles by restricting the particles movement or by attaching the nParticle object to other Nucleus objects. For example, you can constrain nParticles to an animated nCloth or passive object so that particle splatter, fire, or smoke effects move with the object. nParticles can be constrained using Transform, Component to Component, Point to Surface, Slide on Surface, and Force Field constraints.
Internal per particle attribute ramps: nParticles objects have internal per particle attribute ramps created on the nParticleShape node. The internal ramps simplify the workflow of setting per particle radius, mass, color, opacity, and incandescence. nParticle internal ramps work the same way as Maya texture ramps, but provide additional control for setting ranges of input values and randomized multipliers for output values.
The internal ramps per particle attributes can be deleted from the nParticle object when you want to set per particle attributes using expressions.
Generate force fields with nParticles: nParticles provide Force Field Generation attributes that allow you to generate force fields that repel and attract nCloth objects and other nParticle objects. nPartice force fields are defined by the magnitude of the force field as well as distance, which is the distance from the field generating object that the field is active.
Liquid simulation with nParticles: nParticles provide Liquid Simulation attributes that allow you to create nParticle objects that look and behave like liquids. Control over liquid properties, such as viscosity, allow you to create effects that range from fast moving waterfalls to slow rolling lava flows.
nParticle to polygon mesh conversion: Static and emitted Blobby Surface nParticles can be converted to polygon meshes. nParticle output meshes can be edited and manipulated like any other polygon. Before the conversion, you can use the Output Mesh attributes to set the quality of resulting polygon mesh. nParticle output meshes are useful for creating smooth flowing surfaces for realistic liquid simulation effects.
Multi-render passes for mental ray for Maya: The new multi-render pass feature provides an easy workflow for configuring render passes. You can render an unlimited number of render passes, and you can group them into render pass sets. You can also select a subset of the objects or lights in your scene to contribute to each render pass. This subset is called a render pass contribution map.
Using the multi-render pass feature, you can reduce the need to use render layers, thus reducing compute times for scene translation and actual rendering. If you work with complex multi-layered compositions, rendering may also be several times faster. Multi-render passes also allow you perform scene segmentation at render time.
Setting up your scene to use multi-render passes is simple. Follow these steps:
* Use the Create Render Passes window to create your render passes.
* Use the Passes tab under the Render Settings window to create and manage the render passes for each layer.
* Use the renderPass Attribute Editor to set the options for each render pass.
For advanced users, you can also:
* Use either the Render Layer Editor or the Passes tab to create your render pass contribution maps, then use the Passes tab to manage the render passes for each map.
* Group your render passes into render pass sets. Use the Passes tab to create a render pass set and the Relationship Editor (select Window > Relationship Editors or click in the Passes tab) to manage its membership.
mental ray Render Settings re-organization: The mental ray tab in the Render Settings window is now divided into 5 mental ray tabs, including: Passes, Features, Quality, Indirect Lighting, and Options, providing better organization for the mental ray controls. For example, if you need to tweak your final gather settings, you can simply go to the Indirect Lighting tab.
IPR improvements for mental ray for Maya: This section lists the IPR improvements for mental ray for Maya:
Light manipulation improvements for mental ray include:
* Area light changes: switching from a Maya to mental ray area light, shape type changes, changing of High Samples and Low Samples
* Deletion of lights
* Changes to light photon attributes such as energy and color
* Changes to photon attributes for the shaders and lights when caustics, global illumination or final gather is used
* Changes to shadow map settings, including switching from raytraced shadows to shadow maps and back, as well as shadow map format and file changes
* Duplicating a light or object by copying or duplicating a light or object as an instance
* Hiding and unhiding of light source instances
* Light linking and shadow linking
* Rotation of the IBL node.
Object manipulation improvements for mental ray include:
* Interactive creation of objects
* Duplicating a light or object by copying or duplicating a light or object as an instance
* Adding or removing a displacement shader and tuning of the displacement map shading network
* Adding and deleting or topology changes to geometry from the scene
* Changes to the Render Stats and mental ray render stats (under the objects shape node). Previously, onlychanges to the instance render stats (under the objects transform node) were supported.
Options improvements for mental ray include:
* Adding or deleting and tuning of a mental ray approximation node
* Creation of a camera and render camera change.
* Changing camera settings such as the angle of view
* Enabling and tuning the Depth of Field option for the camera node
You can also set IPR specific options such as the verbosity level for error messages by selecting Render > IPR Render Current Frame Options.
Stereoscopic camera: You can now add a stereoscopic camera to your scene. This allows you to create depth of field with the illusion of a three dimensional interface. Choose between various stereo modes such as anaglyph, checkerboard and horizontal interlace. You can render from the stereo camera and view the render output in any of these stereo modes.
For advanced users, you can also customize your stereoscopic camera by adding a custom stereo rig to your scene.
Elliptical filtering: Use elliptical filtering to perform high quality texture filtering and anti-aliasing when rendering with mental ray for Maya. Instead of using point sampling, elliptical filtering uses an area (an ellipse) to perform an image lookup. This ellipse contains many pixels, and the pixels are averaged and the average color is returned as a result.
Elliptical filtering in Maya is very simple to use. You can access its controls through the Attribute Editor of your file node.
Render proxies: Use render proxies with mental ray rendering to manage large scenes with complex geometry. Export your complex object as a mental ray assembly file, then replace it in your scene with a placeholder object that references this file. When you render, the exported object is loaded into memory and rendered with the rest of your scene. Translation time and memory usage are cut down, allowing mental ray for Maya to render large scenes.
Smooth mesh render: Previously, you could preview a smooth polygon mesh in the scene view by pressing 3. Now you can also render the smooth preview in mental ray for Maya. You can choose to use the same level of smoothing for the 3D viewport preview as for your render. Alternatively, you can also use a different division level for the two.
Particle rendering in mental ray for Maya: All attributes in the ParticleInfoSampler node are now supported when rendering particles in mental ray for Maya.
new mental ray Render Settings attributes: new mental ray 3.6 and 3.7 attributes have been added to the Render Settings, including: Importons, Irradiance Particles, Ambient Occlusion and Merge Distance for photons, caustics, and global illumination.
A Render Mode attribute has been added that allows you to render only final gather, or shadow maps, or light maps. In addition, flags that enable you to globally disable light maps and lens shaders have been added. The new BSP2 acceleration method is also available.
Final gathering now accepts multiple final gather map files. New rasterizer controls include: Rasterizer Transparency, Rasterizer Pixel Samples, and Rasterizer use Opacity. New motion blur controls include: Displace Motion Factor and Force Motion Vector Computation.
Render Settings window: Common tab re-organization
The Common tab in the Render Settings window has been re-organized so that there is a clear distinction between the frame and file attributes.
The Frame Buffer Naming and Custom Naming String attributes have been added so that if you are using the OpenEXR file format with the multi-render pass feature, you can customize the naming of the channels in your OpenEXR file.
Texture baking using multiple threads: You can use the Bake Optimization feature to select between baking using one thread per object or baking using multiple threads per object. The former performs better for baking multiple objects and the latter for baking a single complex piece of geometry.
Improved Maya Help system: The Maya Help is now faster and more easily searchable than ever before. New features include several new search methods, search highlighting, and the ability to save favorite pages for easy future reference. For more details, see Maya Help overview.
Very nice, a lot of the modeling tools people have been asking for (though now it's obvious what happend to 2k8 ex3). Tweak, Preselection Highlight, quick loop selection, drag select (raycast selection), and 'merge vertex tool' (target weld).
Very nice, a lot of the modeling tools people have been asking for (though now it's obvious what happend to 2k8 ex3). Tweak, Preselection Highlight, quick loop selection, drag select (raycast selection), and 'merge vertex tool' (target weld).
It's true these features were added in Maya 2008, but they have been improved on since then.
Replies
Linky
I'm no programming expert but I always imagined something like this would fix the problem.
//fake-code
Layer_1.rename('High Poly Helmet') would intelligently replace the spaces with underscores
or maybe add a label attribute to be the layers visible name in the layer area.
Layer_1.relabel('High Poly Helmet') and then the code would check to see where in the interface the rename call came from, and if it came from the layers area it would display the label instead of the actual object/node name. So you could still have a mesh object named "High_Poly_Helmet" while also having a layer named "Layer_High_Poly_Helmet_random1234" but the layer object's "layer_label" attribute would be displayed in the layers area as "High Poly Helmet" and renaming the layer just changes the label and if you wanted to actually rename the layer object itself you could do it with mel.
myLayer = getLayersByLabel("High Poly Helmet")[0].rename('lph_layer').relabel('Low Poly Helmet');
// ok, so I don't actually know mel.
But then you could simplify that further as a function
renameLayer("High Poly Helmet", 'Low Poly Helmet', 'lph_layer');
// old label, new label, new node name
And what about a Connect tool ffs! It's not even in Maya2008!
True that on the selection too. I'd love a selection system like max implemented or something - where you can cycle through items based on their depth in relation to the camera.
btw, fmnoor, I'm not sure why you're having trouble with the edgeloop hotkey. It should convert every selected edge into its respective edgeloop. Are you using the "SelectEdgeLoop" hotkey in the "Polygon Select" category?
They do, at least they did for 3dsmax. They included 1 thing I requested in 2009, Sound Trax. They went above what I was asking for and included Foley Sound. Granted its only available on subscription but will be included in the next.
It also might have helped that I talked to an autodesk presenter.
Are you sure about that? Tapping right just selects the edgeloop for the last selected edge and then starts cycling between edge loops.
:thumbdown:
If it's the hotkey called "SelectEdgeLoop" in the "Polygon Select" category of the window->settings/prefs->hotkey editor and it's not working correctly then I dunno what the problem is. The only time it should expand just one edgeloop is when you're using the "SelectEdgeLoopTool" as far as I know.
I think (not around Maya right now) but reduce's nearest cousin is "optimize" inside of max. Multi-res is the next step up and polycruncher is the step up after that. Hopefully reduce isn't the forgoten bastard child that optimize is...
I am very sad to have found Maya lacking in all regards of modeling and game content creation (aside animation) to Max. How the hell for the last few years have Maya users honestly been trying to justify that this package is better than Max for modeling?
Give me all the fundamentals of edit poly and Nex/Poly boost, Pivot system and some basic history elements that will stay on top of the stack (history all Max) then they will be steering the modeling aspects of the package back on course.
You can do more with mel script sure.... but that doesn't mean the basic user should have to write everything themselves...
/end rant
I think this will start changing in the near future, as more and more users get familiar with hardsurface highpoly modelling done *fast* and realize that Max is way ahead of the league in that one specific are. (someone try to reproduce Per's mechs in Maya, at the same speed...)
Hardcore Maya users tend to say that it's okay, because one can script everything. But most of the time it's just way to time consuming and require skills that an efficient, dedicated artist shouldn't have to have.
As for animation, Maya does have some major advantages, but also some huge set backs. For every 5 great ideas they've put in, there are 1-2 real turds that have you scratching your head thinking hold on why hasn't there been an open revolt? Answer: You don't miss what you never had.
Hopefully more hardcore Maya users get their feet wet in other apps and raise holy hell for some of those features... Because they don't like listening to 3dsmax guys bitch about Maya...
i wish maya would be broken up into smaller packages or modules. if i am a modeling and texturing i don't need bones, or rendering, or 90% of the shit in maya. as the program adds more and more features across the board the longer it takes to load and the more it crashes. i have been using silo a lot lately in my free time and if it can get a few more key features i will probably drop the uber 3d apps altogether when it comes to modeling. i would much prefer a specialized tool rather than a swiss army knife.
Well, that and the modifier stack - history just doesn't cut it. Increased stability/performance and all of the other common sense things, of course.
I'd also really like a faster workflow for projection mapping - like ZAppLink is for Zbrush.
It's true these features were added in Maya 2008, but they have been improved on since then.