Right, but that doesn't matter.

@Luc-Eric:
how about the bugs logged in the 2014 beta? Are these still "hot"?

(I'm happy I pulled a copy of my stuff in time...)


Am 11.10.2013 21:38, schrieb Stefan Kubicek:
+1 on all your arguments Matt, btw if I remember correctly the SAT thread was started by Eugen Sares (not implying that Chris wasn't very proactive for the time he was in charge).


    Autodesk should expose the feature requests which have been logged
    so we know what we have to follow up on, for a few reasons:

    1) We don’t know if our own requests were logged.  I have come
    across cases where I requested a feature, but due to database or
    logging system changes the requests were lost.  For example, when
    changing from Avid to Autodesk ownership, or from Microsoft to Avid.

    2) In past betas not all topics of discussion were not logged
    unbeknownst to us until it was too late.  In other cases like the
    ‘small annoying things’ list which Chris Chia started a year or
    two ago, he only logged some of the items in that thread but
    didn’t tell us which were logged and which were not.  We have no
    idea if our requests are even in the system.  It’s not trivial to
    spend the time to re-write all that information.

    3) Some of us have been around for many years (20+ in my case) and
    do not have access to what has been requested due to changes in
    employment and locale.

    4) Seeing the requests on file would allow items which no longer
    apply to be more quickly filtered out so you can spend more time
    on the ones that are important.  I cannot possibly remember every
    single thing I’ve requested over the past 20 years, but I know
    I’ll recognize my requests in the list when I see them and be able
    to let you know if they’re no longer valid.

    5) Some requests are linked to other requests.  As in, some
    features are closely related and are expected to be implemented
    together.  It would be helpful to see all the requests so we can
    identify which are meant to be paired so you can better understand
    how to organize your development resources.

    Matt

    *From:*[email protected]
    [mailto:[email protected]] *On Behalf Of
    *Stefan Rueffer
    *Sent:* Thursday, October 10, 2013 11:04 PM
    *To:* [email protected]
    *Subject:* RE: Unofficial Softimage user voice

    Hello,

    For sure we will not forget about the old requests, but the
    priority might change over time and so it’s helpful to see that.

    So please mention features and improvements again, even if they
    have been already logged to give them the proper weight.

    Most beneficial would be to get information about the small things
    that might be easy to implement, but would mean a big improvement
    on your daily workflows.

    Please take my apologies for not introducing myself.

    I am Product Designer for Softimage specifying the details for new
    features, enhancements and workflows for Softimage in coordination
    with Product Management.

    Concerning my background I am a long term Softimage user since
    version 2.0.
    I have started on the technical side doing scripting and pipeline
    integration but switched later to be a TD and Generalist.
    During my 8 years in the tv commercial industry I have worked in
    nearly all areas of 3d production like modeling, animation,
    shading, rendering, simulation,… and ICE.

    And a long time ago I made a presentation for ICE that some of you
    might remember :-)
    
http://area.autodesk.com/forum/autodesk-softimage/ice---interactive-creative-environment/vcc-blaupunkt-xsi-7-ice-demo/

    Cheers,

    Stefan




--
-------------------------------------------
Stefan Kubicek
-------------------------------------------
keyvis digital imagery
Alfred Feierfeilstraße 3
A-2380 Perchtoldsdorf bei Wien
Phone: +43/699/12614231
www.keyvis.at [email protected]
-- This email and its attachments are --
--confidential and for the recipient only--

Reply via email to