RE: Friday Flashback #384

[Matt Lind]

The logic is the menu shows the shading mode that will become active when 
you middle click the menu.  If no mode had been chosen yet, then it can't be 
anything other than NONE.  Therefore NONE would make perfect sense, 
especially if you read the manuals. :)

If you start up the application then immediately middle click the shade mode 
menu, most computers will switch to SHADE mode, but not all computers did 
that.  Some stayed in wireframe.  Therefore it would be wrong to display 
WIRE or SHADE in the viewport title bar as the initial value.  The only 
acceptable time WIRE or SHADE could be the initial value is if the 
application were programmed to ensure one of those modes would be active 
upon middle click.

Displaying the next mode makes more sense when the menu has only two choices 
such as a boolean value (check box), but even then I would prefer to see the 
current setting.  The shade mode menu had many choices depending on what 
kind of view it was.  So to show what was next was rather confusing when 
everything else in the UI was displaying the current setting.

In my opinion it should've displayed the current shade mode.  Believe it or 
not, there are instances where two different shade modes can produce the 
same result which only makes the displayed value all the more confusing. 
When you're in a collaborative environment working with other people and 
discussing things, you need to keep track of various settings for 
comparisons / critiques of work so you can give constructive criticism and 
instruction.  Can you imagine if every menu in the application showed you 
what would happen under a middle click instead of the actual value?  You 
wouldn't be able to figure anything out.  It could say SCHEMATIC, but you'd 
be clearly looking at the top view as evidenced by the objects in the 
display.  Instead of showing the current frame number, the timeline shows 
the next frame you'll skip to when you set a keyframe (or the previous key 
you already set).  Huh???

The only time I'd find it handy is if it could display which click will 
crash the application.  There were plenty of those opportunities.

Matt




Date: Mon, 2 Sep 2019 00:44:52 +0200
From: “Sven Constable” 
Subject: RE: Friday Flashback #384
To: "'Official Softimage Users Mailing List.

So a consistent, logical solution would have been “NONE” as the default 
label, I agree. But wouldn't it be more confusing especially since it it's 
only displayed once at start and then never again? Every viewport had to 
display something at start (wireframe back then) so its not that 
disorienting because it showed the correct shading mode at first launch.

As soon as the user started to work and switching back and forth between 
shading modes (most likely in the camera view only), it switched gears and 
changed to show which mode the user will switch to. Kind of a work mode that 
kicked in as the user changed the view for the very first time.

I might be a quirk somehow but it was useful to me (after I got it) and I 
think it was intended. ;)

Sven


--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.

Re: Thoughts on USD in comparison to Softimage 'Referenced Models'

[Jordi Bares]

“Move swift as the Wind and closely-formed as the Wood. Attack like the Fire 
and be still as the Mountain.” 
― Sun Tzu, The Art of War 


Keep a log of everything, you may be able to write an awesome account of the 
journey. ;-)

Jb


> On 2 Sep 2019, at 15:19, Jonathan Moore  wrote:
> 
> Thanks for the recommendation Jordi.
> 
> As to 100% authority, that's in place as most of the accounts within the 
> network are international and the name of the game is seamless market 
> localisation, minimising the repeated recreation of the same campaign assets 
> and recognition of the strengths of particular resources within the network 
> so that work is always briefed to the most apt and capable teams. However 
> this is all fine and dandy in theory, the hardest barriers to overcome in 
> international advertising networks is the silo's and fiefdoms (I'm sure 
> that's the same in any international creative business). There's a lot of 
> politics to negotiate, never mind the specifics of the brief! ;)
> 
> On Sun, 1 Sep 2019 at 18:12, Pierre Schiller  > wrote:
> Thank you for the advise on that book JB.
> 
> I totally agree with Jonathan. People is afraid of technical challenges.
> Most of the time they come from an already wrecked technical background. 
> Unlike us Softimagers, where linear creativity development
> always allowed us to implement things in the middle of production anywhere 
> and not fail. You have to give them a space on that subject... they
> don´t know (with SI EOL, they WILL NEVER know) how friendly and easy it to 
> work with linking assets a' la dot xsi or delta references for LODs.
> Hail .USD? :)
> 
>  www.3dcinetv.com 
> 
>  - 3D.VFX.Post - Click on socials:
> 
>  
> 

Re: Thoughts on USD in comparison to Softimage 'Referenced Models'

[Jonathan Moore]

Thanks for the recommendation Jordi.

As to 100% authority, that's in place as most of the accounts within the
network are international and the name of the game is seamless market
localisation, minimising the repeated recreation of the same campaign
assets and recognition of the strengths of particular resources within the
network so that work is always briefed to the most apt and capable teams.
However this is all fine and dandy in theory, the hardest barriers to
overcome in international advertising networks is the silo's and fiefdoms
(I'm sure that's the same in any international creative business). There's
a lot of politics to negotiate, never mind the specifics of the brief! ;)

On Sun, 1 Sep 2019 at 18:12, Pierre Schiller 
wrote:

> Thank you for the advise on that book JB.
>
> I totally agree with Jonathan. People is afraid of technical challenges.
> Most of the time they come from an already wrecked technical background.
> Unlike us Softimagers, where linear creativity development
> always allowed us to implement things in the middle of production anywhere
> and not fail. You have to give them a space on that subject... they
> don´t know (with SI EOL, they WILL NEVER know) how friendly and easy it to
> work with linking assets a' la dot xsi or delta references for LODs.
> Hail .USD? :)
>
>
> * 
> https://u9432639.ct.sendgrid.net/wf/click?upn=lIXdN6W56FnEjHCwrBXqOq0HQNpV0huvAGw1zu6Xp8eVQuk2cNZiNFjx2k-2FfTNcheFfpiVb5gBjGpm0Nj5Q4I-2FEkbgYMLPK5QvZZt8uottDLih-2BJeeuPV5lW3fMoI9Lu-2B53c77LmTycan03Qo6RkzhbelQxkFdvOS2Ii8qkjBIZYBGG7iMVYX2-2FQ09q5JLl16nD8AaemL9VgjEL8GRdeyX3K6tE5BPK7-2B-2BqrIIO6lDJSUIIW5bCNyya-2FvoM6ZBGc5hZ1otpmaQ9GQTTb-2BszUSzzU7tN0-2FIiC2crWINuQ-2FwRMo2y53tZuBx-2BC-2FgQwtk-2BuERNrPfrXGcFT2N3IhszEgAhvdx2nPicFoTizR8A4SEFsS5FmZr0SUPRB1X2SDDBR_a6oQc7tnfcb0GKvoO27fPkrQ0ATQyF1SDBXJOg7-2FbuTPQyXfBwTG8Y3GU0bOj-2FLx4S1OnHDLK-2BtJaB-2BEsdEq1-2FaOobvFzG0tLVukd2gyb0d13CYaL7d-2BZkt7F3FE1gpSjr12zuDU8KBU7g-2FDEXAh9jAwYZCLxVr-2BrxJXmZdLt9vO3V6nS0gVId94rmUyxapSNjsDTAKy13H38vUhiUZKYV-2FePS7udr4e-2FX7MkuqB9ys-3D
>  
>   >
> - 3D.VFX.Post - Click on socials:*
> *
>