- If you have a null figure with attached props and figures, the texture counter script failes with
I will fix.
- another window scaling bug: The memory usage box you added in the last few builds also cuts off numbers. This is with DPI at 125%
I'll add a few more pixels to the window size.
Another nice feature would be that a duplicated prop or figure would keep its octane materials. Now only the original materials are copied
Save the material back to the Poser Material, then duplicate the prop. Works a treat.
I was copy/pasting a lot nodes: Copy a node, right click, copy, move cursor to next node to change, select it, right click, paste. I had to do that about 200 times with 4 different type of nodes. I made about 10 mistakes (while watching it) because of the bug. Often you just move the mouse to quickly to where the paste menu item is going to be and it ends up being pasted on the node below. You only notice when you render that something is odd
I have a fix for this for you to try out.
Also, Are you running a separate graphics card for your display (or using a graphics card that is also rendering?). If not, then you sure! I just switch to using my onboard graphics for displaying the Windows GUI, and it is fantastic.
If you delete in Poser a figure with parented props or parented figures AND you have the plugin open (autorefresh off), the entire scene is newly refreshed for EACH deleted prop or figure. It the scene is large this can take very, very long
Apparently Poser send a notification that the scene has changed after each deleted object even when it is part of a larger delete, The plugin picks it up and refreshes the scene
It would be nice if something could be done about it, but I am not sure if you can.
Fixed in the next release.