Itoo Software Forum

Author Topic: Disable instance engine for specific item in library  (Read 373 times)

3dcrgr

  • Full Member
  • ***
  • Posts: 128
    • cgarchitect profile
Disable instance engine for specific item in library
« on: May 24, 2017, 03:04:26 PM »
I made this style and added it to my user library in RC.
Anyway this style only works correctly when the  instance engine is off.

So is there some way that instance engine will automatically turn off when I load this specific style only?
I always forget to turn it off, and since it looks fine in the viewport I just waste render time.

Paul Roberts

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1517
Re: Disable instance engine for specific item in library
« Reply #1 on: May 24, 2017, 03:23:37 PM »
Hi,

Thanks for the question. We've been having the same conversation here lately where libraries only work correctly if instancing is turned off for particular renderers. As a result, future versions of RailClone will include a functions that can be called to disable instancing if the current renderer doesn't support a feature. It will use the following syntax that should be added to the library's index.xml.

<maxscript script='@RC_disableInstancing "$(RENDERER)" "corona";' execute_on="item_select"/>

Where corona is the renderer for which you would like instancing disabled. Other options include mentalray, and vray.

If you would like to disable instancing for multiple renderers, just add them separated by a space, e.g.

<maxscript script='@RC_disableInstancing "$(RENDERER)" "corona mentalray";' execute_on="item_select"/>


I'm afraid this won't work quite yet, but the next builds of RailClone 3 will include the function to which this line refers, so you can start using it then.

I hope that helps, please let me know if you have any further questions.

Many Thanks,

Paul
Paul Roberts
iToo Software

3dcrgr

  • Full Member
  • ***
  • Posts: 128
    • cgarchitect profile
Re: Disable instance engine for specific item in library
« Reply #2 on: May 25, 2017, 10:15:41 AM »
Hi Paul,

Thanks for your answer.
Will be waiting for RC3 :)