WorldSpace = ws;
LocalSpace = ls;
So, i have localspace map, and i try to distort it with worldspace perlin
Why that works correctly?
As i understand it is two different datatypes (ws and ls) but why distortion based on ws, applays corretly to ls?
It should not - the failure to warn you and disallow the operation is a bug.
Thank you for your report!
1 Like
waaait please:
but i have macro that uses localspace distortion to impact on position of object in worldspace
and it works fine for me
maybe you could like… add this behavior as checkbox or so?
because i really dont know what to do when you will remove this behavior - my macro, and it is idea will become not available to use
it is very comfortable to use 8km x 8km localspace to impact on something big in worldspace 
I understand that i will need to replace localspace distortion with another in worldspace… but you know, that 8km x 8km localspace square is much comfortable to use as interface - it not such big as 300km world
The reason why it’s important to fix this is that if World Machine does not realize that the placement info is in localspace:
- Not doing any validation of different aspect ratios/resolution/etc. It happens to work when they match, but as soon as you set the localspace resolution to something different, you will receive either nonsense or a crash.
I’m not understanding what using a localspace distortion on a worldspace packet is giving you right now. Again - it’s functioning is more of a happy accident! It will not function correctly for tiled builds, explorer, etc, and
1 Like
it will not function correctly for tiled builds, explorer,
aaa, want to mention, that i made couple of maps projects by using Tiled Builds with this bug - and here was no issues, eheheh
bug is works correctly in mentioned conditions
I’m not understanding what using a localspace distortion on a worldspace packet is giving you right now.
Also i did send you e-mail (on support@world-machine.com) where did describe which benifits this bug gives me currently. I did that not to change your opinion, just want to tell you why i started love this bug for last two years of WM usage and why do not want you to fix it, EHEHEH
also only now i understand what that error did mean… EHEHEHEH
update: no, sorry, it is error related to another device which i dont know how to fix, bruh
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.