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
  • #5762
Closed
Open
Issue created Dec 24, 2020 by wareya@wareyaDeveloper

Movement solver is insufficiently robust

This is an umbrella issue for behaviors fixed by the new movement solver but that don't have other issues filed.

  • The movement solver doesn't actually slide across surfaces (it only does the vector rejection part, not the "get close to touching" part)
  • Lack of a proper safety margin
  • The bit of code in the movement solver that looks like "unstuck"ing doesn't actually function as such
  • Actors don't unstuck themselves in general, which leads to problems with various vanilla entrances/exits that place actors slightly inside of geometry
  • The movement solver gets snagged on sloped concave acute geometry easily (because bounces go back and forth between two nearby surfaces until it runs out of bounces)
  • Various interactions involving jumping, stairs, slopes, etc. do not function the same way as they do in vanilla
Assignee
Assign to
Time tracking