Oh, one question about new Splitter tool - will this eventually work with symmetry? That would be cool.

Hello, I am testing the Linux Flatpak release of 3DCoat 2026.11 on PikaOS GNOME 49.4 Wayland with an AMD Radeon RX 9070 XT. I found two separate issues. Space Navigator / 3Dconnexion 3DCoat initially reported: Space Navigator daemon for 3dconnexion devices: NOT found even though: spacenavd was installed spacenavd.service was running spnavcfg detected the device correctly 3DCoat 2025 native Linux version worked correctly The problem was Flatpak sandbox access. Adding: flatpak override --user \ --filesystem=/run/spnav.sock \ com.pilgway.coat fixed it immediately. After this change: Space Navigator daemon for 3dconnexion devices: FOUND The 3Dconnexion Space Navigator works normally. AMD RX 9070 XT performance problem Unfortunately, the GPU performance of 3DCoat 2026 Flatpak is unusable. The same scene: 3DCoat 2025 native Linux: ~145 FPS 3DCoat 2026 Flatpak: ~3 FPS The host system correctly uses the GPU: AMD Radeon RX 9070 XT radeonsi gfx1201 However, inside the Flatpak: Runtime: org.freedesktop.Platform/x86_64/22.08 The AMD Mesa driver is missing: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Only: intel-vaapi-driver is present. The application logs: MESA-LOADER: failed to open radeonsi failed to load driver: radeonsi Could somebody with an RDNA4 AMD GPU confirm this? Possible questions for developers: Will the Flatpak runtime be updated? Is 3DCoat 2026 expected to support newer Mesa versions? Is there a recommended workaround for RX 9000 series GPUs? System: PikaOS GNOME 49.4 Wayland AMD Radeon RX 9070 XT Mesa 26.1.4 host Flatpak runtime 22.08 I am currently running the native Linux version of 3DCoat 2025 on the same system without any problems. The only workaround I needed was to provide Python 3.10, since PikaOS ships with a newer Python version. Thanks!

Maybe that is not the right place, but I need to figure out something. Right now, I'm mostly using version 2025.17 and sometimes I need quick UV maps, so here is a scenario - I have multiple objects in Retopo Room, all but one are hidden. I will work(mark seams) on selected//visible object, but when I hit Unwrap, 3DCoat will unwrap all objects, absolutely ignoring the fact that all the other objects are hidden/not selected. That's a bug, right?

Hi, Just an FYI I have been testing workflows in 3DCoat for texturing 8K terrains....regarding the performance of 3DCoat2026-12 on my older system with a 2080ti GPU....I've uninstalled it and reverted back to 3DCoat2024-13. It seems to handle things much better. I'll be testing 2025-17 tomorrow.... I could not see or feel any performance improvements with 3DC2026

api bug with scaling objects: """ On a mirrored instance (negative-scale / flipped transform): Object has a negative determinant / reflected axis in the matrix. GetScaling() returns positive components only. SetScaling(GetScaling() * k) (or any SetScaling with those values) drops the mirror and/or corrupts the intended transform, while editing the 3×3 directly by k preserves the flip. """ basically, if you try to use the api builtins to set scale half and set scale double, it will corrupt the matrices, ignore the scale sign, and return mangled transforms. Expected behavior is that a round trip scale 0.5 and scale 2x restores original object scale / position including instance flips

Good to know. Thanks. My UV is packed so tight it would be difficult to separate the offending faces. I will wait for an official fix and work in 2024 for now. 

Edit > Relocate 3DCoat's Data is available in your version ?

Is the user folder saved somewhere different than 2025 on Mac? My 2025 install (and all others) creates a 3DCoat folder in my documents. 2026 did the same, but is extremely small. Usually the folder is about 15GB, 2026.11 is 579MB.   Also can I still migrate my 2025 Alphas/Smart Materials to 2026.

Awesome. Thank you. Although, I could have sworn when I tried selecting things in the UV Preview window, it wouldn't select anything. Or just everything instead of individual shells. But that's sorted it. 

@DustyShinigamiYou can do this in the UV preview window. Click on the UV island and delete it. 

Hi. How exactly can you select a specific coloured cluster of faces? What I mean is, I've added UV seams, so areas are separated into different colours - green for the front faces of the mesh, purple for edges on top, bottom, and the sides, and yellow for the inside faces - and I want to select just the front and edge regions so I can delete them. But using the Select tool, double clicking on any coloured region just selects everything. I've tried Unwrapping it all to see if I can select the Shells in the UV Preview window, but I'm not having any luck with that either. Thanks

Julian post above the right answer Press CTRL-F or use Popups->Search in UI to find and execute any accessible item in UI in the current room.

Hi Yes, is a bad link.  here is the current access https://3dcoat.com/documentation/manual/workspaces-rooms/retopology/autoretopo/baking-guide/

Attention: Dev team   First I'd like to say "well done", this software is amazing. Bug, I get a 403 error when trying to access the "Read the Auto-Retopology Guide"   Access to www.christoph-werner.de was denied You don't have the user rights to view this page.

I think I will just wait for that update fix instead of trying to use it now with this workaround. Reinstalling 3d coat means having to redo all the customization and reupload all the custom stencils and smart materials. I'm sure the node system is great, but I'll have to test it out later when 2026 version is more stable.

I am having the same issue, in a model that has symmetrical UVs. If I recalculate UVs for the full model (now each side has their own UV island, no overlap), the glitch disappears. I have a workaround though: If I select half of my model (X symmetry) UVs and move them one UV tile (in Blender: I "G + X" with Control to eg Right side, you will see an UI like "D: 0.0000 (0.0000) Along X", make it to be 1.0000). In this way: - No glitch - Model still has UV symmetrical, officially they are in another UDIM, but doesnt matter as I won't use this model. If I would perform some sculpt or change, I could transfer UVs from the original model as they would share same topology.

Just copy qa.xml from Documents\3DCoat\qa.xml to Documents\3DCoat2026\qa.xml

Go to Edit -> Preferences -> Theme -> Check "No search in space panel"

1. I found an issue with layer grouping; I'll fix it soon. 2. Since 3DCoat 2026 includes many fundamental changes, we have added `3DCoatGL64Legacy.exe` to every installation—including 3DCoat Textura 2026. This executable runs per-pixel UV texturing on the legacy engine, ensuring identical results when loading projects from previous versions. 3. You can keep both versions of 3DCoat completely isolated from each other: simply copy `doc_folder.txt` into the folder where 3DCoat Textura 2026 is installed. This will create a separate folder in your Documents directory named `3DCoatTextura2026`, allowing versions 2025 and 2026 to run without any conflicts. You can also specify a different folder name inside `doc_folder.txt` if you prefer a different naming convention for the Documents folder. I plan to adjust the default folder in the Documents folder to `3DCoatTextura2026` in future versions; this should help resolve version conflicts, including issues where menus disappear.   doc_folder.txt