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

OS can not open Bambu internal sliced gcode .3mf's #6999

Open
1 of 3 tasks
malventano opened this issue Oct 3, 2024 · 1 comment
Open
1 of 3 tasks

OS can not open Bambu internal sliced gcode .3mf's #6999

malventano opened this issue Oct 3, 2024 · 1 comment
Labels
bug Something isn't working stale

Comments

@malventano
Copy link

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.2.0-beta2, 2.1.1, 2.0.0, 1.9.1, 1.8.0, 1.7.0, 1.6.6, 1.6.4, 1.6.2, 1.5.0

Operating System (OS)

Windows

OS Version

Windows 10

Additional system information

N/A

Printer

X1C

How to reproduce

  1. Download Bambu 'internal sliced files' from here.
  2. Open any of the .3mf's in BS. Note that this works.
  3. Open any of the .3mf's in OS. See below error:

Actual results

image

Expected results

image

Project file & Debug log uploads

N/A

Checklist of files to include

  • Log file
  • Project file

Anything else?

  • Closest related bug I could find was 1.6.2 Failed to open G-code file by OrcaSlicer itself #958, which threw a similar error, and is the only google result for "orca slicer "failed to process the g-code file"".
  • The settings from the gcode do appear to be imported into OS.
  • Opening the same file a second time in a row does not throw the error (but still unsuccessful). If I change a setting and re-open the file, the error returns. Possibly some connection related to the settings already being imported by the prior attempt?
  • Noted that in BS I am prompted to import modified filament and printer presets (does not occur in OS, though it does appear filament and printer settings are imported from the gcode).
  • Same error from 2.2.0-beta2 all the way back to 1.5.0, only change starting with 1.6.6 throws an (expected) unrecognized keys error first:
    image
@malventano malventano added the bug Something isn't working label Oct 3, 2024
Copy link

github-actions bot commented Jan 2, 2025

Orca bot: this issue is stale because it has been open for 90 days with no activity.

@github-actions github-actions bot added the stale label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

1 participant