Replies: 40 comments 102 replies
-
|
It would help if you described what back pressure compensation in Cura is, how to enable / control it and what to expect from it ;) |
Beta Was this translation helpful? Give feedback.
-
From this brief description in the release notes it sounds like a kind of Linear Advance that manipulates movement speed instead of extrusion speed/retractions to achieve the same? |
Beta Was this translation helpful? Give feedback.
-
|
Print quality is improved through dynamically adjusting print head velocity, which slows down or speeds up depending on the pressure of the material through the Bowden tube. ( You can find this setting under Flow Equalization Ratio) https://ultimaker.com/learn/3d-printing-revolution-continues-second-beta-for-ultimaker-cura-arachne |
Beta Was this translation helpful? Give feedback.
-
|
Back pressure compensation is realized in the Flow Equalization setting. By using 100% flow equalization, twice as wide lines are printed half as fast, so that the flow in mm^3/s remains constant. However, when you increase the setting over 100%, wider lines are printed even slower, which compensates for the fact that wider lines also require more pressure to squeeze out so wide. Talk about back pressure compensation is a bit misleading, because it's only realized through that Flow Equalization setting if it's set to over 100%. back pressure compensation is similar/related to linear advance. Linear advance increases pressure in the system when flow (mm^3/s) is increased by feeding more material in the Bowden tube, so it relates movement speed to pressure increase. Similarly back pressure compensation tries to relate line width to pressure increase. However, these concepts are flipped on their head in the Flow Equalization setting. Flow Equalization at 100% changes the movement speed, so that the flow and the internal pressure remain constant, so that they don't need to be adjusted by linear advance. Similarly, Flow Equalization >100% tries to keep the outflow of material constant, by not only taking the internal pressure into account, but also the back pressure of the previous layer, which is greater for wider lines. |
Beta Was this translation helpful? Give feedback.
-
|
@BagelOrb thanks for explanation! Calibration cube is too simple to make it visible, but benchy does it better (setting at 100%). Haven't tried printing it yet. Speed: Flow: I wonder where those bars came from, they don't appear in gcode :/ |
Beta Was this translation helpful? Give feedback.
-
|
Same issue with the bars. Also, I noticed if the camera is oriented such that the origin is somewhere in front then the layer view is only partly drawn, the grey 'ghost' is drawn in the other half: |
Beta Was this translation helpful? Give feedback.
-
|
I tried cura arachne beta 2, the new version still has bugs with filling |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Goodfeat could you share a project file (file - save project) with your stl I can't reproduce your issue. |
Beta Was this translation helpful? Give feedback.
-
|
The experimental bridging settings have some problems. (Note: these problems also exist in mainline Cura.) The screenshot is of the attached project sliced and preview set to layer 11. In "no bridging", everything looks fine. In "bridging w/ no speed change", you can see the bridge skin overlapping with the walls. In "bridging w/ wall & skin 50% speed" (50% in this case being 60mm/sec), you can see the outer and inner walls grow significantly at one or both ends of the line segment. The growth is proportional to the speed change to some degree, though it appears to have a maximum amount of growth (eg you can't inflate it to insane widths by setting a speed like 20mm/sec).
|
Beta Was this translation helpful? Give feedback.
-
|
The yellow lines in bridging were not changed with the Arachne project, so any issues that were there before would still be there. The overlap you're seeing may be an issue you'd want to report as a normal bug report. The walls growing just after the bridge is intentional. It's compensating for the flow changes. This was built into the experimental bridging feature from the start. It looks a little weird, but seems to improve print quality a bit. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. See #11059. |
Beta Was this translation helpful? Give feedback.
-
|
Enabling ironing in the attached project causes slicing to fail with an error message. I thought I was able to get it to get stuck (cancel stopped it successfully) depending on Z seam position, but I'm unable to reproduce this behavior at this time. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed, I can reproduce this crash. I'll put this up with the rest of the team, see if we can make a fix. |
Beta Was this translation helpful? Give feedback.
-
|
We have now a ticket on our backlog for this. Devs see CURA-8756. |
Beta Was this translation helpful? Give feedback.
-
|
Strange resets After updating my installed plugins and restarting Beta2, Cura starts with machines and preferences reset. Settings profiles are intact. Not sure if the plugins has anything to do with it or if it simply was caused by the restart. Next attempt, I only change one thing at a time. This works and I now notice that the new machine has a # 4 on it in the dropdown and I can also see the previous 3 machines. I can't recall it resetting more than twice though. Perhaps something carried over form Beta1? HOWEVER, when I now start Beta1, Beta1 is reset. Only adding a printer with no changes, then restarting again remembers this machine and now I have Custom fff printer # 3 and # 4 in beta1. However not the first two that appears in Beta2. Log found in Cura 0.0 folder says synced cloud printers. I'm usually not logged in but I did log in this time: |
Beta Was this translation helpful? Give feedback.
-
|
Same problem https://prnt.sc/21834y3 https://prnt.sc/21839v9 after uninstalling beta1 and instaling beta2 and i had installed cura 4.10. Printer profile are not displayed config file not missing. |
Beta Was this translation helpful? Give feedback.
-
|
We're seeing some upgrade issues too, but they are related to the weird version numbering of this beta and the stable release being delayed so often. They should not be upgrade issues any more with the stable release of Cura 5.0. We gave this beta (originally "alpha") release a version number of 0.0 and never intended to perform version upgrades from it. Because of that there have been some issues when beta 1 or the alpha was used. And the version upgrade only upgrades up from Cura 4.11 I think. |
Beta Was this translation helpful? Give feedback.
-
|
Could you please link to the download page from this page (and vice versa)? |
Beta Was this translation helpful? Give feedback.
-
|
Done, thanks :) |
Beta Was this translation helpful? Give feedback.
-
|
Top surface skin doesn't work. I set top bottom line width to 0.6mm and top surface line width to 0.35mm. more than one top surface layer doesn't help. |
Beta Was this translation helpful? Give feedback.
-
|
This is also not working for me. Changes to top surface flow, speed, and line width don't seem to have any effect. I tested my settings on 4.13.1 and they are working there. |
Beta Was this translation helpful? Give feedback.
-
|
Before I install Arachne, I wanted to check whether you can get it to co-exist with an existing 4.8 Cura installation - assuming I put it into a separate location to the existing version. Are there any additional steps I should take to do this, or should I rather install it on another machine? |
Beta Was this translation helpful? Give feedback.
-
|
You can install any two versions of Cura side by side without a problem. All config files are stored separately. |
Beta Was this translation helpful? Give feedback.
-
|
Caveat: the two Arachne betas are not necessarily side-by-side compatible (unless I am mistaken). |
Beta Was this translation helpful? Give feedback.
-
|
Correct; The Arachne versions are not compatible side by side. |
Beta Was this translation helpful? Give feedback.
-
That explains my issue above. |
Beta Was this translation helpful? Give feedback.
-
|
I'm new to Cura and had the same question. Perhaps a note about running the Beta alongside the stable version could be added to each Beta download page for new users? |
Beta Was this translation helpful? Give feedback.
-
|
Hole Sizes |
Beta Was this translation helpful? Give feedback.
-
|
Could you please share your project file? Change extension to .zip and upload here. |
Beta Was this translation helpful? Give feedback.
-
|
One of the intended aims of the Arachne project was to get more accurate dimensions with thin parts. I don't know if your hole is surrounded by thin walls or not. But if so, this is a good sign. If not, it's probably due to other unintended effects. We expect that people have to adjust their profiles a bit with this change, which is one of the reasons why we have betas so long in advance. |
Beta Was this translation helpful? Give feedback.
-
|
I was recently testing the clearance I need to print in place screws and axis assemblies and found that sliced in Arachne engine i can reliably get 0.08 mm clearance to work (Creality CR-6 SE printer with direct drive mod). In 4.10 i could at best get 0.15 mm clearance to work. That sounds like it could well be helped by this feature. It also explains why a few of my models get comments the holes are too small even though for me they are perfectly fine. |
Beta Was this translation helpful? Give feedback.
-
|
HI! I installed Cura Arachne beta alongside my Cura 4.12. I am forced to make a printer when starting Arachne the first time to be able to start the program but my printers and profiles from 4.12 are missing ??? Tried to uninstall Arachne and reinstall but same result. Everything is good in 4.12 though. Same situation on both of my computers. When checking the configuration folder in Arachne (the 00 folder in roaming/Cura) my machines (printers) are there but there are some errors when I check the log in cura. Anyone have a clue of what could be the problem? Further I removed the 0.0 folder both from the roaming/cura and local/cura as the 00 folder were there to, but still no luck after a reinstall. Funny thing though, If I make a printer with the same name as one of the missing Cura adds #2 to the printer name so its like its there but I cant see it. If I remember correctly I once had the first beta of Arachne installed besides cura in my first computer and it was working, and later I uninstalled Arachne. Then I installed 4.? on my second computer and copied the configuration files to that computer so I got my printers and profiles. Recently I decided to try Arachne again (the second beta) and after that the problem is as described above on both computers. |
Beta Was this translation helpful? Give feedback.
-
|
We are seeing some upgrade issues because of the version numbering of this Cura version (internally it's version 0.0) and because of the delay in the stable version's release (we used setting_version 18 for Arachne back when stable was at 15, but surpassed that with the 4.12 release which has version 19). As such, it'll only upgrade from 4.11 and this result is to be expected. Not nice for the beta test! But for the final release it shouldn't be a problem any more. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Is it also printing those lines or is it just the visualization? |
Beta Was this translation helpful? Give feedback.
-
|
These are most likely caused by a change to the rendering of layer view. It's not a change in Arachne but a change we made for Cura 4.13. |
Beta Was this translation helpful? Give feedback.
-
|
These were fixed in version 4.13 (and 5.0 as well as a result). |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Wait, the Anycubic Predator is in Cura, but something goes wrong when loading your project file... Lemme see. |
Beta Was this translation helpful? Give feedback.
-
|
Idk. I can't reproduce the issue with that 3mf. When I slice that model with the Anycubic Predator I don't have any problem. Even when I install the Arc welder plugin I cannot reproduce your issue. Did you change anything from the default profile afte you installed Cura Arachne beta 2? Are your video drivers up to date? |
Beta Was this translation helpful? Give feedback.
-
|
yes i have a heavily modified predator and the standard profile doesn't work for me. Sorry I've posted the wrong screenshot. Like I said with an ultimaker s5 and the standard profile I have the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
These are most likely caused by a change to the rendering of layer view. It's not a change in Arachne but a change we made for Cura 4.13. |
Beta Was this translation helpful? Give feedback.
-
|
We have created a ticket on our backlog for this. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Please keep related issues within the same thread. |
Beta Was this translation helpful? Give feedback.
-
|
Please refer to the thread above. |
Beta Was this translation helpful? Give feedback.
-
|
These are most likely caused by a change to the rendering of layer view. It's not a change in Arachne but a change we made for Cura 4.13. |
Beta Was this translation helpful? Give feedback.
-
|
Hi. I've noticed a strange behaviour of settings in Arachne beta2. I installed it alongside with Arachne beta 1 and Cura 4.7. My manually created printer preset was successfully imported. After installing beta 2 I never launched beta 1. |
Beta Was this translation helpful? Give feedback.
-
|
Fuzzy Skin is indeed not yet implemented in Arachne. We have to rework a bit of it there due to the variable wall line thickness. This is still not done, but planned for the stable release. |
Beta Was this translation helpful? Give feedback.
-
|
Ah. Ok. this wasn't mentioned in the release notes so I think it's mine configuration problem. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, it was mentioned in the release notes of the earlier betas of Arachne, and we didn't repeat all of those this time. This is considered a blocker for the 5.0 release. We must have this fixed before it's released in stable. However for testing print quality it was never necessary so we haven't re-implemented it yet. |
Beta Was this translation helpful? Give feedback.
-
|
Hey all. Had no idea a new beta was available, and went to download it immediately and see the features of 4.12 while keeping my, well, everything, I have in Arachne. Unfortunately, I faced the same issue that some other folks here have faced. #5e60cc6
While I understand to keep related issues together, I didn't recognise this as a problem to begin with and merely a graphical bug. That's fine. However, I did get an issue when switching profiles (and I'll try to supply a 3mf here, which is difficult, as it crashes).
As with the crashing, I can provide a log file which I hope some data can be inferred. I apologise for the likely very long post filled with images, let me know if I should remove any of them to truncate the data a little. I'll be reverting back to Beta 1 for the time being, I can only rarely generate a gcode, and when I do, I don't trust it as I can't see a preview... Is Arcs messing things up here? Good luck with the continued development, I look forward to playing with this in the future <3 EDIT: Forgot to add, every single time I open it, I end up on this screen: This is a moderate inconvenience, as I don't need to keep adding machines. I ended up with quite a few machines, and I went through and deleted them. Little did I know that I had deleted my actual machine that was defined. It's running on an SSD so it was genuinely gone forever™. No big deal, I've seen lots of posts of people incredibly salty about losing their profiles. It's an inconvenience, sure, but... Well, when something says it'll delete something forever with no way to recover, maybe take a second and think before clicking the big blue button. |
Beta Was this translation helpful? Give feedback.
-
|
So, this may not work, but here goes: In further investigations, I've found that particularly "large" models have the most difficulty. I sliced an XYZCube, and that worked fine. Had the graphical error with the large lines at the beginning, but took the gcode over to IdeaMaker to validate the gcode file. Of course, Arcs make the preview broken like nothing else (even with a cube), but it was enough for me to be confident in the gcode itself (as in, everything looked fine, the two large extrusion lines from origin did not carry over). I then tried to slice a file that I need to print for my partner. It was a request, so I designed the model quickly. I threw it into Cura Arachne Beta 2 (after going through the "Add your printer" process for the umpteenth time, then deleting the added printer and going to my already configured printer), observed that the model had been imported correctly, then waiting for it to slice. It took a while, but it was a fairly large model with a short layer height, so that's fine. It got to the very end, told me how long it estimated to print the model (which is between 20-40% longer than it actually takes). So I went to preview, observed a... something show, and it crashed. I'll provide a screenshot, log, and 3mf here: And a little about my computer: EDIT: Turns out, a coarse layer height of 0.3 has the same effect. I can anticipate it happening as well, as if it takes more than 10-15 minutes to slice, it will crash if I attempt to view the preview. My next step would be slicing one of these "larger" projects, and then just saving the gcode. I suspect this will also fail, as the small XYZCube I tested took over a minute to save the file after verifying the preview didn't have anything particularly game-breaking. |
Beta Was this translation helpful? Give feedback.
-
|
This is a duplicate report. This issue was also present in master (before the merge) and is fixed for Cura 4.13. Try Cura 4.13 to see if it is indeed fixed. It had nothing to do with Arachne or with arcs. Arachne was just unlucky to capture the front-end in a state where this happened on AMD GPUs. |
Beta Was this translation helpful? Give feedback.
-
|
I am being reminded to update to the latest version whenever I open the latest version.... Also, small diameter holes in the first layer are always ripped off the print surface. The print speed needs to be slowed when printing smaller diameter hole (below 4mm diameter) to allows for surface adhesion. It would also be great if, particularly during tall thin prints, if it could alternate between N and N+1 walls. Having every second layer of infill anchored from above and below will add strength to taller, thinner pieces. |
Beta Was this translation helpful? Give feedback.
-
|
The version number in this release is a bit weird. Internally it's version 0.0. I'm guessing that's why you're getting that message. This won't be a problem for the actual release, luckily.
So set the Small Hole Max Size to 4mm and the Small Feature Speed lower?
You mean Alternate Extra Wall? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I did not know these features existed. Far too many settings for mere mortals. :-) |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
I'm not sure this is a bug, but during the first layer of prints that have busy first layers and even sometimes with normal looking models the slicer builds the first layer with many tiny little spots instead of solid lines. This many smaller dots make it real easy for the print to fail during the first layer. We all have experienced issues with bed adhesion and having to test how good our adhesion is that many times really entails that at least of one those little dots will fail and consequently make the upcoming dots fail. If this is simply a setting I must change I do apologize. I will include the STL I'm using and the profile as well. Print Settings:
Model: https://github.com/kevinakasam/BeltDrivenEnder3/tree/main/V3/Voronparts One more thing, when will we see this Arachne engine being implemented into the main Cura slicer |
Beta Was this translation helpful? Give feedback.
-
|
It's true that Arachne can result in more of such small wall islands. That's because Arachne does round offsets instead of mitered. If you want the outer walls to be printed first then make sure the Wall Ordering is set to Outer to Inner. |
Beta Was this translation helpful? Give feedback.
-
|
Combing in Arachne beta 2 causes unretracted moves which cross between objects. This creates strong unwanted connections between separate parts.
Here is the project file |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I could reproduce this issue. To prevent retracting or unretracting on the outer wall (which would cause a blob), Cura will move the nozzle further inside first, while unretracted. I think this problem comes from that it tries to move 1 line width away from the centreline of the outer wall (1.5 line widths from the model contour) but that model is less than 3 line widths wide. So the closest point it could go that is 1.5 line widths away from the outer wall is in a different part. There's probably a limit to how far it can move (because in sharp corners the inner wall is further from the outer wall than 1 line width) but maybe this is still under that limit since the surfaces are so close to each other. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for looking into that. Part of the problem seems that the outer walls are printed first and Cura does not want to comb over an empty space between outer walls (it would probably be better than what happens currently). BTW, here is what 4.12 does (I set 'print outer walls first' to match arachne behavior and 'retraction minimum travel' to 0.5):
Interestingly the starting points of walls are aligned in 4.12 but not in arachne (both use 'shortest' starting point strategy), don't know if that matters. |
Beta Was this translation helpful? Give feedback.
-
|
This was added to a similar ticket that our testers had found before. It's not exactly the same case, but I guess they'll discover that soon enough. Developers, see issue CURA-8131. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
-
|
We did update that. But we didn't make a release of that yet. A release will come, no worries. |
Beta Was this translation helpful? Give feedback.
-
|
Gradual infill produces very short infill lines next to walls (4.12.1 works fine)
Project file: |
Beta Was this translation helpful? Give feedback.
-
|
Indeed, I can reproduce this. It seems to be caused by Infill Overlap. Setting that to 0 removes the issue. It probably sees that this overlapping part of the infill is very closely below the walls (it is actually inside the walls) and then decides to use the highest infill density there. |
Beta Was this translation helpful? Give feedback.
-
|
We have a ticket on our backlog for this. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Hi! I've had great results with this release on my Ubuntu machine using the provided AppImage. But for my Alpine Linux machine, I'll need to run it from source[1]. What CuraEngine branch/commit was used to generate the provided release downloads, or will master give me the same results? [1]: There are too many unsolved compatibility issues with AppImage itself, unrelated to Cura... |
Beta Was this translation helpful? Give feedback.
-
|
Master will give different results since we've continued developing since the release. Hopefully the results are better on master than in the beta though. We don't know of any regressions that have been introduced in master since this beta release. To reproduce this beta release, check out the tag |
Beta Was this translation helpful? Give feedback.
-
|
I have a lot of travel moves between walls with Arachne_engine_beta_2. The same part in 4.12.1 looks much better. Travel settings are the same. |
Beta Was this translation helpful? Give feedback.
-
|
The problem with this model is that the sides are 0.4mm thick, while the corners are 0.8mm thick. The behavior of the old Cura could sometimes cause overextrusion, where it would print the sides twice instead of once. That's hard to see in the image. With Arachne the corners get 4 polygonal walls and the sides get 4 polyline walls, which are printed separately from each other. With the new Wall Ordering fixes (which have currently not been merged to master yet), the printing order might be different from the current Arachne beta 2. However, those travel lines shouldn't cross the gap in the middle. I know combing was broken in some of the older Arachne beta releases, but we should check whether this is still a problem with the current master branch. |
Beta Was this translation helpful? Give feedback.
-
|
For you the problem can currently be resolved by using a larger rounding on the outside than on the inside. Specifically: make those outer fillets with a radius of the inner fillet plus 0.4mm. |
Beta Was this translation helpful? Give feedback.
-
|
at what branch this changes ? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Hello! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @bromor I |
Beta Was this translation helpful? Give feedback.
-
|
Understood, thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Skin removal and expansion is misbehaving. What is really interesting is that if I change layer height by as little 0.01, the issue worsens significantly. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, indeed. The layer height having an effect on it indicates that there may be something of an edge case going on. Skin Removal Width should only have an effect where the skin can get replaced by infill. In this case that is not happening either. Perhaps it thinks there's a thin sliver of infill in between there somewhere. |
Beta Was this translation helpful? Give feedback.
-
|
We created a ticket on our backlog for this. Devs see CURA-9058 |
Beta Was this translation helpful? Give feedback.
-
|
Was this supposed to be fixed in 5.0 beta? |
Beta Was this translation helpful? Give feedback.
-
|
Hey @printingotb, Quick update from our side 👋 We are cleaning up our open issues, so we can focus on the most requested and needed features and bug fixes from our community and from UltiMaker, I stumbled upon your issue around the skin removal distance. The behavior will change in Cura 5.5 and look like this: Would you still consider this an issue? |
Beta Was this translation helpful? Give feedback.
-
|
I think this was mainly a bug report to make you aware of it though using these settings has allowed me to improve my prints. With a big reservation that the following only happens when the removal width is significantly larger than the Skin expand distance (3 mm in this case): A reason to increase the removal width is if you are printing something organic shaped with sloped walls, you may get loads of small pieces of internal skin that are not needed and adds to the time and material used. Removing these can be very beneficial and may require a larger value. I believe the behavior is unintended and shouldn't be able to affect the outer top and bottom layers (as Ghostkeeper mentioned above) ) but if you think it's not a big deal and shouldn't be prioritized, I wont argue. Especially since the Removal width seems to need to be much larger than the expansion. |
Beta Was this translation helpful? Give feedback.
-
|
Cant slice any model. Installed cura 4.13.1 and Arachne beta 2. But with the beta i have unexpected erros when slicing a model. |
Beta Was this translation helpful? Give feedback.
-
|
Could you share a project file that reproduces this issue? Most models/settings should work fine. We fixed some crashes since this beta was released though. If it's not yet fixed, that would be a serious issue. |
Beta Was this translation helpful? Give feedback.
-
|
Is there still seam issues? No matter what seam options are selected on a thin walled model, the seam just appears to be totally random
|
Beta Was this translation helpful? Give feedback.
-
|
I'm getting a similar issue, but I want random seams and it's producing output like above. Not random enough in my case. |
Beta Was this translation helpful? Give feedback.
-
|
I don’t want to speculate but Ultimakers marketing emails have been alluding to Arachne engine being released with Cura 5, which is happening today 21/04 4pm CEST |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, we've made a lot of changes and there are also fixes in where the seam is located. But yeah, you might want to check out the event tomorrow at 4pm ;) See: https://ultimaker.com/showcase |
Beta Was this translation helpful? Give feedback.
-
|
Sorry I forget that I’m always ahead of the rest of world! It’s exciting, but I won’t be staying up til I’ll 2am to watch |
Beta Was this translation helpful? Give feedback.
-
|
Depressed but PLEASE put the Z height on preview (it only shows layer #, which starts at "1" whereas the gcode starts at 0!). Also make "Skin" fuzzy, or call it "Fuzzy Wall". I have to upload into o'print and use gcode viewer to figure out where a layer is height-wise. I guess I can do it myself since this is open source, but you know better. |
Beta Was this translation helpful? Give feedback.
-
|
You're posting to a thread which is completely out of date. If you've go new issues, you need to add them as a feature request or a bug report. |
Beta Was this translation helpful? Give feedback.
and others
-
Welcome to the discussion thread of the second beta of Arachne!
Earlier this year, we released the first beta of Ultimaker Cura Arachne engine. Which received an overwhelmingly positive response, thank you for all your feedback!
You are here because you probably want to share some feedback about Arachne engine beta 2! Share your feedback, show your results and/or provide us your input for print profiles for your preferred 3D printer with us here in the comments below.
We really appreciate it if you would follow the following guidelines while posting:
• Read the release notes before posting. Make sure that it isn’t already a known issue.
• Please note the printer you used, as well as any profiles or changes.
• If you need to share a model, please save as a project (file – save project) and attach here as a .zip.
• A picture really does say more than a bunch of words sometimes.
New features:
New settings:
Bug fix highlights:
Known issues:
Download the beta now!
Beta Was this translation helpful? Give feedback.
All reactions