[TopAce]

I noticed that the 'rand' integer disappeared from the lists of usable SEXPs. FRED_open yells at me when it sees a 'rand' integer which I implemented into the mission using FRED_retail.
So how about this 'rand' thing? What do you know about it?

[Bobboau]

hmm, someone broke something, I thought this got fixed

[karajorma]

Just tried it. He's right. It's not in the menu in either the Open GL version or the 20th Jan build.

[Goober5000]

Confound it, this was fixed.  Post it in Mantis, along with your mission.

[TopAce]

I am not posting that mission. The mission is not the problem.
Any missions with the rand SEXP would fail.
Just update it in the new build.

[Goober5000]

TopAce, if you don't tell me what the problem is, I can't fix it.

Post the mission, or if you don't want to give the mission away, just post the sexp that's causing problems.

[Bobboau]

uh, the rand sExp, just run any mission that has that sExp in it and see if it complains in debug

[karajorma]

It's completely missing from the SEXP menu too. It's like it never existed at all!

Topace stop calling rand an integer. It's not. It may output one but rand itself isn't one.

[Deathstorm V2]

I've had this problem ever since 3.5.5_e (the first one with the extended thruster trails).  If I want to play the main FS2 campaign, I have to go back to 3.5.1.

[TopAce]

Originally posted by Goober5000
TopAce, if you don't tell me what the problem is, I can't fix it.
...

1. the rand operator is not in the list of available SEXPs.
2. FRED yells at me when it sees a rand operator used.
3. I think the game works only with the lower value of the rand. But as far as I can remember, it doesn't complain at you.