Watched this a while back and my take away way it might.
Watched this a while back and my take away way it might.
The larger photo shows a lot of wear on the end compared to the new nozzle (the flat area on the top is larger). It’s hard to tell from the photos but in my experience this generally correlates to a widened nozzle diameter and decreased print quality.
Great work. This is how you really unlock the potential of your printer!
When we visited Europe a number of years ago I had to learn stick and we all practiced quite a bit because renting an automatic wasn’t reasonable. It’s actually pretty hard to find a manual to learn on and not all learner agencies even have one.
Don’t think half the comments understand what the Chromecast is…
Interested in finding out more about fcast now though.
Maybe. I actually have a dehydrator I use with plenty of airflow.
But I think that only solves part of the problem because that makes it really good at drying the outside but it’s still going to have trouble past the first couple layers. I think the fact moisture would also have a hard time penetrating means current options work well enough.for most people.
Anecdotally I can support this, recently I had a particularly old roll of petg that I dried for a larger print and later in the print started getting all stringy and messy.
Yeah, I’m definitely interested to see some experiments. I was surprised it worked as well as it did but if it does it’d be super useful
Wonder if you could use some sort of buffer system to extend the time in the dryer
Yeah similar but when I’ve tried a lot of the UI ends up looking wrong. Bad font or UI colors, etc.
Not hating on freecad, I like it and they’re working hard, just want to make clear it’s not fair to suggest a normal person could make it look the same.
Additional note. It’s a weird discussion. My understanding is development is flowing back and forth with the intention of ondsel being mostly a set of pro cloud plugins. Use what you like today because you can swap tomorrow.
Some of the nightlies are actually ahead of ondsel in features actually. But while you can get close, the theme and UI changes don’t work very well in freecad. You might be able to write some plugins to do it but I haven’t seen them.
I really appreciate this change. Prior to it was always a struggle to deploy servers successfully. You’d reboot and your database would be on the wrong interface and you could even remote in because the management interface was suddenly on a firewalled external only network. Ask me how I know.
With virtualization and containers this just got more complicated. I would constantly have to rewrite kvm entire configs because I’d drop a new nic in the machine. A nightmare.
Sure, it’s gibberish for the desktop user but you can just use the UI and ignore the internal name. Not even sure the last time I saw it on my laptop. So no big deal.
Libwebkit isn’t actually chromium, it uses blink which is a fork of part of webkit. Understandable confusion though because webkit was part of kde, forked by safari, and then used by through chrome variants for a long time.
The rest of this comment is going to necessarily be nerdy Linux internals. sorry.
Unfortunately, I’m pretty sure chromium includes it inside it’s binary and does provide or use any webkit libraries.
Orca uses it internally for it’s browser so it won’t start unless it has access to the library. When you build a Linux app it includes the name of the library which includes the ABI (basically the version). Newer Linux release include a different version.
You can see how that specific library stops appearing in Ubuntu releases https://packages.ubuntu.com/search?keywords=libwebkit2gtk-4.0-37
The new version is 6.0 I believe.
Appimage is one of the ways you get around this distro problem by including the versions of libraries. That’s why they’re so big. There are problems with that like how big the apps are stale bundled libraries with security issues but I digress.
Orca hasn’t bundled webkit in the appimage and because of another problem/feature of appimage it falls back on the os library. Since new distros have dropped the older obsolete library version orca can’t start.
That’s a lot but I hope it explains the problem better.
I would like to help but my personal computer doesn’t currently have enough memory to compile orca so back to just watching warning people it’s a coming problem for them too.
That’s good. I assume you’ve got the old libwebkit installed somehow. There are a dozen reports around this though so it’s a pretty real problem. https://github.com/SoftFever/OrcaSlicer/issues?q=libwebkit2gtk-4.0.so.37
Ubuntu but it also affects fedora https://github.com/SoftFever/OrcaSlicer/issues/185
The image just isn’t being built correctly which is more a problem with appimages but the fact it’s still broken… Linux is clearly a neglected platform for them.
All the problems I listed have bug reports just nothings happening to fix them.
Appimage doesn’t start because it relies on a system package that does exist anymore, dialogs with grey text on grey backgrounds in dark mode, stl repair not included…
Flatpak is in the works but honestly and hope that helps bit I get better prints out of prusaslicer for some reason so not holding my breath or anything.
Does it work on recent Linux releases yet?
Thanks! That makes it weirder… But good to know it’s on my side.
I assume incompetence over malice. Which is to say it’s probably a bug or a mistake setting up the model. The user isn’t selling anything so it really seems like some sort of bug
I would have guessed the same as others that it was interactions between the nozzle and the bed or some texture on the bed. Especially since we don’t see any normal extrusion lines which are normal on the first layer.
Since you’re confident it’s not, are there artifacts elsewhere on your prints that might be a clue? Is there anything going on with your nozzle? Maybe some wear, chips,or inconsistent flow? If you print just the first layer what does it look like from the top? Does it help describe what we’re seeing?