Jump to content
3DCoat Forums

SERGYI

3DCoat Developer
  • Posts

    330
  • Joined

  • Last visited

Everything posted by SERGYI

  1. The "Python" dependency was added since "48". I will try to statically link with "Python" to get rid of the dependency.
  2. To stop blaming "PNG" I have built 2 special executables for you without the library "PNG" inside: https://pilgway.com/~sergyi/Linux-No-Png/3dcoat-no-png-simple-dialog.zip Download the archive into existing "~/3DCoat-2022.49" which contains "3dcoat". Then unzip it: $ unzip 3dcoat-no-png-simple-dialog.zip Make the 2 new files executable: $ chmod u+x 3dcoat-no-png $ chmod u+x 3dcoat-no-png-simple-dialog Run "./3dcoat-no-png". It will not be able to load a bunch of icons because they are in "PNG" files. But all the icons are in their places, and they are clickable regardless of whether they are invisible. Therefore, you will be able to click the invisible icon "Camera" in the top-right corner of the viewport. Then select "Background". Then "Ref image for X-axis". I suspect that the behavior will be the same as it was in the normal executable which includes the library "PNG". To furthermore isolate the problem, I have built another special executable for you "./3dcoat-no-png-simple-dialog". The file dialog inside "3DCoat" has been replaced with the simplest code taken from the GTK official site. The code doesn't modify the file dialog class in any way. It simply calls a couple of lines.
  3. Please log in into our site: https://pilgway.com/user/login (in case you don't know the password click "Forgot your password?") There on tab "LICENSES/ACCOUNTS" click "DOWNLOAD LICENSE". On "3DCoat 2022" startup click button "Load license" and select the downloaded license-file. If the problem persists contact me directly by email "sergkryzh AT gmail dot com".
  4. Sometimes source code of "3DCoat" is not possible to build outside Windows because of substantial changes that our programmers make only under Windows. That requires some work from me to make "3DCoat" cross-compatible again. But when "3DCoat" will be possible to build under Mac, I will build it under WSL in sync. Thanks for your offer, Allabulle.
  5. Thanks, Allabulle, for your feedback and your understanding. Actually, I was planning to buy an additional dedicated machine for Linux builds/development. But the war has changed that plan. I don't want to purchase any things now. So in the nearest future WSL on my existing machines will be the tool for Linux builds.
  6. After numerous requests from Linux users, "3DCoat" adopted "spacenavd" a while ago.
  7. Hi, Allabulle! Everyone in Pilgway is using only Windows. I have 2 Macs, and since some point, the native installation of Ubuntu is not working properly on either of them. So to give love to Linux users requires a lot of effort from me. Under Windows 11 on one of my Macs, I have installed and configured WSL with Ubuntu. Then I built the latest "3DCoat 2022.43" under it: https://pilgway.com/~sergyi/links-Linux.html
  8. У меня как раз Wacom Intuos 3. На чистой Windows 11 установил старый драйвер Wacom 6.3.15-3 за 2015 год - это последний, который поддерживает Wacom 3. После перегрузки и подключения, зашёл в Wacom Tablet Properties. На вкладке Grip Pen > Pen убедился, что Right Click назначен на боковую клавишу пера. Зашёл в последнюю 3DCoat 2022.39 для Windows. Парение пера Wacom с зажатой боковой клавишей над поверхностью планшета - масштабирование. Движение пера по поверхности Wacom с зажатой клавишей на пере - панорамирование. Если в 3DCoat > Edit > Preferences > Brushing > Tablet Interface поменять значение с WinTab (Wacom) на WindowsInk, то панорамирование не работает. Режим WindowsInk предназначен для перьев Microsoft Surface - они не поддерживают интерфейс WinTab (Wacom).
  9. After investigation and meeting, the USD library has been temporarily removed from "3DCoat/Textura/Print" under macOS. We will add "USD" later using a completely different approach. New builds "3DCoat/Textura/Print 2022.35" for macOS have been uploaded: https://pilgway.com/~sergyi/links-macOS.html "3DCoat/Textura/Print 2022.35" should run on older macOS versions.
  10. Thanks for the report. This is because of the recently added USD libs (they were absent in 2022.24). I was able to reproduce the problem on my parent's iMac with old macOS 10.13. Now I am thinking about how to overcome this issue.
  11. After 3 weeks of work and several unsuccessful tries to notarize 3DCoat for macOS (there were problems with code signing and notarization because of USD file format support integration), the build for macOS has been uploaded to FTP. USD import in 3DCoat for macOS works as well as under Windows: 3DCoat imports geometry from USD, USDA, USDC, and USDZ. Export under macOS works for binary USD and USDC. Export under macOS distorts geometry in textual USDA and USDZ. This problem will be investigated this week as well as I will try to build 3DCoat under Linux with USD support.
  12. Please contact me by email: support.linux@pilgway.com. Provide your online floating serial and number of seats.
  13. Please contact me by email: support.linux@pilgway.com. Provide your online floating serial and number of seats.
  14. Personally, we don't have M1 Macs. But some users reported on the forum and in emails that they are running "3DCoat" on M1. You can freely check that on your Mac using the latest "3DCoat 2022" for macOS from here: https://pilgway.com/~sergyi/links-macOS.html
  15. When I installed the new Ubuntu 21.10 to debug "Bake w/ Normal Map", it turned out that the crash was occurring when calling "pthread_mutex_lock" inside the system library "libc.so.6". I double-checked that the std::mutex is correct (its 40 bytes are not overwritten by some code in "3DCoat"). Thousands of times "pthread_mutex_lock" was successful. But at some point, it wasn't (as I said the std::mutex is valid). This mutex was used in the memory pool class. To workaround this crash for Linux I changed memory allocation from the pool to standard "new" operator (which doesn't require mutex).
  16. This problem has been fixed since "3DCoat 2022.11". The links to the latest "3DCoat 2022" for macOS are always here: https://pilgway.com/~sergyi/links-macOS.html
  17. Licensing instructions for "3DCoat 202x": Sign in to your account on our website: https://pilgway.com/user/login From there click the button [DOWNLOAD LICENSE] (make sure that [IP WHITELIST] is empty). On every workstation make steps from section "3DCoat(Textura) 2021" and the .license-file in this document (pages 1-2): https://pilgway.com/~sergyi/FServer/FServer.pdf
  18. This problem has been fixed in "3DCoat 2022.05" for macOS which has been uploaded today. The link to the latest "3DCoat 2022" for macOS is always here: https://pilgway.com/~sergyi/links-macOS.html
  19. Since "2021.83" the crash in AUTOPO under macOS is fixed. The links to the latest "3DCoat" for macOS are always here: https://pilgway.com/~sergyi/links-macOS.html
  20. AUTOPO is currently in the process of complete reconstruction. AUTOPO crashes in "3DCoat 2021.70". Please use the previous macOS build before AUTOPO reconstruction: https://pilgway.com/~sergyi/3DCoat-2021/3DCoat-2021.67.dmg
  21. New build "3DCoat 2021.71" for Linux should run with its own "LinuxLibs" (3 files). Please check that: https://pilgway.com/~sergyi/links-Linux.html
  22. Thanks for the report! No, we don't know that. It is working on my Ubuntu 20.04 with all updates. And we were hoping that it would work in newer distros because there was a lot of rework in that code (to make it more quick and portable).
  23. "3DCoat 2021.70" for Linux has been uploaded. The links to the latest "3DCoat 2021" for Linux will be always here: https://pilgway.com/~sergyi/links-Linux.html
×
×
  • Create New...