Matrix on non-primary canvas

[Jimmy]

I have a q. about when you use matrix commands like Scale, Transpose, SetMatrix etc.
Excuse me that I dont' have any computer and code to share right now but it does not need any example really.

But the fact is simple really, if you use any matrix-related commands on the main canvas, they make it look really nice and smooth, camera motion aneverything. It has aa and whatnot enabled to take care of everything. You don't need to activate anything even.

But if you use any matrix commands on a secondary canvas. It's ugly. You will have non-AA etc, and you will see lots of uneven steppings everywhere. It's a big quality difference allround.

Why is this? What can you do about it in CX?

So I tried to set every compiler directive and every Load or New image canvas flags. No luck yet.

Anyone out there that knows what to do?

 

[Phil7]

Please give an example. What do you mean by secondary canvas?

 

[Jimmy]

I first tried to isolate the problem from 7000 LOC to give some example code and It took quiet a few days to do so, sorry about the delay.
Eventually I reached a point where I reliased it was not needed.

The problem I was struggling was has the famous title "phat pixels" / "fat pixels".