nallath

I just loaded a 1116mb file (7 mil verts) and I get a bunch of lag when sending the model to the slice engine. I'll have a look into that. It seems the new cura crashes when the object is too large (eg; it even refuses to send the message to the engine as the message is too big). This is not handled properly which blocks everything.

I don't have the issue with a 20 MB stl model. There I can simply ignore the slicing process and change the camera / settings whatever. This pc only has those shitty onboard intel graphic cards aswell, so thats not the issue either. 20 mb of data (a little over 1.3 million polygons!) doesn't have this effect, so i'm pretty sure its another issue. An issue that I want to fix, not hide behind a checkbox. **edit** Even with 80 mb of data (so about 5 million polygons) I was still able to change settings without any issues. The view did start to slow down a bit, but this also happened when the slicing was disabled. I could not find a significant decrease in performance.

I dunno. It was a while ago (3+ months)

I don't know which version they are using. If they are using 15.06> it should work. They dont communicate with us :(

Yep, latetst build is 15.09.81

We're already aware of the fact that the touching buildplate support option is broken.

I love rafts! The people who use the UM for a while hate them, because they used to be very bad. At a certain point we *ahum* "stole" the settings from some other not to be named printer manufacturer which improved them a lot.

http://software.ultimaker.com/Cura_closed_beta/15.10/

I just tried it with the 15.10 branch (which includes changes that are not in 15.09.81 yet) and it works correctly there. It also shows support correctly.

Writing to an SD card is dangerous, especially when there is a chance of random power surges. If you're writing to an SD card and the power drops, there is a chance that you ruin the entire card.

It should be doing the firmware updates, but i don't think we've added a upload custom firmware button (yet). The build time should be calculated (and thus updated) automagically.

15.04 has it automatically. The 15.04 doesn't have a plugin system as extensive as 15.06>

You can find the beta at http://software.ultimaker.com/Cura_closed_beta/15.10/

I might sometimes come across somewhat jaded with regards to adding new features. This has a lot to do with the fact that a lot of people mistake open source for "If I want a feature, you must make it". It's a lot less than it used to be, but the 20th time someone does this, you tend to get a bit blunt in your responses (Note that it's not an excuse, its a reason. You're right to notify me, or any of us, if this happens). We're not against adding features suggested by the community (have a look at the github, we've included a lot of features that were suggested by you guys), but we like to see better arguments than "But my work flow requires this" or "I think this is nice". I want to know -why- you think this is nice or why a certain workflow would be better (or even better; state a problem and spar with us on how to improve this instead of pushing a single 'solution').

The usb print plugin is packaged with Cura by default. The new version of cura should be perfectly capable of generating g-code. If not, file bug reports so we can fix it.

We gave you an answer? You need to put the plugin with the other plugins in the plugin folder. If it's not recognised, post the log file. With the little information you give, I can't help you any further.

I'm not aware of such plans. Yeah we did. But it's a lot of work to get right. We're already over our ears in work with everything, so something like this won't get a high priority. There are marlin firmware builders out there that work pretty good.

The same is also said of audio design in games. If someone finds it good they don't notice it, but if they find it bad, all hell breaks loose. I've used cura back in the day where the auto slicing wasn't an option yet (you had to press the slice button every time), which was fairly annoying. I think the current problem with the auto slicing is that the message pops up and pops down again, which is quite distracting. For all the developers shouting that they want this feature, I've yet to see a pull request. We're considering adding an energy saving mode which disables auto slicing, but due to the feature freeze we're in at the moment, it won't be added until the 16.01 release. I don't think this has anything to do with bravery so i don't quite understand what that has anything to do with this discussion.

I have no idea. I'm not aware of any changes in that area, but it could be some settings were mixed in the engine. Whoops, that's my bad. I added the keyboard controls because someone requested it for notepads, but forgot that layer view also reacts with keyboard presses.

It seems like your system font is wrong.

Cura does not have a debug mode as such. You can find more info on logging & issues on https://github.com/Ultimaker/Cura#logging-issues

We do want people testing the new version, else it will never get out of beta

Could you post the log files?

That's a nice bug. @sybold at what OS did you get this? The mac version is also up now.

https://github.com/nallath/BarbarianPlugin