Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account
Jump to bottom

prusa 2.3.0 crash with 0.25 nozzle #5825

Closed
PowerChaos opened this issue Jan 18, 2021 · 2 comments
Closed

prusa 2.3.0 crash with 0.25 nozzle #5825

PowerChaos opened this issue Jan 18, 2021 · 2 comments

Comments

@PowerChaos
Copy link

PowerChaos commented Jan 18, 2021 •
edited

Version

PrusaSlicer
Version: 2.3.0-rc3+win64
Build: PrusaSlicer-2.3.0-rc3+win64-202101081019

Operating System: Windows
System Architecture: 64 bit
Windows Version: Windows 10 (build 19041), 64-bit edition
Total RAM size [MB]: 17,093MB
OpenGL installation
GL version: 4.3.0 - Build 20.19.15.5144
Vendor: Intel
Renderer: Intel(R) HD Graphics 4600
GLSL version: 4.30 - Build 20.19.15.5144

3D printer brand / version + firmware version (if known)

Ender 3 V2 + bltouch ( merlin 2.0.1 i guess)

Behavior

*Crash when using 0.25 nozzle
**This only apply to the version 2.3.0 as LATEST STABLE , this does not occur in the RC3 version ( where this report is based on )

Project File (.3MF) where problem occurs

prusaerror.zip

*This file also include my printer profile , exported from verion 2.3.0 and imported in the RC3 version
this can be repeated by just using the import config and then the program will crash with that file , STL file also included ( as i use STL instead AMF

Greetings from PowerChaos
@rtyr
Copy link
Collaborator

I can reproduce crash when importing PrusaSlicer_config_bundle-0.25.ini using "Import Config..." option (Import Config Bundle... works).

bubnikv added a commit that referenced this issue Jan 19, 2021
@bubnikv
Fix of prusa 2.3.0 crash with 0.25 nozzle #5825
5294a48 
Importing a config bundle as a config file was broken for
multi material FDM printers, where a different filament was active
for each extruder.
@bubnikv
Copy link
Collaborator

Fixed with 5294a48

Importing a config bundle as a config file was broken for
multi material FDM printers, where a different filament was active
for each extruder.

Thanks for the report.

@bubnikv bubnikv mentioned this issue Aug 6, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bubnikv @PowerChaos @rtyr