[RP-1] Broken automation scripts

[aihaw]

Hi! Playing under RP-1, I scripted my low (150km) polar orbit photograph satellites to shut down the experiment when battery is low and re enable it when high.
Obviously the energy balance is positive when in sunshine, avionics off and the experiment running (with real antenna at 100% transmission rate and time in the planner). The battery lasts longer than the nighttime, but it is balanced so that it needs form time to time to shut down the experiment to resplenish a bit.

To monitor how it works I enabled the scripts logs in the GUI.
I have four of them and when warping unloaded form the KSC or the tracking station the scripts only work once or so but not much more and I end with either a totally depleted satellite which I have no control upon or a fully charged useless (concerning experiments) satellite.

I also tried disabling the experiment when in night time and enabling it when in sunshine but it messes up as well and works only from time to time and often definitively enable/disable the module. Obviously when doing so I deleted the other rules depending on battery so they don't conflict.

Is it me messing up with it? or is it a known issue with RSS? Maybe it doesn't like warping for faster than 1000x (needed when mission lasts for more than 150 24h days)? I can't find any helping tutorial on scripting... Is it that we can only enable one kind of script at a time?

And thank you for the mod, it is amazing! I'm discovering it with realism overhaul and it's a bummer that I did not know about it earlier!

[gotmachine]

EC level / sunlight state automation events don't work reliably at medium/high timewarp speeds.
The issue is that at those speeds there isn't enough sampling points and solar panels EC production and sunlight become evaluated as a averages.
There isn't any way around that (and it isn't specific to RSS or RO).
Since that issue keep popping, and because we have no way to make those automation triggers work reliably, we have decided that they will be removed in the future.

We are also revisiting how things works regarding EC management to make those "underpower" situations a bit less annoying, in particular by allowing you to keep control when the vessel doesn't have any EC left but is still producing enough for "basic needs" like comms and command (or avionics in RO)

But no matter what we do, there will always be a discrepancy between what happen at low timewarp speeds and at high timewarp speeds, due to the fact that past a given speed the simulation step duration becomes greater than a single orbit duration. In practice, the effect is more visible in RO because the solar panel production is quite low and you usually build with tighter margins than in stock.

[aihaw]

Thank you for the quick answer! I guess I'll take that into account in my future mission planning (MoAr BaTTeRIes probably). As for the mission I already began, do you know a way to overcome the shortages like an infinite electricity option, but for background processing?

[gotmachine]

No, there is no cheat available.
But actually, the answer isn't "more batteries", it's "more solar panels".
Because of what I explained, at high timewarp speeds, batteries are useless (although experiments may work slower depending on battery capacity, but that's another issue)

[tsehao-hu]

Hi, I'm facing a similar issue.

I put a satellite on a sun-synchronous orbit (dawn/dusk), so theoretically the solar panel will always produce EC.

@gotmachine mention that

at those speeds there isn't enough sampling points and solar panels EC production and sunlight become evaluated as a averages.

But from what I've seen, it doesn't seem to produce EC at all at high time warp speeds (> x1000). The battery remains at 0 level even if I shut down the experiment. If I turn on the experiment, there's no data produced at all.