SERGYI

Broken file dialogs are a known problem on non-Ubuntu distros: "3DCoat" is built under Ubuntu 20.04. The problem occurs inside the function gtk_file_chooser_dialog_new. I am porting the system code from GTK2 to GTK3 to overcome this. Here is a raw framework of "3DCoat" for Linux that uses GTK3: https://pilgway.com/~sergyi/TestStroke/TestStroke.tar.bz2 The framework is still built under Ubuntu 20.04, but the file dialogs should work on other distros. Press key [O] for "Open Image File Dialog" to test. Key [S] for "Save Image File Dialog". Key [B] for "Browse for a Folder". Key [I] for "Input String Dialog". The tablet support still needs to be implemented. Please provide feedback on my email sergkryzh AT gmail dot com

I have checked the Resample to 10K on the standard body model inside "3DCoat 2024.20" for macOS, and it works. Try to rename your user data folder "Documents/3DCoat" into something like "--3DCoat". Start "3DCoat 2024.20" and it will create a fresh user data folder with default settings. Restore your scenes manually to filter out settings. There were cases when corrupted settings affected the app's behavior.

Hello! Despite several complications and trash in our country, I am actively working on the build for Linux using GTK3 and feel optimistic about it. As I said, the code has already been successfully compiled and linked. The problem is that some things are not working as expected. Again, it's worth waiting for the build because I have restructured the code, and it seems like it will be possible to migrate to GTK4.

GTK is the bridge between the app and Linux. Although it may seem that "3DCoat" does not use GTK widgets, several thousands of GTK/GDK code lines are inside it. This code handles the main window, input events, and file dialogs. Input string dialogs appear above every entry inside "3DCoat," using GTK widgets. So you are right about proprietary GUI, which is drawing using OpenGL. Still, app and OS links are implemented using platform-dependent libraries. Web apps are free from such dependency. As an example, I have ported the core engine to WebAssembly and made a demo: https://collectallitems.com/ As you can see, it works on any platform. Using Cocoa to run under macOS, Win32 API for Windows, or GTK/GDK under Linux is unnecessary. I hoped to port "3DCoat" in such a way, but the web has enormous limitations. They are related to stripped OpenGL support, the absence of third-party libraries, and no multithreading. Therefore, for "3DCoat," there is no other way except to maintain and update platform-dependent APIs. I have installed Ubuntu 24.04 under WSL to try GTK4. I could write and build a simple GTK4 app, and it ran. Still, the resulting window has visual artifacts, and the console has several errors related to visuals/graphics. The standard and default "gedit" is not showing its window when running in Ubuntu 24.04 under WSL and the console has the same visuals/graphics errors as running my simple app. Therefore, I cannot get a working environment for GTK4 under WSL.

Yes, GTK4 is very welcome. However, the difference between GTK2 and GTK4 is greater than between GTK2 and GTK3. So, I plan to make steps from GTK2 to GTK3 and then from GTK3 to GTK4.

Hello Sorn! I am porting from GTK2 to GTK3. The code is compiling and linking, but it is not working yet. The step from GTK2 to GTK3 was needed because GTK2 is deprecated. Some distros don't have GTK2 by default. Also, there is a probability that the deprecated GTK2 causes the problem with file dialogs under some distros. As soon as I will get a workable build, I will upload it.

The log shows "Renderer: GDI Generic". This message means that the proprietary graphics driver is absent from the system. Please install the proprietary driver: NVIDIA https://www.nvidia.com/Download/index.aspx AMD https://www.amd.com/en/support If your system is a laptop, plug it into the power adapter. The laptop on battery may use an integrated Intel adapter (older versions of Intel adapters don't support OpenGL properly). But when the laptop is plugged into the power adapter, it uses a dedicated graphics chip (check for dedicated graphics in [RMB] START > Device Manager > Display adaptors). Note that "NVIDIA Control Panel" in "Manage 3D settings" allows you to select between "High-performance NVIDIA processor" or "Integrated graphics".

Thank you all for the feedback. I have uploaded "3DCoat 2023.31" for macOS: https://pilgway.com/~sergyi/links-macOS.html The build is for Intel (not Universal). Here is the reason. I have bought a Mac mini M1 and investigated the cause of the issues you have encountered. It turned out that the "AngelScript" library does not support the native calling of functions and methods on the Apple M1 chip. "3DCoat" is heavily dependent on the "AngelScript". All functions and methods (thousands and thousands of them) are registered in "3DCoat" in a way that counts on the native calling of functions and methods. We will discuss this situation at the meetings to understand what we can do with this problem.

"3DCoat 2023.29" for macOS has become "Universal": https://pilgway.com/~sergyi/links-macOS.html Does it run/work on your Silicon/ARM Mac?

Thanks for the details. I have testes your steps in "3DCoat 2023.27" for Linux under Ubuntu 20.04 and Ubuntu 22.04. No crash. Frankly, I want to fix this. But I don't understand the source of the problem.

This is the first time you mentioned that the problem is not with all file dialogs but a particular one. Specify the steps to reproduce: every click, navigation, and selection. The principal here is the operation when the crash occurs: on opening a particular file dialog; on navigation inside an already opened file dialog and inside what folder (all folders or a particular one); after opening a selected file of concrete type.

1. Linux is a family of operating systems. The "3DCoat" executable has been built under "Ubuntu 20.04". This is noted in the "Downloads" section on the site and inside download links. Compatibility with other distros is not guaranteed. 2. In "3DCoat 2023.27" for Linux Ubuntu there are two executables. One has been built under Ubuntu 20.04 (Python 3.8). The other one is under Ubuntu 22.04 (Python 3.10). Is this a good idea? Please provide your feedback on running these executables directly to me: sergkryzh AT gmail DOT com. https://pilgway.com/~sergyi/links-Linux.html 3. To test the Python inside "3DCoat 2023.27" for Linux Ubuntu do: 3DCoat > Scripts > Run Script > inside folder "3DCoat-2023.27/UserPrefs/PythonAPI/Templates" select any py-file (not pyi).

Thanks to the detailed explanation, the problem has been reproduced and fixed in 2023.26 for macOS: https://pilgway.com/~sergyi/links-macOS.html

Building for Apple Silicon (arm64) is on the way. I have already built all third-party libraries for arm64. There is only one but the most critical step: migrate from the Intel-based TBB library into the standard library of modern C++. This complicated step is also in progress.

Please download "3DCoat 2023.25" for macOS: https://pilgway.com/~sergyi/links-macOS.html For an unknown reason, the tab "Render" was crashing in "2023.23", built using the "Release" configuration (even on my Intel Mac). But it works in "2023.25".