1
Pathfinder / Future Release Wishlist
« on: October 07, 2021, 12:13:35 am »
Hi,
I have been using Pathfinder for a while and think it is a very impressive piece of software. There are some features I'd like to see in future and thought that others could chime in with theirs, too. I did find an older post about a wishlist but it didn't seem to catch on. There was a link to some other forum to talk about future features but this link was dead. Is there somewhere else we should discuss this?
In the meantime, here goes:
I'd like to see some sort of devices class that could be used to control behaviour switching and door availability. For example, instead of just having a door availability switch at a predetermined time as inputed to the table in the door properties, the door could be tied to a central timer and the availability changes are triggered based on that. That way if you had multiple doors that are to follow the same schedule but you want to change the schedule you could just edit the timer rather than find all the doors you want to affect and change their schedules. Maybe the trigger for these could be more complicated than just a timer, i.e. a door availability based on the number of occupants still in the room, or the flow rate through the door. I guess I'm thinking of something like the control logic in FDS.
How about scheduled (or triggered as above) accepted profile properties for doors/rooms? Just another level of evolving complex behaviour.
An idle wandering function, or random walk behaviour where an occupant enters a space and waits, but rather than following the current wait protocol of standing still and moving away from active doors etc, they just spread out randomly and walk slowly.
I have been using the new feature of attractors as triggers for behaviour changes based on occupants entering a room and these have resulted in some resonably complex behaviour, at least complex enough for what I wanted. So this is a nice feature and it has given be the taste for more complex modelling.
Please take this as an appreciative wish list, not a list of demand. Let me know if there are ways I have overlooked to achieve the desired functionality within the current model.
Cheers.
I have been using Pathfinder for a while and think it is a very impressive piece of software. There are some features I'd like to see in future and thought that others could chime in with theirs, too. I did find an older post about a wishlist but it didn't seem to catch on. There was a link to some other forum to talk about future features but this link was dead. Is there somewhere else we should discuss this?
In the meantime, here goes:
I'd like to see some sort of devices class that could be used to control behaviour switching and door availability. For example, instead of just having a door availability switch at a predetermined time as inputed to the table in the door properties, the door could be tied to a central timer and the availability changes are triggered based on that. That way if you had multiple doors that are to follow the same schedule but you want to change the schedule you could just edit the timer rather than find all the doors you want to affect and change their schedules. Maybe the trigger for these could be more complicated than just a timer, i.e. a door availability based on the number of occupants still in the room, or the flow rate through the door. I guess I'm thinking of something like the control logic in FDS.
How about scheduled (or triggered as above) accepted profile properties for doors/rooms? Just another level of evolving complex behaviour.
An idle wandering function, or random walk behaviour where an occupant enters a space and waits, but rather than following the current wait protocol of standing still and moving away from active doors etc, they just spread out randomly and walk slowly.
I have been using the new feature of attractors as triggers for behaviour changes based on occupants entering a room and these have resulted in some resonably complex behaviour, at least complex enough for what I wanted. So this is a nice feature and it has given be the taste for more complex modelling.
Please take this as an appreciative wish list, not a list of demand. Let me know if there are ways I have overlooked to achieve the desired functionality within the current model.
Cheers.