Kryslin

One drive was removed from my system prior to upgrading from 2021 to 2022. The problem appeared to be entirely Avast not liking something about 2024.01's initialization, but having no problem with 2023.41's start up. I've got things working now.

Been having an issue running 3DCoat 2024.01, 2024.02... I get the splash image, Window forms, and then crashes. Happened with both 2024.01, 2024.02... Intel i7 960 w/24gb, Win10 Pro 22H2 19045.3930. nVidia RTX 3060 w/12gb, and Avast AV 2312.6094.870.813. (It appears that it's a firewall or Avast issue causing the crash - disabling Avast brought up a firewall dialog from Windows Defender. Allowed the executable, and 2024.02 loaded just fine. I'll add the executable to Avast's firewall and see what happens... It appears to be a problem between 3DCoat2024 and Avast Antivirus. Any advice beyond trashing/changing my AV program? Definitely something changed in the last 2023 release and 2024.01...) For some reason, Avast AV was blocking 3DCoat 2024 from running. I'll have to check the logs for Avast to see what was tripping it... I should be sorted out, though. My Solution was to go and manually add an exception for 3DCoat in Avast.

You can change the normal wireframe color, yes. And I have done so. But not the low poly wireframe. It's always a pale yellow. Which is a pain to work with when the base color is anywhere near that, like gold, brass, lemon, etc.

This is probably an unfamiliarity problem than it is an actual issue with e curve stroke tool. It appears to me that the Curve stroke has problems interpolating the radius along with curve. 1) Import one of the provided plane object, enable wireframe, low poly, and snap to low poly verts in the view menu. 2) Select the paint brush tool, curve stroke, and draw a curve, changing the radius at each control point, then apply the curve. This is the result I get: If I don't vary the brush radius, it paints at the correct width down the stroke. Varying the radius, especially across three or more control points, seems to bring this out. I don't think this is unintended behavior on the tool's part, because It's done this on multiple versions (4.9 and up). So it's possibly a user issue. So, what things should I be looking at to insure the brush radius interpolates correctly down the stroke? Is there a tutorial somewhere on how to use this properly? I know I've gotten it to work a couple of times, but I can't figure out what I did to do it. Thanks for your time.

Feature requests: 1) Be able to change the low poly wireframe color. When up against a similarly colored surface, one has to turn the lighting brightness down nearly to all the way in order to work on the mesh in the paint room. 2) Wireframe line thickness. I'm working on a pair of 2560 x 1440 monitors, the wires can be awfully hard to see. Thanks.

You're welcome. And yes, it is verified fixed. Thank you.

Pretty much a repeat of the last couple of posts. Problem persists in 2022.58. Managed to update drivers to current studio drivers. (Had to update the BIOS in my monitor. *****?) Same methods to generate. And it's only the stamp brush in the paint room.

And here we go again... After re-downloading 2022.54 after the updater ate the executable, and re-installing... Bug is still there, using the aforementioned steps to reproduce, across all forms of symmetry, using multiple brushes of varying resolutions. On the off chance it might be me, Are there any particular version driver versions known to cause issues? I'm running an nVidia RTX3060, Studio Drivers 517.40, under Windows 10 Pro 21H2 19044.2251, on an i7-960 3.2ghz w/ 24GB ram (which tests good). DirectX runtime is 12.0, feature level 12_1. OpenGL is 4.6.0. I've been having issues after trying to update to newer nVidia drivers, because they're not recognizing the second monitor properly on installation on version past 517.40.

Again, updated version to 2022.53, problem presents itself on provided models (Cube, Sphere, Torus) and an Imported, symmetric model, all Axis (X, Y, Z). Steps to reproduce are the same.

Just updated to 2022.49, and sadly, this bug is still there. 1) Start a new project, paint UV mapped mesh. 2) Load Cube 3) Enable X axis Symmetry (either X Mirror, or Radial Mirror). 4)Choose the Stamp Brush, choose an alpha, and begin to paint. 5)Bug should present itself. Tends to happen at smaller sizes and angles. Does not happen in all instances. It's almost like 3DCoat is losing the symmetry across the X-Axis. This happens with X/Y/Z Mirror and Radial Mirror. The work around of using the stamp drag brush works fine so long as the size of the alpha remains constant, and it doesn't have to change orientation on the mesh. It also gets flaky about orientation when you snap to a vertex.

Ok, so it was a bug. Excellent. Thanks for the reply. Will try the work around, too.

I've come across something strange in 2022.48 (in fact, in the 2022 series): When using the stamp brush to place details on a mesh, with Symmetry enabled on the X axis, It sometimes does not place the details on one side. I've noticed that as the surface you're stamping on approaches vertical, the chance increases. Steps to repeat: 1) Create a cube, centered on the origin, and take it into the paint room. 2) Enable symmetry across the X axis, chose a brush alpha, and stamp mode. 3) Most of the stamps should appear across the x axis, but not all. Also, varying the size can cause symmetry to fail as well - usually smaller. This doesn't happen in 4.9.65 (which is the most recent version I could get working; 2021 wants to crash). If someone could verify this and let the devs know, or knows a workaround/fix for it, I'd appreciate it.