When I open 3D Coat the workspace is always as I left it the last work session, but if I try to open a project or start a new one, it reverts to the default workspace. I tried to reset defaults, restore Windows, uninstall and reinstall 3D Coat, boot it as administrator, uncheck and check Store Window State but nothing works and each time I have to Windows->Restore Workspace. It's not a big issue, but it's a bit annoying to have to fix the workspace everytime I open the software. How do I fix it?

Thanks for the tip. I just wanted to share my experience and I was pleasantly surprised by 3DCoat's Auto-Retopo result, without any tweaking (although I did later do some tests with Stroke guides because it was a tool that was available in 3DCoat and thus it would be fair to use it and compare with Quad Remesher's best result). I did acknowledge that Quad Remesher is probably more strict with its Hard Edge detection and forces edgeloops to stick to those edges better than 3DCoat. That makes it a better option for Hard Surfaces than 3DCoat's. However, for organic meshes, I find that 3DCoat's AutoRetopo often delivers results that exceed my expectations and are surprisingly good. As you can see from the comparison screen captures, 3DCoat performed as well...if not better...than Quad Remesher, in this example. 3DCoat's Auto-Retopo is the 1st image, in green, while Quad Remesher is the 2nd image, in orange. With some stroke guides, I think the 3DCoat result would be improved.

Try turning ON Autosnap in the upper middle viewport

Sure thing. Sorry for the late response  https://drive.google.com/file/d/1p7U91AvuOTVLWYc12LI1-VwBga892zW9/view?usp=share_link

Just found, that you do have the option to not overwrite the current mesh, but use a duplicate and hide the input mesh automatically. So is is possible for Exoside Quadremesher to behave like Coat in that regard by simply ticking this checkbox:  

Specifically nothing snaps to the sculpt . It starts ok but then the strip floats somewhere in 3D space. Is there maybe another setting Im not looking at?Im on the latest  Mac OS Tahoe  and 3DCoat version 2025.11

Yep that worked fine, thank you 

I frequently exchange meshes between 3D Coat and Blender to use the Exoside Quadremsher. I don't find 3D Coat Autopo to be a decent replacement for ZRemesher (which is what Exoside Quadremesher is, it is the same algo by the same author). Autopo in Coat can be good for organics, but as soon as you have to e.g., quickly autopo a belt or something more hard surface'y, it can be difficult to work efficiently. I think it is safe to say that 3D Coat still would need a decent Autopo like ZRemesher/QuadRemesher. I come from Zbrush, and I never had to think about the quality of my quickly zremeshed meshes much during the process of modeling and re-projecting. In 3D Coat, when using the Multi Res workflow on pieces, I often have to bring my meshes to Blender to Exoside Quad Remesh them, and then back. Even tho I love the bridge and it works flawlessly for me, it costs precious wok time. So for me, I would def also welcome and pay for an integration. Although I admire your passion for 3D Coat @AbnRanger and I often think you are right with a lot of points, in this I find it hard to agree that 3D Coats Autopo is just as good. This is not my experience.   The other annoying thing I noticed about Quad Mesher is that it sort of replaces the high poly mesh instead of building the low poly retopo mesh on top of it. This is just how it is supposed to work. It is a RE-mesher, not a Re-topoer. 3D Coat does it this way yes, but it is not what is needed during the modeling phase, where you often just need a quick fresh mesh to re-project onto. If one doesn't want a mesh directly to be remeshed, one can simply hit Shift+D to duplicate it prior to the remeshing. I find there to be little "annyoing" about that pluging or ZRemesher. I find 3D Coat Autopo to have much more annoying aspects. I think as passion users, we also need to stay real at some points and not try to shift truth around to make 3d coat more flawless seeming. I think this would help the software much more. Also, with Exoside Quadremsher in Blender, you do have the option to use material ids quickly created from facesets to replace the Curve Guide functionality. It works reasonably well. You can more or less imitate curve guides with this in the latest versions this way. Of course, if 3D Coat would integrate Exoside, a curve functionality would be welcome and necessary I think. 

I recently did a fair one to one comparison of the QuadMesher addon, using the Black Rhino from Rygaard as the high poly mesh (about 10mill polys) and to be very frank, I was surprised that 3DCoat did as good of a job Auto-Retopologizing the Rhino as QuadMesher. Even better in the eye region where the QuadMesher addon just kind of ignored the circular/oval shapes of the eye and socket surrounding it. 3DCoat did too, but at least with 3DCoat, I have the option to use stroke guides to correct that. QuadMesher doesn't, and I was very surprised about that. You almost need that feature sometimes. The other annoying thing I noticed about Quad Mesher is that it sort of replaces the high poly mesh instead of building the low poly retopo mesh on top of it. At least I could not figure out how to unhide the original high poly mesh. It's like grayed out in the outliner to where you cannot unhide it. I think the Quad Remesher does apply Edgeloops along hard edges more strictly than 3DCoat's Auto-Retopo toolset, though. So, in total, as a Blender user, you would need to buy this plugin, plus one or two manual Retopo addons to try to replace 3DCoat's Retopo toolset.

Try exporting without subpatches & turning on Use Source Position   I have imported the lwo into Blender, but cant find any issue  

Hello Try downloading a previous version from here https://d345hrihx5j0zk.cloudfront.net/3DCoatTextura-2025-11.exe

Hi   I have just downloaded the latest 3D Coat Textura on a trial but the menus at the top seem to be missing. Have tried deleting the "custom rooms" and "rooms" folder as suggested by similar problems with earlier versions but no joy.   Am running the latest 2025.12 version.