Moderator: face_off
Thanks Paul.face_off wrote:I have refreshed the installers at the top of this thread with:
2.16.0.25
- Default materials are now saved in OCS format rather than ORBX format (for reasons excluded in the plug TEST thread)
- Any embedded texturemap files found when importing an ORBX will now be extracted into the LiveDb texturemap folder
Paul
Hi Seeker....not sure what you mean here. There is no OCS proxy import, but ORBX proxy importing is supported, and these proxies have already been textured in Octane Standalone, so bypass any plugin material defaults.This change is not going to make OCS proxy import any easier, is it? Just shooting from the hip here...
I should have phrased that better I guess. Will it make the prospect of getting OCS proxy import any better now that OCS is the native material format.face_off wrote:Hi Seeker....not sure what you mean here. There is no OCS proxy import, but ORBX proxy importing is supported, and these proxies have already been textured in Octane Standalone, so bypass any plugin material defaults.This change is not going to make OCS proxy import any easier, is it? Just shooting from the hip here...
Paul
Ok, let me try again. Here (http://render.otoy.com/forum/viewtopic. ... at#p197827) you said:face_off wrote:Hi Seeker. The ability to import ORBX proxies as added in 2.12.1.15.
Paul
This was only 5 months ago. Yet, today we have ORBX proxies in addition to OBJ format - which is brilliant of course. The point is that things move quickly around here so I was wondering if the fact that you changed the standard material format to OCS has any influence on giving us ability to use OCS file as proxies (as we do in SketchUp). Obviously ORBX files have made this much easier and allows us to texture in Octane standalone before importing into Revit (the core reason for the request) but there are limits to editing ORBX file textures once imported into Revit. More options gives us more flexibility. It's just a question...face_off wrote:There is too much that can go wrong loading an OCS/ORBX as a proxy.
OK - got you now! I can add the ability to load OCS in addition to the current ORBX format in the next release.This was only 5 months ago. Yet, today we have ORBX proxies in addition to OBJ format - which is brilliant of course. The point is that things move quickly around here so I was wondering if the fact that you changed the standard material format to OCS has any influence on giving us ability to use OCS file as proxies (as we do in SketchUp). Obviously ORBX files have made this much easier and allows us to texture in Octane standalone before importing into Revit (the core reason for the request) but there are limits to editing ORBX file textures once imported into Revit. More options gives us more flexibility. It's just a question...
OCS proxies? Wow. Great! Thanks Paul.face_off wrote:OK - got you now! I can add the ability to load OCS in addition to the current ORBX format in the next release.This was only 5 months ago. Yet, today we have ORBX proxies in addition to OBJ format - which is brilliant of course. The point is that things move quickly around here so I was wondering if the fact that you changed the standard material format to OCS has any influence on giving us ability to use OCS file as proxies (as we do in SketchUp). Obviously ORBX files have made this much easier and allows us to texture in Octane standalone before importing into Revit (the core reason for the request) but there are limits to editing ORBX file textures once imported into Revit. More options gives us more flexibility. It's just a question...
Paul
Thanks Paul, I'll install the latest release and get back to you. I'm also updating my nvidia drivers.face_off wrote:Which version of the slave and which version of the plugin are you running pls? They need to be the same (ie. 2.16).Hi again Paul,
There is also another issue that is recurring and really slowing our work down - the slave keeps on disconnecting when networking. A message comes up in the console saying that it can no longer detect the slave heartbeat. This happens randomly. I have to close octane, revit and the slave daemon on the slave computer and re-launch everything. Generally it starts happening after one or 2 renders... This was not an issue previously and only seems to have come up with the 2.16 release
Thanks
Paul
Hi Paul, I've updated the plugins to the latest release - 2.16.25 - on the two computers I'm using at the moment (one slave, one master); I've also updated the graphic drivers on both - to the latest Nvidia release, but unfortunately I'm still encountering the issues - ie Octane not loading default materials at start up (having to load them individually and manually); Slave crashing at pretty much every render when networking.face_off wrote:I have had no other reports of these issues - so I wonder if there is an installation issue. Can you pls reboot and reinstall the latest 2.16 version of the plugin.I've encountered another issue with the revit plugin
Every time i close Octane and then re-open it 2 things happen:
- Some of my materials revert to an earlier default. These are different types of materials (some diffuse, some Glossy, mix etc). I have to reimport the materials each time.
- For some reason it also selects the navigate button (little camera icon at the top of the render window) so always loads a previous render first.
Thanks
Hi again Paul,
There is also another issue that is recurring and really slowing our work down - the slave keeps on disconnecting when networking. A message comes up in the console saying that it can no longer detect the slave heartbeat. This happens randomly. I have to close octane, revit and the slave daemon on the slave computer and re-launch everything. Generally it starts happening after one or 2 renders... This was not an issue previously and only seems to have come up with the 2.16 release
Thanks
It's actually happening every time now
Also, which exact version number of the plugin is giving you the above problem? And which version of Revit are you on?
Thanks
Paul
I am not quite sure what you mean by this. Can you explain more pls? The "default" material is only used the first time a Revit material is converted to an Octane material in a given scene. So if you load a .rvt file, it will load the Octane materials that were previously saved in that .rvt, not the defaults. You can see all the materials which have defaults in your C:\Users\[username]\AppData\Local\OctaneRender for Revit\Defaults folder. The latest release will save defaults in OCS format, and if there is a default for a material in both OCS and XML format, it will load the OCS file (if there is no OCS, it will load the XML file).Octane not loading default materials at start up
How are you doing this pls? What plugin menu items are you using to load them?(having to load them individually and manually)
