Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • openmw openmw
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenMWOpenMW
  • openmwopenmw
  • Issues
  • #5771
Closed
Open
Issue created Dec 29, 2020 by AnyOldName3@AnyOldName3Maintainer

ori command should report where a mesh is loaded from and whether the x version is used.

When trying to debug things, it's useful to know which mesh file is actually being loaded. Unfortunately, with our VFS and support for BSA archives, it's not always clear, especially as the engine will sometimes use the x-prefixed version of a mesh without ori saying so.

If the ori console command reported which data directory, and, when relevant, which BSA file, a mesh was loaded from, as well as whether it's actually using a different file, this would be much easier.

Edited Dec 29, 2020 by AnyOldName3
Assignee
Assign to
Time tracking