Some semi-transparent edges of sphere() meshes are rendered in higher density. #4720

Closed
chrisjj opened this Issue Oct 27, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@chrisjj

chrisjj commented Oct 27, 2016

On Processing 3.2.1 for Windows, run

void setup() {
  size(480, 480, P3D);
  colorMode(HSB, 6.0, 1.0, 1.0, 1.0);
  noFill();
}

void draw()
{ // For tweaking
  translate(width/2, height/2);  
  background(0);
  stroke(0.0, 0.4, 1.0, 0.5);
  rotateX(-0.1);
  rotateY(0.01*millis()/100);
  strokeWeight(5);
  sphereDetail(4);sphere(100);
}

Expected: wireframe sphere with edges rendered in uniform density
Observed: wireframe sphere with some edges rendered in higher density:

image

Discussed here: http://web.archive.org/web/20161027162717/https://forum.processing.org/two/discussion/comment/77501%23Comment_77501

@chrisjj chrisjj changed the title from Some semi-transparent edges of sphere() meshes are rendered at double density. to Some semi-transparent edges of sphere() meshes are rendered at higher density. Oct 27, 2016

@chrisjj chrisjj changed the title from Some semi-transparent edges of sphere() meshes are rendered at higher density. to Some semi-transparent edges of sphere() meshes are rendered in higher density. Oct 27, 2016

@jeremydouglass

This comment has been minimized.

Show comment
Hide comment
@jeremydouglass

jeremydouglass Oct 27, 2016

Contributor

In tests, the single high-density edge is the ring immediately below the mesh pole (see forum thread linked in issue).

Contributor

jeremydouglass commented Oct 27, 2016

In tests, the single high-density edge is the ring immediately below the mesh pole (see forum thread linked in issue).

@codeanticode codeanticode self-assigned this Oct 30, 2016

@codeanticode codeanticode added the opengl label Oct 30, 2016

@codeanticode

This comment has been minimized.

Show comment
Hide comment
@codeanticode

codeanticode Oct 30, 2016

Member

thanks for reporting the issue, fixed with 4da26d1

Member

codeanticode commented Oct 30, 2016

thanks for reporting the issue, fixed with 4da26d1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment