[p5.js 2.0 Bug Report]: Warnings about omitting strokes on high-detail 3D primitives don't use FES

[davepagurek]

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• Build process
• Unit testing
• Internationalization
• Friendly errors
• Other (specify if possible)

p5.js version

All

Web browser and version

All

Operating system

All

Steps to reproduce this

Steps:

1. Turn off FES
2. Draw a cylinder with a high level of detail
3. It still logs a warning

That's because these sorts of warnings are raw console.logs in the codebase:

p5.js/src/webgl/3d_primitives.js

Lines 2582 to 2585 in 9799ead

	console.log(
	'Cannot draw stroke on cylinder objects with more' +
	' than 24 detailX or 16 detailY'
	);

Snippet:

p5.disableFriendlyErrors = true
function setup() {
  createCanvas(400, 400, WEBGL);
  cylinder(20, 100, 40, 40)
}

Additionally, this also triggers when you are drawing to a p5.Geometry, i.e.:

function setup() {
  createCanvas(400, 400, WEBGL);
  const myGeom = buildGeometry(() => cylinder(20, 100, 40, 40))
  noStroke()
  model(geom)
}

Arguably we should just silence this error if inside of buildGeometry since we don't know if it will eventually be drawn with strokes or not, to avoid misleading false positives.

[Aayushdev18]

I’d like to work on this. The warning appears to bypass FES due to a raw console.log. I’ll investigate fixing or silencing it appropriately

[shuklaaryan367-byte]

This does look like a clear FES consistency issue.

From reading the code, it seems the warning for high-detail cylinders is currently emitted via a raw console.log, so it still appears even when p5.disableFriendlyErrors = true. This also seems to trigger inside buildGeometry(), where stroke usage isn’t yet known, which could lead to misleading warnings.

I’d be interested in helping fix this and align the behaviour with the Friendly Error System if that sounds reasonable.
Thank you 😇