UV rendering exception

[q2434006]

What happened?

The example code is as follows, rendering a surface using texture coordinates. The texture coordinates of the point in the upper right corner cannot be assigned, I don’t understand why it doesn’t work,I don't know if it's a problem：

Reproduction steps

No response

Sandcastle example

https://sandcastle.cesium.com/#c=hVRdb9owFP0rFk8gUcffH5SiaajSpG1qpU3bA/CQEhfS5YMlpi2d+t93DUlJaaf5IYl97znn3vjYCC3LovboPnUPrkIXqHAPaOrqdJvjH/u1/ry33M+nZeHjtHDVvDc4nxfzAsE4oL179NvKJddltluVBdAc+LArfOpTV+M4Sfp/DpAwijh3IzTvXT76apu45IUBbRqKh9Sv0cZVZ5uyBgpYWbt0tfY1iosELbe1L/MWBVWUVZIWsXf1vDc8yjRkI9SRDmOduiquluvdCM1mZ0xoQ7nBkljCqFaMD5EwTBpJsYKgpZKZIeJcMCsMJsQKq+GpF0PUohXm0hrNjBKqRcMaV/CpmG3RDBsOUtxKKzpog4FBGqGJatFKYEpBh0ppZQPnZK9iuSGqIy4otpQJprSwLVpjqoSQ1DDRohnHjDBNrTQdrMGCKEOlVtq0YIa1VNYYommLFbBECSGa066yxEwTkKGW6xZNMAtDG6s7hStLAWyN6PQtODbGSGOJoC//HPqG9qyStEULaBs2JWyOEq/EBTArroLOAQw6UimqLWuxAqoB1fAvFwucx5t+ji4mXZtP4wp8k8YF7+czAvz5jO6fbDEYDF8bpzHc9Oi3N946+O7g2Tr4iwxRYN2/oRilqSZhf7lSQuqXiCZMai40eIBrRVQTCKXM6PH9fiL9J3eI/K9x1mn8TcvPJ3M4k9dNe5/2J3KE4Ay7kyzXHOw2hZzEc/h3VRpn4RJYe7+pR1FUM5yVWYoL5yNwqowIjQiPPlVXP7/ePn2+Uzn7ffkR321Wrw55W+Dz8VZqbp+nssy/l/2Tu2hw3hv2xrXfZW7SsnxI801ZebStsj7GkXf5Jgu7G91sl7+cx8u6DuwhdRx1oeMkvUdpcvHOJYmWWVzXELndZtm39MnNe5NxBPlvoFkZg5tWV/euyuJdSFvTyZfDIsZ4HMH0faQvy+wmrk6Y/wI

Environment

Browser: Google Chrome
CesiumJS Version:1.125
Operating System:

[javagl]

Just to have the connection: This was also brought up in the forum at https://community.cesium.com/t/uv-rendering-exception/37711

[ggetz]

Thanks for the report @q2434006!

@javagl Generously checked back to version 1.95 and saw that the issue was still manifesting.

This could be related to dependency update, (which would explain why going back to a previous release didn't help). However I just check this against #12412 and it did not appear to fix the issue. We'll need to investigate further.

[q2434006]

Thanks for the report @q2434006!

@javagl Generously checked back to version 1.95 and saw that the issue was still manifesting.

This could be related to dependency update, (which would explain why going back to a previous release didn't help). However I just check this against #12412 and it did not appear to fix the issue. We'll need to investigate further.

Thank you for your reply and record