Cycles uses different amount of memory for viewport viewport with border and final render #43179
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#43179
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Windows 10 x64
GTX 970 GTX 560ti
Blender Version
Dont think its something that is broken
Short description of error
Exact steps for others to reproduce the error
Render voronoi procedural with many noise textures displacing the texture coordinates
Changed status to: 'Open'
Added subscriber: @derekbarker
Sorry forgot its in blender 2.73
Changed status from 'Open' to: 'Archived'
I do not see any bug here? viewport and final render are usually not the same size, to start with! And not the same number of samples, etc.
If i had a scene full of procedural textures like this it wouldn't be able to be rendered in view port but if i switch border on it could fit. Why is that?
Keep in mind a bug could fall under unexpected behavior and thats pretty unexpected for an end user.
Then please attach here a .blend file with such scene, that you cannot render in viewport but can in real render… Theorical bug is not a bug ;)
Also, please remember mem report during render is merely informative, it does not always reflect reality quite well.
Ok haha well that makes sense :P
One last question you may know the answer to
If you get closer to a procedural texture does it load more of it or is the texture in the scene 100% of the time
Also after posting this i have realized it was the resolution causing it sorry for the useless posts i always make haha <3 keep up the good work :D
regarding procedural tex, each pixel is generated on demand. So yes, the closer you get, the more pixels (texels, actually) will be generated, so if they are cached somewhere (not sure about that), cache will use more mem.