Jump to content
3DCoat Forums

Sorn

Contributor
  • Posts

    225
  • Joined

  • Last visited

Everything posted by Sorn

  1. I agree, mostly. They would show that much more love for the Linux platform (and Mac, for that matter) if they would streamline their building process to be able to release Linux (and Mac) builds within hours after the initial Windows build is published. Having to wait for days (and days) for critical bug fixes already solved is a tad frustrating. Other companies manage to do so (and not just by delaying the publish of the main build, in this case, the Windows one (that's not what this is about)) and this great team can do it too. Then, they'll show that absolute commitment to all selling platforms. During a Beta phase is not optimal to wait for days to try to help to find bugs in all platforms, but is not a big deal. Now, though, we're even skipping entire build releases, for days on end, on a released product. That being said, the work done for the new 2021 version is patent, and with a bit of extra organisation, or allocation of resources, it'll be fantastic, for sure.
  2. Can we please have a new Linux build? We're still at 2021.06 as of July the 23rd. We're missing out on a ton of bugfixes already present in more recent builds. Could it be possible to streamline the internal building methodology so we wouldn't have to wait for days before the Linux build is released? It would mean a lot to some of us. Thanks in advance.
  3. It worked here, but the new primitive stays "inside" the large sphere, if I hide the layer in the sculptTree I can see the primitive generated.
  4. The [E] Stroke mode panel is empty in 2021.RC2 Linux That in the main UI and invoking it with the "e" key.
  5. Fine by me. I just don't want to have to remember to turn it on every time. I just want to be able to let it on by default (and turn it off if needed be) or vice versa.
  6. Could we please have settings in the Preferences panel to enable "CUDA" and "Cuda (sic) Smooth Boost" by default when we start a new session of 3DCoat? Now we have to enable it every single time in the Geometry menu. Even for saved projects that were usign it. It makes a significant difference in performance, at least in my system. That is using the Linux Build, I don't know if the issue is the same in other operating systems' builds. Apologies if it's already there, I couldn't find it.
  7. The Choose the UI font in the Theme tab in the Preferences panel does nothing in Linux (Ubuntu 20.04) 2021.B56 Linux Build.
  8. MatCap creation no longer works in beta 2021.B56 Linux With 2021.B55 Linux (previous) build I can, in the Shaders Panel in the Sculpt Room, follow these steps to create a new MatCap: - Right click on a MatCap - Construct New Shader - Enter a name for the new MatCap Shader being created - Change parameters in the Shader Settings - Click OK and that's it. With the new build now creates a black one (shaderless?) and the options to tweak the about to be new MatCap are not cloned from the MatCap selected, as before, but seem like options for a new PBR shader. It still doesn't create one.
  9. Adding some psd files as alphas in the Brushes panel crashes 3DCoat instantly. Not all, but some psd files definitely crash 3DCoat. Linux 2021.B55 build. Again, like in the case of exr files, psd files should work in 3DCoat. But if not, it shouldn't crash the whole program. Sounds like a bug. The same files work perfectly well in various other sculpting and 3D software.
  10. Nice to know. Thanks for the explanation! I'm on the fence about buying a new rig, knowing that difference in performance in a software I do use helps a lot. Also my CPU is ancient by today's standards.
  11. May I ask which CPU did you upgraded from? It would be interesting to be able to ballpark the perceived increased performance knowing both CPU's. Still, congrats on the new machine! :-)
  12. Yes, thanks! I already converted some exr files to png. It's not ideal for a variety of reasons, but at least I can manage with png. It shouldn't crash, though. I wanted to report the crash, mostly. Being able to use exr could be a feature request. I assumed it was requested before, indeed. To sculpt is pretty useful to use different matcaps here and there for many reasons also. I don't want to bother everyone in this thread as to why. But, as stated, it shouldn't crash, at least. Hopefully they'll fix the crashing. Maybe later we can have exr for the matcaps. Using png's has its issues. Thanks again, sprayer.
  13. When editing a Shader in the Sculpt room, choosing an EXR file to drive the Modulate color by texture setting crashes 3DCoat instantly. Trying to use an EXR file in the Color Modulation panel, in the IMG tab, crashes 3DCoat instantly too. EXR files should be supported, preferably. If not, it should issue a warning. In any case, it shouldn't crash. It looks like a bug to me. Not tried editing shaders in this way in any other room. The purpose was to re-use .exr files to create custom matcaps in the sculpt room to, well, sculpt. Build used: Linux 3DCoat 2021.B55
  14. When editing a Shader in the Sculpt room, choosing an EXR file to drive the Modulate color by texture setting crashes 3DCoat instantly. EXR files should be supported, preferably. If not, it should issue a warning. In any case, it shouldn't crash. It looks like a bug to me. Not tried editing shaders in this way in any other room. The purpose was to re-use .exr files to create custom matcaps in the sculpt room to, well, sculpt. Build used: Linux 3DCoat 2021.B55
  15. Thanks, but sadly I already have the camera viewport FOV at 50. I tried it at more and less values, too. It doesn't seem to have any effect when starting a new scene. Only hitting the house icon in the top bar in the viewport ("Reset the camera to the default position") can I see the sphere. No FOV changing helps.
×
×
  • Create New...