Soyuz Guidance MFD is giving me trouble rendezvouing with the ProgressM. I seem to run short on fuel.
I have tested a lot of times, I will redo the whole flight but I have never had a problem going to ISS using Soyuz guidance MFD.
I've recently noticed that Rotation RCS burns as of Beta 3 to 4 seem to mess with relative velocity when docking even in close range. Seems slightly unbalanced. Just undock in the included docked scenario and use the RCS in rotation mode and look at the velocity vector. Earlier it wasn't disturbed at all. I Don't know if this is intended and a real behaviour of the progress in real life so decided to mention it.
Ok, I have noticed the problem too, I am on it.
I don't know where the problem is exactly, if you fire left as well as right yaw thrusters or both up and down pitch thrusters, it's intended as their positions induce that but firing just one line should not induce change in velocity.
So it seems like we'll have some delay before the release...
EDIT:
I was unaware of that, the rcs model induces this comportment, more precisely it is pitch and yaw thrusters firing direction (one thruster oriented at 45°from z axis instead of 2 thrusters balanced over cog and firing at 90° from z axis).
That's pretty annoying, especially if you use Gravity gradient torque. I have tested one addon with the same kind of thrusters directions (some using 45° as well) and I get exactly the same comportment.
In the past, I used to idealize the thrusters but that's impossible with particles streams as AddExhaustStream() doesn't offer a way to indicate a direction for the stream. It follows the direction vector declared in the thruster definition, so the thruster must provide the 45° orientation. No way to cheat on this.