Skip to content

Specify defalt state #906

Answered by Robadob
SYkirk asked this question in Q&A
Aug 19, 2022 · 1 comments · 15 replies
Discussion options

You must be logged in to vote

There are two possible causes I can think for this off the top of my head.

  1. You're using an old build of FLAMEGPU2 and spatial messaging, there was a bug that causes this exception to be thrown and has been resolved.
  2. You're calling a function which has a default argument default and need to specify the desired state. The most obvious one that comes to mind is FLAMEGPU->agent(agentName, stateName) within the HostAPI (this is what caused the above bug).

If you could grab the call-stack or location the exception is being thrown from, it would help narrow down the cause.

The problem was confirmed as issue (1) via email.

Replies: 1 comment 15 replies

Comment options

You must be logged in to vote
15 replies
@SYkirk
Comment options

@Robadob
Comment options

@Robadob
Comment options

@Robadob
Comment options

@SYkirk
Comment options

Answer selected by SYkirk
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants