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
GreasedLine changes #14943
GreasedLine changes #14943
Conversation
…d simple material vertex shader
Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s). |
Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s). |
Snapshot stored with reference name: Test environment: To test a playground add it to the URL, for example: https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14943/merge/index.html#WGZLGJ#4600 Links to test babylon tools with this snapshot: https://playground.babylonjs.com/?snapshot=refs/pull/14943/merge To test the snapshot in the playground with a playground ID add it after the snapshot query string: https://playground.babylonjs.com/?snapshot=refs/pull/14943/merge#BCU1XR#0 |
Visualization tests for WebGPU (Experimental) |
WebGL2 visualization test reporter: |
Visualization tests for WebGPU (Experimental) |
You should remove the |
Sorry, I didn't even notice it. |
I think it's because we still commit this file on our side when necessary, but it's not supposed to be done by the end user. @RaananW will know better than me, though. Note that you should not remove the file from the repo, but from your PR only :) Also, you shouldn't have any change in your local |
I removed it using the GitHub app on my mobile while I was in the commits section for this PR. I did this for the first time but who in the world could have guessed it will remove it from the repo not from the commits. Sorry :) Should I take any action? What should I do? Thanks!
Yes, all was up to date. This is why I always use |
You should do a |
@deltakosh there is a commit 182fbcb by you which introduced an error:
Doesn't count this as a breaking change though? Changing the return type of a public getter? :) I can fix the thing, just don't know what approah you prefer, reverting the commit or I will fix the issue in this PR. Thanks! We could actually support // added FloatArray
interface GreasedLineMeshOptions {
uvs?: number[] | FloatArray;
}
set uvs(uvs: number[] | FloatArray) {
this._uvs = uvs instanceof Float32Array ? uvs : new Float32Array(uvs);
this._createVertexBuffers();
} |
Aaaarqgh :-D
Edit: |
Visualization tests for WebGPU (Experimental) |
@Popov72 I've managed to fix the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
package-lock is being deleted (unless I see a wrong state?)
A git reset, reverting this change and force-push a commit to your branch will probably be the best fix here.
Visualization tests for WebGPU (Experimental) |
Visualization tests for WebGPU (Experimental) |
@RaananW is it now ok to merge? |
Visualization tests for WebGPU (Experimental) |
Added AuTO_DIRECTIONS_FACE_TO mode.
Added support for custom UVs.
Fixed simple material shader for non camera facing mode.