Luis

Dev

[Luis @_blubs]

∀😂∈𝕌 ∃😘👌∈𝕌 → (😂≠😘👌)

[Luis @_blubs]

went silent there for a bit, had a few surprise design decisions to iron out before I could continue

... but I've got FTE and PSP running off the same QuakeC progs again and will begin writing the new AI to work with IQM + navmeshes on both platforms simultaneously

[Luis @_blubs]

the great synchronization begins

time to tie it all together

[Luis @_blubs]

@DerpedCrusader soon 👀

a few more features on Vril, then I pivot to getting FTE and Vril to have the same feature-set while I get the AI to use these things on all platforms simultaneously!

[Luis @_blubs]

no time to explain, but trust me when I say this is cool as hell
#nzportable

[Luis @_blubs]

traversal entrance / exit widths are planned to be adjustable via the navmesh editor

Ex1) AI can hop along a fence straight across to the other side and land anywhere on the traversal exit line segment
OR
Ex2) AI can hop along a fence but they'll always land at the same point

[Luis @_blubs]

So traversals are back (AI doesn't use 'em yet, but the navmesh pathfinding code uses them), with a new feature...

Traversal entrances / exits can be line segments!

You could place a single traversal along a fence and the AI will hop that fence anywhere along it!

See vid

[Luis @_blubs]

no time to explain, but trust me when I say this is cool as hell
#nzportable

[Luis @_blubs]

It's been a few months of steady marching, but I might finally be back to the fun part of gamedev where progress can actually be seen visually again and shown off :')

[Luis @_blubs]

@DerpedCrusader lmao it was scary to take a close-knit moderately complex system, rip it apart and put it all back together 😅

many design decisions no longer held and needed redesigns

but it’s in the best shape of its life now 🫡

[Luis @_blubs]

this took a long time…

pretty major rewrite of IQM for #nzp to make most of the code platform-agnostic and cleanly separate that between platform-specific bits

finally tried it on HW and it worked first try :-)
(also note the test navmeshes)

… just a few more loose ends

[Luis @_blubs]

:')

[Luis @_blubs]

smooth
#nzportable #navmesh #dquakeplus

[Luis @_blubs]

yellow: raw path from A* on polygons (similar to old waypoint path)
red: smoothed path through the navmesh

Note the missing navmesh polygons on the bottom left due to frustum culling, just a visual bug, the navmesh is there

[Luis @_blubs]

@Turenightmare Pathfinding on a navmesh generally has two:

1. A* on the polygons (done)
2. path smoothing to calculate final path (wip)

NZP's will also have:
3. Mix-ins to handle traversals along the path, which requires handling throughout

[Luis @_blubs]

cookin'
#nzp #dquakeplus #navmesh

[Luis @_blubs]

@DerpedCrusader lol cooked him

[Luis @_blubs]

I WANT TO BELIEVE
#nzp #dquakeplus #navmesh

[Luis @_blubs]

@DerpedCrusader What was once just shitposting is becoming REAL

[Luis @_blubs]

YES

Took me way too long to fix the debug line drawing. (Occasional stutter due to console prints getting written to disk)
#iqm #nzportable

[Luis @_blubs]

@DerpedCrusader Seeing the animated camera on an actual PSP is incredible :’)