Hello Martin,
Thank you for the detailed message, and for your many years working with PlayCanvas. We appreciate that long-running client projects can still require small updates from time to time.
Unfortunately, we won’t be extending the July 1st deadline or providing a dedicated Engine V1 Editor link. The Engine V1 Editor fallback has already remained available for a long migration period, and keeping it open would still mean maintaining a separate Editor/runtime path.
To clarify the available options:
- Existing published PlayCanvas builds are not affected and will continue to serve their current version.
- Any new update published through the Editor or PlayCanvas Hosting after July 1st will need to use Engine V2.
- If a project must stay on Engine V1 for now, we recommend downloading a known-good build before July 1st. The Vite download option can help with faster local iteration on exported builds, but that workflow is outside PlayCanvas Hosting and Editor publishing.
- For projects that need ongoing Editor or PlayCanvas Hosting updates, the path is migration to Engine V2.
The User Manual includes docs for Engine compatibility, Engine V1 to V2 migration, and scripting migration. The Asset Auditor in the Editor can also help identify common migration issues, especially around sRGB texture settings and visual differences. The PlayCanvas VS Code extension may also help with script migration by mirroring text assets locally and working well with source control, type checking, and AI-assisted review.
If you hit specific Engine V2 migration blockers, please share details, screenshots, console output, or a minimal repro. We can look at concrete migration issues, but we can’t keep the Engine V1 Editor fallback open past the deadline.
Regards,
KPal