Try fiddling with the arguments to ActivityMan:StartActivity.
Probably the third argument could be an optional scene argument.

That's what I was looking for. I'll see if it works.

Again, make a big list of activities. They should all have the same script path, but each one should specify a different default theme and have a different name.

But then they all appear on the scenario menu. This is the conundrum.

...I'm not sure why I didn't think of that.
As I recall, that third argument is what you need, so give it a try.

Rodger that. We'll see how we go.

There is no third argument.

So, that throws that idea aside.

Hmm.
Maybe there is a hidden function/variable to set it.
Or maybe it's not bound to the interface at all.

So we wait for B25 for the scenario toggle?

Or ask data.

TLB, I know you've been watching, could you ask him?

I didn't ask him yet, but I just ran a test and SceneMan:LoadScene seems to work. Not sure what the second argument is, but make sure you load the activity before you load the scene, because otherwise it crashes.

I'll have to try that tomorrow, it's getting late. Will update to tell you how it goes.

Trying to make a tutorial mission about all of this and encountered one problem. After I've loaded a scene inside my MissionLauncher activity and replace activity functions with dofile actors are not added when activity is initialized, but initialization function runs and without any errors. Enumeration actors don't give a single actor.

UPD:

Figured that out, case closed.