Cuq

You can't do that on Cura. Cura is very limited compare to PrusaSlicer or SuperSlicer on the Per Model modification and in general on model parameter customisation. So SuperSlicer (or Prusa ) would be a good choice.

Oui pardon je pensais que c'était connu et j'oublie que c'est pas une évidence pour tout le monde, désolé . La 4.20 est la version développé par Mark Burton Aka Smartavionics ou @burtoogle sur ce Forum, C'est aussi lui qui fait le plugin pour les SpaceMouse. Tu trouveras ses versions et la dernière ici : https://github.com/smartavionics/Cura/releases/tag/4.20.3 Pour l'ensemble des différences tu peux lire le ReadMe avant ( En anglais seulement ) : https://github.com/smartavionics/Cura/releases/download/4.20.3/README.pdf

Oui le problème du pontage n'est pas lié à la version 5.X il existait déjà en 4. Et Malheureusement je pense que ces options ne seront jamais intégrées par Ultimaker. La 4.20 intègre une soixantaine de paramètres supplémentaires par rapport à ta 4.12 et il y en a toujours un ou deux qui sont intéressants , donc quitte a en garder une sur son poste autant virer la 4.12 et installer celle là. ( Enfin c'est mon avis) [EDIT] Oui ca marche dans toutes les orientations pour la direction du pont. Version Cura 5.X Version Cura 4.20

Bel Exemple de pourquoi ma version de base est toujours la 4.20 .. 5.X C'est bien si tu as "besoin" du nouveau moteur d'Arachne mais pour le reste ca reste plus rapide et plus "stable" . En version 4.20 la direction est correcte. Note : La 4.20 te permet aussi d'activer l'option "Bridge over support" et plein d'autres options qui permettent de diminuer le recours au support. Comme le "Remove Holes Above Air" qui va ignorer le contour des trous sur le premier layer non supporté. Ainsi tu as juste à ouvrir le passage après l'impression avec un foret ou au cutter et tu gagnes beaucoup en besoin de support.

That's the Prime Tower Prime Tower Activated And Certainly the Brim/Skirt set to Extruder 2 and Part Extruder 1 something like that

Yes, normal M221 instruction as well as M220 are not reconized by the GCode reader of Cura. If you want to get a vizualisation of your Gcode you can use the GCodeViewer of SuperSlicer

Set the adhesion type to none

In the color scheme, perhaps have you uncheck the extruder option ?

Stange to use the RepRap Flavor to output the Gcode for a CR10 as well to not use any initialisation Start and End Gcode ? Any reason for that ?

You can try the profile analyser plugin to analyse in your current configuration where is set the output values. Or solution number 2 : I don't need to use the material values and create a profile adapted to each material.

Prusaslicer, superslicer, ideamaker, IceSl... so many other free software.

In this case it's the tooltips of the Settings Guide. And yes in this case in the option of the plugin you can desactivate it

Do you have installed the calibration plugin ?

In a simple way and accessible to everyone: no 🤔

Yes because your "New machine profile" is just a modification of the initial machine and the "Filter" is done on the initial machine. More explanation on how the stacked profile system works by @nallath : https://github.com/Ultimaker/Cura/wiki/Profiles-&-Settings Your new machine profile is considered in this case as a definition-changes container : https://github.com/Ultimaker/Cura/wiki/Profiles-&-Settings#definition-changes

It seems difficult to implement, the only "filter" on the profiles is related to the machine. It would probably be possible to have a plugin that would do this, something like the Startup Optimiser plugin from @fieldOfView but it seems complicated for a limited number of users in the end.

I had the same issue 😉 https://github.com/fieldOfView/Cura-MeshTools/issues/26

Mesh tool plugin installed ?

It's not an issue due to your OS but to the hardware. Probable origin of the problem : It's not the same Computer and on this one the graphics card is not compatible OpenGL It's the same computer and in this case the driver of your graphics card is not compatible. In this case you can perhaps solved the problem with a new driver but the chances of solving the problem are often small.

Are you sure ? In the lay flat by face it's the Selection.getSelectedFace() method instead ? This method works fine but I cannot use it to get also the selected point .

You are in mode print : One at a time. What's why you have this message ( and the Huge black rectangle) notice by @gr5

Hello, I'm trying to use the getFaceIdAtPosition function to get information about the existing face under the mouse clicked position. By specifying the mouse click position (event.x, event.y), the success rate on the return of a face ID is quite low. I often get the value -1 as a result and I am forced to zoom in to get a better return. Is there a way to improve the success rate of the return of this function ? Note : I'm also using getIdAtPosition , with this function the result is always correct.

Mesh Fixes -> Remove All Holes

The principle is validated, it works. Sometimes of course depending the shape of the part "the longest" border is not necessary the right "main" orientation . But it works as intended .