Blender 3.2.1 - Particles - Particles generate differently on Linux vs Windows #100369

Open
opened 2022-08-12 10:31:13 +02:00 by Carlo Andreacchio · 17 comments

System Information
Operating system: Linux-5.4.0-122-generic-x86_64-with-glibc2.31 64 Bits - Windows 10 x64
Graphics card: NVIDIA GeForce GTX 1080 - NVIDIA RTX 3080

Blender Version
Broken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: a2d59b2dac
Worked: 2.7.9

Short description of error
Particles render differently between windows and linux.
Linux:
particles_linux.png

Windows and MacOS:
particles_windows.png

Exact steps for others to reproduce the error

particleTest_v001.blend

  1. Open attached blend file on a Linux machine
  2. press f12
  3. save image to network drive
  4. open attached blend file on a windows machine
  5. press f12
  6. open the image from the network drive in another window
  7. press alt tab to flick between them and see that the particles generate differently.
**System Information** Operating system: Linux-5.4.0-122-generic-x86_64-with-glibc2.31 64 Bits - Windows 10 x64 Graphics card: NVIDIA GeForce GTX 1080 - NVIDIA RTX 3080 **Blender Version** Broken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: a2d59b2dac Worked: 2.7.9 **Short description of error** Particles render differently between windows and linux. Linux: ![particles_linux.png](https://archive.blender.org/developer/F13369321/particles_linux.png) Windows and MacOS: ![particles_windows.png](https://archive.blender.org/developer/F13369326/particles_windows.png) **Exact steps for others to reproduce the error** [particleTest_v001.blend](https://archive.blender.org/developer/F13369328/particleTest_v001.blend) 1. Open attached blend file on a Linux machine 2. press f12 3. save image to network drive 4. open attached blend file on a windows machine 5. press f12 6. open the image from the network drive in another window 7. press alt tab to flick between them and see that the particles generate differently.

Added subscriber: @candreacchio

Added subscriber: @candreacchio

Confirmed the bug to still be present in 3.4 Alpha - b5e92c3dfe

Confirmed the bug to still be present in 3.4 Alpha - b5e92c3dfe
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

Rendering the attach file on Linux produces the Linux image in the report, so I will wait until someone on Windows can reproduce the Window image on Windows.
But meanwhile, you say that it is consistent in older versions like 2.79, is that correct? Which image of them does the older version produce?

Rendering the attach file on Linux produces the Linux image in the report, so I will wait until someone on Windows can reproduce the Window image on Windows. But meanwhile, you say that it is consistent in older versions like 2.79, is that correct? Which image of them does the older version produce?

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

I tested it here on Windows. The result matches the Windows image in the report.
I also adapted the file for Blender 2.79:
particleTest_279.blend

The result is the same there.
I couldn't check if it's a regression.


System Information
Operating system: Windows-10-10.0.22000 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.7.1.220725

I tested it here on Windows. The result matches the Windows image in the report. I also adapted the file for Blender 2.79: [particleTest_279.blend](https://archive.blender.org/developer/F13389205/particleTest_279.blend) The result is the same there. I couldn't check if it's a regression. --- **System Information** Operating system: Windows-10-10.0.22000 64 Bits Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.7.1.220725

I just tested both windows and linux on 2.79 (cac3e16cfb) (this a build that we have been using, from after 2.79 was released during 2.8 production), and they were the same as each other, but different results to both results in 3.4
untitled.png

I just tested both windows and linux on 2.79 (cac3e16cfb) (this a build that we have been using, from after 2.79 was released during 2.8 production), and they were the same as each other, but different results to both results in 3.4 ![untitled.png](https://archive.blender.org/developer/F13389673/untitled.png)

Will this be fixed for the 3.3 release?

Will this be fixed for the 3.3 release?
Member

@candreacchio That would unlikely since 3.3 is already preparing for release.

@candreacchio That would unlikely since 3.3 is already preparing for release.

Yes, critical fixes only. And this is a critical issue. How are artists supposed to have confidence in their renders if what they are generating may be incorrect.

Especially in small - medium sized VFX houses, where linux machines are more used for rendering, and windows machines are used more for the artists.

Yes, critical fixes only. And this is a critical issue. How are artists supposed to have confidence in their renders if what they are generating may be incorrect. Especially in small - medium sized VFX houses, where linux machines are more used for rendering, and windows machines are used more for the artists.
Member

The problem is that the particle system is end of life and is not actively maintained. Maybe using Geometry Nodes for some of those tasks is a better option for now.

The problem is that the particle system is end of life and is not actively maintained. Maybe using Geometry Nodes for some of those tasks is a better option for now.

Yes, but it is still part of this release and even so, it is a critical issue for LTS releases and needs to be maintained.

Yes, but it is still part of this release and even so, it is a critical issue for LTS releases and needs to be maintained.

Confirmed that this is in the LTS release of 2.93 as well.

It is a critical issue. It should be treated as one, even if it will eventually get deprecated, right now it is not deprecated so it should be treated as such.

Confirmed that this is in the LTS release of 2.93 as well. It is a critical issue. It should be treated as one, even if it will eventually get deprecated, right now it is not deprecated so it should be treated as such.

Will this be fixed for the LTS of 2.93, 3.3 and the 3.4 release?

Will this be fixed for the LTS of 2.93, 3.3 and the 3.4 release?

With the latest comments about "LTS releases should be done once a month, even if there is just one (high priority) bugfix", it would be great to get this fixed for the next release, as this is a significant issue for those running multi-platform render farms.

With the latest comments about "LTS releases should be done once a month, even if there is just one (high priority) bugfix", it would be great to get this fixed for the next release, as this is a significant issue for those running multi-platform render farms.

Any chance that this will get fixed relatively soonish?

Any chance that this will get fixed relatively soonish?
Philipp Oeser removed the
Interest
Nodes & Physics
label 2023-02-10 08:43:49 +01:00
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#100369
No description provided.