Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

_stepCount internal env prop should not be mapped #815

Closed
Robadob opened this issue Mar 2, 2022 · 0 comments · Fixed by #817
Closed

_stepCount internal env prop should not be mapped #815

Robadob opened this issue Mar 2, 2022 · 0 comments · Fixed by #817
Labels

Comments

@Robadob
Copy link
Member

Robadob commented Mar 2, 2022

It appears that the step counter's internal environment property is being mapped to submodels.

This causes any agent functions (and host functions) after a submodel, before the end of the step to report the incorrect step value when FLAMEGPU->getStepCounter().

Confirmed the problem, by updating the step counter env property after the submodel returns. However, the proper fix would be to block it from being mapped in the first place.

I would presume agent _id var wants to always be mapped. But there doesn't appear to be anything explicit in the code to handle this so far, just all existing usages use automap which maps all matching.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant