Another thought of the texturemap usage issue - try a complete uninstall of the plugin (via the Control Panel), and then reinstall.
Paul
Moderator: face_off
face_off wrote:Another thought of the texturemap usage issue - try a complete uninstall of the plugin (via the Control Panel), and then reinstall.
Paul
I have just uploaded a new build - can you tell me if that version still has the issue pls?Uninstall and reinstall do not solve this. Other issues:
The current proxy system was intended to have different proxy OBJ file for each instance, so you are right, it doesn't cater for the above situations. From memory, you can copy and paste an instance and the proxy fields carry over to the copy, but there is current no way to copy proxy into to already placed instances. Whilst functions could be added to the plugin to do this, there is a separate addin in development which will most likely address your requirements.> there's no way to convert all instances of an object into a specified proxy;
> cannot convert all selected instances of same object into a specified proxy;
Can you provide more information on this this?> the proxy obj units are not scaled as specified on proxy details;
face_off wrote:I have just uploaded a new build - can you tell me if that version still has the issue pls?Uninstall and reinstall do not solve this. Other issues:The current proxy system was intended to have different proxy OBJ file for each instance, so you are right, it doesn't cater for the above situations. From memory, you can copy and paste an instance and the proxy fields carry over to the copy, but there is current no way to copy proxy into to already placed instances. Whilst functions could be added to the plugin to do this, there is a separate addin in development which will most likely address your requirements.> there's no way to convert all instances of an object into a specified proxy;
> cannot convert all selected instances of same object into a specified proxy;Can you provide more information on this this?> the proxy obj units are not scaled as specified on proxy details;
Paul
Yes, pls use the same version.Can I use the same file of the first plugin version?
face_off wrote:I have just uploaded a new build - can you tell me if that version still has the issue pls?
The current proxy system was intended to have different proxy OBJ file for each instance, so you are right, it doesn't cater for the above situations. From memory, you can copy and paste an instance and the proxy fields carry over to the copy, but there is current no way to copy proxy into to already placed instances. Whilst functions could be added to the plugin to do this, there is a separate addin in development which will most likely address your requirements.
Can you provide more information on this this?
andredms wrote:This is an absolute must have feature - since we can put the information (name,specs) of the proxy directly into the rfa (or rpc) object name or description, do not have this capability severely disrupts any bim work. Do not have this feature inside the plugin is a big problem.
There are no texturemap limits in Octane 2.01, so no need to display them.The 2.1.0.5 shows correct texture usage and other info, but do not show the inherent limits (cuda cap. vers.).
This is the first time this feature has been requested. At the moment you can copy and paste proxy info via the 'C' and 'P' buttons on the Material tab (if the selection is a copy). If you want this functionality expanded, pls provide a very clear and detailed description of what you want and I can look at how it can be implemented.This is an absolute must have feature - since we can put the information (name,specs) of the proxy directly into the rfa (or rpc) object name or description, do not have this capability severely disrupts any bim work. Do not have this feature inside the plugin is a big problem.
Users browsing this forum: No registered users and 11 guests