hello everybody,   I am new to 3DC and I am looking for a way to use the voxel tools to repair and cleanup 3d scans. Now, I got a mesh and the problem is, that it has some holes (camera could not look deep enough inside some cracks/holes) Is there a brush or some other tool(s) within 3DC that allow to "just add a thin layer of clay on the backplane" kind of hard to explain, let me try: on the image you can see the backside of my mesh - this was created automatically in Realityscan to make this "watertight": what I want now, is a way to close the hole on this backplate but without filling clay overt to the front and affecting any other "plane" than the backside. Something like the "planar" brush maybe - but not for cutting, instead it should "fill along a defined plane". I tried most brushes, but seems non does this job. Also tried "Fill voids" - but no filling of this either... I would appreciate any ideas and help on how to do this. I am counting on 3DC to become my go-to-app for all scan cleanup stuff and some sculpting... and quick texturing... an maybe (Auto)retopo... Cheers!

hello Carlosan, would it be possible to get a bridge to RS? Like doing the point-cloud and mesh in RS and then start 3DC, do scuplting and then send this back to RS for texture reprojection for example? This would save us to guess the right scale, rotation and location - would be very comfortable! Like import from active RS Project into 3DC - clean up scan - send back to RS with exact coordinates, scale and everything. kind regards

1. I have built 3DCoatTextura for Linux as a Flatpak. Here is the link and instructions below 3DCoat instructions: https://pilgway.com/~sergyi/links-Linux.html 2. I have updated the 3DCoat itself. Now it has access to the external drives. 3. It turned out that the space navigator mouse is not working in the Flatpak app. With Copilot, I have tried a bunch of different options, but none worked. In the end, Copilot said: You cannot make /var/run/spnav.sock visible inside Flatpak - it's blocked by design.

Yes, as you said the only relation between RS and 3DC was importing a mesh into 3DC and do normal sculpting pass. RealityScan and Colmap are used as engines as 3D reconstruction based on images and video. PointCloud import only support .las file format.  At current stage of development it is not as effective as solution found on other apps. To create a 3D model from a point cloud in 3DCoat, you will first need to use another application to generate the mesh from the point cloud. You can use Meshlab to convert the pointcloud .ply format to a 3d tin model.

ok - so we hope for a fix in next version of 3DC, I guess? I think I saw a 2026 beta around... fingers crossed !

realityscan hasnt worked for a while inside 3dcoat , i have to use the actual software outside of 3dcoat  

nope...  RealityScan works on it´s own, yeah - but the tools (in 3DC) do not seem to do anything, besides giving me this msg when importing a ply. I also follwed along the video series you linked, interesting stuff. But the only relation between RS and 3DC was importting a mesh (I think it was fbx) into 3DC and just do normal sculpting pass. I thought with the photogrammetry tool we could calculate the mesh via RS API and get this directly into 3DC or something like a bridge to push the mesh over from one app to the other back´n forth. Or even drag in images into 3DC and under the hood, RS does the math or something like this... but... no

On windows version, when we select the Edge Scatter, 3DC automatically switch to the recently baked NM texture. This is not working as expected, it is a bug * Reported Thanks for point it up

Is RealityScan working now ?

Yes, I have thanks. This crash in this thread is achieved by following different steps than the thread you linked to. See the video for precise steps. Is this crash also related to OpenGL?

So I re-installed RS directly in C: drive and set path to engine. When I import a ply, exported from RS, I still get:    

OK - then I have to re-install RS to my C: Thank you so much for this competent support and very quick replying - this helped me a lot ! best regards

RS only work w/3DC if it is installed on drive C: Check this playlist to see 3DC <> RS full workflow Hope it help

Okee, I can expand it and browse for a ply, las or laz file. Maybe I got this totally wrong, but I was assuming this tools to be kind of a live bridge between RS and 3DC - but I guess, this is not the case. I exported a ply from RS for testing (it seems to just export a sparse point cloud, around 27MB filesize). When I hit "Generate Mesh", I get: and that´s about it.   I also tested with another ply exported from another app - but after hitting "Generatge Mesh" it just flashes quickly and still nothing happens. So I guess, I am using this tool totally wrong. May you can explain, what it is used for and what is the main benefit of using this, instead of staying in RC for mesh generation? Thanks in advance    Edit: Oh - RS is installed on Drive D, not C !

Expand Tool option Parameters, Point Cloud must pick the location of the pointcloud model hmmm... could be perrmissions ? try running 3DC as administrator * RealityScan was installed on dive C:/ ?   if that step isn't working, another option will be to downgrade to Reality Capture and try again.  

Hello Carlosan and thank you very much for this quick hint. So yes, I think this is activated, but the tools seem to be not: I set the path to engine a few times now, but when I click again, it defaults to C: Documents/3dCoat once again... Maybe something wrong with windows permissions? Cheers