yoda64

I'm looking into the bug , but I'm not sure if I can fix it fast , because I'm going at saturday in my planned holidays (without computers ...), and after fixing it takes around one day to recompile all versions . It's look like only the windows versions are affectet , it can be, thats the cause is a compiler switch (Intel2015 to Intel 2016)

I'm on this , Please file a bug report . And Nancy is right , it's a numerical problem ...

Without a sample project I can't say what's going up here , nor fix if this is really a bug ...

My mac development machine is a Mac mini (Mid2011) Core I7 , 8GB Radeon 6630M using OSX10.7.5 (the last version , where I'm able to compile A:M, newer versions won't work, due same framework incompatibilities)

Yes there will be intermittent resolutions (1024,2048,4096,8192) . As maximum a decal with 8192x8192 will be possible , because 16384x16384 is too big (around 1,5 GigaByte per decal) ... The second problem is solved for the next version too. But please open a bugreport anyway for this .

I extends t he limits for the next version , is 16384x16384 big enough ?

It's changed as default to Numpad9 as in the changelog written , must look why it's not displayed .

Is "Show Particle/Fur" on ?

Is fixed in the next version , sideeffect from the camera switch

Not in 18k , one version later first ....

Please open a report and attach there Your master.log file .The SSE4 version is only installed , if Your Cpu has AVX support . But a I7 should have this . Have you selected "Install AVX version" in the setup (page4)? Your cpu doesn't support the AVX instruction set , thatswhy the SSE3 version is installed , I have upgraded silent from SSE4.2 to AVX for the fastest A:M version .... Update A changed version, where SSE4 (without AVX) included, is on the way Update2 My provider doesn't like me , has anything against the update

For the driver problem . The error messages (for nvidia gpu's) means , that the gpu was "overrunning" with opengl commands from the application (in special glBegin/glEnd, which are producing a errorstate when no draw commands are in between) , for the amd gpu's , it's loke like they are more tolerant in such a case . If this error occurs , please try to use the wireframe view , or reduce the resolution for shaded views (Decrease Subdivisions) .

woo hoo! what was the problem? and by the way - How do you get bones to show in stick mode? - I haven't located the magic button yet. You can find it under Tools -> Customize -> Commands -> Draw

From the doc for RGB expression Creates a color by combining the three floating point values r, g, and b. These numbers should be expressed as 8 bit color, from 0 to 255. Version 18e , will clamp the values between 0 and 255 self and using absolute values, so a translate propertie can used as example .

Please uncheck the SSE4 option at installing , this files are not correct build . I'll rebuilding the 32bit version tonight .

Was my fault , while I had changed some things to a faster random number generator . It will be fixed in V18d . Hope I get it this version this weekend to Jason too .

Maybe a problem with decals, discovered also on Nvidia gpu's (v18a , which will fix this is on the way) , but I don't have a machine with a intel gpu, so I can't test this . The logfile is always written , no longer need to enable this extra . It's located in the A:M installation directory (master.log) .

thanks guy's, but there's no reason to party .... ;-)

Not yet , V18 will also be avaible for OSX , what I mean is , that a upcoming OSX version after 10.9 may be not longer supported , when Apple removing frameworks which are needed for A:M and no workaround exists (and I wouldn't spent so much time as yet to find a workaround) .

After a week I have spent for trying to solve the problem with Maverick , I have a solution , but I'm not happy with this solution ,it's in my eyes a dirty hack ..., but nothing other has worked This solution will be integrated in the installers , but they are not up to date yet . So I have made temporary fix , which You can download After unpack this file , open a terminal window (/Applications/Utilities/Terminal.app) , navigate to the directory , where you have unpacked the archive and type "./install_libs" , then Your password is asked , type it in , and the needed libaries are installed in the correct place (/opt/local/lib) . I have tried to make this more userfriendly with Platypus , but this program doesn't work correct on Maverick too . A general word about the future for the mac version (from my point of view). After I have read the posts in this thread , my personal conclusion "end of life for the mac version" . I wouldn't spent more time on it ,I don't recreate around 200 xcode projectfiles, which where needed to compile A:M under 10.9 (the XCode version I'm using yet doesn't run on 10.9 -> Kernel panic ) , no'r I'm switching to Clang/LLVM (the apple favoured compiler), no'r buying a new mac (which would be necessary for the next osx version, I assume in the next year ...) . If there is another developer , who would maintain the mac version in the future , all changes are in the svn ...., good look . Regards Steffen Added: Jason has posted the fix/update for Mac OS Mavericks here for downloading: v17g+ Note: There is no change to the Windows version from v17 to v17g+.

Have to update my last post , both version have worked , while I had done a update installation for 10.9 over 10.7 , here some libraries in /usr/lib not overwritten , thatswhy it has worked . After a fresh install for 10.9 on another partition (without transfering the data from the existing 10.7 installation) , I see the problem now . It looks like Apple has changed functions/entrypoints in the libstdc++ :-(. I'm looking for a solution to solve this , but can't promise that I have success . There is no need for more crashlogs for 10.9 . And the reason why 16.0 is working is simply that this version is compiled with the apple gcc 4.2, starting from V17 A:M is compiled with a homebrew gcc 4.7.

I have installed now Maverick on my developer mac and can't reproduce the problem , that V17 or V18 are not working . Here I need the crashlog , to see, where the problem occurs . But installing Maverick was a absolute bad idea , now I'm not able to compile A:M on the mac :angry:

Testcase please , can't see this behavior

There was a dongle version for A:M and the code for this is still in , but I didn't if they is still selled at this time .

I think this will be a new (updatet) toy for You . Will come with alpha3