v2.3.0

🔥 It’s official — the PlayCanvas Editor frontend is now open source! 🧑‍💻✨

• 🎥 Check out this demo video to see how you can tweak the Editor UI to your liking!

• ⭐️ Help to support us and our community by starring our repository

• 📝 For more information read out most recent blog post

What's Changed

• Open sourcing of PlayCanvas Editor Frontend by @kpal81xd in #1346

New Contributors

• @kpal81xd made their first contribution in #1346

Full Changelog: v1.24.9...v2.3.0

v2.2.0

Note

Please note that these release notes are to track new features and changes to the PlayCanvas Editor. They do not contain the source code to the Editor.

Removals

• Support for v1 flag for using legacy Editor running with Engine V1

Important

This does NOT remove support for Engine V1 projects. This change will only support Engine V2 in the viewport but will continue to allow for Engine V1 in the launcher and published/downloaded apps for Engine V1 projects.

v2.1.2

Note

Please note that these release notes are to track new features and changes to the PlayCanvas Editor. They do not contain the source code to the Editor.

Deprecations

• Deprecation warning message for Editor powered by Engine V1.

Important

Please make sure all projects run correctly in the Editor powered by Engine V2. The deprecated Editor is scheduled for deletion on 22nd April (Postponed to 28th April). For details see here

v2.1.1

Note

Please note that these release notes are to track new features and changes to the PlayCanvas Editor. They do not contain the source code to the Editor.

Bug fixes

• Template create invalid name error handling #1284
• Script create entity reference fix #1285
• ADD COMPONENT menu position fix when pressed using keyboard #1286

v2.1.0

Note

Please note that these release notes are to track new features and changes to the PlayCanvas Editor. They do not contain the source code to the Editor.

What's New

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.

Important

This switchover does not impact any project data. If you encounter issues running with the Editor running Engine V2 for your project use the query parameter v1 to use Engine V1 in the Editor (deprecated)

Viewport Camera Settings

Editor V2 now has separate gamma and tonemapping settings for the viewport located under Settings -> Editor

Asset Auditor

Editor V2 adds a new status bar option for asset audits to help aid setting sRGB flags on textures depending on their usage.

Important

Remember to check the Asset Auditor If your materials look different in the viewport compared to the launcher. Differences in appearance are usually related in incorrectly set sRGB flags

Audit Warning

Audit Error

In most cases sRGB flags can be automatically set however conflicts have to be resolved manually following console errors.

Dialog

This auditing feature will be expanded on in the future.

Documentation

For further information on engine compatibility in the Editor can be found here

v2.0.7

Note

Please note that these release notes are to track new features and changes to the PlayCanvas Editor. They do not contain the source code to the Editor.

What's New

• Decolorized icons for console status icons so they will only color for if there is a console entry

Editor V2 Only

• Moved assets auditor button left of job counter in status bar
• Updated sRGB checker to only warn if sRGB is off and texture is used by StandardMaterial (Material Assets and any UI Component)

v2.0.6

Note

Please note that these release notes are to track new features and changes to the PlayCanvas Editor. They do not contain the source code to the Editor.

What's New

The ASSET AUDITOR has now been moved to the status bar to complement the console better. It now shows the number of available audits.

Note

This feature is only currently available for the Editor running with Engine V2

Bug fixes

• sRGB conflict fixes
• WebGPU launcher fixes

v2.0.5

Note

Please note that these release notes are to track new features and changes to the PlayCanvas Editor. They do not contain the source code to the Editor.

What's New

📚 ESM Import Maps

You can now create Import Maps in the editor 🥳 This allows you to define custom module resolutions directly within a project, making it easier to work with bare modules.

Create an Import Map in the Project Settings panel.

Import maps allows you to set rules for resolving modules in your ESM Scripts. You can create shorthand names for local modules or external modules or paths.

{
  "imports": {
    "react": "https://esm.sh/react",
    "@utils/": "./scripts/utils",
     "@math": "./scripts/utils/math.mjs",
  }
}

You can then import them directly in any ES Module in your app.

import react from "react"
import tools from "@utils/tools.mjs";
import math from "@math"

When you export or publish your project, local modules are resolved in the build step whilst external modules, like those pointing to https:// resources are kept external.

Engine 2.5.1 📣

We're promoting v2.5.1 of the engine to the editor. This includes a few fixes and updates. Check the release notes for more.

Fixes

2.0.5 includes a number of small fixes that catch edge cases with attribute parsing. We've also fixed some issue relating to the code editor when creating new text assets

v2.0.4

Note

Please note that these release notes are to track new features and changes to the PlayCanvas Editor. They do not contain the source code to the Editor.

What's New

Load more apps button

We have added a button to allow you lazy load as any published apps as far back as you would like instead of restricting you to just viewing the most recent 16 applications.

Saved Primary Scene

When publishing your primary scene (indicated with the orange bookmark) is now saved per branch per project.

Note

Additionally when toggling your primary scene the order of scenes will now remain the same.

Bug fixes

• IDE autocomplete fixes

v2.0.3

Note

Please note that these release notes are to track new features and changes to the PlayCanvas Editor. They do not contain the source code to the Editor.

What's New

New Asset Auditor

This new dialog is aimed to give users more control and oversight over the usage of assets within their project.

This release includes texture auditing to help fix sRGB flags on textures in projects running on engine v2.

Note

For more information on how gamma is handled in PlayCanvas refer to our user manual

More features will be included in subsequent updates so stay tuned!

Bug fixes

• ESM script fixes