PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk)

  1. 7 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Scripting Enhancements » MAXScript  ·  Flag idea as inappropriate…  ·  Admin →
    PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk) shared this idea and gave it 3 votes  · 
  2. 27 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Scripting Enhancements » MAXScript  ·  Flag idea as inappropriate…  ·  Admin →
    PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk) gave this 3 votes  · 
  3. 37 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk) commented  · 

    I agree that Autodesk should work with 3rd party developers to expose what they need to add support for things like Particular. Red Giant Software has already developed Particular for Nuke, and I am guessing this is based on the Nuke API/SDK since it is specifically developed for Nuke (and not other OpenFX apps like Composite or Fusion).

    PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk) gave this 3 votes  · 
  4. 15 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk) commented  · 

    .ai and .eps have their place, but I want support for an open ASCII format, not a closed proprietary format. With .ai and .eps it would require a code change anytime Adobe changed their plugins, or released a new version of their tools, that isn't the case with .SVG. Also, just about any vector editor can import/export .svg, that is not the case with .ai/.eps and their functions and compatibility. So no I don't want .ai or .eps added to this idea.

    PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk) shared this idea and gave it 3 votes  · 
  5. 371 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk) shared this idea and gave it 3 votes  · 
  6. 50 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Small Annoying Things » Materials/Maps  ·  Flag idea as inappropriate…  ·  Admin →
    PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk) gave this 3 votes  · 
    PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk) commented  · 

    I agree both Color Correction and Composite Maps need to adhere to HDR workflows. Right now both clamp at 0.0-1.0 and only operate within this color range. There really should be an HDR toggle (this would disable tools that need to operate 0.0-1.0 color space) and/or color scaling functionality (this would scale colors to fit into 0.0-1.0 color space, and either reverese the scaling after the color operations or display the scaling so it can be reversed through an output map to get the values back to the original HDR range).

  7. 7 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Scripting Enhancements » MAXScript  ·  Flag idea as inappropriate…  ·  Admin →
    PiXeL_MoNKeYAdminPiXeL_MoNKeY (Admin, Autodesk) shared this idea and gave it 3 votes  · 

Feedback and Knowledge Base