UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
Not directly, but something like this can be done. It's a bit cumbersome though.
You can get the face-id of the face under a screen-position with SelectionPass.getFaceIdAtPosition, then work out the intended object, then get the normal from the/that mesh. (For example as happens in SelectionTool._pixelSelection)
As an alternative; if your plugin has it's own stage (like next to Prepare, Preview, Monitor) then I think it becomes an option to write your own RenderPass and shader to get the normal out that way.
if your plugin has it's own stage then I think it becomes an option to write your own RenderPass and shader
You don't need your own stage for that. The SupportEraser adds the picking pass to the Prepare and Preview pass, and OP's plugin could do the same. The problem though is that you can only get 8 bit RGBA values from the pass. Pickingpass uses a shader to encode a 24 bit "greyscale" value in the 3 R,G and B bytes. But for a normal vector, you would really want to have 3 16 bit floats. You could try to encode floats in ints, but you would still need 3 of them, and with a single renderpass you only get 4*8=32 bit maximum.
My still-in-development measuring plugin creates 3 passes to get a more accurate position than what the pickingpass affords. Perhaps OP can have another look there: https://github.com/fieldOfView/Cura-MeasureTool/
Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more.
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
Recommended Posts
rburema 26
Not directly, but something like this can be done. It's a bit cumbersome though.
You can get the face-id of the face under a screen-position with SelectionPass.getFaceIdAtPosition, then work out the intended object, then get the normal from the/that mesh. (For example as happens in SelectionTool._pixelSelection)
As an alternative; if your plugin has it's own stage (like next to Prepare, Preview, Monitor) then I think it becomes an option to write your own RenderPass and shader to get the normal out that way.
Link to post
Share on other sites
ahoeben 1,948
You don't need your own stage for that. The SupportEraser adds the picking pass to the Prepare and Preview pass, and OP's plugin could do the same. The problem though is that you can only get 8 bit RGBA values from the pass. Pickingpass uses a shader to encode a 24 bit "greyscale" value in the 3 R,G and B bytes. But for a normal vector, you would really want to have 3 16 bit floats. You could try to encode floats in ints, but you would still need 3 of them, and with a single renderpass you only get 4*8=32 bit maximum.
My still-in-development measuring plugin creates 3 passes to get a more accurate position than what the pickingpass affords. Perhaps OP can have another look there: https://github.com/fieldOfView/Cura-MeasureTool/
Link to post
Share on other sites
ahoeben 1,948
Alternatively, you could look into using the picking that is provided by Trimesh:
https://trimsh.org/trimesh.ray.ray_triangle.html
Link to post
Share on other sites