I have to turn up my HDRI environment way up higher than before. An HDRI that used to work with a setting of 1 now needs 200+ to make the HDRI visible in the background and then the character is blow out. Am I using it wrong now?
Edit: I've attached the HDR.
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.
- Attachments
-
- gardasee_low.rar
- HDR
- (4.43 MiB) Downloaded 215 times
Last edited by slash on Fri Feb 14, 2014 11:22 pm, edited 2 times in total.
Windows 7 x64 | GTX670 | i5 2500k | 16GB
Cinema 4D
Daz3D Studio 4.6
Cinema 4D
Daz3D Studio 4.6
200 is really extreme; with the usual hdri's i never needed more than 2 @max (of course hard to compare without knowing the particular map); have you checked the gamma setting? does the importance sampling option make a difference? there are of course differences between octane 1.13 (old version) and 1.20, but not that big...slash wrote:I have to turn up my HDRI environment way up higher than before. An HDRI that used to work with a setting of 1 now needs 200+ to make the HDRI visible in the background and then the character is blow out. Am I using it wrong now?
„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
In some complex materials, when I change a certain map in one node (diffuse, bump etc.) it automatically changes in all nodes. I'm yet to determine what it's down to (it always happens with 3dmania's kindly shared SSS skin preset from another thread http://render.otoy.com/forum/viewtopic. ... 3&start=10). Breaking down the material in NGE doesn't seem to affect this issue.
2x RTX 2080ti, AMD Ryzen Threadripper 1920X, 128GB RAM, Win10 Pro 64, Dual Monitor Setup
mh, i expect it depends on where you select the map from; i.e. recently loaded, sorted by name, object menu (which currently contains way too much entries btw) - since it is a rather expensive operation to build specific parts of the menu, they are shared between all image nodes - and this might lead to mismatched updates to all other images of the same name; thought to have found a solution already, but apparently not for any possible selection. unfortunately it's not as easy as it sounds to trace back the origin, once the menu is shown...Jazbee wrote:In some complex materials, when I change a certain map in one node (diffuse, bump etc.) it automatically changes in all nodes. I'm yet to determine what it's down to (it always happens with 3dmania's kindly shared SSS skin preset from another thread http://render.otoy.com/forum/viewtopic. ... 3&start=10). Breaking down the material in NGE doesn't seem to affect this issue.
„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
I checked and it doesn't matter what menu you choose the map from, be it "recent", "by object", "browse disk"... it always behaves the same way. I'll try to find another material that does that as well. BTW. it would actually be a nice feature (automatically replace all maps of certain type within a material), as long as it has an on/off switcht_3 wrote: mh, i expect it depends on where you select the map from; i.e. recently loaded, sorted by name, object menu (which currently contains way too much entries btw) - since it is a rather expensive operation to build specific parts of the menu, they are shared between all image nodes - and this might lead to mismatched updates to all other images of the same name; thought to have found a solution already, but apparently not for any possible selection. unfortunately it's not as easy as it sounds to trace back the origin, once the menu is shown...
2x RTX 2080ti, AMD Ryzen Threadripper 1920X, 128GB RAM, Win10 Pro 64, Dual Monitor Setup
Probably it's the same problem I already reported, but nothing is shown where the name of the image should be.
Here a screenshot
The textures are loaded anyway.
Note : I applied a material from the DS library ... Also I get a lot of crashes and probably because this.
Note 2 : No textures shown when I open a scene file.
Note 3 : after some testing I think the problem is related to the other one I reported previously.
Here a screenshot
The textures are loaded anyway.
Note : I applied a material from the DS library ... Also I get a lot of crashes and probably because this.
Note 2 : No textures shown when I open a scene file.
Note 3 : after some testing I think the problem is related to the other one I reported previously.
- Attachments
-
Yes thats the one im getting, happens to me after I save a .DUF then later re-load it.AlfaseeD wrote:Probably it's the same problem I already reported, but nothing is shown where the name of the image should be.
Here a screenshot
The textures are loaded anyway.
Note : I applied a material from the DS library ... Also I get a lot of crashes and probably because this.
Note 2 : No textures shown when I open a scene file.
Note 3 : after some testing I think the problem is related to the other one I reported previously.