ah, OK, after paying a little more attention here I know what's up.
I was testing the macro in the first post of this thread which works fine -- the followup posted, however, depends upon having the plugin DLL available. WM 2.3 updates the core architecture and renders all previous plugins invalid -- it will have to be recompiled for WM 2.3.
So bottom line -- its just not possible to use this macro at the moment. However, as mentioned the more limited one does work fine.
I get the "There was an unknown error loading this macro." message with Rotator. I put the .dev and .dll in "C:\GRAPHICS\WorldMachine\WorldMachineDocuments\Macros" which is the path set in my preferences "Paths" for macro storage. This is with Beta 2.3 x64.
your macros are placed in the WM documents folder under your username. The one in the program files directory is the "stock" macro folder that it creates each users repository from.
Regarding the first problem, sometimes macros produced in earlier versions of WM are not loadable. When I have found an incompatible macro I have created the upgrade path so if you can post the offending one here I can see what I can do
one of the things I've wanted to do in mid-term feature planning is introduce the concept of local-space maps and bitmaps that are detached from the world represented in WM. You could then, for example, splat height features around your world according to a distribution map, or do the same for texure features.
Hey guys, I figured posting here would get more views.
I've generated a series of colormaps and heightmaps for a bunch of objects I wanted to place on terrains, but I wanted their placement to convey a natural appearance and having them all facing the same direction was hindering me. I found Rhalph's clever rotation macro that helped some, but it could only rotate in 90° increments. So I expounded on Rhalph's idea with this link to create a plugin that can rotate in arbitrary degrees between 0 and 45 (other angles are achievable in combination with Rhalph's macro).
There's a catch, though. Without trigonometric devices I'm losing edge information (see details here). I think it's currently good enough for my application (and possibly yours), but if someone could provide a basic trigonometric device or help me with my environment, it could be better.