If for some bizarre reason you need to pass a ridiculously huge amount of values, it's time to start experimenting with arrays.

Arrays - great things in proper programming languages with a manual. Gobbledygook in Simantics via SimPE

I've dabbled in them a fair deal in things like the Macrotastics shop-production for nonstandard production types, as well in Bathroom Uses you for caching purposes. Does SimPE even support it? I use Ye Olde SimPE, so I did it manually using documentation from Disasims and EAxis samples.

Well SimPE doesn't ban arrays - and it parses the array commands into text in as far as it knows about them. But I wouldn't say it was exactly "supportive" lol.

Tuna -- thanks! Those FFs have always been a puzzle.

What I've understood is:

Peter, are you quoting yourself?
Also the "starting with the temps" makes me think that there may be other sources for the values to be copied in the Params... What sources may they be? Global variables? Values read from "Me" (i.e. the interacting sim)? Anyway, I can't think to one single case where those values (Temps, Globals, sim's attributes) wouldn't be accessible using the standard ways (e.g. Param0 := Temp0)...

Yes Peter, that's roughly, briefly what we know

I was going to wait until I'd checked some more before bothering you about updating SimPE.
Just checked some more, so it's a bit less rough, and the code you wrote last time is still good :D
If you can change the string 'unknown operands' to 'Use Temps' - fix done.


I modified Numenor's test object and plugged in the lines where kill=1 from the old truth table.

[PHP]Test NV X72 X1 X0 Kill P_out Method
2 0 ? ? 1 1 0x0F NAR -> NAR
3 0 ? ? 0 1 0x0F UNK -> Temps
4 1 ? 0 0 1 0x0F UNK -> Temps
5 1 1 1 1 1 0x0F UNK -> Temps
6 1 ? 0 1 1 0x0F NAR -> NAR
7 1 ? 1 0 1 0x0F NAR -> NAR
8 1 0 1 1 1 0x0F NAR -> NAR[/PHP]

I did 2 tests, one using 0's for the ?'s, and one using 1's. Identical results.
So the existing null arguments bit ('all zeros') is still correct.

Thanks Tuna. Just to confirm my understanding:
[php]Test NV X72 X1 X0 Kill P_out Method
3 0 ? ? 0 1 0x0F UNK -> Temps
2 0 ? ? 1 1 0x0F NAR -> NAR[/php]Node version 0:
Does this mean that you can put anything you like in the other bits of b[12] (apart from X0) and it'll still pass Temps (if X0 is 0)? What about FF? Can you put anything in b[8-15] other than zeros? Or must b[8-15] be zeros completely (like I expect)? Or b[8-15] all FFs?
[php]4 1 ? 0 0 1 0x0F UNK -> Temps
6 1 ? 0 1 1 0x0F NAR -> NAR
7 1 ? 1 0 1 0x0F NAR -> NAR
8 1 0 1 1 1 0x0F NAR -> NAR
5 1 1 1 1 1 0x0F UNK -> Temps[/php]Node version 1:
In test 4, was X completely zero? Did setting any of X72 make a difference? What about values elsewhere in b[8-15]? (Expected result: same as tests 6-8.)
In test 5, what values are in the rest of b[8-15]? Zeros? FFs?

(In your earlier testing, you showed that if the receiving BHAV had >8 args defined, it received nothing from the caller - or UNK, which now know are the Temps and, it seems, go regardless! What we don't know is what, if anything, can fill the remaining params in the called BHAV.)

Node version 0.
Yes, it doesn't seem to matter about the other flags of b[12]. I didn't try every combo, but when the '?' are all zero, or all 1 it gives the same result. So that includes the b[12] := 00 -> Temps, and b[12] := FF -> NAR.

Node version 1,
test 4, with b[12] set to 00, or FC, it still worked out to be Temps.

In all the tests, the remaining values of b[8 - 15] were all zeros.
I didn't test those this time as I remember they made no difference whatsoever last time, hence why I left them out of the original truth table.


Yep, still no idea what the values of param8+ are when 'Use Temps' is in effect.
The values in the logs of both Numenors and mine are very similar though.
0 n 0 -1 97 0 0
Value for n were from 0 to 7. The others never changed.

I've still got the test objects and logs. So if you or anyone else wants to test a hunch just say so and I'll zip them up and post them

Heh but that would mean running the game!

OK, I'll work on the basis you've explained above. Thanks!

Most of my modding experience has been in The Sims One, but the basic structure of the Simantics Language (which strongly resembles the old Single Command Timex/Sinclair Basic I started with)...lol...I noticed that the interchangeability of parameters and temps is default. If a parameter was actually input into the command call, then it would override the temp, and allow that temp to pass info also. (Such as entering a value of 25 for decreasing social in a social interaction. In routines like create baby, a temp value was passed with parents Object ID, but the create DNA routine read them as parameters. used this routine to create sperm and zygote objects to more accurately simulate natural conception.)