-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visual transparancy behavior on gazebo6 and default #1790
Comments
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). I forgot to mention I started a jenkins job for the gazebo6_to_default branch. It should confirm the failing expectation in |
Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina). The cascade parameter for transparency was added in pull request #1851, but maybe it doesn't make sense to ever set it to false. |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). Another build: |
Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033). I decided to follow ogre's node api where |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
|
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
|
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
|
Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
I was recently trying to merge gazebo6 forward to default and I found some conflicts in Visual class. I tried resolving those conflicts in the gazebo6_to_default branch, which I think is pretty similar to @iche033 's
derived_transparency
branch from the declined pull request #1987, though I added and modified a couple expectations in the ChildTransparency portion of Visual_TEST.cc. There is currently one failing expectation in the test, though, at line 420.It's one of the few places where
SetTransparency
is tested withcascade=false
, and it's unclear to me what the expected behavior should be.I discussed this with @chapulina a bit, but I'll step aside so the rendering masters can sort it out.
The text was updated successfully, but these errors were encountered: