All Activity

Source... Throughout the years, I have been trying to understand normal mapping and the problems that usually appear when working with them. Most explanations I found are usually too technical, incomplete or too hard to understand for my taste, so I decided to give it a try and explain what I gathered. I recognize that these explanations may be incomplete or not 100% accurate, but I want to try anyway. PDF file (Gumroad) / PDF file (Artstation)

Try triangulating the model BEFORE baking. And use this preset (experimental) for the export step (preset location is C:\Users\<username>\Documents\3DCoat\data\ToolsPresets\ExtTools) Blender & SPainter.xml Should you triangulate meshes before exporting to substance? Yes. Different 3d engines will triangulate quads in different order, and with different rules about which way it splits them (ie. which two corners to use). This can result is slightly different lighting as the normals will interpolate in different ways. It can also affect the way textures are applies on trapezoids and other quads as shown here- although that can be a problem anyway as the texture will be strangely mapped. It's not a major problem normally, although I have had issues with a few props looking very funky, but there's no downside to triangulating things before the texturing so why not do it ?

> Show tool options settings

The 3B file is way too large to upload because I am using VPN. The file I share contains both normal maps from SP and Coat. As for the steps, I used Instant Mesh to do autopo to decease the poly count to around one fortieth. Then I auto unwrapped the UV sets, auto mapping and auto check for overlaps. I then baked and exported the low meshes and normal maps from Paint Room, with all presets set to Blender Cycles. The meshes and maps were then imported to SP. I baked maps in SP except for the normalmaps.

a weird crash to look out for , my spacing for claybrush was 0.000 so when i would use it , it crashed .. after changing it to 0.005 it was fine

to bake I need the high and low poly, only get the low poly. * and the steps you do to bake it in 3DC.

Perhaps I send the reports anonymously. I reinstalled 17 and it got back to work again. Still it's quite unstable and I have met several crash when I did multiple Ctrl Z. Yes my PC has some issues too, for which I still couldn't identify the reason. It crashes often(around once per three to four days). I am not sure if it's from the software(I upgraded Blender and Coat right before) or hardware(a reassemble?). Will do a check on hardware. Thanks for the info. I'll try to pass those automated reports to your.

I looked your crashes logs and that looks really unusual, like there are some random changes in memory. Each crash is very different, no single reason. May it be that PC overclocked and there is sort of overheating? Also, please try (if it will not start again) to get to 16 using the updates manager. Wil it still not start? Also, sending automated reports are very helpful, I am getting a lot of info to analyze and find the reason. I see no reports from you in our database. Please send and set some email there to identify.

3DCoat Low-Poly Modeling for Beginners #9. Creating a simple object in the Modeling Room. Part 2.View the full article

3DCoat Low-Poly Modeling for Beginners #8. Creating a simple object in the Modeling Room. Part 1.View the full article

https://drive.google.com/file/d/1anJx-UNznMRaJbpQeraJwOQExbu6iu1r/view?usp=sharing I shared the blender file with the mesh and textures, both from SP and Coat.

I've never really used onedrive. Still, I checked the onedrive folder(seems it was there on every windows by default) and nothing there so I assume it's not about onedrive. I do use two screens, and pretty certain 3DCoat was running on the first one because I manually matched this when wacom matching issue happened. I'll send report but I've lost the log files last night when I replaced the folder(still have the files two days ago, hope them help). In the meantime, I'll deactivate AV scan for Coat like AbnRanger suggested.

please share only one mesh with issues to take a look

I had something similar happen a few years ago, and it was pretty frustrating. I even tried to ask support what it could be, and since they could not replicate the issue on their end, I tried something pretty different. I checked to make sure that 3DCoat was on the EXCLUDE/EXCEPTION list in both Windows Firewall and Avast Anti-Virus. I didn't think it would help, because it was never an issue before. But, sure enough, that is precisely what the problem was. Somehow, Avast did not have 3DCoat on it's Exception list (meaning to leave 3DCoat alone and don't fool with it). Once I put it back on the list, everything worked fine. I guess the AV software was keeping a critical file from loading and thus 3DCoat would crash every time.

This feature was recently added in one of the latest updates , thank you very much!

Send this crash report to andrewshpagin@gmail.com Do you have onedrive installed ? Look at this. Or if you have 2 monitors, try opening 3DC on the first monitor.

And it crashed again the moment I restarted the software.