This morning, I saw the announcement of the upgrade for Editor v2.1.0 version,
This resulted in a very high exposure of the entire scene in my previous project, even causing issues with the rendering of the UI layer
This is the status displayed in the editor
This is the display status of the browser
公告里说
The Editor by default will now be powered by Engine V2 Projects using Engine V1 will launch, download and publish with Engine V1 however the viewport in the Editor will use Engine V2.
Since that’s the case, why does it affect the display effect of v1 version and the editor hasn’t switched to v2
Playcanvas. js always has bugs during upgrades. As a commercial engine, can you be more reliable? We have spent money on it
All the img objects in the UI layer have become highly exposed, and I just watched helplessly as they changed. Can the official provide an explanation? Don’t pretend not to see them, okay? I have already posted a post and haven’t received a reply yet. Is this a bug that can be fixed urgently
Do you have any warnings or messages in the Editor console (not the browser console)? If no warnings or messages in the console, an example project would help.
Reasons for Conflict:
Due to the sRGB setting of jiantou.jpg not meeting the expectations of the element component (false vs true)
In PlayCanvas engine v2, the color space processing of textures is more stringent, especially in lighting calculations and rendering pipelines
But manually changing it to true also has a completely different effect than what the browser displays
The new project I tested yesterday was fine, but today I found that when I changed the SRGB attribute, it miraculously returned to normal. I think you should have already solved this problem
Besides, since you changed the v2 engine version, the project has encountered various problems. The colors of the browser and editor are exactly the same, making debugging difficult. What is the reason for this
This way you select which engine is used for your project. Which means when you launch your project, or publish it.
The Editor internally uses engine v2 regardless of that.
And so two things need to set up correctly for the viewport to render well (matching the launcher):
srgb setting on the textures. The Asset Auditor helps here - see if it reports any errors / warnings
Tone mapping. If your game is using tonemapping (you can see it as a setting on your cameras in the scene), ideally you use the same mapping in the Editor. There is a tonemapping setting for this in the Settings->Editor.
I’m sorry your reply didn’t solve my problem. I copied the official project and it also has this issue. I didn’t use any images, I just created a texture ball. Whether I use v1 or v2 versions in the editor, the display is different from the browser
@Guohao6666 - could you please be more specific, what issue do you see with this attached project? I switched the editor to use the camera from the scene, so that I see the cube from the same angle, and they seem the same to me, see the screenshot. I don’t see a brightness difference.
But the color displayed here is clearly different. Now, in my previous project, whenever I fork a copy and reopen the material ball, the color changes. What’s the reason for this
I really don’t understand why my editor is clearly in v1 version and hasn’t switched to v2. The color effect is completely different from the browser now. Although some images have textures that must be set to sRGB prompts, the basic material colors are also incorrect. Previously created projects had some sRGB prompts, but it didn’t affect the effect. However, when I fork a project, the color and effect become very dark
Why is the picture of the Sky Box I downloaded from the store now black and gray when it comes to the engine? It wasn’t like this before, and why are there so many problems now
Hey thanks for pointing this out, nobody has noticed that yet We’ll investigate.
The good news is that only the thumbnail is dark, but the zoomed in preview is correct, as well as the rendering. So just the thumbnail.
Projects using Engine V1 will launch, download and publish with Engine V1 however the viewport in the Editor will use Engine V2.
