-
Posts
238 -
Joined
-
Last visited
Recent Profile Visitors
3,002 profile views
Mystical's Achievements
Novice (3/11)
51
Reputation
-
Did External 2D Editor options in Paint Room disappear? In previous versions if you were in paint room and went to Edit in the menu bar there were several 2D External Editor Options to export the current layers + model wireframe to an external 2D Editor (would open file automatically in your paint program). In preferences in/out options the 2D External Editor option is still present though: Options looked like this:
-
2021.05 seems to be missing the same import object option V49 had as well. When I go to File > Import Model for Per Pixel Painting in 2021.05 it asks if I want to save scene before it opens a new one instead of allowing me to import multiple objects into an already existing scene. The only way I am to import multiple objects at once is if I choose all the models at once but it seems I cannot choose the import option later to add any additional models to the scene afterwards.
-
I seem to have an issue with 2021.05 that I never had with old V49 When I expand 3D Coat 2021.05 so it fits two of my monitors if I reopen the program it doesn't remember the size I re-scaled it to. This is rather annoying having to re-scale all the contents each time I relaunch the program. Saving/Load a theme doesn't help retain the window scale. Also is there no direct X option anymore, its just 3DCoatGL64.exe?
-
For me the normal map corruption occurred when I was painting with a strip on the side of my mesh on a different layer. I think the eraser bit I had done to layer 0 was after the corruption occurred. Thanks to the advice of Silas Merlin I repaired my layer by exporting all the texture maps for that layer then re-importing and being able to finally erase the weird normal map issues afterwards. It still is quite a lot of work to fix the corruption I feel shouldn't ever get that bad though. Hopefully the new 3D Coat 2021 version doesn't have this issue or if it does it gets fixed as a priority concern.
-
Thanks that is indeed a workaround solution. Since its not the same corrupted layer I can finally erase that junk and repair that small section. In the future if layer 0 being partially erased was the culprit I'll just make sure the layer is locked from now on. I usually save often and in-between big changes but didn't think being able to not erase normal map data would ever be possible but now I know 3d coat can break that way so to look out for it and not save the file if I see that occur again. Carlosan also being able to get a strip to be corrupted until unwrapping the model is worrying too. You could be 90% done through a perfectly fine model and if the only solution is to start over/re-unwrap that doesn't sound good.
-
That is odd the file I sent doesn't have the corrupted layer. For testing purposes I did reapply unwrap and it seems to remove all my normal map data from every layer (color and gloss retains though). The corruption unfortunately still retains as well on that corrupted layer for my real scene. The test file I sent however the issue does 'fix' itself after I saved and reopened the file when repainting the layer 0 to be fully filled again with the grey color. However trying to replicate the same thing in my real scene the corruption retains itself. Also for exporting layers from my real scene, the normal map corruption is applied to the file itself as well, I upgraded to 4.9.68. I think I'm just going to cut my losses and accept that small section will have a weird spot on it, its very small and thankfully for what I'm using the model for it would be hard to see, just annoying to have a layer seem to be permanently damaged. I've never seen an error like this occur before and hopefully never see it again.