Jump to content
3DCoat Forums

Metromot

Member
  • Content count

    38
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Metromot

  • Rank
    Neophyte
  1. Metromot

    V4.5 BETA (experimental)

    Shift Tool not working on Mac Hello, I have a problem with 3DCoat, think this is a bug.. The Shift (Layer) Tool in Paint Room is not doing anything for me in 3DCoat v.4.5 and above. Neither the Smudge, Pinch nor Expand Tool Options work, but the smoothing with <Shift> works. I reproduced like this: - (optionall) delete the ~/3D-CoatV45 folder to have a fresh start - open 3D-Coat 4.5.19(GL64) - import Model for PPP, load the sphere or anything else - paint a stroke with the brush with depth, diffuse and gloss - switch to Shift tool and draw across that stroke - nothing happens in V3.x and up to 4.1 the Shift tool works for me as expected. If you can not reproduce it, I will be glad to give you any more info you need. Unfortunately V4.1 does not seem to open files that were created with V4.5, is there any way to achieve that? Specs: iMac (27-inch, Mid 2010) 3.6 GHz / Intel Core i5 12 GB / ATI Radeon HD 5750 1024 MB OS X 10.10.5 (14F1021)
  2. Metromot

    V4.5 BETA (experimental)

    Great! can't wait to finally give it a go - Thanks for the info Andrew!
  3. Metromot

    V4.5 BETA (experimental)

    I apologize if anyone feels there is too much impatience about Mac/Linux versions being expressed here. I am confident Andrew does the right thing but the last time we heard about it was back in January and we are all anxious to see it.
  4. Metromot

    V4.5 BETA (experimental)

    Thats awesome! But wait, month after month goes by and still no Mac/Linux versions? We're starting to feel a little abandoned, just a teeny-weeny tiny little bit..
  5. Metromot

    V4.1 BETA (experimental 4.1.17D)

    OK I installed a new OS on a wiped partition and added fresh installs of 3D coat B14A and 3.7.18F - the same problem: most of my .3b files would make 3d coat hang at load or give an out of memory error. After lots of fiddling, I found a strange thing: While using the 'Open' Menu command or CMD-o does not work, if that same file is in the 'Open Recent' menu and loaded from there, it works just fine ! Now I can edit the Options.xml file and put a filename in where the recent files are and then I can access it either from the menu or the panel at startup. Works for both versions I tested B14A and V3.7.18F.
  6. Metromot

    V4.1 BETA (experimental 4.1.17D)

    Thanks AbnRanger. I deleted that whole folder (the Mac OS equivalent of it) already as mentioned. It might be something with the demo period/licensing mechanism and thus not easy to find and discuss here.... I will now try using a new clean system and see if that brings any clues and contact support/Andrew then.
  7. Metromot

    V4.1 BETA (experimental 4.1.17D)

    I am not sure there is an offending file unless you mean a file somewhere in my system which by its mere presence causes a crash on any 3D coat version when opening ANY non-small .3d file and which I dont know where to find. I was working on several different files before it became apparent and It might as well have been just an action I performed. I don't remember and I cannot reproduce how the problem comes into existance because for that I'd have to get rid of it again in the first place. Again, is there anything being installed by 3D coat other than what I mentioned? How do I completely uninstall 3D Coat getting rid of ANYTHING that gets installed or altered?
  8. Metromot

    V4.1 BETA (experimental 4.1.17D)

    I cannot tell because of cause and effect. I ran 14A when the problem started, as if it 'poisoned' my system. The effect of that 'poison' is, every version I run, at least back to V3 has those memory problem which I never had before. I can not remove the poison with a delete/reinstall of 3D-Coat and the mentioned files/folders. As long as my system has that condition and I can not get rid of it, I can not see if any other versions would introduce the same problem. Please tell me which files does 3D-COAT write or change, other than the ones mentioned. If I can delete/reverse all of 3D-Coats marks and changes, logic tells me that should get rid of the problem and I can switch to older versions and see if it happens again. Otherwise, the only thing I can now try is setting up a new OS on a clean disk and hopefully, I will be able to continue my work.
  9. Metromot

    V4.1 BETA (experimental 4.1.17D)

    Hi. I'm having a very serious memory issue with 3d-Coat after using V4-BETA14A for a while on Mac OS X 10.8.3 with 12GB Ram. I can no longer open most of my .3b files bigger than about 10MB which all worked fine before. Even when I use V3 to open projects from last year, the program hangs forever, sometimes giving an "Out Of Memory" error before that. Activity Monitor shows that 3D-Coat uses less than 300-900 MB while it hangs and there are more than 8GB free. Everything else than 3D-Coat seems works fine. What I did so far without success: - Reboot, repair disks and permissions - Delete and reinstall the 3DCoat V4 application folder, trying out different of the latest versions (remember, even the V3 installation is affected) - Delete the 3D-Coat V3 and V4 folders in the home directory - Delete ~/Library/Preferences/pilgway.-D-Coat - Installi and run 3D-Coat with a different user account - Boot the System via Firewire on a different computer to eliminate hardware issues - uninstall the license key Sometimes after entering the registration code, it would again load a somewhat smaller .3b file fine, but after it hung on loading a bigger file, that same smaller file wouldn't load again. It seems as if 3DC is putting (or maintaining) something in the system that causes any version to consume too much memory afterwards. Did I miss anything to delete to completely de-install 3D-Coat or are there any other suggestions? This is leaving me unable to use 3D-Coat and continue important work, so any help is very much appreciated.
  10. Metromot

    V4.1 BETA (experimental 4.1.17D)

    Wasn't there supposed to be Collada (.dae) export beta since 3.7.18? I can't see in the menus/file types shown in 3.7.18F and 4.00 B5 Mac Version. Beta tools is enabled in prefs. Is it somewhere hidden or is it not in the Mac build yet? @Candy-floss Kid: System requirements for 3.7 (stable) is stated on the download page as being OSX 10.4.5 minimum. But I would doubt that testing with all OSs up to 6 years old is a priority in beta development.
  11. Metromot

    3D-Coat 3.5 updates thread

    Not using a USB Drive here but an SATA SSD for everything... Looks like a memory leak to me - when and if it crashes probably depends on how much real and virtual memory is available.
  12. Metromot

    3D-Coat 3.5 updates thread

    I saw the same memory issue shortly after using 3.5.25 for the first time. But it was in Paint Mode here. It told me to save but when I clicked ok on the dialog-> boom. There were no problems before using the same .3b file in V. 3.5.24 -- OSX 10.6.8, 3.6 Ghz Core i5, 12GB
  13. Metromot

    Massive lagging with merged objects

    I tested again in 3.5.06 and it seems to be fixed - Thanks a lot Andrew
  14. Metromot

    Massive lagging with merged objects

    Still there in 3.5.05
  15. BUILD: 3.5.04B OS: Mac OS X 10.6.4 Hardware: iMac 2010 3.6Ghz i5, 12GB, ATI Radeon HD 5750 1GB BUG DESCRIPTION: Some operations become increasingly/very slow when moving/rotating/scaling merged objects. STEPS TO REPRODUCE: - Start 3DC with per pixel painting, choose the tiled subdivided plane to start - File/Merge Object, choose TiledSubdividedPlane.obj to merge another into the scene - Switch to Sculpt Mode, click 'Select/Move', 'Select Objects' and click on the plane(s) to select one - Click 'Move' in the Tool Options and move the plane back and forth continuously At first, the plane moves fluidly, it 'sticks' to the cursor. Then within a few seconds it gets more and more disconnected, updating the position less than once a second which makes precise positioning quite impossible. Same thing with Rotate or Scale. Switching Modes (Paint, Sculpt,..) also becomes very slow. Now, if you save, quit and start 3DC again and re-open the same scene, the performance is fine again, but decreases just as fast when doing move/rotate/scale on the objects.
×