Asset LOD and Texture Budget Auditor
Audit declared per-asset LOD triangles and shared texture usage against explicit budgets, retaining missing resources and exact uncompressed mip estimates.
Loading tool…
How to use Asset LOD and Texture Budget Auditor
A shared texture should count once in a project estimate, while each asset still needs a delivery budget. Inspect LOD ordering and declared resource references before checking the actual engine build.
- Enter measured metadata and buyer-agreed budgets.
- Inspect LOD ordering and shared texture estimates; missing references hold completion.
- Review actual scale, rigging and appearance in the target engine; this tool does not inspect geometry.
Good to know
- Estimated uncompressed texture bytes exclude alignment, compression, mesh buffers and runtime copies.
- Metadata/rights and actual compatibility remain unverified.
- Independent local review of supplied records. No account/API access, AI, publication, outreach, source-truth verification, legal certification or income forecast.
- Each field is limited to 8,000 UTF-16 characters and each CSV to 100 data rows with the exact displayed header. Quoted commas/newlines and doubled quotes are accepted. Unsupported controls, unpaired surrogates, duplicate identities and invalid records are refused rather than silently removed. Ordinary decimal inputs have magnitude at most 999,999,999; the smallest supported nonzero magnitude is 0.000000001. Exponents are refused; whole counts use exact integer checks before numeric conversion. Results use exact rational arithmetic, with at most 18 decimal digits and an ellipsis when further fractional digits remain.
- Markdown and CSV are editable review exports. CSV retains unresolved records and apostrophe-prefixes spreadsheet-like formula text; review your real import settings. Tool outputs can contain your entered pseudonymous records, so inspect them before sharing.
- Independent deterministic ToolJovia workflow. Inputs stay in this browser. No vendor account, model call, upload, publication, outreach, payment, saved input or outside service is used. A local reconciliation does not validate source truth, customers, income or legal compliance.
Research behind this workbench
These cases explain the business mechanism. The workbench is ToolJovia's independent adaptation, not a claim about the company's internal workflow or an endorsement.
Common questions
Are the byte estimates measured VRAM?
No. They are exact uncompressed channel-byte totals with the selected floor-halving mip dimensions. Alignment, compression, mesh buffers, residency and runtime copies are excluded.
Does a missing texture count as zero bytes?
No. Known bytes remain visible but a missing referenced texture withholds the complete project estimate. Inspect actual assets, rights, rigging, scale and engine behavior separately.
Keep going with related tools
All data →Binary STL Mesh Inspector
Inspect local binary STL triangles, source dimensions, area and edge incidence. Download complete geometry JSON or facet CSV without uploading the model.
FilesglTF and GLB Resource Inspector
Inspect a glTF 2.0 JSON or GLB file, its buffer ranges, node hierarchy and inert image-resource references.
DataTraining Dataset Consent and Split Auditor
Audit pseudonymous dataset hashes, actual split labels and purpose/date-bound permission declarations while keeping coverage separate from permission clearance.
EducationStudy Family Identity Auditor
Audit declared paper-to-study families for repeated DOI assignments, registry conflicts and unassigned reports without inferring independent evidence.