ahoeben

Ultimaker has no interest in supporting USB printing. So if it does not work you will have to use something else untill someone from the community or eg your printer manufacturer steps in and fixes it.

I feel it would become a support nightmare. Many reports don’t even spell “Cura” properly, let alone the version number. Having daily builds only complicates that.

I meant in the sidebar, not in the setting visibility dialog. But that might not work (not sure). What may work is using the Per Model Settings tool, go to Add Settings, and tick the "Show All" and use the search in that dialog.

Use the search field to find the "Drop Down Support Mesh" setting and turn it off.

You add the files you want to be added in the correct location inside your own branch.

Have you tried the similar menu next to the "Search..." box in the sidebar? Does that work better?

Scroll down to the BETA section, all the way on the bottom of the page @smartavionics linked to.

Yes, sofar this looks correct

Does the external reader have drive letters associated with it? What happens when you disconnect the reader? Not as a solution, but as a step in troubleshooting.

You run Cura as Administrator. Bad, bad, not good.

What makes you think Cura tries to do that? It doesn't. Never did.

I'm sorry, I did not actually test this with Cura 3.5. I have edited the opening post to reflect that. The plugin is 3.6 and 4.0 only (for now)

The important thing here is that your model is concave, and the polygon around the model is convex. Doing intersection-calculations on concave is much harder, more computationally intensive, thus takes longer, than doing the same with only convex polygons.

What I think he meant, sort-of tongue in cheek, was that I somehow disable my plugin on computers at ultimaker hq, force-dog-feeding the 4.0 interface to Cura developers. I can appreciate the joke.

I would very much appreciate it if the Marketplace could keep serving older versions of my plugins for older versions of Cura. If not, I would still have to test new versions of my plugins with the older versions. Take the OctoPrint Connection plugin as an example. Due to changes in Cura, there has only been one recent release (3.5 -> 3.6) where the plugin did not need minor or major changes to work with the next version, in a way that broke it for the previous version. If the version I released for Cura 2.7 would still be available in the 2.7 plugin browser, it would still work. But there's no way I'm going to be able to make a version that works correctly in Cura 2.7 and Cura 4.0.

I’m going to need a screenshot, with the Per Model Settings panel showing what you changed.

You mean "pay particular attention to faces that are light-blueish versus white/grey". Right?

Plugins that are downloaded via the Marketplace/Toolbox are not installed in the Program Files folder, but in the configuration folder. See Help -> Show configuration folder, and then open the folder named "plugins"

Miyagi father says: First learn stand, then learn fly. If your printhead has the hole for the seocnd extruder, the motherboard likely has the second driver chip. But you also likely have an Ultimaker 2, not an Ultimaker 2+. The original plans for the Ultimaker 2 dual extrusion kit fell through because printing with two fixed nozzles is hard to do right. The second nozzle will be rubbing or scratching over the print while printing with the first nozzle, with a decent chance of knocking parts of the print off the buildplate. Any material stuck to either nozzle will smudge into the print. It just does not work very well.

The current stable version is Cura 3.6. Cura 4.0 is only available in beta. Plugins need to be adapted for Cura 4.0. In the past few weeks it has become apparent that plugins currently can only be available in the Toolbox/Marketplace for one Cura version at a time. Most plugins are available for Cura 3.6

It looks like when a new version of a plugin is published, the previous version of the plugin is removed. So when a version of OctoPrintPlugin was published for Cura 3.6, the version for Cura 3.4 became unavailable. I will see if I can make it available through other means than the Toolbox (it is called Toolbox in Cura 3.4, right, or was it still the Plugin Browser?)

I accept your gratitude 😉

Cura 3.3 introduced the concept of setting visibility presets: When I implemented that menu, I always meant to follow up with a way to add custom presets. I never got round to doing that. As a stop-gap measure, here's a plugin that will let you save your current set of visible settings in a preset: For Cura 3.6: http://files.fieldofview.com/cura/SettingVisibilityProfileCreator-v5.0.0-2019-01-12T13_50_55Z.curapackage For Cura 4.0: http://files.fieldofview.com/cura/SettingVisibilityProfileCreator-v6.0.0-2019-01-12T13_50_26Z.curapackage After downloading the file for your Cura version, drop it into a running Cura window. Then restart Cura. The functionality of creating a new set can be found in the "Extenions" menu.under "Setting Visibility Sets". Selecting "Store Custom Setting Visibility Set", you currently visible settings will be stored into a new preset. In this first version it is not possible to edit a preset, but you can overwrite a previously stored preset. It would be better if functionality would be available in the setting visibility hamburger menu, but that cannot be done with a plugin without a lot dirty tricks. Ideally the functionality of this plugin will be moved into Cura itself, but that will not be added before Cura 4.1, and by making it a plugin I could make it available for Cura 3.6 and newer.

What you did not mention was that the error does NOT say "There is No Disk in Drive D" or "There is No Disk in Drive X". Windows wants a disc inserted into \Device\Harddisk11\DR11. For future reference, omitting that detail makes it harder to help you. First step is trying to find out what drive \Device\Harddisk11\DR11 is. What sort of drives do you have connected to your computer, including cardreaders, optical drives. and usb (hard)drives? Also, what version of Windows do you use?

Just drop the curapackage into the Cura window. I think you can also use File -> Open, but never tried that.