Working now in latest dx11 March version - outdated information.

Here's the second model we discussed

What exactly do you mean by this. What is dynamic?



This is because Lee is incorrectly creating a compound collision shape for the EBE structures.

Seems the problem is with the waypoint node not connecting with the terrain.

I have found an alternative solution:

1. Make your EBE structure as normal, using the EBE stairs (not a separate model).
2. Erase the piece of floor at the foot of the stairs.
3. Place floor zones where you want NPCs to go.
4. Place a waypoint extending from the patch of terrain at the foot of the stairs up to the next floor at the top of the stairs.
5. Press E.
6. Place a new EBE building site.
7. Within the new site place a piece of floor matching the one you erased from the first site.
8. Press E.
9. Extract the piece of flooring you just created and drag/drop it into the gap you made in your first structure.
10. Save the piece of flooring as an EBE structure.
11. Edit the flooring's FPE file: collisionmode = 0

Worked for me. The trick is to make sure the waypoint stays connected to the terrain. This, of course, only works for ground floor stairs.

However, it is possible to get an NPC to go up/down EBE stairs by using a floor zone and a waypoint. It is extremely fussy but it can be done.

@STAB-Making an entity dynamic, such as an EBE building or barrel or character, you can add LUA scripts to them. On a side note, I found when creating my apps, that NPC's work better if a building is set as dynamic. They respond better, but that was a few months ago when revisiting glass breaking for FPSC levels. IF I made an FPSC level that I'd imported into GG and set that level to dynamic and added a couple of character enemies, they climbed through the windows (when broken). With building set to static they didn't do much just looked lost.

This seems strange to me. I have an EBE structure with three levels. Only the first set of stairs (which are the EBE stairs) has a floor zone. The second set of stairs doesn't have a floor zone. Yet an NPC is able to go up the stairs. Is this normal?

BTW, I am using smallG's altered module_combatcore.lua script to minimise getting shot through walls.

Well, then this is one of the major problems with GG. Buildings should NEVER be DYNAMIC.
Setting an entity to DYNAMIC causes GG to make the entity a dynamic physics object.
The more DYNAMIC objects the physics solver has to handle the slower GG runs.
Only entitys that will be moved by physics (e.g. a rolling barrel) should be DYNAMIC.
All other entitys that will be not be moved by the physics engine(e.g. a stationary building) must be STATIC.
Seems very wrong that an entity needs to be DYNAMIC to have a script attached to them.
Another slow down is that GG creates a DYNAMIC NPC controller which when interacting with
say a building that you have made DYNAMIC adds to the work load of the physics solver.
The NPC should be Kinematic only. Kinematic interacting with STATIC objects do not
slow down the physics solver.

Updated first

@Stab in the Dark software . Hello. Oh, yes dynamic stairs. Don't worry I know it wasn't the best option, though an option.
Thank you also for explaining physics solver and helping me make the decision to search for a new option.

@lordjulian , Great work around with waypoint. And thank you for your information for others also.

@Bored of the Rings, Out the windows. very nice. Yeah dynamic shows interesting results, I noticed a slight barrier and letting the Npc glide down the stairs.

Are you basically saying the NPCs will climb stairs as long as there are 22 steps?

I have found I can get them to do any number using a floor zone. Trouble is if I try adding a second floor zone it breaks this AI.

OK. Thanks, Defy. My NPCs are now using stairs flawlessly (no pun intended) just with waypints. The key seems to be the polygon collision plus extending view range.

@Lordjuilian, You're welcome. Happy game dev.