Hav you solved it? For me its happening in both sculpt room and retopo. I don't have a solution for you but can confirm this infuriating situation. Its weird cause when painting with brush everything works fine, as soon as I try to draw vertex lines/curves symmetry gives some. is there somewhere or some way to revert to a previous release? I bought it through Steam so I guess that might be a bit of an issue. Hey there I decided to download newest version of 3d Coat 2022, ever since I moved on from 3D Coat 4.9 Ive been experiencing symmetry issues when drawing vertex lines in paint mode. For OpenGL users: Note that some GL features are available for NVIDIA GPU only and may not work / lead to driver crashes with AMD or Intel GPUs. is there somewhere or some way to revert to a previous release? I bought it through Steam so I guess that might be a bit of an issue. Is this a known issue? is there a proper fix? It seems to happen more reliably when using a tool that has selection highlight overlays. The only way to bring it back is to frame all, but that's not really a solution when it's disappearing every few seconds. It's not that the view of the camera has changed, the viewport is simply displaying nothing but the environment background. 3D Coat is a popular cross platform 3D application for voxel based sculpting, UV mapping, retopology, texture, rendering and more. Moving the mouse over the mesh for more than a couple of seconds will cause the mesh to disappear every time. I've always found 3DC to be the best retopo solution I've come across, but currently it's bordering on unusable in my pipeline due to the mesh disappearing every few seconds. I also have this problem and it seems to me that it is very much a bug that didn't seem to be in previous versions of 3D-Coat. Firstly is GL or DX mode better for RTX cards Secondly how do I get it to run. It starts in DX mode however the installer sounded like GL would take advantage of new card better. Nevertheless, AMD CPU's are fantastic at most everything else and it seems unfair to be penalized because the Multi-threading in 3DCoat and other apps use an Intel compiler.I saw someone else post a topic about the mesh disappearing in the retopo room but they marked it as solved and I'm not sure it is solved. I have purchased 3DCoat and a new rig with a GeForce RTX card however i am unable to get 3DCoat to start in GL mode. Notice, that on OpenGL normal map it looks as if there is. I reported this issue to him a few years ago, and he said he might look at using another compiler, but switching could be a massive undertaking. This image shows an optimized version of normal map conversion, because it doesnt convert between number and color, so it is faster with Cycles and EEVEE: This second picture shows how you can recognize OpenGL normal maps just by looking at them. If anyone is having similar issues, please let Andrew know about it. Therefore, it can make AMD CPU's seem slow when these Intel tools are used. I think the common denominator is that some applications use Intel's compilers or libraries.which are optimized for Intel CPU's only. What matters is how well that piece of hardware is optimized for the OS. That's an important distinction because, at the end of the day, it doesn't matter if something seems more promising on paper. I'm saying it performs worse with the 3D software I use on Windows. To be clear: I'm not saying AMD is worse than Intel. 3D Coat is a popular cross platform 3D application for voxel based sculpting, UV mapping, retopology, texture, rendering and more. I'll surely stick to Intel for my next build. My question is this: When I downloaded the demo I got two. The integration with Lightwave is really impressive. I've been an Intel user for years, the 1950x was my first AMD CPU. I have been playing with the demo of 3D Coat and am very impressed so far. X-Particles for C4D suffered the same fate, painfully slow compared to cheaper Intel CPUs. Another example of how fuss not necessarily equals facts. At the time when it came out, on every 3d forum, it was welcomed as the Intel killer. My threadripper worked ok, but I can't say it met the expectations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |