Help - Cycles settings

[nathanletwory (Nathan 'jesterKing' Letwory)]

@Jarek

It just makes is less discoverable since intuitively making changes there seems to have no effect, unless the user knows to switch back-and-forth.Maybe there could be a popup if any of the Cycles adv. settings were changed that they will take no effect until the mode is restarted…I don’t know, doesn’t seem very elegant either. I don’t have a good solution other than writing this somewhere in a help file

I do agree the current state isn’t the easiest to grasp. I don’t find it ideal myself, either. It certainly must be improved upon, but I think that this might go into v7.

The help-file is indeed the best place currently - that reminds me I still have to write documentation for all the commands RhinoCycles provides

@Jarek

Simplest solution could be to defaulting the ShadowMap quality to 512 or 1024 max

It is indeed likely we will just hard-code this to some low, but acceptable setting. I’m not knowledgable enough currently about how I could get any UI fiddling opportunities for the user done, but I’ll learn about it soon enough without doubt.

@Jarek

Having a defined delay to kick-in the raytracing would allow to play with the camera adjustments, which often consist of a series of micro-movements, until the view is set and one just waits to see it raytraced. Currently with no delay there is a micro-hang between the micro-movements. I feel like having this at 300-500ms by default could help for FastDraw mode, if this is achievable as an additional setting.

Very nice idea, but will have to go to v7. If I get my other stuff cleaned up in a timely manner I might push it to some 6 SR, but we won’t be doing those forever either (i.o.w. time is running out). Anyway: RH-49724

@Jarek

Let me know if you think it is available - I am tryin to control this programmatically in case user does not have it enabled but can’t tell as of right now. Would it be this one?
https://developer.rhino3d.com/api/RhinoCommon/html/M_Rhino_Render_RealtimeDisplayMode_UseFastDraw.htm

No, that is a function an engine has to implement if it wants to signal the usage of fast draw to the pipeline. What you need is the plug-in setting for RhinoCycles for this. Ignore anything that says virtual in the function or property signatures.

I was actually referring to the method that stevebaer showed you for controlling UseTessellationShaders in this thread. To get it to work with Raytraced you need the plug-in ID. Here a snippet:

import Rhino as rh
import System

settings = rh.PlugIns.PlugIn.GetPluginSettings(System.Guid("9bc28e9e-7a6c-4b8f-a0c6-3d05e02d1b97"), True)

cursetting = settings.GetBool("UseFastDraw")
print("Old setting", cursetting)

settings.SetBool("UseFastDraw", not cursetting)
print("New setting", settings.GetBool("UseFastDraw"))

You could make it so that you have a button that runs this, then after toggling you toggle with a macro the viewport mode to say Wireframe and back to Raytraced.

@Jarek

RealtimeDisplayId=69e0c7a5-1c6a-46c8-b98b-8779686cd181

This is indeed the RDID for Raytraced:

mcneel/RhinoCycles/blob/rhino-6.x/Viewport/RenderedViewport.cs#L43

@Jarek

For all other non-Cycles mode, the ID=00000000-0000-0000-0000-000000000000

It is Guid.Empty for all non-realtime display modes. For instance you’d get an ID other than Guid.Empty for ProRender display mode, and so on for each engine that opts to provide an integrated display mode.