I had a couple tree supports break after a color change and during printing I noticed the 2 layers between different nozzles are offset on the y axis. They are fine on the X axis.
I re ran the calibration and even swapped nozzles from one side to the other and had exact results.
The attached pics show one side of my right angle test print with the red hardly showing.
Could you link us your 3MF file so we can take a better look?
Just a heads-up to anyone sharing their .3mf
files:
These files often contain your full model, slicer settings, orientation, supports—everything. If it’s your own design, you’re essentially giving it away. Before uploading, consider whether the file includes original work you want to protect. Screenshots or exported settings are often enough to help troubleshoot safely. Stay smart and protect your IP.
People that want to really protect their IP really shouldn’t be using the free community support to solve their slicing issues. If you want help in that case a NDA and associated consulting fee should be your route.
Still should be mentioned with the ease that people request 3mfs nowadays. Precautions wont harm anyone will they?
Requesting the .3mf is the quickest way to solving most slicing issues. Otherwise it often takes multiple back and forth conversations and picture requests to solve the issue. Being able to upload the .3mf file to the forum has been a game changer for solving slicing issues.
Sure no disagreement there. But lets be honest here, its a data breach nonetheless if one is not carefull. So in my opinion a headsup is needed. Might already be in the corner of everyones mind, but if I save someone the headache of his design being stolen because in his frustration , he didnt think through what he’s (or she) is sharing, im happy. No need for arguement here, especially with how many stolen designs circulate the internet and the known “artisan” websites. Been there done that, if I help out a bro, im happy.
There is perhaps also a middle ground where the .3mf is shared but everything not pertaining to the issues is cutoff? That protects the IP while still being able to troubleshoot the issue.
Yeah or a dummy model , or any workaround really