Please rollback the Displacement node back to old version

Forums: Please rollback the Displacement node back to old version
Sub forum for bug reports
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.


All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)

Re: Please rollback the Displacement node back to old version

Postby ChrisH » Thu Mar 28, 2019 7:17 pm

ChrisH Thu Mar 28, 2019 7:17 pm
grimm wrote:I just did a quick test with 16.3.3 and didn't have any issues. These are the steps I followed:

1 - created a plane
2 - went to top view (7)
3 - UV unwrapped with project from view
4 - Pack islands (to make sure that the UVs exactly match the image)
5 - Added an array modifier to test tiling
6 - Set up the nodes and rendered in the preview (I set the displacement texture size to 4096x4096)

I'm thinking that either your UVs are not exactly on the image borders or there are some artifacts in your displacement images?


So, I'm 99.9999% sure that the borders of the UV are right on the edge (Doing a simple UV unwrap of a single face plane will do that, as will Project from View (Bounds) do). I even tried UV unwrapping the way you described*, but with the same result.
I can also look at the edge of the plane with just the texture in the diffuse channel (no Displacement) and see that the texture fits perfectly (no weird lines etc).

What I think differs from our test (to yours) is that you used a tileable texture (right!?). Tileable textures is not a problem, since the repeated edge ([0,0] to [0,1]) matches perfectly to the "last edge" ([1,0] to [1,1]), and thus if it goes a pixel or so over, it makes no difference.
If the texture isn't tileable (like from the World map generator) the issues appears (since the edges doesn't match).

As seen in my screenshots, there's bleed over if there's no displacement (and UVs are right on the image edge [or 1px inset]). I used those colors (via a Gradient node, the OG texture is greyscale, loaded into a float image texture) to add some contrast (so we can see if there's some "bleed").
Octane_Displacement_7edt.png


(*Your approach actually made the UV edges like 1px inset from the actual image border)


(ETA: I've added my test .blend, plus a screenshot of the UV scaled slightly bigger than the image)
Attachments
Octane_DispTest.blend
(23.27 MiB) Downloaded 146 times
Windows 10 Pro - AMD Ryzen 7 2100X 8 core 3.70GHz - 32GB RAM - GeForce GTX 1080 8GB
Octane Prime - Blender Plugin user

Metal IOR values for Octane (with .blend library): https://chris.hindefjord.se/resources/rgb-ior-metals/
User avatar
ChrisH
Licensed Customer
Licensed Customer
 
Posts: 103
Joined: Sun Mar 06, 2011 12:13 am
Location: Lidköping, Sweden

Re: Please rollback the Displacement node back to old version

Postby grimm » Thu Mar 28, 2019 7:40 pm

grimm Thu Mar 28, 2019 7:40 pm
Do you have the blur filter turned on? I can see some of these artifacts when I turn it on, but looks good when turned off.
Linux Mint 20 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 460.56
User avatar
grimm
Licensed Customer
Licensed Customer
 
Posts: 1321
Joined: Wed Jan 27, 2010 8:11 pm
Location: Spokane, Washington, USA

Re: Please rollback the Displacement node back to old version

Postby ChrisH » Thu Mar 28, 2019 8:16 pm

ChrisH Thu Mar 28, 2019 8:16 pm
grimm wrote:Do you have the blur filter turned on? I can see some of these artifacts when I turn it on, but looks good when turned off.


The filter is set to None in the tests, but I tried it with the radius from 0 to 15 (and all the resolutions), and these "edge artifacts" are still there.
Windows 10 Pro - AMD Ryzen 7 2100X 8 core 3.70GHz - 32GB RAM - GeForce GTX 1080 8GB
Octane Prime - Blender Plugin user

Metal IOR values for Octane (with .blend library): https://chris.hindefjord.se/resources/rgb-ior-metals/
User avatar
ChrisH
Licensed Customer
Licensed Customer
 
Posts: 103
Joined: Sun Mar 06, 2011 12:13 am
Location: Lidköping, Sweden

Re: Please rollback the Displacement node back to old version

Postby grimm » Thu Mar 28, 2019 9:39 pm

grimm Thu Mar 28, 2019 9:39 pm
Hmm, not sure then what the issue is? I have tried both tiled and non-tiled displacement maps, 8-bit and 16-bit versions, simple and view projected UV unwrapping, and still do not have those artifacts. The only time I can see some problems is when I turn on the filter. Could it be an OS issue, I'm running Linux Mint 19?

Jason
Linux Mint 20 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 460.56
User avatar
grimm
Licensed Customer
Licensed Customer
 
Posts: 1321
Joined: Wed Jan 27, 2010 8:11 pm
Location: Spokane, Washington, USA

Re: Please rollback the Displacement node back to old version

Postby grimm » Thu Mar 28, 2019 9:56 pm

grimm Thu Mar 28, 2019 9:56 pm
Just wanted to add, if anyone has a displacement map they would like me to test, I wouldn't have any problems testing it.
Linux Mint 20 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 460.56
User avatar
grimm
Licensed Customer
Licensed Customer
 
Posts: 1321
Joined: Wed Jan 27, 2010 8:11 pm
Location: Spokane, Washington, USA

Re: Please rollback the Displacement node back to old version

Postby ChrisH » Fri Mar 29, 2019 2:48 pm

ChrisH Fri Mar 29, 2019 2:48 pm
grimm wrote:Just wanted to add, if anyone has a displacement map they would like me to test, I wouldn't have any problems testing it.


You're welcome to download my test scene (above), the texture is packed into the file. :)
Windows 10 Pro - AMD Ryzen 7 2100X 8 core 3.70GHz - 32GB RAM - GeForce GTX 1080 8GB
Octane Prime - Blender Plugin user

Metal IOR values for Octane (with .blend library): https://chris.hindefjord.se/resources/rgb-ior-metals/
User avatar
ChrisH
Licensed Customer
Licensed Customer
 
Posts: 103
Joined: Sun Mar 06, 2011 12:13 am
Location: Lidköping, Sweden

Re: Please rollback the Displacement node back to old version

Postby grimm » Fri Mar 29, 2019 5:56 pm

grimm Fri Mar 29, 2019 5:56 pm
ChrisH wrote:You're welcome to download my test scene (above), the texture is packed into the file. :)


Yarrg! I didn't even notice that, downloading it and checking it out. :D I definitely see the issue now, it looks like Octane is going past the edge or wrapping the edges around? I double checked my displacement tests and can see some of the same issues, they are just harder to see. I also brought your image into Krita and took a look at it. I didn't see anything wrong with it, although Krita did load it as a 8-bit image. I converted it to 16-bit, but it didn't make any difference. Looks like a bug to me.
Linux Mint 20 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 460.56
User avatar
grimm
Licensed Customer
Licensed Customer
 
Posts: 1321
Joined: Wed Jan 27, 2010 8:11 pm
Location: Spokane, Washington, USA

Re: Please rollback the Displacement node back to old version

Postby milanm » Fri Mar 29, 2019 7:07 pm

milanm Fri Mar 29, 2019 7:07 pm
There is one more filter.

The artifacts are caused by bilinear interpolation between pixels on the opposite edges of the texture because it's being tiled. And tiling can not be disabled (currently).

Notice the gray edges:

ImageImage
Here is the 5x5 pixel map.
5x5.zip
(1011 Bytes) Downloaded 147 times

There was a big discussion about this in the C4D forum too.

I hope this makes sense.

Regards
Milan
Colorist / VFX artist / Motion Designer
macOS - Windows 7 - Cinema 4D R19.068 - GTX1070TI - GTX780
milanm
Licensed Customer
Licensed Customer
 
Posts: 261
Joined: Tue Apr 30, 2013 7:23 pm
Previous

Return to Bug Reports


Who is online

Users browsing this forum: No registered users and 0 guests

Thu Mar 28, 2024 9:47 pm [ UTC ]
cron