nallath

Huh? All Cura versions suport non-ultimaker machines, even 15.06.x (but no-one made a profile for the rigid bot yet).

You could have found this if you googled it

Judging by the anvil in the background and the red boxes that say something about steel, I'm going to go with "The stuff you get from milling brass, a bit like chippings / sawdust from woodworking"

So yeah, this slipped through. Sorry bout that. The new Cura does not quite handle things in the same way the old one does. The old one actually parsed g-code to show the layer view. The new version gets polygons from the engine which it uses to display the layers. If I remember correctly we haven't implemented the infill part of this yet. It should print, so I have no idea where that is from. Post an issue on Github so we can assign it and attempt to fix it.

I can't (and won't) keep track of everything that's in the forum (because I can't guarantee that a topic won't slip through, like yours did), especially not stuff like bugs. A forum is simply not suited for issue handling, so we use the Github issue tracker for that (To which Cura should point you if you have a crash) I see the forum as a great place to discuss why things aren't working but not as a good place to keep track of the issue (and the fix, if any). Tagging me will greatly increase the chances of me reading it, as I get notifications.

15.04 works. I'm pretty sure that it does. I don't have experience with the other software. Is the error also in the (just released) 15.04.03 version?

Cura 15.04 is a stable version of Cura. Cura 15.06 is a new re-worked version of Cura and therefore not nearly as stable as the old 15.04.

All right I've added a pause at height script to it as well. Now it actually does something

Ugh. It was the dot mistake again. It added the dot to the link. Fixed it now. Also @dim3nsioneer I believe you were waiting for this plugin

A quick update for those of you who want the tweak at z, pause at height and others back. I've been working on a plugin that allows for the loading & execution of such scripts. The layout is still rubbish, localisation doesn't work correctly and it hasn't been fully tested, but I still want to share this with you guys. You can find the plugin here; https://github.com/nallath/PostProcessingPlugin . See this as an early alpha / beta. If you want to make your own script, have a look at the examplescript (that does nothing) that is in the scripts folder. The plugin should automatically load all scripts that it finds in that folder.

We don't have a hardcoded limit, but dear god 500 mb is a lot of verts. Most computers will choke on that even if it loaded. The windows version is 32 bit (for 15.04), so that will limit the memoery that can be used. Mac and linux don't have that problem.

https://github.com/nallath/PrintCostCalculator There ya go! I've made a plugin that does exactly what you need.

You are going to be hard pressed to find a software engineer that isn't fluent in English in the Netherlands

Github only. New features are on the master branch. Fixes are on the 15.06 branch.

I don't know. I've never seen it before, so its probably caused by something in your system. Could be because of the hack, could be because of other system settings. Yeah. This is caused because we do a bit of a nasty; we use a development version of protobuf. We needed features from protobuf 3, which is in late development. This problem should go away with time though. If you have any questions or want to help more with Cura, feel free to drop me a message.

Agreed. Next version will be in open beta before we release it. Keep an eye out on the forum, we will post it there. There already are a number of (contributed) printer profiles.

We're working on it. Not more than already provided. The description should provide a lot, together with the settings class, but that would require that you know python.

We do fix things when people mention it

The json file is not meant for normal users to change, but a lot of people here aren't normal users. They are the kind of people that tweak these kind of things. These people have touched those files and will continue to do so. The main design principle of cura is that the first use should be simple, but that we will not prevent a user from doing the really weird stuff. We want to give the people the ability to pull open the hood and change everything. If you don't do that, thats fine, but the posibility is there. The reason why its not there is time. There will be one in the future. Someone already made a web page that spits out the JSON files that Cura needs.

Nice writeup. Sorry we couldn't spend more time on fixing this ourselves but we're stretched thin enough as it is. Glad to see that you were able to fix it!

Actually, it does have the prusa profile. Its just not in the current version yet. You can find the profile here; https://github.com/Ultimaker/Cura/blob/master/resources/settings/prusai3.json

Please post issues about Cura on the github issue tracker. Its okay to double post them if you want to discuss this with people (It's a good way to get quick responses) but it's impossible for us to keep track of issues on the forum.

It works just fine for me. Don't use the direct links, use this list: https://ultimaker.com/en/cura-software/list

All right, there seems to be a bit of uncertainty what the .json files actually do. Let me explain that a bit more. The settings are hierarchical in nature. Lets have a look at a setting like "line_width". As you can see it has a "children" option, which contain the settings "wall_line_width", "skirt_line_width", "skin_line_width","infill_line_width","support_line_width" and "support_roof_line_width". Each of the children setting will inherit their value from their parent ("wall_line_width") if they are not enabled / visible. This is to ensure that users who don't want to tweak stuff only have to change one setting. If you make "skin_line_width" visible and change it, it overrides the value of "wall_line_width" for that specific setting (all other children still inherit!). If all children of a setting are visible, the setting becomes invisible as it no longer does anything. We also have something called an "inherit_function". You can put a python script there which should return a value. This is useful for values that need to be calculated based on other settings (eg; "wall_line_count"). Setting files can also be inherited, which you can see if you look at the ultimaker2.json, which inherits fdmprinter.json. This was done to even allow printers that dont use FDM (or even non printer machines. Uranium would be suited for CNC mills / laser cutters aswell)

Ultimaker crew to the rescue! I've seen this bug before, but i'm not sure if anyone reported it on the github. Could you post it on https://github.com/Ultimaker/CuraEngine/issues? Then one of our engineers will have a look at it. I'm not aware of a quickfix at this moment.