SSH terminal is slow / laggy. Colors are weird

Questions Royal TS (for Windows)
1

I am in the process or switching from Remote Desktop Manager to RoyalTS. I keep finding weird things that i cant seem to find an answer for. Here’s one thing that seems off.

In my ssh connections the redraw seems very slow in RoyalTS. I am using the same host, username, and workstation. When i use bashtop to view system performance the redraw in RoytalTS is very slow and the colors are way off.

What can i do to increase terminal performance? I’m including a screenshots to demonstrate the color in RoyalTS. I can’t upload one from RDM because i’m limited to one image since i’m a user user. This is the same host, username, and workstation. RoytalTS is very sluggish when drawing the graphs in the terminal. RDM is smooth.

This screenshot is from RoyalTS

Screenshot 2026-03-12 154032
Screenshot 2026-03-12 1540321978×933 33.1 KB

Here is a imgur link that shows two screenshosts.

https://imgur.com/a/W1Wqwjq

One from RDM and one from RoyalTS. Same machine / user.

Again this is the same remote host, same user, and same source workstation. RDM is smooth and fast, RoyalTS is sluggish and slow with weird colors.

Any suggestions?

2

Hi!

In Royal TS (for Windows) we have two plugins available: Rebex based and PuTTY based. I guess you are using the Rebex based one which has known issues and limitations regarding true color rendering and glyph fallback rendering. If you switch to the PuTTY plugin, this should work much better.

Let me know if this helps.

3

When i switch to putty it ignores my private key file specified in the credentials section, even if i save the keyfile password. It only prompts for a user password.

4

That’s weird. Are you using an exotic key file algorithm? Can you connect to the same machine using PuTTY alone using your key file?

5

I’m using a .ppk file generated for putty specifically. If i use the same .ppk file in putty itself the connection works just fine and allows me to auth with my key.

6

That does indeed look like a bug. Can you open a new ticket with all the details so that we can try to reproduce the issue?