Skip to content

lightposition in Surface plots does not function correctly #2176

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

Open
cpomsoft opened this issue Feb 10, 2020 · 2 comments
Open

lightposition in Surface plots does not function correctly #2176

cpomsoft opened this issue Feb 10, 2020 · 2 comments
Labels
bug something broken P3 backlog

Comments

@cpomsoft
Copy link

When setting the position of the light source in a 3d surface plot using

go.Surface(z=myz,x=myx,y=myy,lightposition=dict(x=1e5, y=0, z=0.),

the x,y,z components of the light source position do not appear to make any sense. They do not work as sensible vector, and will flip the light position with minor changes of x,y or z. Currently it seems you have to spend ages trying different random combinations of values until something vaguely works. This is very unsatisfactory. The documentation is not at all helpful as it implies the light position is a sensible vector, which it doesn't appear to be:

lightposition
Parent: data[type=surface]
Type: dict containing one or more of the keys listed below.
x
Parent: data[type=surface].lightposition
Type: number between or equal to -100000 and 100000
Default: 10
Numeric vector, representing the X coordinate for each vertex.
y
Parent: data[type=surface].lightposition
Type: number between or equal to -100000 and 100000
Default: 10000
Numeric vector, representing the Y coordinate for each vertex.
z
Parent: data[type=surface].lightposition
Type: number between or equal to -100000 and 100000
Default: 0
Numeric vector, representing the Z coordinate for each vertex.

@Liisjak
Copy link

Liisjak commented Feb 10, 2021

For me, the light does not respond to lightposition at all.

@oscarrutt
Copy link

Oh crap. Is Plotly maintained any more? I just spent days learning Plotly as a replacement for my soon-to-disappear commercial plotter. I have this same problem, and I notice that this bug was posted more than three years ago and there has been no response from the developers.

@gvwilson gvwilson self-assigned this Jul 8, 2024
@gvwilson gvwilson removed their assignment Aug 2, 2024
@gvwilson gvwilson added P3 backlog bug something broken labels Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something broken P3 backlog
Projects
None yet
Development

No branches or pull requests

4 participants