RE: Friday Flashback #384

[Sven Constable]

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 

 

From: softimage-boun...@listproc.autodesk.com 
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Matt Lind
Sent: Sunday, September 1, 2019 11:40 PM
To: softimage@listproc.autodesk.com
Subject: RE: Friday Flashback #384 

 

Yes, it was only the case before the first switch, but that is exactly the 
problem as not all viewports will endure a switch.

It's very common to change shade mode in viewport B as that's the official 
camera view, but less so in the other viewports as they often remain as front, 
right, or top projections with no need to be anything but wireframe. From time 
to time one or more of the other viewports will be converted to a perspective 
view and in those cases shade mode changes are common.

If the desire was to have the previous mode displayed, then the solution is to 
show SHADE not WIRE as the initial value (or show an empty value such as '-'). 
By showing WIRE as the initial value, and have the behavior change upon use, it 
puts the system into a mixed viewing mode where some viewports (front, right, 
top) will show WIRE instead of SHADE because they haven't been manipulated yet, 
but the perspective view will likely show SHADE when it's in wireframe mode.

If you've started a fresh session of Softimage|3D then this is likely not too 
big a deal as you have all your edits at the front of your mind. However, if 
this is a scene loaded from disk that you worked on some time ago, you're not 
going to remember which viewports have had shade mode changes and which 
haven't, in which case seeing WIRE vs. SHADE when two adjacent viewports use 
the same shade mode will be disorienting.

Matt

Date: Sun, 1 Sep 2019 14:44:33 +0200 From: “Sven Constable” 
 Subject: RE: Friday Flashback #384 To: "'Official 
Softimage Users Mailing List.

Alright, maybe the word quirk is appropiate, however I'd rather call it 
“unusual but useful”. :) I think the initial value after launch (WIRE) was just 
because there was no preassigned state. I agree it might confuse a user at 
first, having two viewports using different shading modes effectively while 
both having “WIRE"in the header. But that was only the case before the first 
switch. After that, all viewports used the "before rule”, no?

Sven

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

  
 

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

RE: Friday Flashback #384

[Matt Lind]

Yes, it was only the case before the first switch, but that is exactly the 
problem as not all viewports will endure a switch.

It's very common to change shade mode in viewport B as that's the official 
camera view, but less so in the other viewports as they often remain as 
front, right, or top projections with no need to be anything but wireframe. 
From time to time one or more of the other viewports will be converted to a 
perspective view and in those cases shade mode changes are common.

If the desire was to have the previous mode displayed, then the solution is 
to show SHADE not WIRE as the initial value (or show an empty value such as 
'-').  By showing WIRE as the initial value, and have the behavior change 
upon use, it puts the system into a mixed viewing mode where some viewports 
(front, right, top) will show WIRE instead of SHADE because they haven't 
been manipulated yet, but the perspective view will likely show SHADE when 
it's in wireframe mode.

If you've started a fresh session of Softimage|3D then this is likely not 
too big a deal as you have all your edits at the front of your mind. 
However, if this is a scene loaded from disk that you worked on some time 
ago, you're not going to remember which viewports have had shade mode 
changes and which haven't, in which case seeing WIRE vs. SHADE when two 
adjacent viewports use the same shade mode will be disorienting.

Matt


Date: Sun, 1 Sep 2019 14:44:33 +0200
From: “Sven Constable” 
Subject: RE: Friday Flashback #384
To: "'Official Softimage Users Mailing List.

Alright, maybe the word quirk is appropiate, however I'd rather call it 
“unusual but useful”. :) I think the initial value after launch (WIRE) was 
just because there was no preassigned state. I agree it might confuse a user 
at first, having two viewports using different shading modes effectively 
while both having “WIRE"in the header. But that was only the case before the 
first switch. After that, all viewports used the "before rule”, no?

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'

[Pierre Schiller]

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-2BqrIIO6lDLgW1nIfJE1pxCtdij-2BgAqzXkIePoeBeWSbnCEA1HYeLI6ekr2h-2B5RZd46V5szYUbgvBvMpUU8ZurJtKgHA-2B8bF-2Fk-2BZ2VJGSDW-2BJkDyDn8wJ0fu1am76btkKCuwjXwqhxMpeGXODTPgdBBg6U3Z-2FgsI_a6oQc7tnfcb0GKvoO27fPkrQ0ATQyF1SDBXJOg7-2FbuQN2zacKJaVt-2Fbe-2FzKFlwTj71TI0HKfydOn3ckNp0onD-2FPT4T-2Fws7v2TlavedSY1QtjcuzUll6-2FbT1z1ODPeXNDREoIki-2F8M5atoQGfStyFv4E0AvGUl9YLGydj7goGH9C-2BLyfQLwRP4FxkqXZOn3jEzdPjDKVz8iOC-2B7AS0Kcnb84kA0-2Fxj9wwzykuRGep8KM-3D
  
 - 3D.VFX.Post - Click on
socials:*
* 
 

 

RE: Friday Flashback #384

[Sven Constable]

Alright, maybe the word quirk is appropiate, however I'd rather call it  
"unusual but useful". :) I think the initial value after launch (WIRE) was just 
because there was no preassigned state. I agree it might confuse a user at 
first, having two viewports using different shading modes effectively while 
both having "WIRE"in the header. But that was only the case before the first 
switch. After that, all viewports used the "before rule", no?

 

Sven

From: softimage-boun...@listproc.autodesk.com 
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Matt Lind
Sent: Sunday, September 1, 2019 10:25 AM
To: softimage@listproc.autodesk.com
Subject: RE: Friday Flashback #384

 

It's definitely a quirk.

When you launch the application the title bar shows “WIRE” as the shade mode. 
Which it is. But when you toggle to SHADE mode, it still shows WIRE because 
that's what'll happen if you click it. In other words, the rules changed. A big 
no-no because it'll deceive the user. It isn't until the menu is changed again 
that SHADE or another mode will be displayed.

Example:

If you adjust the shade mode of viewport B to be Shaded mode but don't touch 
viewport A, then both will display WIRE as the mode, but for different reasons. 
That's the problem. The bug is the initial value is WIRE when it should be 
something else, OR, change the logic to show the current mode instead of the 
toggled mode.

Matt

Date: Sat, 31 Aug 2019 00:46:28 +0200 From: “Sven Constable” 
 Subject: RE: Friday Flashback #384 To: "'Official 
Softimage Users Mailing List.

I don?t think it was a quirk but intendend. :) Even that feature likely felt 
illogical at first, it's intriguing how much thought went into the tiniest bits 
of the GUI. Btw it was the only feature where a “before-state” was displayed, I 
think.

Workwise it made sense because switching to a viewmode like Shaded or Textured 
would took some time. Knowing to which viewmode you'll switch was surely an 
advantage.

Besides this, its kinda obvious which viewmodeis currently used because the 
viewport is displaying it already. Therefore, having a label that indicates to 
which viewmode you will switch is more useful. Otherwise it would be redundant 
information.

I work that way even today (middle click to switch modes) and to be honest I 
would prefer the old way telling me to which viewmode I'll switch. Rather than 
in which viewmode I am currently in.

Sven

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

  
 

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

RE: Friday Flashback #384

[Matt Lind]

It's definitely a quirk.

When you launch the application the title bar shows "WIRE" as the shade 
mode.  Which it is.  But when you toggle to SHADE mode, it still shows WIRE 
because that's what'll happen if you click it.  In other words, the rules 
changed.  A big no-no because it'll deceive the user.  It isn't until the 
menu is changed again that SHADE or another mode will be displayed.

Example:

If you adjust the shade mode of viewport B to be Shaded mode but don't touch 
viewport A, then both will display WIRE as the mode, but for different 
reasons.  That's the problem.  The bug is the initial value is WIRE when it 
should be something else, OR, change the logic to show the current mode 
instead of the toggled mode.

Matt




Date: Sat, 31 Aug 2019 00:46:28 +0200
From: “Sven Constable” 
Subject: RE: Friday Flashback #384
To: "'Official Softimage Users Mailing List.

I don?t think it was a quirk but intendend. :) Even that feature likely felt 
illogical at first, it's intriguing how much thought went into the tiniest 
bits of the GUI. Btw it was the only feature where a “before-state” was 
displayed, I think.

Workwise it made sense because switching to a viewmode like Shaded or 
Textured would took some time. Knowing to which viewmode you'll switch was 
surely an advantage.

Besides this, its kinda obvious which viewmodeis currently used because the 
viewport is displaying it already. Therefore, having a label that indicates 
to which viewmode you will switch is more useful. Otherwise it would be 
redundant information.

I work that way even today (middle click to switch modes) and to be honest I 
would prefer the old way telling me to which viewmode I'll switch. Rather 
than in which viewmode I am currently in.

Sven


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