Skip to content

Add documentation and scripts for comparing builds using UnityDataTool #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

SkowronskiAndrew
Copy link
Collaborator

No description provided.

@SkowronskiAndrew SkowronskiAndrew requested a review from Copilot June 18, 2025 21:26
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds documentation and PowerShell scripts for comparing Unity build outputs using UnityDataTool.

  • Introduces a new guide (comparing-builds.md) detailing file-level and database-driven comparisons, plus deeper AssetBundle inspection steps.
  • Adds a link in analyze-examples.md pointing to the new comparing-builds guide.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
Documentation/comparing-builds.md New end-to-end guide for comparing builds and AssetBundles.
Documentation/analyze-examples.md Added reference to the new "Comparing Builds" documentation.
Comments suppressed due to low confidence (1)

Documentation/comparing-builds.md:88

  • SQLite does not support FULL OUTER JOIN natively. This query will fail; consider emulating a full outer join with LEFT JOIN/UNION or another workaround.
FULL OUTER JOIN (


Each time a build is performed the output can change, based on changes in the Unity project.

A common question is "what changed", especially if more files changed that were expected. This question arises most frequently in the area of AssetBundles, rather than the player build, so the examples here focus on the AssetBundle case. But the same principals can apply to Player builds.
Copy link
Preview

Copilot AI Jun 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in wording: change "principals" to "principles" to use the correct term.

Suggested change
A common question is "what changed", especially if more files changed that were expected. This question arises most frequently in the area of AssetBundles, rather than the player build, so the examples here focus on the AssetBundle case. But the same principals can apply to Player builds.
A common question is "what changed", especially if more files changed that were expected. This question arises most frequently in the area of AssetBundles, rather than the player build, so the examples here focus on the AssetBundle case. But the same principles can apply to Player builds.

Copilot uses AI. Check for mistakes.


UnityDataTools does not natively support comparing two builds, but it can be done by analyzing each build individually into separate SQLite databases, then running queries to compare the contents of the two databases.

For example suppose two database are generated as follows:
Copy link
Preview

Copilot AI Jun 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar issue: "two database are" should be "two databases are" to match plural form.

Suggested change
For example suppose two database are generated as follows:
For example suppose two databases are generated as follows:

Copilot uses AI. Check for mistakes.

@@ -214,6 +214,10 @@ object_id type name pretty_size crc32
3866367853307903194 Sprite red 460.0 B 1811343945
```

## Example: Finding differences between two builds

This is a larger topics, see [Comparing Builds](comparing-builds.md).
Copy link
Preview

Copilot AI Jun 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar issue: change "topics" to "topic", and optionally split into two sentences for clarity ("This is a larger topic. See ...").

Suggested change
This is a larger topics, see [Comparing Builds](comparing-builds.md).
This is a larger topic. See [Comparing Builds](comparing-builds.md) for more details.

Copilot uses AI. Check for mistakes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant