Before answering questions about DTS product usage, configuration, interfaces, or faults, first look up the official documentation matching the product and version. Applicable pages already read in the same session may be reused; query again when updates, different versions, or uncovered interfaces are involved. Do not infer product requirements solely from old project code or experience.
Identify the Product and Version
Determine based on the user's explicit statements, the current question, the SDK referenced by the project, configuration, logs, and installer information; do not load documentation for unrelated features just because the repository uses DTS.
- Distinguish server-side product versions from front-end SDK versions; they may differ.
ac_conf.jsPaths, old class names, and source code comments are only clues and do not independently prove the running version. - When the user provides documentation for a certain version, read that documentation first; when local evidence is inconsistent, point out the discrepancy.
- When the version is unknown, first check accessible project evidence. Ask for the version when necessary, while continuing version-independent localization; do not default to the latest version.
- Cloud rendering front ends usually involve both Cloud + SDK: check Cloud for service deployment, and check the SDK for player parameters and scene APIs. Do not fix-route the entire project to a single manual.
Choose a Documentation Entry Point
Main entry:DTS Documentation Center. Enter the target version from the version navigation on the homepage, then follow the product and chapter links. Below are verified 7.0 entry points (2026-10-29); for other versions or when links fail, rediscover from the homepage, and do not guess links by substituting the version number in the URL.
| Capability involved in the question | Documentation entry and lookup direction |
|---|---|
| Creating projects, editing scenes, materials, layers, tours, and client operations | Explorer |
| Cloud rendering deployment, CloudMaster service configuration, nodes, instances, connections, NodeService | Cloud, then enter the corresponding subchapter |
| Data conversion, 3DT, input formats, and processing software | Engine |
| Web integration, player, fdapi, scene interfaces and callbacks | SDK、Quick Start, then look up specific classes and methods |
| Responsibilities of the scene SDK and the Cloud management tool/MCP | SDK and AI Integration, then read the target tool documentation |
| Error codes, logs, licensing, or cross-product common issues | Enter from the support/topic navigation on the homepage, and verify the applicable product and version |
Lookup and Verification
Use currently available web page reading and search tools; do not bind to a specific plugin. Prioritize reading known pages and in-site links; when a page is only a table of contents, continue opening the relevant chapters; do not use a table of contents as a substitute for interface evidence. When content cannot be found, use site:doc.freedo3d.com plus the product, version, interface name, or error code to search, and open the result body.
For configuration and APIs, verify field names, requiredness, default values, the object containing the parameter, callback timing, and applicable versions. Before code changes, also verify the ac.min.jsactually loaded by the project, bundled examples, or type declarations; the documentation having a capability does not mean the current SDK supports it.
- Distinguish between explicit documentation rules, example usage, and local implementation behavior; the documentation not mentioning something does not mean it is explicitly unsupported.
- Historical version documentation and update records can explain migrations, and are not silently concatenated with target version parameters.
- When the current documentation differs from the local SDK, provide evidence for each separately, choose the adaptation approach based on the user's actual environment, and do not automatically upgrade the SDK.
- If reading fails, try other available reading tools, official site search, or local bundled materials. If it still cannot be confirmed, state the missing evidence, do not fabricate APIs, and do not treat search snippets as complete specifications.
Cloud / SDK integration troubleshooting key points
When encountering ac_conf.js、ws://undefined or player connection issues, check along the chain of "HTML load configuration → global configuration fields → application concatenated address → SDK constructor parameters → actual request".
Confirm the purposes of the player connection and the management connection separately. Do not assume that all Cloud integrations must provide /manager just because an old application connected to Managerfirst; nor should you remove the management functionality the user needs just because of a direct-connection example. Decide based on the target version examples, the local SDK, and user requirements.
Note that application configurations such as HostConfig.UseHttps and the SDK's options.useHttps belong to different layers; check whether the application actually passes them through.AirCityPlayer Whether compatible names such as are usable depends on the actually loaded SDK. The SDK-supported instance/project selection, events, and reconnection capabilities should be reused first.
Output
Give the conclusion and the applicable product/version first, and provide specific official section links adjacent to key explanations. When project issues are involved, point out the relevant configuration or code locations, and distinguish documentation verification, static inspection, simulated testing, and real service verification.
Consulting documentation does not automatically authorize deployment, service restart, modification of remote instances, or tool installation; act within the scope of the user's current task.