[UPDATED] Editor running Engine V2

Announcements
1

In the next coming days we will be switching the Editor over from running by default with Engine V2 over Engine V1.

NOTE This will not affect your project engine version which is used in the launcher and when published.

This editor experience is aimed to be identical to running on Engine V1 however should there be any issues please do reach out in Help & Support, on Github Issues or in our Discord Server

Whilst we are resolving this issue you are able to still use the Editor running on Engine V1 by appending the v1 query parameter to the end of your url e.g. https://playcanvas.com/editor/scene/2148249?v1

10th March Update

We have fixed the remaining issues differing Engine V2 from Engine V1 in the Editor. Any visual differences in Gamma are likely to be because of incorrect sRGB flags being set. Please refer to the Asset Auditor to resolve your issues. This is located in the status bar as shown below.

image
image812×130 7.43 KB

We have scheduled the switchover of the default Editor to run Engine V2 to happen on 12th March (Delayed).

12th March Update

We have deployed the switchover to Editor powered by Engine V2 being the default editor. Please refer to the Editor Release Notes for changes

13th March Update

We have compiled an FAQ for the switch of Editor to being powered by Engine V2

5 Likes
3

Please don’t do it. Our projects will look different due to that, especially the ones using UI.
Our artists will have difficulty on visually working with Editor due to that, as they will have to use Launcher to see how things look instead of Editor. Which is unnecessary workflow overhead.

1 Like
4

We had some differences against v1 when it rolled out (by adding v2 to query). However, those were related to materials in the 3d world. I think that is why the team gave a period for us to report any findings. Both versions look the same for us after they fixed our reports. We don’t use PlayCanvas UI, though, so there might be something there? If you do see a difference, I bet the team would like to hear about those.

5

Thanks for the report @moka , we’ll investigate your findings and make sure those are fixed before the release.

1 Like
6

I can confirm the effect on the UI elements

This is a UI screen in v2

image
image380×565 63.3 KB

While this is in v1

image
image369×565 35.5 KB

1 Like
7

Can you confirm that this has been fixed?

8

Fixed for me

2 Likes