IR Rotatron MK2 wrong direction after time warp

[CMXLargo]

After a timewarp rotatron turns in wrong direction. See my video.

https://www.youtube.com/watch?v=Cgnj45xc5Ak

InfernalRobotics 2.0.10
KSP 1.2.2

[ZiwKerman]

Interesting. Can you post the craft file as well, so I can test it, please?

…

Sent from my iPad On 19 Dec 2016, at 22:10, CMXLargo <[email protected]> wrote: After a timewarp rotatron turns in wrong direction. See my video. https://www.youtube.com/watch?v=Cgnj45xc5Ak <url> InfernalRobotics 2.0.10 KSP 1.2.2 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#140>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKuLcNhM2DCH9-QWQM9MDhzREBO7IXZjks5rJwDPgaJpZM4LRPXk> .

[CMXLargo]

Only with OPT 1.9.2 Parts.... please

Prototype.zip

[ZiwKerman]

Can you try replacing your current InfernalRobotics.dll with this one:
https://drive.google.com/open?id=0B9f5PHcywXQIQXJ0RHdaZWJQQWM

It is a minor change, but it solves couple issues. Also with this dll I could not reproduce your problem.

[CMXLargo]

The problem still exists. But it is only present when the rotor is not in the zero position during the time warp. Have you tested it with my Craft-File?

[ZiwKerman]

I did, though not extensively. Will do more tests tomorrow.

[CMXLargo]

I've found the problem is not the rotor, but the angle of the rotor base is changing. The IR Rotatron MK2 has an arrow or nose that change position abruptly.

[ZiwKerman]

Did you try the dll I posted, it should fix the rotating base issue with timewarp.

[CMXLargo]

I replaced the DLL with yours. Problem still exists. I think that after the Timewarp the base to the last rotor position is set to zero. Thus, although the rotor is still the base at the adjusted angle, the base is rotated as if the rotor were in the zero position. If you want I can make you again a video in which you can see it exactly.

[CMXLargo]

I tested again today. The problem is solved with the new DLL. No idea why the error was active again this week.