'engine-conflict' ​Contract 2.0.0 · package sha256
a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e· generated fromconfigurator-runtime.d.ts,tables/problems.jsonandservices/onsite-scripter/scripts/contract-docs-what-to-do.jsonbyservices/onsite-scripter/scripts/build-contract-docs.mjs; edit the source, not this file.
A member of ProblemCode · stable · since 2.0.0
Another 3D engine instance on the page conflicts with the runtime's (info().renderer.engineConflict).
Another copy of the 3D engine was loaded on the page before the runtime: remove it from the page unless the page draws its own canvas with it. Content in the runtime's scene goes through session.collection(name).set(spec), never engine objects; session.info().renderer.engineConflict reads the flag.
testing.FakeSession.record: For Problems the fake has no route to, such as 'render-lost', 'engine-conflict' or 'frame-budget'.The set is open: handle a code you don't know ('other').