I have discovered this problem before, and I don’t know if it can be solved. If there is no solution, perhaps a module for converting between worldspace and localspace can be added.
1 Like
Fully support this idea
Very annoying stuff
It did ruine a lot of good optimization for my projects’s macros
Also need to notice - WM already have some Materials nodes that already accept and process two different coordinate spaces - for example instance scattering use world and local spaces togher to produce output - so this idea already implement in WM, just need to make such for macros
1 Like
The intended process:
Inside your macro, select the Input device. For the inputs you want to be in localspace, change them from “Inherit” to “Localspace only”.
There does appear to be a bug that causes the macro settings to lose this property. This bug has been fixed for the next release.
3 Likes
THANK YOUUUUUUUUUUUU
increadible how one accidental post of bug report may make life easier - i did cry a lot for last three year of WM usage due to that bug, lol