Cycles Bake requires to save externally first/won't let me save file externally #40054

Closed
opened 2014-05-06 22:41:00 +02:00 by NG · 16 comments

System Information
WIN7 / I7 3930 / 32gb Ram / Gtx 560 TI 2GB

Blender Version
Broken:2.70 7660218
worked 2.70 362b25b3

Short description of error

Issue 1: Since cycles Bake in master, I am required to first save the image externally, then bake, then save the image again, and then reload image to actually see the result. As far as I know, cycles bake should show image in editor, right after bake, no external saving required.
Issue 2: In 7660218 in won't even let me save the image externally, I get an error message, that I have screenshoted below.

I have provided a blend file, attempting to bake a normal map from multires. Just press bake.

It doesn't produce any result, and I can not even save externally.

thanks.

testbake.blend

issue1.jpg

**System Information** WIN7 / I7 3930 / 32gb Ram / Gtx 560 TI 2GB **Blender Version** Broken:2.70 7660218 worked 2.70 362b25b3 **Short description of error** **Issue 1**: Since cycles Bake in master, I am required to first save the image externally, then bake, then save the image again, and then reload image to actually see the result. As far as I know, cycles bake should show image in editor, right after bake, no external saving required. **Issue 2**: In 7660218 in won't even let me save the image externally, I get an error message, that I have screenshoted below. I have provided a blend file, attempting to bake a normal map from multires. Just press bake. It doesn't produce any result, and I can not even save externally. thanks. [testbake.blend](https://archive.blender.org/developer/F87338/testbake.blend) ![issue1.jpg](https://archive.blender.org/developer/F87342/issue1.jpg)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @NGMAT

Added subscriber: @NGMAT

Added subscribers: @Sergey, @dfelinto

Added subscribers: @Sergey, @dfelinto

tip: use one bug report per issue ;)

I am required to first save the image externally, then bake, then save the image again, and then reload image to actually see the result. As far as I know, cycles bake should show image in editor, right after bake, no external saving required.

You don't need to save the image externally before baking, only after.

Issue 2: Here it saves fine tangent.png. Does that problem happen if you don't bake too? If so it's not related to baking and could/should be reported separately

It doesn't produce any result

Right, this seem to be the only bake related part of the report. If you change your image to be sRGB and uncheck "linear" this will work. In fact the same issue happens if the colorspace is 'non-color'.

I think I'm doing something wrong in write_internal_bake_pixels(), introduced when I addressed @Sergey's concerns regarding color management.

tip: use one bug report per issue ;) > I am required to first save the image externally, then bake, then save the image again, and then reload image to actually see the result. As far as I know, cycles bake should show image in editor, right after bake, no external saving required. You don't need to save the image externally before baking, only after. Issue 2: Here it saves fine ![tangent.png](https://archive.blender.org/developer/F87345/tangent.png). Does that problem happen if you don't bake too? If so it's not related to baking and could/should be reported separately > It doesn't produce any result Right, this seem to be the only bake related part of the report. If you change your image to be sRGB and uncheck "linear" this will work. In fact the same issue happens if the colorspace is 'non-color'. I think I'm doing something wrong in write_internal_bake_pixels(), introduced when I addressed @Sergey's concerns regarding color management.
Author

i thought they where related. apologies. I will report that separately.

yes I know you shouldn't need to save externally, but I do, otherwise I get no result in the image editor. This goes for all bake builds i've used on my machine since it was included in master.

I changed to srgb as your recommended on BA before, and I still have blank image.

Did the same thing in yesterdays build 362b25b3, had to save externally and reload, and I got this result, which is a lot different to yours.

badbake.jpg.

i thought they where related. apologies. I will report that separately. yes I know you shouldn't need to save externally, but I do, otherwise I get no result in the image editor. This goes for all bake builds i've used on my machine since it was included in master. I changed to srgb as your recommended on BA before, and I still have blank image. Did the same thing in yesterdays build 362b25b3, had to save externally and reload, and I got this result, which is a lot different to yours. ![badbake.jpg](https://archive.blender.org/developer/F87354/badbake.jpg).

This issue was referenced by blender/blender-addons-contrib@2c4ea2a11e

This issue was referenced by blender/blender-addons-contrib@2c4ea2a11ed7e9724b7b5c736ed5ff5db1681662

This issue was referenced by 2c4ea2a11e

This issue was referenced by 2c4ea2a11ed7e9724b7b5c736ed5ff5db1681662

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Closed by commit 2c4ea2a11e.

Closed by commit 2c4ea2a11e.

@NGMAT you changed the color space to sRGB but forgot to uncheck the 'float' option. Anyways, it should be fixed now. If you still have troubles (related to that issue) let me know and I reopen the entry. Thanks for reporting ;)

@NGMAT you changed the color space to sRGB but forgot to uncheck the 'float' option. Anyways, it should be fixed now. If you still have troubles (related to that issue) let me know and I reopen the entry. Thanks for reporting ;)
Author

Ah you where right!

ok so it wiil be set that way by default after this report now?

my bake still doesn't looks as yours though. this what it looks like after following all the advice.

separate issue?

badbake2.jpg

Ah you where right! ok so it wiil be set that way by default after this report now? my bake still doesn't looks as yours though. this what it looks like after following all the advice. separate issue? ![badbake2.jpg](https://archive.blender.org/developer/F87360/badbake2.jpg)

I forgot, I also opened your mesh and set all faces to Shade Smooth ;)

I forgot, I also opened your mesh and set all faces to Shade Smooth ;)

ok so it wiil be set that way by default after this report now?

No, not set by default, we will respect whatever the user was using. But now we show the result even when the user is not using sRGB with no float.

> ok so it wiil be set that way by default after this report now? No, not set by default, we will respect whatever the user was using. But now we show the result even when the user is not using sRGB with no float.
Author

you shouldn't have to set it to shade smooth.

If you are working on a high detail at level 6 or something, smooth shading can actually ruin the details.

in the past i've not had to set it to shade smooth.

(I may have to confirm this amongst sculptors on BA, ignore for now)

thanks for clarification.

you shouldn't have to set it to shade smooth. If you are working on a high detail at level 6 or something, smooth shading can actually ruin the details. in the past i've not had to set it to shade smooth. (I may have to confirm this amongst sculptors on BA, ignore for now) thanks for clarification.

@NGMAT anyways let's agree that this is an unrelated issue :) if you think internally it should handle the normals differently please let us know, but I have a feeling that the map I baked is correct for when using lowpoly smooth faces, and yours is correct for flat faces. So it's all good.

@NGMAT anyways let's agree that this is an unrelated issue :) if you think internally it should handle the normals differently please let us know, but I have a feeling that the map I baked is correct for when using lowpoly smooth faces, and yours is correct for flat faces. So it's all good.
Author

yep, it was confirmed to me that your way is correct anyway, I was wrong..

thanks for fixing this bug.

yep, it was confirmed to me that your way is correct anyway, I was wrong.. thanks for fixing this bug.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#40054
No description provided.