Behaviour when loading file is different to behaviour when re-running file

[hybridherbst]

This file tests all math nodes for float types:
20250109-MathTests.zip

! This issue requires the fixes from our fork at the moment – registering missing nodes etc.

However, when initially loading it, it looks like this:

When pressing Play again, it looks like this:

I'm unsure what's wrong here. I believe the data is correct but maybe there's something else going on.

[boguscoder]

@hybridherbst quick question, unrelated to your observation but related to your file:
are inputs to ADBE/output_console_node spec - compliant? Id imagine it need to be
value: ["message"]
instead of
value : "message"
They fail in my parser hence the question

[boguscoder]

Actually I just realized that no string value types are spec-compliant, but are often needed to test anything..

[hybridherbst]

Yeah, good question, and I believe it depends on the spec for ADBE/output_console_node, which is basically an extension – we're just using that because this viewer here supports it. Where strings are used in the rest of the spec is as configurations, and configuration strings are never arrays, so I'm honestly not sure.

Unfortunately I don't know how to get Aero (where I believe the extension is coming from) to actually export a KHR_interactivity file...

@lexaknyazev for string types used in extensions, like the ADBE/output_console_node, do you have a recommendation? Should the value be stored as value: [ "some message"] or value: "some message"?

[boguscoder]

Its one of those things I asked to clarify in spec, I think values are never not-arrayed whether custom types or not (your test file also have few booleans that need to be put into array, I think)

Speaking of custom types, spec only mentions them for variables not for inputs, so its unclear if its even allowed