CADQuader — Join the Testing Dear friends, We’re starting testing of our new application, CADQuader, and invite you to take part. CADQuader generates polygon meshes, primarily made up of quads, from parts imported in STEP format. It offers several meshing algorithms and lets you export the results in OBJ format. Download the application at cad2quads.xyz. After installation, CADQuader runs with full functionality for two months without a license. We welcome your feedback, bug reports, and suggestions for improvement, especially regarding the quality of the generated meshes. When reporting a problem, please include the application version and the meshing settings you used. If possible, attach a screenshot and the model file to help us reproduce and fix the issue. Thank you for helping us test CADQuader!    

Hi It's expected that a normal map be non-color. Try changing it   Another situation is to set NM as DX or openGL You can switch using this node's connection

Hello, I'm having a persistent issue with normal maps when exporting FBX models from 3DCoat. My export workflow is automated: Decimate → Auto-UV Map → Export (converting voxels to mesh). As shown in the attached screenshot, both arch models are identical and have no textures applied. The only difference is that the model on the right has the exported normal map enabled. This causes strange artifacts and unwanted fragments to appear in Blender. All other exported textures work perfectly fine. When comparing UV coordinates, the diffuse map and normal map look the same. The problem only occurs with normal maps, and I've been struggling with it for years across every model I export. Does anyone know what causes this issue and how to fix it? Is it a problem with 3DCoat's normal map export settings or with how Blender interprets the normal map? Any help or suggestions would be greatly appreciated! Here is a download link to the exported FBX Model with all the textures: https://www.filemail.com/d/psjowoyjpcnqddy (link stays active for 7 days)  I am using Blender 5.2 and 3DCoat 2026.25NS.

Heads up, Linux flatpak build was updated to .25, right click on Node Editor works now.

3DCoat Sculpt Sessions Pt 49View the full article

3DCoat Sculpt Sessions Pt 48View the full article

https://gamefromscratch.com/october-free-gamedev-assets-round-up-2/ It’s time for the next Epic Games bi-monthly asset giveaway on the Fab marketplace, with 3 free assets from October 20th to November 3rd. Once “purchased” the assets are yours free to keep forever. This giveaway contains 3 Unreal Engine assets (and 1 Unity asset), of course you can also expert many assets to work in other game engines, we showcase one such asset exported to the Godot game engine, https://youtu.be/VB7IS2Bwe8Q

oh... please share the project to take a look (PM), could be ?

I want to clarify that the files were originally made in the latest non-legacy version, not a previous version. I made the files and saved them, then a bit later I reopened the files and saw that they are messed up.

Node-Based Texturing in 3DCoat#3DCoat #NodeBasedTexturing #ProceduralTexturing #3DTexturingView the full article

Use Legacy version to keep the same workflow used on previous version

https://youtu.be/H9CiaGGq59s

Hello,   This is an urgent issue.  I am using the latest version of 3DCoat Textura  (26.25). I only paint using Opacity. Depth and Glossiness is turned off. I worked on two files today and exported the textures when I was done. When I go to reopen the files, they are changed with the strokes having depth and glossiness on my object. In one file, the Depth was turned on by itself. In another file, only the opacity was turned on as I always have it.  I am attaching an example of one of them. On the left side, is how the file was when I was done and exported the texture. On the right side is how the file looked when I reopened the project.

Turn Video into a 3D Model in 3DCoat with RealityCapture!#3DCoat #RealityScan #PhotogrammetryView the full article

Real-Time Node-Based Sculpting, Texturing & Displacement in 3DCoat#3DCoat #NodeBasedTexturingView the full article