If you thought this was simple… lol #FAIL
@Dan_Ghiciulescu you’re free to pool money to make a machine design wizard.
Also, the JSON generator tool (online website) should help a lot already, and does require the start code on a single line.
Anyhow, people will bitch&complain no matter what we do. Always have, always will.
I’m curious about start and stop G-code part. I haven’t used Cura UI or Cura 2, although I looked at a sample Cura 1 profile given to me (for OctoPrint plugin). In the profile, these two parts are written with the ordinary line break convention like the following:
end.gcode = ;End GCode
M104 S0 ;extruder heater off
M140 S0 ;heated bed heater off (if you have it)
G91 ;relative positioning
G1 E-3 F2000 ;retract the filament a bit before lifting the nozzle, to release some of the pressure
;G1 Z+0.5 E-5 X-20 Y-20 F{travel_speed} ;move Z up a bit and retract filament even more
;G28 X0 Y0 ;move X/Y to min endstops, so the head is out of the way
G28
M84 ;steppers off
G90 ;absolute positioning
;{profile_string}
Has this changed?
@whackyhack yes, we rebuild the code base for 2.x, we have actual machine definitions now. Which are written in json files. It solves a whole heap of problems we had in the old code. But makes it currently a bit harder to use the 2.x versions on custom machines.
@Daid_Braam Yup, there are always people bitching and complaining.
But that doesn’t mean they are always wrong, are they?
If I didn’t like you and Ultimaker so much, I would call your reaction quite arrogant. But I won’t. I’ll just use something else to do the slicing (better), and save myself the hassle.
@Rien_Stouten but I AM arrogant 
one of the reasons I managed to make Cura 
But I also see that the current situation isn’t perfect, however, we cannot do everything at once. So work with what we do have…
@Daid_Braam
Okay, fair enough.
It’s not as difficult as the chap in the video makes it seem. That said, it’s pretty trivial to put a json generator in the app to allow for other configs. They didn’t put it in there because the didn’t want to put one in there. Over the last year or so Ultimaker has been focusing the tools on their machines first and foremost. I don’t blame them though.
Its certainly not difficult - But my dayjob is IT, and ive been messing with computers since 1994 
for average John Doe this will be a HUHHHHH?
@Anthony_Martin Those that are using or making DIY machines should be able to edit a Marlin config and flash a board. This isn’t any more difficult than that. Quilford has a generator on his github, you could roll that into the main app and submit a pull request or fork it on your own.
Not at all - I have 3 or 4 printers none of which are in the list - my fault as a consumer?
PS i dont touch CURA usually but im doing a series on slicers and have to test them.
Funny how Simplify3D works fine. and Slic3r. and Craftware
@Anthony_Martin Are you the bloke in the video? The same chap that looked at a list of some well known variants of Reprap/DIY machines and didn’t know what they were.
@Anthony_Martin yes, your fault for not mentioning the 3/4 printers. And/or providing json files for them. As you mention you are in IT and are capable of delivering those files, why don’t we have them yet so that we can include them in our official release? Instead of us breaking in in your home to see what printers you have.
https://github.com/Ultimaker/Cura/tree/master/resources/machines
This list needs to grow.
@Daid_Braam My response to you is just wow.
man I know it’s a Beta but wow. I just tried to load an STL into v2 vs Cura v15.whatever and Cura 2 just kind of stalled and refused to load the layer preview. Combined with ultra slow stl loading and… nope. Will stick with v15.0.x
I think most users that didn’t have an Ultimaker never left v15.04. Where the open slicers are falling behind is in multi head extrusion and manual support editing.
@dstevens_lv multi material extrusion is one of the reasons we decided to re-architecture quite some code. As this is a more complex problem then most people think. But it is next on our plan. Manual support editing is somewhere after that (not exactly planned yet)