the idea was to quickly find light emitting materials in a scene without the need to give them a particular names, to speed up tuning the scene lighting. i think this is the case, but the colors, well; i may skip the additional "active" inking if the colors are identical...vortex3d wrote:I thought the Emitters were fine in the "Used" group with the rest of the mats.
OcDS 1.2.120.34xx - BUG REPORTS
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.
„The obvious is that which is never seen until someone expresses it simply ‟
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
ok; looks like a map was not correctly unregistered when it got deleted (or its usage was decreased) by the mat deletion, so the textures list did try to access an non-existing object at some place...vortex3d wrote:I had just deleted a material from the "Unused" group.
„The obvious is that which is never seen until someone expresses it simply ‟
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
Absolutely. I just hope it stays consistent with the rest of the mats.t_3 wrote:the idea was to quickly find light emitting materials in a scene without the need to give them a particular names, to speed up tuning the scene lighting. i think this is the case, but the colors, well; i may skip the additional "active" inking if the colors are identical...vortex3d wrote:I thought the Emitters were fine in the "Used" group with the rest of the mats.
Win 8.1 Pro 64bit | GTX 660Ti, GTX TITAN, 6GB GDDR5 | Intel Core i7 3970x, 3.5 GHz | ASUS P9X79WS | 64GB RAM
any installer/updater will just replace any current by the version it contains. what are you facing?DrHemulen wrote:What's the easiest way to downgrade to an earlier version to check if an error is new?
*Edit* You just install the relevant update on top of your current install.
„The obvious is that which is never seen until someone expresses it simply ‟
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
The "Automatic material updates after content loads" option is adding negative numbers next to the each related material with every change.
So far this feature strips Octane materials upon related surface changes in DS.
So far this feature strips Octane materials upon related surface changes in DS.

Win 8.1 Pro 64bit | GTX 660Ti, GTX TITAN, 6GB GDDR5 | Intel Core i7 3970x, 3.5 GHz | ASUS P9X79WS | 64GB RAM
should be both fixed now (the latter was somehow connected with the multiplying mat issue).vortex3d wrote:The "Automatic material updates after content loads" option is adding negative numbers next to the each related material with every change.
So far this feature strips Octane materials upon related surface changes in DS.![]()
btw, thanks for the constant issue updates

„The obvious is that which is never seen until someone expresses it simply ‟
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
Is drag/drop of materials on figures with geografting supposed to work now? I'm getting some funky results with the material groups being changed (the surfaces linked to the OCD material are scrambled) when I drop materials on them. What's worse is that I can't seem to manually group them correctly afterwards, either they just shuffle around again, or nothing happens if I unlink the surfaces and try to assign the correct OCD materials to them :-/
The other stuff was some hotpixels, was not related to the update.
The other stuff was some hotpixels, was not related to the update.
GTX 780, 6 gigs of VRAM - Win 7 Home Premium 64 bits
there was no change to this.DrHemulen wrote:Is drag/drop of materials on figures with geografting supposed to work now? I'm getting some funky results with the material groups being changed (the surfaces linked to the OCD material are scrambled) when I drop materials on them. What's worse is that I can't seem to manually group them correctly afterwards, either they just shuffle around again, or nothing happens if I unlink the surfaces and try to assign the correct OCD materials to them :-/
The other stuff was some hotpixels, was not related to the update.
in general there seems to be no ultimate rule how grafts and daz mats are bound together or affected by each other. at least i haven't found one yet... at least in a way it would fit octane. this means to not have duplicate geometries in the rendering, just hidden by zero opacity mats.
currently the probably best way is to have 1:1 material links between daz surfaces and octane mats. and it needs to be clear that not all of them will be reflected in the rendered geometry. the daz tree now just shows any of the surfaces that grafts and base nodes presents. the geometry on the other hand only contains the final set of vertices, which apparently don't map 1:1 to theses surfaces.
i'd need one or two weeks alone to try different stuff, to maybe find out what depends on what else, and how to resolve it into a single static link for octane. i'm unfortunately dealing with an undocumented black box here, but i'm of course going to do this sooner or later. i have once tried to rebuild a bot genesis in the standalone, but have given up on it after 10 mins of connecting pins to test mats and still not having completed a third of all the pins...
„The obvious is that which is never seen until someone expresses it simply ‟
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
It's weird, because it actually works well with the autogenerated materials. It's only when I try to drop my own materials on the autogenerated ones things go wrong. Also I can't map a single OCD material to a DAZ surface sometimes. This is just ignored.
GTX 780, 6 gigs of VRAM - Win 7 Home Premium 64 bits