OcDS 2.1 PRE RELEASE 5th
Moderator: BK
Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
how can we zoom in and out in the node graph editor now? The mouse wheel doesn't work anymore
DAZ Store: http://www.daz3d.com/elele
Renderosity Store: https://www.renderosity.com/mod/bcs/vendor/elele
Deviant Art Page: http://eleleoke.deviantart.com
Renderosity Store: https://www.renderosity.com/mod/bcs/vendor/elele
Deviant Art Page: http://eleleoke.deviantart.com
- linvanchene
- Posts: 783
- Joined: Mon Mar 25, 2013 10:58 pm
- Location: Switzerland
As far as I know this bug was reported by a user allready and t_3 is aware of it.Elele wrote:how can we zoom in and out in the node graph editor now? The mouse wheel doesn't work anymore
I have not yet figured out another way to zoom in and out in the NGE.
Win 10 Pro 64bit | Rendering: 2 x ASUS GeForce RTX 2080 Ti TURBO | Asus RTX NVLink Bridge 4-Slot | Intel Core i7 5820K | ASUS X99-E WS| 64 GB RAM
FAQ: OctaneRender for DAZ Studio - FAQ link collection
FAQ: OctaneRender for DAZ Studio - FAQ link collection
Ok thanks. I can double click which zooms in once, but it is usually too big and there is no way to unzoom (reselecting the material resets the original zoom)
hmmpff, there are a lot of these small bugs in this version (its the first i tried since 1.1) that really boil my blood, like:
-when selecting a new node in the menu, you have to keep on it all the way when dragging it in the NGE otherwise it will select the last one you were on when going out of the menu.
-if you want to drag an existing material onto another material zone, you have to make sure not to acidentally go over another object or it will apply the material to that object
-the render window that randomly pops to the forefront if it isn't dragged off screen or minimized, blocking whatever you were doing
...
All just stupid stuff but it happens constantly and can really drive me nuts.
hmmpff, there are a lot of these small bugs in this version (its the first i tried since 1.1) that really boil my blood, like:
-when selecting a new node in the menu, you have to keep on it all the way when dragging it in the NGE otherwise it will select the last one you were on when going out of the menu.
-if you want to drag an existing material onto another material zone, you have to make sure not to acidentally go over another object or it will apply the material to that object
-the render window that randomly pops to the forefront if it isn't dragged off screen or minimized, blocking whatever you were doing
...
All just stupid stuff but it happens constantly and can really drive me nuts.
DAZ Store: http://www.daz3d.com/elele
Renderosity Store: https://www.renderosity.com/mod/bcs/vendor/elele
Deviant Art Page: http://eleleoke.deviantart.com
Renderosity Store: https://www.renderosity.com/mod/bcs/vendor/elele
Deviant Art Page: http://eleleoke.deviantart.com
- larsmidnatt
- Posts: 499
- Joined: Tue Sep 25, 2012 12:28 pm
OK I finally tested rendering a scene in the plugin vs the standalone and rendering performance is exactly the same for me. Which is good 

Win10 x64
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
I also don't seem to be able to save materials in my presets anymore?
Whenever I reopen Studio, the saved presets are gone.
Whenever I reopen Studio, the saved presets are gone.
DAZ Store: http://www.daz3d.com/elele
Renderosity Store: https://www.renderosity.com/mod/bcs/vendor/elele
Deviant Art Page: http://eleleoke.deviantart.com
Renderosity Store: https://www.renderosity.com/mod/bcs/vendor/elele
Deviant Art Page: http://eleleoke.deviantart.com
- larsmidnatt
- Posts: 499
- Joined: Tue Sep 25, 2012 12:28 pm
Yeah thats a known bug for all of us sadlyElele wrote:I also don't seem to be able to save materials in my presets anymore?
Whenever I reopen Studio, the saved presets are gone.

Win10 x64
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
Is anyone else getting "duplicate formulas found in file" when loading a file with octane data?? It seems to happen when I've saved a couple of times, both scene and scene subsets. Afterwards it feels like stuff is more unstable and crashes are more frequent.
Log file has a couple of pages of this:
WARNING: fileinput\dzassetdaz.cpp(5450): Duplicate formula found linking OctaneRender_generalVisibility & OctaneRender_generalVisibilityERC in /Octane%20Shaders/TS2_testting.duf.
Log file has a couple of pages of this:
WARNING: fileinput\dzassetdaz.cpp(5450): Duplicate formula found linking OctaneRender_generalVisibility & OctaneRender_generalVisibilityERC in /Octane%20Shaders/TS2_testting.duf.
GTX 780, 6 gigs of VRAM - Win 7 Home Premium 64 bits
I've found that pretty much anything I save lately suddenly gets this message, even architectural stuff that shouldn't have any crazy, complex shaders applied. I've just kinda accepted it for now and moved on.
t_3 seemed pretty confident it is a Daz Studio thing, I'm nearly positive it's something in how the materials are getting saved to the .duf files, since the error almost never occurs if if I turn off auto or .duf mat loading. Given that I am also frequently finding random hidden nodes in the NGE that may or may not actually be linked to anything, I'm assuming it's probably something to do with these. (These nodes are usually what make people think their mats have been messed up, since they occasionally have nothing input, and usually output a solid color, which made people think their mats were missing diffuse images). I frequently find from 2 in simple to 7 in overly complex materials, usually out to the left, usually RGB, or greyscale, and almost never linked to anything at all. Given that the log file usually has a bunch of stuff about not being able to link nodes or duplicate links, my thought would be that it probably sees these nodes not linked or that they are attempting to link to identical inputs, and is letting you know they are not linked, since they can't do that. I unfortunately have no idea what I did to start this trend, but it's in pretty much every save I have made since the first 2.x prerelease, and the same error rarely pops up on those same files if I open them in 1.2.
On the flip side, I've never had a noticeable reduction in stability from this error itself, it just tends to extend the time required to fix things in NGE, and perhaps requires me to pay more attention to click "okay" when loading a file. I also tend to restart Daz Studio pretty frequently though, as it occasionally still has issues with memory leaking, though it's much improved in 4.7.
t_3 seemed pretty confident it is a Daz Studio thing, I'm nearly positive it's something in how the materials are getting saved to the .duf files, since the error almost never occurs if if I turn off auto or .duf mat loading. Given that I am also frequently finding random hidden nodes in the NGE that may or may not actually be linked to anything, I'm assuming it's probably something to do with these. (These nodes are usually what make people think their mats have been messed up, since they occasionally have nothing input, and usually output a solid color, which made people think their mats were missing diffuse images). I frequently find from 2 in simple to 7 in overly complex materials, usually out to the left, usually RGB, or greyscale, and almost never linked to anything at all. Given that the log file usually has a bunch of stuff about not being able to link nodes or duplicate links, my thought would be that it probably sees these nodes not linked or that they are attempting to link to identical inputs, and is letting you know they are not linked, since they can't do that. I unfortunately have no idea what I did to start this trend, but it's in pretty much every save I have made since the first 2.x prerelease, and the same error rarely pops up on those same files if I open them in 1.2.
On the flip side, I've never had a noticeable reduction in stability from this error itself, it just tends to extend the time required to fix things in NGE, and perhaps requires me to pay more attention to click "okay" when loading a file. I also tend to restart Daz Studio pretty frequently though, as it occasionally still has issues with memory leaking, though it's much improved in 4.7.
| Intel i7-5960x @ 3.8 GHz| ASUS X99-E WS | 64 GB G.Skill DDR4 2400 Ram | 4x EVGA GTX 980 Ti | Win10 Professional x64 | Watercooled