If you will press on Center button, input data will be not moved to center as it should i guess
I can not replicate this.
interesting
could you send me project with those nodes?
maybe we have some difference or in project settings or in nodes placement settings ![]()
Start new project
add nodes
select Crop nod and change position to 0,0
Press center
Radial goes back to center
But your radial grad
Have shift
If you will center main radial grad
And press “center” in crop and transform - shift will appear again
And that will be with every localspace node
So you can reproduce it ![]()
I can not replicate it.
But when I look at your pixtures it show 512px on the second picture but in the third picture it show only 2px…. Should it not say 512px there also?
i really think we have different settings in Radial Grad
my is centered by 4km, 4km
i guess your may be not centered
or we have different project settings
Could you repeat it
And send here project file, please? ![]()
![]()
I did own tests - and do not understand what difference between mine and yours projects ![]()
just reminder ![]()
![]()
say no if no ![]()
![]()
Thanks!
Bug caused by difference in project settings
If you will set origin to 0, 0 - it will count center of you project as center position for all LocalSpace objects, ignoring actual center
Radial Grad use actual center at all cases even beening in LocalSpace mode
But Crop&Transform ignore it and dependent from projects settings, which make it usage uncomfortable - because you need to change project origin settings each time to match new center
For example, your project will break localscape position, if you will make you nodes to be 2.0 LocalSpace. Center button will work inside Radial grad - but will not work in CropTransform
i dont know is it a bug
or i’m wrong in localspace usage
or it is potenrial feature request fix
project:
test.tmd (20.2 KB)
Ohh . Now I understand .
You are correct.
The node Crop & Transform are using Position 0,0 instead of 4km,4km……
This will requer the user to change the Position every time the nod is used…..Strange?!?!?
Feature, Finess, Bug??
@Stephen might have the answer for this?










