Holes in normal map
Closed, ResolvedPublic

Description

System Information
Windows 10 Professional x64
Nvidia GeForce GTX 650 Ti Boost

Blender Version
Broken: 2.79b
Worked: n/a

Baking produces holes in the normal map.

  1. Open .blend file
  2. Bake at any ray distance
  3. Normal map has holes in it

.blend file: https://www.dropbox.com/s/dhoz618knqw0yp7/anvil.zip?dl=0

Details

Type
Bug
Philipp Oeser (lichtwerk) triaged this task as Incomplete priority.Mon, Jun 11, 1:18 PM

Cant confirm here, using a Ray Distance of e.g. 0.08 gives following result here

[also using a slightly fattened copy of the lowres as a cage also works fine here]

  • Could you confirm this is working for you, or
  • could you show us what the holes look like [when using Ray Distance of 0.08]?

Marking as incomplete for the time being...

Tyler (dizziless) added a comment.EditedMon, Jun 11, 2:34 PM

Here's what it looks like at 0.08.

Trying to use a cage gives me an error message: "Invalid cage mesh the cage mesh must have the same number of faces as the active object".

edit: Here's with cage selected and a distance of 0.08.

Philipp Oeser (lichtwerk) raised the priority of this task from Incomplete to Needs Triage.Mon, Jun 11, 4:02 PM

Hm, still cannot reproduce, maybe someone else can?

Is it possible the bake is not completing for some reason? I never see the status percentage go from 0 to 100. It usually stops at 1% - 7%, "completed", and then saves the normal map.

Philipp Oeser (lichtwerk) triaged this task as Incomplete priority.Tue, Jun 12, 12:46 PM

Not completing would make sense (output with holes expected then).

  • does this happen on both GPU and CPU?
  • could you launch blender from the commandline with --debug-cycles option and post the output as a .txt file here? [maybe there is something we can learn from that...]

Marking as incomplete again until we have an answer...

Tyler (dizziless) added a comment.EditedTue, Jun 12, 1:20 PM

CPU Compute

GPU Compute

could you launch blender from the commandline with --debug-cycles option and post the output as a .txt file here? [maybe there is something we can learn from that...]

Not sure how to do this, could you give me further instructions?

Seems like GPU only then.
Could it be that you are running out of GPU memory?
(if I look at my NVIDIA Server Settings I have it peaking at a little less than 2 GIGs -- which might be a little too much for the GTX 650 Ti...)

reg. the --debug-cycles option: open a command prompt in windows and run blender.exe --debug-cycles (instead of just blender.exe)

btw: There was a change in GPU rendering since 2.79b [so only included in current master] that allows for rendering larger scenes, so you could try a recent build from https://builder.blender.org and try your luck...

CUDA rendering now supports rendering scenes that don't fit in GPU memory, but can be kept in CPU memory.
This feature is automatic but comes at a performance cost that depends on the scene and hardware.
When image textures do not fit in GPU memory, we have measured slowdowns of 20-30% in our benchmark scenes.
When other scene data does not fit on the GPU either, rendering can be a lot slower, to the point that it is better to render on the CPU. (rBc621832)

My GPU does only have 1 Gb of VRAM, so that could be the case.

reg. the --debug-cycles option: open a command prompt in windows and run blender.exe --debug-cycles (instead of just blender.exe)

I tried doing this now, but my command prompt can't find blender.exe. I tried reading the wikihow article on how to add a program to the command line, but it reads like the person who wrote it has never spoken English or used a computer before. Maybe you can tell me how to add it and then I can debug cycles for you. In the meantime, it looks like I'll just have to render different things on my CPU and GPU as required.

You could just drag and drop the blender.exe into the command promt and add --debug-cycles to the end

Also: did you check if you can render on GPU with a new build from https://builder.blender.org?

Other than that, I think you are left with your CPU...

I disabled sandbox mode on Comodo and gave it a bake in the June 15 version of blender using my GPU and it worked as it should. Problem solved. Thank you for all the assistance.

Philipp Oeser (lichtwerk) claimed this task.

Glad to hear! Closing then...