Jump to content
3DCoat Forums

ymesh

Member
  • Posts

    10
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Kyiv, Ukraine

ymesh's Achievements

Newbie

Newbie (1/11)

3

Reputation

  1. This looks like a christmas miracle ))) In my case, 2023.40 still didn't work, even I've switched from Cinnamon with Nemo to Xfce with Thunar on Fedora 34. So lets wait for next try... In any case, for some unknown reason I bought a 2023 license (((
  2. Probably, it is possible to use other FileDialog for non-Ubuntu cases? Or somehow trace/ignore any system exceptions that cause to crash on other distros?
  3. Ooo! I even didn't know that it possible to try beta so easliy ))) Thanks @Allabulle But unfortunately, 2023.2 behaves the same way on Fedora 34 in regards of "Open/Save" dialogs (((
  4. I've checked this scenario by saving files from Chrome inside Gnome. The Save dialog is surely from Nautilus. So, the default file browser is realy Nautilus in this case. # The contents of ~/.config/mimeapps.list: [Default Applications] inode/directory=nautilus.desktop Though, I can run Nemo from Gnome console, both file managers coexist on the same system. But I'm not ready to kill Cinnamon yet ))) I used to work with it too long and found it more convenient. Any way, thank you for suggestions, @Allabulle. Of course, I'm pretty sure, that developers can not afford to test all distributives. Especially, when they officially prefer Ubuntu, and not promised good work experience with other distros ))) Ok. I'll wait. At least 3DCoat-2022.49 still works just fine.
  5. Yes, indeed, I'm using Cinnamon... but I've already tried to logout into Gnome with Nautilus (even Gnome Classic)... and even have tried to add a new user with default environment... Unfortunately, 3DCoat-2022.60 still crashes on standart File Open/Save As dialogs, without any warning in console. This is the last line in Log.txt: Crash occured. Trying to save object...
  6. Hi, I'm currently using 3DCoat on Fedora 34. I would like to inform developers, that after 3DCoat-2022.49. all new updates (including last 3DCoat-2022.60) crashed on File Open/Save As dialogs ((( Though, 3DCoat-2022.49 still works without such problems.
  7. The 3dcoat is running through Rosseta 2, of course... But this process is hidden from a user. You just clicked on icon, and MacOS desided how to run this app.
  8. At least it starts and works on MacBook Pro M1 8Gb I just have no time to dig deeper, though... But at first glance, it looks pretty well )))
  9. Hi My last try to render with RenderMan on Linux was with version 4.9.69. Finally it works ))) but I had to do some extra steps for this... 1. Add the slash "/" at the end of path in RMANTREE variable: export RMANTREE="/opt/pixar/RenderManProServer-23.5/" Other apps don't need this, though... Otherwise, 3dcoat will warn you that RenderMan is not installed ((( 2. After selecting "RenderMan" as Render Engine in Render room, and pressing "RenderPreview" button, 3dcoat will stop responding. But in System Monitor, "prman" apears beneath "3dcoat" process. 3. Kill this "prman" process by "Kill" command in RMB menu. ("End Process" button doesn't help) 4. After this step, 3dcoat will display "RenderExport" progress bar and respawns new "prman" process that will start to render into "it" display. Hope, that this may help someone...
×
×
  • Create New...