Narann

My feedback

  1. 2 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Narann shared this idea  · 
  2. 62 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas for Maya forum » scripting & API  ·  Flag idea as inappropriate…  ·  Admin →
    Narann supported this idea  · 
    Narann commented  · 

    The main idea is to help new scripting artists to jump in Python directly.

    In the MEL era, getting and analysing script editor output what the first thing you where doing while learning scripts.

    A simple python-formated output whould really help new scripters not used to documentation.

  3. 108 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Narann supported this idea  · 
  4. 18 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Narann commented  · 

    Wow! I just understood why instances was so slow! It's a shame default shading group have to had real connections on millions of nodes. :(

  5. 50 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback on this idea. It’s under review. (This does not mean that we are committing to this idea. Please read the FAQ for more detail.)

    Narann commented  · 

    The simple you do the faster you are. As @Roland Reyer mention, doing such effect is not free. Having a such effect on massive scene can drastically decrease performances.

    That's why it shouldn't be ON by default.

    However, It's definitely a valid request from a modeler perspective. Modelers often work on specific asset and such display could definitely help them. A way to switch to this effect would be very interesting for them.

  6. 4 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Narann shared this idea  · 
  7. 38 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 48 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Narann supported this idea  · 
  9. 3 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Narann shared this idea  · 
  10. 2 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Narann shared this idea  · 
  11. 377 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Ideas for Maya forum » file import/export  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous responded

    thanks for the feedback – please make sure to log the bugs and add any that you feel strongly about to uservoice

    question to the voters: how many of you are developers that would contribute to such an initiative? I would like to get a better feel on how much this reflects “FBX needs improving” vs “I want to personally extend FBX capabilities”.

    for the devs, make sure you fill out the API survey http://area.autodesk.com/blogs/cory/our-annual-api-wishlist-surveys-are-now-live

    Narann commented  · 
  12. 44 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Narann commented  · 

    Amazing idea!

    If I can have a suggestion, default values should be defined "by user". :)

    Narann supported this idea  · 
  13. 41 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Narann commented  · 

    @Mr-SaMsOoM
    I've tested on Maya 2013 and it doesn't work... :(
    ctrl+middle mouse button

    A left mouse button entry "Reset to default" (like houdini) could be great. :)

    Narann supported this idea  · 
  14. 211 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks to everyone who’s voted on this issue. It is being moved to the Ideas for Maya forum, because although it’s annoying you, it’s not a small thing to address.

    Enjoy spending your Small Annoying Things to fix votes on other ideas!

    Narann commented  · 

    For information: In VRay, when you're rendering, "undo" seems to be disabled. I'm not sure you can enable "undo when rendering".

    Narann commented  · 

    Sorry for my bad words. I was just very suprised to see the problem is not only technical but also "an assumed choice".

    Narann commented  · 

    Are you serious? I can't believe what I am reading... You really "block" this because of "users don't understand what they do?", this is not a technical problem to unlock this? o_O

    I completely agree with Matthew, Maya is a professional software.

    VRay handle render in a separate thread, you can change parameters while the render is computing in your render view and this is very useful to change settings while you discover your render, even if the settings you are changing will operate on the next render. This is a very pleasant workflow. You save a lot of time!

    If the user experience really can't "think" about this. You could provide an option in preferences to let peoples "that know what they do" to launch render in separate thread.

    Narann supported this idea  · 
  15. 53 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. 4 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    @sebd_856: This has been moved to the Small Annoying Things to Fix forum, because it’s small enough scope.

    Enjoy using your Ideas for Maya vote on something else, thanks.

    Narann commented  · 

    Override the Python "import" behavior could be really bad.

    I personally use:

    reload(subModule1)
    reload(module1)

    etc...

    This could be boring but this is the pythonic way. :)

    I'm not even sure automatic recursive reloading is possible in python without add instability. :(

  17. 185 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    To all the people who are entering great comments: If you feel strongly about an idea you mentioned, please enter it as a separate idea in the forum. Getting a more specific understanding of concrete ideas we can address is more helpful than general ideas.
    -————
    Thanks for your feedback on this idea. It’s under review. (This does not mean that we are committing to this idea. Please read the FAQ for more detail.)

    Narann commented  · 

    As I can't create a new "Idea" (I don't know why...) as you purpose, I put my list there:

    - A threaded Render View to be able to manipulate Maya stuffs during rendering.
    - A well tested and crash safe progressive rendering in the Render View because now, many will use progressive rendering to have a quick feedback of the whole lighting.
    - You should be able to click on a pixel and have a menu with three entry: Material/Light/Geometry (and maybe others like Textures). Each of this three entry should list a list of material/light/geometry used by the samples of this pixel. Once you've selected a material/light or geometry from the list, it should show it in the Attribute Editor. This is a major feature that could increase a lot the whole rendering workflow.
    - Possibility to display render layers directly in the Render View.
    - In a "Render history list", you should have a list of every render you've made (with thumbnail of course), this list should stay, even if you close your session. A button with "clear render history" could be provided.
    - From this render history, you could define a "A" and a "B" render (see the next part).
    - A Diff tool should help to check what pixels are differents from different renders (A and B).
    - A wipe tool (left/right, top/bottom, or manual, like Nuke one) should help to quickly change from the image A to the other (B).
    - A textual diff tool should display render time differences (Between A and B).
    - A "watched nodes" list could be provide. For every render you launch, the attributes values would be stored and, with A and B, you could compare two render (in the Render View, you have the both render images with, below each of them, a list of different values in your watched nodes). This could help a lot during lookdev and/or tweaking.
    - Exposure/Gamma shouldn't be changed in the Attribute Editor. It should be changed directly in the Render View and the Render View should be 32bit by default.
    - Addind textual note to an entry of the render history.
    - GLSL shaders on the Render View with layer access.
    - A one click way to save every render in the Render History List with a preseted naming pattern (foo.####.exr) and file options (compressions).
    - A threaded Render View (yes, again ;) ) to be able check your Render History (and every idea I've purpose) during the current render and start to tweak some others attributes for the next render.

    This are my requests. :)

    Regards,

    Dorian

  18. 179 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Ideas for Maya forum » dynamics  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks to everyone who’s voted on this issue. It is being moved to the Ideas for Maya forum, because although it’s annoying you, it’s not a small thing to address.
    Enjoy spending your Small Annoying Things to fix votes on other ideas!

    Narann supported this idea  · 
  19. 280 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Ideas for Maya forum » rendering & lighting  ·  Flag idea as inappropriate…  ·  Admin →
    Narann supported this idea  · 
  20. 3 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1

Feedback and Knowledge Base