Currently Ctrl+hover it is not working, it is a bug that will be fixed on the newest versions

I did't even know that there is a different version. That helps a lot, thank you!

Hi, thanks pointing it up. The version Legacy is working as expected

App Version: 3DCoat Textura 2026.17 OS: Windows 11  GPU: NVIDIA RTX 5080 Note: I updated the software today and am immediatley regretting it >.< guess I'll change back to an older version until this is fixed or need to downscale my textures. Description: When importing a model like a cube (reproduced on both FBX and OBJ formats) using an initial texture resolution below 512x512 (e.g., 256x256 or 128x128), 3D Textura 2026.17 fails to allocate/initialize the texture map in the Texture Editor. (I used the Blender Normal Map Preset, all other checkboxes were default or unchecked. Just "Treat materials as seperate textures" is checked. The viewport displays a flat grey-shaded mesh (resembling MatCap mode) and painting on active layers has no visual effect in the 3D viewport or Texture Editor. Importing the exact same model files (FBX or OBJ) with an initial texture resolution of 512x512 or higher works as expected—the texture map initializes properly and layer painting renders in real-time. Steps to Reproduce: Launch 3DCoat Textura 2026.17. Select File > Import > Model for Per-Pixel Painting. Choose a custom model file (FBX or OBJ) with valid UVs. Set the initial texture resolution to 256x256 (or lower) in the import dialogue. Result: The Texture Editor shows the UV wireframe without active texture maps; the Viewport remains grey/unshaded; painting on layers does not affect the 3D mesh. Repeat steps 1–4 with the exact same file, but select 512x512 (or higher). Result: Texture maps initialize correctly and real-time painting works immediately. Expected Result: Texture maps and GPU buffers should initialize correctly for all supported resolutions, including lower-res targets (128px, 256px).

Hi ! Bug confirmed  https://3dcoat.com/mantis/view.php?id=2649 thanks for point it up

Thanks, Carlosan. 

In V2026.17ns, negative depth on a layer disappears when that layer is put into a Layer Group, but reappears when taken out.   Case 1:  Disappear negative depth Layer    Group1         +--- Depth layer ( including negative depth)     <- This layer is in the Group1   Case2: Appear negative depth Layer     Depth layer ( including negative depth)  <- Root layer     Group1

<- confirmed

Is anyone else having issues with Mesh tears and Ghost Mesh tears (it looks like a tear in the viewport, but it is not a real mesh tear because using a relax or tangent smooth brush on them will easily remove them) and problems with Spline Projections like you see in the following video? I am at my wits end with 3DCoat because I report these bugs and the developers say the reports are too long and they just ignore them. I am trying to explain what is happening, when it happens and what steps I am taking to fix or work around the problem. But sometimes, it's just unreliable buggy tools. I am really very frustrated.  

What exactly are you trying to do here? It looks like you are randomly hitting buttons .... I watched all of the videos and still not sure what are you having problem with? 

what are you pc specs, drivers etc?

Very strange, sorry I am out of ideas You did a complete fresh install deleting all the folders content ?

the legacy app had the same issue.

As a recommendation to call the attention of many users, you will need to create this kind of examples using the new node system. https://www.youtube.com/shorts/-v5MBQ7gcb0

You can use the Legacy version, try it. 

take care of this bug  

Non destructive texturing in 3DCoat. 2026 Last day of the 3DCoat sale! #3dtexturing #3dgraphicsView the full article

Hi Carlosan, Thank you for all the time and effort you put into helping with this. I really appreciate you sticking with it and testing the files.Unfortunately, even after following the steps and testing your cleaned file, the material and resolution issues keep returning. At this point I’m going to have to abandon the Paint room / node materials for my main texturing workflow and use other tools instead.Thanks again for trying.

Hi there everyone, I was trying out some noises in the NodeRoom and wondererd if there is a way for solving this issue with tiling. I am using a tiling mesh with all squares UV mapped in 0-1 space with 2 UV sets. I believe there is a PBR Tiler extension but didnt manage to set it up. Any thoughts   2026-08-05 02-32-08- MakingTiles Seamless.mp4