Jump to content

Search the Community

Showing results for tags 'navmesh'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Categories

  • Models
    • Animals
    • Barriers
    • Characters
    • Containers
    • Environments
    • Furniture
    • Props
    • Rocks
    • Vegetation
    • Vehicles
    • Weapons
  • Materials
    • Brick
    • Cartoon
    • Decals
    • Dirt
    • Grass
    • Industrial
    • Medieval
    • Metal
    • Plastic
    • Plaster
    • Rock
    • SciFi
    • Sky
    • Signs
    • Tile
    • Stone
    • Walls
    • Wood
  • Plugins
  • Scripts
    • GUI
    • Object
    • Utilities
  • Shaders
    • Post-Processing Effects
    • Surface
  • Sounds
    • Ambience
    • Effects
    • Music
  • Tools
  • BATTLE LEAGUE's Assets
  • BATTLE LEAGUE's Mods

Blogs

There are no results to display.

There are no results to display.

Forums

  • Leadwerks
    • Technical Assistance
    • General Discussion
    • Programming
    • Game Art
    • Suggestion Box
    • Bug Reports
  • Platforms
    • Windows
    • Mac
    • Linux
  • Community
    • Showcase
    • Promotion
    • Off-topic
  • BATTLE LEAGUE's Topics
  • Vec-Tec's Releases
  • Vec-Tec's Topics
  • Forth's Development
  • Forth's Game design
  • Forth's Graphics
  • Forth's Documentation
  • Forth's TODO
  • Forth's IMPORTANT
  • Forth's Screenshots
  • The uncertain world's Game Design
  • The uncertain world's Programming
  • The uncertain world's TODO
  • The uncertain world's Graphics
  • The uncertain world's Screenshots

Categories

  • Records
  • Entity
  • Command Reference
  • Vec3
  • Vec4
  • Script Reference
  • Shader
  • Index
  • Material
  • Object
  • Buffer
  • Asset
  • Font
  • Shape
  • Sound
  • Texture
  • App
  • Context
  • Model
  • Light
  • DirectionalLight
  • PointLight
  • SpotLight
  • Attractor
  • Camera
  • Emitter
  • Listener
  • Pivot
  • Bone
  • Sprite
  • FileSystem
  • Key
  • Source
  • Surface
  • Math
  • AABB
  • dVec3
  • Mat3
  • Mat4
  • Plane
  • Transform
  • Vec2
  • Vec3
  • Vec4
  • Mutex
  • Prefab
  • PickInfo
  • Map
  • Stream
  • System
  • Thread
  • Time
  • Window
  • World
  • Driver
  • SoundDriver
  • GraphicsDriver
  • PhysicsDriver
  • OpenGL2GraphicsDriver
  • OpenGLES2GraphicsDriver
  • OpenALSoundDriver
  • NewtonDynamicsPhysicsDriver
  • Draw
  • Color
  • Blend
  • Joint
  • Debug
  • Component
  • Steamworks
  • LensFlare
  • Vehicle
  • Decal
  • Quat
  • Leaderboard
  • Probe
  • Analytics

Categories

  • Games

Product Groups

  • Software
  • Gear

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Interests

Found 6 results

  1. This is a continuation of the "Carved CSG causes incorrect navmesh generation" thread since it was locked: http://www.leadwerks.com/werkspace/topic/13848-carved-csg-causes-incorrect-navmesh-generation/ I am using the latest Beta build with the CSG Carve fix. After using the Hollow command on a CSG brush, the colliders are incorrectly positioned outside of the brush. This issue affects NavMesh. Below is a screenshot displaying the issue: However, when you save the map and reload it, the issue correct itself and positions the colliders correctly as shown in the screenshot below:
  2. today i made a test because i want the navmesh see the doors. can we get a input field player radius, that is used for the space around the obstacles? in the screenshot the left door is 88cm, then come 1 meter and then 1,5 meter
  3. If I import a mesh into Leadwerks and set the physics property to convex hull or polymesh in the Physics tab and enable the nav obstical option, the models do not affect the navmesh at all.
  4. hello, it seems the nav mesh is not generated at my stair modells , this models using a polymesh collision. (the ai can not find me.)
  5. How limited are our abilities to play with Nav-Meshes? I can tell an entity to use one and be told whether its possible or not and as far as I know thats pretty much it. Can Nav-Meshes be targeted functionally? I was trying to see if I could use Camera::Pick() to know when the mouse was over a Nav-Mesh. I can have half the solution in that I can tell if the returned position is within a Nav-Mesh but I cannot guarantee that the Pick() will choose the surface with the Nav-Mesh
  6. Hi when I build a Nav mesh in the editor or through my scripts it doesn't reach the ends of my terrain(using Leadwerks terrain). What can I do? Picture--
×
×
  • Create New...