MDT System: setup checks & troubleshooting
Investigate startup, access, interface and record-saving issues in the Five Studios police MDT without guessing configuration values.
Use this alongside the instructions included with your purchased release for exact resource names, supported versions and configuration values.
Confirm your supported setup
Read the instructions supplied with your MDT release and match them to your framework or standalone setup. Use the documented integration option and dependency versions. Do not assume that a configuration for another framework works unchanged. Back up the existing configuration and database before updating an installed system.
Install the complete package
Keep the original resource name, manifest, scripts and interface assets together. Start the documented dependencies first. Apply a supplied database migration only as instructed for your installed version; do not repeatedly import a schema into an existing live database. This guide does not supply replacement SQL, table names or undocumented configuration keys.
The MDT does not open
Check that the resource and its dependencies start. Use the opening command, key binding or interaction documented for your release. Confirm the test character has the configured job, grade and duty status. If an authorised character can open it but another cannot, investigate access configuration before reinstalling the interface.
Blank interface or controls that do not respond
Check for missing interface files after upload and capture a short relevant client or server error with secrets removed. Test the original configuration and close other custom interfaces before comparing. Describe whether the interface never appears, appears blank or opens but ignores input; these are different failure points.
People, vehicles or records are missing
Verify the supported framework integration and database connection using the package instructions. Test with a known record in your test environment and distinguish an empty search from a save operation that fails. If data disappears after reconnecting, describe exactly which record type and action failed. Do not paste a database password, a real person’s data or a full database export into a ticket.
Calls, duty controls and updates
Check the documented permissions and integration settings for the feature affected. Test one action at a time, such as changing duty status or handling a test call. When upgrading, read the release’s migration notes and retest existing records as well as new ones. Preserve a rollback copy rather than mixing files from two releases.
Ask for help with evidence
Open a private ticket and identify the MDT System in the subject. Include purchase evidence, release version, framework and dependency versions, the action that fails and what you have already tested. If MDT is not yet available in the product selector, choose General / purchase enquiry and clearly state that this is an MDT support request from the product owner. Attach sanitised screenshots, not log files.
Reference: Official FiveM resource structure and dependencies