Daid

It's easier to replace the 5 unused spots, else you need to dive into the glButton code to account for the changed texture size.

The problem is actually that the sample rate it too low. I spend the last week doing some tests on this and improving it, the latest git version is better at getting at stable temperatures now.

Problems with that are: A: Models are not manifold, causing your inside/outside BSP tree to fail. B: It takes more time to calculate your BSP tree then you are actually using it. (Especially on a high poly model, this can be expensive) Instead of slicing planes with the model. I slice the triangles with a list of planes (which have a fixed distance). This is pretty quick, and only has the disadvantage it uses quite a lot of memory. https://github.com/Ultimaker/CuraEngine/blob/PinkUnicorn/src/slicer.cpp#L321 Which gives 2D lines on every slice plane, for each triangle.

Just wondering, why are you selling it? (Just curious why some people buy a 3D printer and sell it later when it has seen little use)

I think this mixes a few things up. I started on the CuraEngine while I was already working for UM. Before that, I did work on my own Java version, which never really worked. Also, no idea why you would want to build an BSP tree... Cura builds a connected mesh, and uses a hash-map of the vertex positions to speed this up: https://github.com/Ultimaker/CuraEngine/blob/PinkUnicorn/src/mesh.cpp#L14

Think I fixed it for the next RC.

As for speeding up Cura, people might notice that the latest Beta is up to 40% faster on large objects, due to some optimizations in the infill code. http://software.ultimaker.com/Cura_closed_beta/

Uploaded RC4 to: http://software.ultimaker.com/Cura_closed_beta/ This has the latest German translation for you guys to check. I've also got a few reports about support material not working on the german translated version, does anyone have this problem as well?

It has the same firmware as 14.09, so no update required.

Nope, that's not the same problem. I'm seeing some top/bottom infill parts in there where it is moving to, but nothing else. And I assume 14.07 will show exactly the same results with the same settings.

Warranty won't void. But if you have a problem which is clearly caused by the other filament, then that's at your own risk. Blocked nozzle for example with 3th party wood fill or PVA, that's not covered under warranty. In general, just use common sense :-)

And, the printing time/filament use also isn't translated. Just updated everything that I could find that had missing things. And I forgot to update the po files to contain some translations, so I have new files now. But those don't contain the changes done in the above download yet.

It deforms under stress. So, in your case, it will most likely deform. I would recommend ABS, Nylon or ColorFabbTX

Yes, should be easy to fix. I'll put it on my list.

These are the main firmware links for the Ultimaker printers. Ultimaker Original (Green electronics, Arduino) https://github.com/Ultimaker/Marlin/ Ultimaker Original with Heated Bed Upgrade KIT (Green electronics, Arduino) https://github.com/Ultimaker/Marlin/tree/Marlin_UM_HeatedBedUpgrade Ultimaker Original PLUS (White electronics) https://github.com/Ultimaker/Marlin/tree/Marlin_UM_Original_Plus Ultimaker 2 (White electronics) https://github.com/Ultimaker/Ultimaker2Marlin All these firmwares can be build with the Arduino environment from http://arduino.cc/en/Main/Software Ultimaker 2 - Building problems! Note that to build the Ultimaker2 firmware you will have to make an adjustment to the Arduino environment, or else you will get an error. The file at "C:\arduino-1.0.3\libraries\Wire\utility" called "twi.c", open it in wordpad or any other text editor (except for windows notepad). And search for the line that starts with "SIGNAL(TWI_vect)". Remove this line and everything below it. You might want to keep a backup of this file, or install a seperate Arduino environment for the Ultimaker 2 if you use the Arduino environment for anything other then building Ultimaker firmware. (This change does not conflict with the Ultimaker original firmware) Origin The Marlin firmware is based of the work of countless people. The "main" marlin version which is used as base for every other Marlin firmware can be found at: https://github.com/ErikZalm/Marlin/ Online Marlin Builder An online tool for building slightly customized firmwares has been made. This saves you fiddling with the Arduino environment if you just want to change a minor option. Cura can upload the resulting hex file to your printer. http://marlinbuilder.robotfuzz.com/ Final note of warning While it should be quite safe to test around with custom build firmwares, there are protections in the firmware to prevent problems with the hotend melting itself. Installing customized firmware is at your own risk.

Uhm. Don't know? The current translation was done by iGo3D I think. Not sure what type of german they picked.

(Cura)ultimakers-Mac-mini:~ ultimaker$ pip freeze -e git://github.com/GreatFruitOmsk/Power.git@2cfe611348d84512a1590840a7e0d24bec1 d1d93#egg=Power-dev PyOpenGL==3.0.2 altgraph==0.10.1 macholib==1.5 modulegraph==0.10.2 numpy==1.6.2 py2app==0.7.2 pyobjc-core==2.5.0b1 pyobjc-framework-Accounts==2.5.0b1 pyobjc-framework-AddressBook==2.5.0b1 pyobjc-framework-AppleScriptKit==2.5.0b1 pyobjc-framework-AppleScriptObjC==2.5.0b1 pyobjc-framework-Automator==2.5.0b1 pyobjc-framework-CFNetwork==2.5.0b1 pyobjc-framework-CalendarStore==2.5.0b1 pyobjc-framework-Cocoa==2.5.0b1 pyobjc-framework-Collaboration==2.5.0b1 pyobjc-framework-CoreData==2.5.0b1 pyobjc-framework-CoreLocation==2.5.0b1 pyobjc-framework-CoreText==2.5.0b1 pyobjc-framework-DictionaryServices==2.5.0b1 pyobjc-framework-EventKit==2.5.0b1 pyobjc-framework-ExceptionHandling==2.5.0b1 pyobjc-framework-FSEvents==2.5.0b1 pyobjc-framework-InputMethodKit==2.5.0b1 pyobjc-framework-InstallerPlugins==2.5.0b1 pyobjc-framework-InstantMessage==2.5.0b1 pyobjc-framework-LatentSemanticMapping==2.5.0b1 pyobjc-framework-LaunchServices==2.5.0b1 pyobjc-framework-Message==2.5.0b1 pyobjc-framework-OpenDirectory==2.5.0b1 pyobjc-framework-PreferencePanes==2.5.0b1 pyobjc-framework-PubSub==2.5.0b1 pyobjc-framework-QTKit==2.5.0b1 pyobjc-framework-Quartz==2.5.0b1 pyobjc-framework-ScreenSaver==2.5.0b1 pyobjc-framework-ScriptingBridge==2.5.0b1 pyobjc-framework-SearchKit==2.5.0b1 pyobjc-framework-ServerNotification==2.5.0b1 pyobjc-framework-ServiceManagement==2.5.0b1 pyobjc-framework-Social==2.5.0b1 pyobjc-framework-SyncServices==2.5.0b1 pyobjc-framework-SystemConfiguration==2.5.0b1 pyobjc-framework-WebKit==2.5.0b1 pyserial==2.6 wsgiref==0.1.2 wxPython==2.9.4.0

You can try the latest test version I uploaded today: http://software.ultimaker.com/Cura_closed_beta/ I changed a bit on how the bootloader reset routine works, which should make it a bit more reliable.

Gives a "list is not a command" as reply. ultimakers-Mac-mini:~ ultimaker$ pip list Usage: pip COMMAND [OPTIONS] No command by the name pip list (maybe you meant "pip install list")

Ok, working on 2 things right now. 1) Fixing the problems with "Timeout" happening on firmware install. 2) Making sure you cannot install an UMO+/UM2 firmware on an UMO and UMO firmware on an UMO+/UM2

Any idea how to list that? I've packed up and stored my virtual environment at: http://software.ultimaker.com/virtualenv.tgz Maybe that helps?

Ah, yes, time flies... Good to hear the main problem is fixed. And yes, the travel on top infill areas is a bit "random" and hard to predict. So you are more lucky that you get a single travel instead of it being a feature.

The changes for this introduced a bug with the infill code, causing lots of unneeded travels. Just fixed that problem and will build a version for you guys to test ASAP. EDIT: http://software.ultimaker.com/Cura_closed_beta/ Windows right now, will build&upload mac&linux a bit later. (machine that builds that is still in the old building, so need to move that first before I can build the mac and linux versions)

For updating the translations, you want poedit: http://poedit.net/ This is an editing suite for the language files. Next, you want to edit the language files. These are .po files in side of Cura. In the windows version they are at Cura/resources/locale On MacOS, you need to open the package contents (right click, show contents) and find the .po files there in the resources. With poedit you can edit these files, and update the translation. While you could update the po files trough git, that's complex, you can also email me the updated file, at d.braam@ultimaker.com As for parts that miss translation, could be 3 things, could be that in the po file there is no translation made. Could be that it's not in the po file, but that it's properly marked in the code for translating. Or, it could be that it's not marked for translation at all. Best would be to tell/show screenshot for these parts, so I can figure out which of these 3 it is.

I'm skeptical about everything till I see it and can use it. So far, all they have to show, is a logo and a lot of marketing talk.