Closed MohanKishan closed 1 year ago
Hi, thanks for the report! Issue #599 may not be the cause of all crashes, so there may be another reason.
Please provide the following items and answers to troubleshooting questions:
Let us know if you have any questions or if you find any more information about the issue.
Blender Version: 3.4.1, blender-v3.4-release, 2022-12-20 08:50, ef9ca44dee7f Addon Version: A FLIP Fluid Simulation Tool for Blender (v0.6.1 Demo 06-JAN-2023 (DEBUG BUILD)) OS: Windows-10-10.0.22000-SP0 GPU: NVIDIA GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24 CPU: 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz CPU Threads: 16 RAM: Unknown (fill in)
Blender Binary: C:\Program Files\Blender Foundation\Blender 3.4\blender.exe
Addon Path: C:\Users\Mohan\AppData\Roaming\Blender Foundation\Blender\3.4\scripts\addons\flip_fluids_addon
Renderer: CYCLES
Cycles Device: GPU
Viewport Modes: SOLID
Objects: 37
FLIP Objects: 14
FLIP Domains: Cube.001
no crash log
and one more thing it's crashing while rendering too its renders a few frames and crashers
baked it by command line baking process it works now
just wanted to share this bug this was caused by one of the objects in my scene
Thanks for the update! I'll add some info from the other messaging channels in case others come across this issue:
This issue seems to be related to a conflict with the Megascans plugin and possibly the Blender Kit addon which are producing errors in the attached console output. From past feedback, these addons can potentially trigger crashes while the simulation is baking/rendering.
From the screenshot above, it looks like the initial error is originating from the Megascans Plugin (startup/MSPlugin
) that is running on startup.
At the moment, the only known workaround is to disable these addons.
Let us know if you have any questions, or feel free to contact us at suppor[at]flipfluids.com.
i did remove the meagscan addon
Hi, just to clarify: was the error you received last after removing the Megascans addon?
According to the error output, there are still Megascans scripts running
and triggering an error. The scripts appear to be running from the Blender
startup folder located at Blender/3.4/scripts/startup/MSPlugin
.
The uninstallation instructions for the Megascan plugin mention removing
the MSPlugin
from the startup folder:
https://help.quixel.com/hc/en-us/articles/360003342778-Removing-the-Blender-Plugin
Does removing this folder solve the issue?
ahh yes I forgot to save it it's baking fine now. Thanks for the help.
599 i have followed all the steps and used studio drivers