I have refreshed the installers at the top of this thread with:
2.22.2.44
- Added Material node button "Scale Texturemaps", to scale all texturemaps and procedural textures for the given material simultaneously
Any chance of expanding the option to other fields, like setting all Specular or Roughness values at once? Would also appreciate an option to "preserve textures when multiplying", and "always multiply by RGB Color".
This is a much larger change, and IMO falls under the option to be able to select multiple materials/nodes and edit them simultaneously. It's something on the long-term list.
face_off wrote:This is a much larger change, and IMO falls under the option to be able to select multiple materials/nodes and edit them simultaneously. It's something on the long-term list.
Paul
Oh I see. I thought it could be simpler to change all values of the same kind (e.g., roughness value) instead of changing the value of manually selected fields. For example, there could be a combo box containing a list of the field types, and a value field to enter a fixed value to that the field values to.
An example of usage scenario would be when loading hair models with 10 different MAT zones, and we have to set all roughness values to a fixed value, and then repeat to set the specular values, 10 times each.
What about options for "keep textures when multiplying" (not loosing the texture when adding a multiply node), and "always multiply by RGB Color" (instead of number). Are those possible?
I thought it could be simpler to change all values of the same kind (e.g., roughness value) instead of changing the value of manually selected fields. For example, there could be a combo box containing a list of the field types, and a value field to enter a fixed value to that the field values to.
An example of usage scenario would be when loading hair models with 10 different MAT zones, and we have to set all roughness values to a fixed value, and then repeat to set the specular values, 10 times each.
I think changing a value field for all materials in a prop in practice would not work, because, specially with hair props, there will usually be a material you DON'T want to change the value for (the skullcap for example). IMO it would be better to allow you to select multiple materials, and then paste to those materials.
face_off wrote:I think changing a value field for all materials in a prop in practice would not work, because, specially with hair props, there will usually be a material you DON'T want to change the value for (the skullcap for example). IMO it would be better to allow you to select multiple materials, and then paste to those materials.
Paul
Scullcap uses a different texture, but takes the same roughness/specular values as the rest of the hair. And even if it didn't, it's still only one material to edit instead to 10.
I'm having a problem with the Plugin when out of core memory is used and it seems to be related to HDR Light Studio. (All my specs are in the signature). This explanation is going to be a little convoluted so please bear with me. Using version 2.2.22.42 everything worked fine, even when using quite a bit of out of core memory (1GB+). I have one scene that used 3GB+ and it worked fine.
The quick version
With scenes using out of core memory, moving a light within HDR Light Studio (or turning a light off/on) instantly causes CUDA 700 errors.
Long version
I didn't use large scenes with 2.2.22.43 so I have no experience with that version. When I updated to 2.2.22.44 I began to get CUDA 700 errors with large scenes that used out of core memory and HDR Light Studio. I've tested four different scenes and get the errors with each scene, each time. The errors themselves seem to be random; sometimes they're listed as memory related problems (unable to allocate memory, unable to deallocate memory, unable to access page locked memory, etc.), sometimes they are listed as "direct lighting failed", kernal problems, etc. About 60% of the time they cause Poser to crash.
All of these errors occur when using HDR Light Studio (HDRLS). So far in my limited testing (about 20 attempted renders spread among 4 different scenes averaging about 1GB of out of core memory) I haven't been getting CUDA errors when I'm not using HDRLS.
Symptoms
When rendering a large scene that requires out of core memory and HDR Light Studio, moving a light within HDRLS instantly causes a CUDA 700 error, or multiple errors (the errors themselves are not consistent).
When rendering a scene using HDRLS but without out of core memory usage, no CUDA errors have occured.
What I've tried
I verified that SLI was disabled.
I re-downloaded version 44 and reinstalled it on top of the existing Plugin. Errors persisted.
I uninstalled version 44 through the Control Panel, rebooted and reinstalled. Errors persisted.
I uninstalled version 44 through the Control Panel, rebooted and reinstalled 2.2.22.43. Errors persisted.
I uninstalled 2.2.22.43 and manually deleted all files in Poser 2014/Runtime/Python/OctaneRender for Poser and in AppsData/Roaming/OctaneRender (Except for "octane_render_v1_live_account.cfg"); then rebooted and reinstalled version 2.2.22.42 thinking that it would get me back to a version which worked. Errors persisted.
I deactivated first one video card, tested, and then the other card. Errors persisted.
I reset the Plugin to use 32GB of memory for out of core textures (system has 64GB), then 24GB
Thoughts
The errors now continue to occur even after reinstalling version 42, which previously was okay. I have considered that I might not have done a "clean enough" install, or that I messed something up with all the uninstalling and reinstalling, because uninstalling through the Control Panel leaves files and directories behind in the AppsData/Roaming section.
I've also considered that there might be a problem with one or both of my video cards, however, I haven't experienced any blue screens or memory errors, etc. I've experienced no obvious video card problems while gaming, and I've rendered video which uses CUDA etc. and everything works fine.
Sorry for the huge wall of text but I wanted to be as complete in my explanation as possible. I'm really puzzled by this and hoping for suggestions.
Windows 10 64bit | 2 x NVIDIA TITAN XP 12GB | Intel i7-6900K (8 core/16 thread) | 64Gb RAM | GeForce Driver 376.33 | PoserPro Game Dev 2014 SR4, 10.0.5.28925 | Poser Octane Plugin Version: 3.4.4.79 | HDR Light Studio 4.3.20131206.1249, Poser v1.0.3
With scenes using out of core memory, moving a light within HDR Light Studio (or turning a light off/on) instantly causes CUDA 700 errors.
Hi - this was reported a few days ago to Otoy, and they believe they have a solution which will be in the next release of Octane. So for the moment, turn OFF Out of Core if you are getting these errors, or try going back to 2.21.1.
I have refreshed the installers at the top of this thread with:
2.22.2.46
- Fixed a bug preventing the Material Id pass from rendering
- Fixed bug where render passes were not displaying when selected in the Viewport
when loading older files I usually get these errors
Traceback (most recent call last):
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\__init__.py", line 76, in Render
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 5175, in ShowSetupForm
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 184, in CreateNodesFromPoserScene
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\MaterialManager.py", line 214, in ConvertMaterial
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3549, in createNodeFromSavedTree
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3549, in createNodeFromSavedTree
File "C:\Program Files\Smith Micro\Poser Pro 2014\Runtime\Python\addons\OctaneRender for Poser\UiManager.py", line 3223, in createNodeFromSavedTree
File "D:\Programme\CGI\Poser\Poser Pro 2014\Runtime\Python\lib\encodings\utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xfc in position 10: invalid start byte
tried that with version 2.15, 2.16 and 2.22
they're usually gone when I close the plugin and open it again
oh, and another one:
when I exit Poser normally (File -> Exit) with this plugin (2.22.2.46) the Poser window closes and then Poser crashes. I'm on Poser Version 10.0.5.28925, if that matters.
It doesn't matter if I did open the Octane Plugin or viewer or not.
Uwe
