# Problem code `'engine-conflict'`

> Contract 2.0.0 · package sha256 `a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e` · generated from `configurator-runtime.d.ts`, `tables/problems.json` and `services/onsite-scripter/scripts/contract-docs-what-to-do.json` by `services/onsite-scripter/scripts/build-contract-docs.mjs`; edit the source, not this file.

A member of [`ProblemCode`](../api/ProblemCode.md) · stable · since 2.0.0

Another 3D engine instance on the page conflicts with the runtime's (`info().renderer.engineConflict`).

## What to do

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)`](../api/Collection.set.md), never engine objects; `session.info().renderer.engineConflict` reads the flag.

## Where the declaration names it

- [`testing.FakeSession.record`](../api/testing.FakeSession.record.md): 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'`).