Originally created by: alexis.b... (code.google.com)@gmail.com
Originally owned by: timoor... (code.google.com)@gmail.com
What steps will reproduce the problem?
1. --aircraft=f-14b
2. hit Ctrl-C, only the legacy hotspots highlight in yelow. Pick animations
still work but remain invisible for transparent objects like those of the
altimeter and the airspeed indicator knobs.
What is the expected output? What do you see instead?
Transparent objects use to be hilighted in yellow and was visually similar
as the legacy hotspots. Now they are invisible.
What version of the product are you using? On what operating system?
CVS around 03/10/10, linux.
Please provide any additional information below.
The problem seams to be a few months old.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: alexis.b... (code.google.com)@gmail.com
May affect several aircrafts
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
I can confirm with current CVS that there is a pick "problem". It looks like (with
shaders enabled), the hotsports are not coloured the usual yellow, instead they
adapt the color of the to-be-picked object. So a pick animation on a red button,
will result in a yellow hotspot, making it (almost) invisible...
Status: Accepted
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: alexis.b... (code.google.com)@gmail.com
my guess,
scene/model/animation.cxx line 2191
stateSet->setAttribute(material, osg::StateAttribute::OVERRIDE);
doesn't override anymore.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
CC-ing Tim in case there's an easy solution here.
Labels: Rendering
Cc: timoore33
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: vivian.m...@lineone.net
See also Issue 209
Related
Tickets:
#209View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: timoor... (code.google.com)@gmail.com
(No comment was entered for this change.)
Owner: timoore33
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
Issue 219 has been merged into this issue.
Related
Tickets:
#219View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: timoor... (code.google.com)@gmail.com
fixed with simgear [rc934b47f2e94fcefb719b9b6186abc4fd8562670]. There were two different problems visible in the f-14b cockpit: transparent pick animations would not be highlighted at all, and others might take on a color of the real object. This was fixed by making the state attributes of the pick animation compatible with the default model shader, which already contains some parameters that are settable from material animations. Also, a combination of OVERRIDE and PROTECTED flags are specified to override (duh) the attributes in the picked object and protect from any material animations specified in parents.
I don't understand why modelers use transparent pick objects; the "visible" attribute in the pick animation xml hides the animation.
Status: Fixed
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Temp
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Fixed