Removing sky texture

[Seekerfinder]

Hi again Paul,
I have (accidentally) set my default Render Target to include an image map under the Daylight environment settings. Now I can find no way to remove it which is needed for some views.

The Sketchup plugin has a 'remove node' type function. How do we do it here?

I have been wondering about this for some material settings as well. Would it be a good idea to perhaps add a 'no node' function to all nodes like Octane standalone?

Thanks,
Seeker

[Seekerfinder]

IGNORE...
Just found the Disconnect

I think I'm a bit rusty...

Seeker

[Seekerfinder]

A related issue... Once I removed the texture file from one view, I got the error below. Thankfully no crash, just the error.

Also, do I understand correctly that all Revit views share the default render target setting (including the texture) unless a view has been saved to a render target?

Thanks,
Seeker

[face_off]

Hi Seeker - is that error reproduced if you restart Revit and render that view again? If so, can you pls send me the file.

Also, do I understand correctly that all Revit views share the default render target setting (including the texture) unless a view has been saved to a render target?

Correct.

Paul

[Seekerfinder]

Hi Seeker - is that error reproduced if you restart Revit and render that view again? If so, can you pls send me the file.

Just completed a deadline. I restarted Revit a number of times as a matter course since I got that issue. I had a clean run until this morning when all of a sudden I got a plethora errors in short succession, apparently related to either material picking (in the plugin vp) or refreshing the render (among other things telling me that the render window can only refresh from a Revit perspective view, while I was in one). I don't think I've ever had so many warnings but the interesting thing is that not the plugin, nor Revit crashed and (right after I peed in my pants) I continued with the same file and completed the deadline. It turned out to be a scare more than anything else but I want to make sure the file does not become corrupt or anything. So, I captured most of those notices and will post them in the next few days to hopefully establish what all the fuss was about. Unfortunately, I was not using your very latest 'debug' version (just did not have time) but rather the second one you had posted.

I am slowly developing a more efficient workflow and the plugin was key to completing a fast track concept design presentation with a colleague in the last week. Displacement grass is passable for probably 70% of my projects. Lighting is the current learning curve. So despite the kind of teething issues mentioned above, with a bit of persistence, the plugin has proven to be an extremely usefull design tool. I am still going to be holding out for a solution to import (my textured) OCS proxies but perhaps there's another solution coming via ORBX soon (?).

Also, do I understand correctly that all Revit views share the default render target setting (including the texture) unless a view has been saved to a render target?

Correct.

Paul

Cheers Paul.

Best,
Seeker

[face_off]

I am still going to be holding out for a solution to import (my textured) OCS proxies but perhaps there's another solution coming via ORBX soon (?).

Seeker - the next version of the Revit plugin will allow you to import materials from an ORBX file - so that's a (small) step closer...

Paul

[Seekerfinder]

That would certainly help! Thanks Paul.

[Seekerfinder]

Hi Seeker - is that error reproduced if you restart Revit and render that view again? If so, can you pls send me the file.

Just completed a deadline. I restarted Revit a number of times as a matter course since I got that issue. I had a clean run until this morning when all of a sudden I got a plethora errors in short succession, apparently related to either material picking (in the plugin vp) or refreshing the render (among other things telling me that the render window can only refresh from a Revit perspective view, while I was in one). I don't think I've ever had so many warnings but the interesting thing is that not the plugin, nor Revit crashed and (right after I peed in my pants) I continued with the same file and completed the deadline. It turned out to be a scare more than anything else but I want to make sure the file does not become corrupt or anything. So, I captured most of those notices and will post them in the next few days to hopefully establish what all the fuss was about. Unfortunately, I was not using your very latest 'debug' version (just did not have time) but rather the second one you had posted.

I am slowly developing a more efficient workflow and the plugin was key to completing a fast track concept design presentation with a colleague in the last week. Displacement grass is passable for probably 70% of my projects. Lighting is the current learning curve. So despite the kind of teething issues mentioned above, with a bit of persistence, the plugin has proven to be an extremely usefull design tool. I am still going to be holding out for a solution to import (my textured) OCS proxies but perhaps there's another solution coming via ORBX soon (?).

Also, do I understand correctly that all Revit views share the default render target setting (including the texture) unless a view has been saved to a render target?

Correct.

Paul

Cheers Paul.

Best,
Seeker

Hi Paul,
Below are those screenshots I was referring to. It's like they came all of a sudden without me particularly dong anything out of the ordinary.

Best,
Seeker

Error 1

Error 2

Error 3

ERROR_3.jpg (12.01 KiB) Viewed 6781 times

Error 4

Error 5

[Seekerfinder]

On the same model, I just got 2 'Nvidia driver has stopped working and has recovered' Windows notices and then the plugin error shown below. The renderer pauses but resumes upon acknowledging the error. It happened when switching to path tracing kernel. Using the latest Nvidia driver.

Best,
Seeker

[face_off]

Seeker - all the issues you posted above look like a problem where the installer has been able to update the plugin, but could not update the Octane API DLL (potentially Revit is still running, or still in memory). I suggest rebooting, then uninstalling the plugin via the Control Panel, then re-installing the latest version.

Paul