Skip to content
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

Playground fails permanently when Babylon.js 3.3 is selected #12341

Merged
merged 1 commit into from
Apr 5, 2022
Merged

Playground fails permanently when Babylon.js 3.3 is selected #12341

merged 1 commit into from
Apr 5, 2022

Conversation

RaananW
Copy link
Member

@RaananW RaananW commented Apr 5, 2022

Fixes #12336
Removes 3.3,
moves the 4.2.X branch to 4.2.1

Fixes #12336
Removes 3.3,
moves the 4.2.X branch to 4.2.1
@azure-pipelines
Copy link

Please make sure to tag your PR with "bug", "new feature" or "breaking change" tags.

@deltakosh deltakosh enabled auto-merge (squash) April 5, 2022 15:50
@azure-pipelines
Copy link

Snapshot stored with reference name:
refs/pull/12341/merge

Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/12341/merge/index.html

To test a playground add it to the URL, for example:

https://babylonsnapshots.z22.web.core.windows.net/refs/pull/12341/merge/index.html#WGZLGJ#4600

To test the snapshot in the playground itself use (for example):

https://playground.babylonjs.com/?snapshot=refs/pull/12341/merge#BCU1XR#0

@deltakosh deltakosh merged commit a36a929 into BabylonJS:master Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Playground fails permanently when Babylon.js 3.3 is selected
2 participants