Skip to content

Last release 175 breaks all my ExtrudedGeometry top and bottom faces #30855

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
Kikedao opened this issue Apr 3, 2025 · 4 comments
Open

Last release 175 breaks all my ExtrudedGeometry top and bottom faces #30855

Kikedao opened this issue Apr 3, 2025 · 4 comments

Comments

@Kikedao
Copy link
Contributor

Kikedao commented Apr 3, 2025

Description

Top and bottom faces of ExtrudedGeometry are not visible any more when updating to r175, all was fine in the previous versions.

I think this PR could have broken it but I can't be sure:
#30750

r174, all fine:

Image

r175, top and bottom missing:

Image

Reproduction steps

  1. Create a shape for example this rounded corner rectangle:
const shape = new THREE.Shape();
const angleStep = Math.PI * 0.5;
const size = 0.64;
const radius = 0.32;

shape.absarc(size / 2 - radius, size / 2 - radius, radius, angleStep * 0, angleStep * 1);
shape.absarc(-size / 2 + radius, size / 2 - radius, radius, angleStep * 1, angleStep * 2);
shape.absarc(-size / 2 + radius, -size / 2 + radius, radius, angleStep * 2, angleStep * 3);
shape.absarc(size / 2 - radius, -size / 2 + radius, radius, angleStep * 3, angleStep * 4);
  1. Extrude the shape using ExtrudeGeometry:
const geometry = new THREE.ExtrudeGeometry(shape, {
	depth: 0.2,
	bevelEnabled: false,
	bevelThickness: 0,
	bevelSize: 0,
	bevelSegments: 0,
	curveSegments: 6
})
  1. The top and bottom faces, the ones corresponding to the original shape, are missing.

Version

r175

Device

Desktop

Browser

Chrome

OS

Windows

@hxmwr
Copy link

hxmwr commented Apr 4, 2025

Have the same problem.

@WestLangley
Copy link
Collaborator

Duplicate of #30819 and #30836.

Please check the dev branch to see if #30822 fixed your use cases.

@Mugen87 I think an r175 patch release is appropriate.

@Mugen87
Copy link
Collaborator

Mugen87 commented Apr 4, 2025

I do not have all user permissions to make a patch release (e.g. I can't update the npm package). @mrdoob needs to do that.

@Saltallica
Copy link

Yeah this is a biggie

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

No branches or pull requests

5 participants