pr1970

Hi I`m trying to export a 61m triangle obj file but keep getting this. I have 64gb ram and 3d coat is only using 15gb. Using 4.9.57 GL. Thanks

Yes when I made more space around the uv shells. I went and tried the same scene in substance painter, its so much faster in that package, at 4k texture its like the speed 3d coat is at 512x512 :-( thanks for the help.

Hi , thanks for the help. Yes its the padding of my uv`s, i`d allocated for a 4096 texture. So i can adjust that to allow for the padding at lower resolution. I tried the padding settings aswell. But back to the flood fill lag... i noticed at 512 is instant, at 2048 its less than a second with the fill tool, but 4096 it jumps to about 4-5 secs per fill. Really would be nice to have that reduced down in time to make it more user friendly.

Unfortunately it didnt quite work, my fear was the seams and you can see. I dropped down to 512 textures resolution, much faster btw, filled with surface material. It left a few areas, see at top of chair . I then put texture resolution back up to 4096, smart material filled out but seams still there. I then did a fill with surface material at 4096 and that got rid of the seams. My uv`s were set out for 4k textures, so can see why it struggles at 512 resolution. Unless i`m doing something wrong? thanks

Thanks, think that may work until they can fix that. Only concern is if any seams are also reduced in resolution, and when i ramp up the resolution the seams show up. I`m using smart materials anyway. Will have a try, thanks again.

Hi, I feel the fill tool is just too slow to be really useable in the paint room with anything above 4k textures. I have a 45k tri scene, all one material and selecting polys to paint on regardless if its a smart material or just a colour with disabled normal/roughness, its taking about 10 secs for it to complete each fill. This gif shows how sluggish it is. Any ideas? thanks.

Thanks for the quick turnaround.

Yeah it has some issues that model, its not mine but wanted to try some quick tests in 3d coat and another mesh were loading it with lots of issues. Only when i tried other packages that all seemed to deal with those problems that i was a bit concerned with 3d coats handling.

no probs, Thanks.

Sorry, didnt have notify on. v4.9.49 (latest beta) I tried an obj that i exported in from blender, but still had the same issues. I`ll PM you the model. Thanks

ah ha, thanks. Weird i`m getting mixed results. The initial ones i tried didnt convert to depth. But i`ve now found others that are working ok. I think it doesnt like 8 bit png`s

Thanks , but i think this should be an option to allow normal maps to be used. I have a library of hundreds of normal maps which would be nice to be able to import into 3d coat without converting them. Like substance painter does https://docs.substance3d.com/spdoc/normal-map-painting-109608964.html

Anyone managed to get normal maps to import as a brush? It imports it but doesnt recognise its a normal map, just adds the colour and then ignores any height information. Or am i doing something wrong. I do this in substance painter, but doesnt seem to be a setting to allow it in 3d coat?

Thanks but no difference. I tried triangulation and merging vertices before saving as 2014 fbx. I tried a range of software, only packages with issues are knald and 3d coat. The rest just worked with the original, there are some n-gons in there but like i say , even clearing them up i couldnt get it to load properly in 3d coat.

Hi All, Noticing that this fbx i`m trying to import is having alot of issues. It doesnt have decent uv`s so its doing an auto-map on import. But it just doesnt understand the face normals. I tried the same object in Maya, blender and cinema 4d without any issues. But 3d coat just fills it with holes. Tried all combinations of settings, weld vertices, invert normals, lock normals,etc but nothing works. Any suggestions? Thanks

Additional Quixel folder question... I have a quixel folder that has folders with the unpacked textures, but it looks like because there is no .zip file 3d coat isnt recognising them. With quixel mixer when you download materials it automatically creates folders and discards the zip. Is there anyway to automatically import to 3d coat with just the folder??

Hi Sorry, havent got back to you before. Thing is the 3dcoats data is all on my c:\user\***\documents not in a onedrive folder. There are some textures on layers that the project i saved that were on onedrive, including the .3b. In the end i used an autosave that was only about 15mins from my project save.

Hey all, I save some work to my onedrive folder (.3b file) that has some attached albedo/ao textures in the paint layers. This morning I go to continue my work and i get this error. I`ve tried copying the .3b to another directory outside onedrive directory. checked hard drive has 20gb free Quitting one drive Disabling anti-virus. Checking texture files it uses arent read only. This is in 4.9.39 version. Also you cant get out of it, clicking ok just doesnt do anything. I have to remove the task from task manager. Any ideas? Thanks

Trying to set it up, the tutorial video looks like it was made 10 years ago and is all old interfaces. I`m having issues with maya opening up multiple 3d coats, also no idea of which export settings from 3d coat should be used, i`m missing gloss/metalness when it does go back to maya. The docs say you should have mental ray plugin enabled, but this has been removed since Maya 2018. Would be nice to get some Maya/3d coat applink love in 2020.

Noticing in v4.9.28 , in paint. If you freeze some polygons, then invert and then hide frozen polygons it hides some unfrozen polygons.

Great, thanks

Any idea of an ETA on that smart pinch? I really could have used that feature recently, looks great!

I didn't say anything about 5 minutes of playing. I've spent hours on the beta versions only for it to crash. But I have lots of beta versions of applications but I don't throw my toys out of the pram if they crash on me which they often do. Beta means just that, expect it to be very unstable and use full releases for production work.

Agree with Jarvis. Andrews doing an incredible job improving this software and allowing us to beta test new features as they go along. I personally love seeing new versions every week to try out. I wish more companies did this. I don't quite understand why people are trying to use the beta version for any major work. If I have to use 3d coat for work I go back to the release version from months back. I just experiment with the beta versions. Keep up the good work Andrew and team.

Just discovered 4.9.10 that if you attach a smart material to layer, then go upto smart materials, and then "attach to the current layer" (again)..causes crash.