Jump to content
Hash, Inc. Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


thefreshestever last won the day on October 12 2014

thefreshestever had the most liked content!

Community Reputation

3 Known


About thefreshestever

  • Rank
  • Birthday 11/23/1977

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Name
  • Location
    hamburg, germany

Previous Fields

  • Hardware Platform
  • System Description
    macbook pro 2,33 ghz dual 4 gig ram am15
  • Contests Won
  1. thefreshestever


    good job... i like the first render better.
  2. wow! this is really cool.
  3. thefreshestever

    What I'm working on...

    ouch... sounds like a nightmare. i hope you´re well insured... good luck with everything! usb sticks are really robust, had one in the washing machine once, still works.
  4. thefreshestever

    A:M fix for Mac OS "Mavericks"

    nobody said you can´t carry on using it for now... and i suppose the fix will work for v18 as well, so of course, mac users can use a:m for another year or two. but after that it will be gone as it seems...
  5. thefreshestever

    A:M fix for Mac OS "Mavericks"

    thanks, steffen... much appreciated... i can understand your frustration and even not wanting to maintain the mac version any longer, as sad as it is... i´m sure you have a life outside of coding a:m, it sounds very time consuming... again, thanks for all the effort and keeping it alive for so long.
  6. thefreshestever

    A:M fix for Mac OS "Mavericks"

    rodney, i didn´t mean to say i will never come back here, but since i will be mostly realizing stuff in another app, it doesn´t make all too much sense to post my questions here. and i certainly can´t post wips and finished projects here, since this is the a:m forum, not a software independent cg-forum. this won´t stop me from visiting once in a while, it´s more like moving to another city and visiting friends and family from time to time... so yeah, i´ll be missing you guys for sure!!! who knows, maybe i´m moving back home someday because i´m sick of polys, but for now i want to explore the big city.
  7. thefreshestever

    A:M fix for Mac OS "Mavericks"

    rodney, i´m not saying i wont have a:m installed at least on one computer in the future (given that it still runs on a mac), but i want to have one 3D app to realize a project from start to end, i don´t want to have to switch between several programs all the time. so in most cases that won´t be a:m, because of many reasons: 1. as stated before, a:m has its limits, and given the circumstances the last couple of years it´s only logical. 2. a lot of stuff can be done more productively in other apps (some other stuff not, but for MY purposes in most cases this is true). 3. the renderer. it´s improved a lot, but still slow compared to others. that alone wouldn´t be dramatic, but i have to say i like the look of some other renderers better. you might say it depends on what you do with it, and that´s partially true, but there are renderers that have a special kind of look. it´s a matter of taste, and i´m sure you can create almost every look with a:m, but it always means a lot of tinkering to achieve what some other renderers just spit out like that. i´d still recommend a:m for everyone it is suitable for. if i´d only do cartooney character animation and the future of a:m would be a bit more secure i´d propably stick with a:m for the rest of my life, but 3D is becoming more and more essential in my job, i need it for printdesign, product design, motion graphics and of course character animation, too... but once i´m comfortable with another app, there will be no need to come back to a:m very often. i´m just beeing realistic, if i can do everything in one app and can improve my skills everytime i´m doing something in that app, what would be the reason to come back to a:m that much? let´s say next week some client comes along and wants a character animation done, and there´s enough time, no tight deadline. i´d do it in the other app, because that would mean i´d learn a bunch of stuff. if i´d do it with a:m that would mean i´d miss the opportunity to learn how the other software works. that wouldn´t be all to clever i think... and since the next couple of years i will be learning by everthing i´m doing in this app, i´ll take that opportunity. but as i said before, i´ll probably have an a:m version running on at least one machine. in the beginning for savety, later more for nostalgic reasons i guess.
  8. thefreshestever

    A:M fix for Mac OS "Mavericks"

    @ gerald: that´s only one way to see it. for me it´s only logical that when you develop an OS, you want to make it faster and better with every version. sometimes this means to get rid of some old ballast that slows the whole thing down. i doubt that apple doesn´t think thoroughly about making an OS incompatible with previous software versions. @ jesse: i feel pretty much the same way. i think there was a chance back then, and in my opinion there have been many chances for hash in the past, just the wrong decisions were made. i know it´s easy for us to say now they should have done this and should have done that, but looking at a:m and comparing it to other 3d packages, i still believe it had the potential to be a much bigger player in the business, not despite the fact it works with patches instead of polys, more because of that. a:ms general workflow efficiency is still much better than most of the software out there. but there are things in a:m that are quite complicated to accomplish which can be done in other packages with just one or two clicks. it´s not always a bad idea to go out and look how others do it. it seems martin has lost any left piece of interest since TWO and SO didn´t turn out the way he imagined it, and he decided to let it go. for me THATS the real dealbreaker. if there are just users left who care about the future of a software, it can´t work forever unless it´s open source. i´ve made my choice and i´m learning a new software. it´s not easy, but not thaaat hard, too... i still find myself trying to use a:m shortcuts and wondering why they didn´t make this or that like a:m does. but in other cases i often think "hey, that´s pretty clever, and much easier". for me it´s really a relief, because i was struggling with myself for years now, and never had the guts to jump into it. it´s also a relief to know i can do nearly everything i want if i know how, in some departments like particle simulations i felt limited with a:m, that´s not a:ms fault, just wasn´t their focus... compatibility is another thing, i don´t need a 3d package to be necessarily compatible with all other 3d apps, but i need it to be compatible with after effects and after effects plugins, since i do a lot of motion graphic stuff, too. 8 years ago when i first got into 3D a:m was the only software i could figure out, but now that i´ve learned so much about 3D in a:m other software isn´t all that hard to figure out anymore, most things are transferable. so i´ll always be grateful for that. the thing i will miss the most ist the community here, this is by far the best and most supportive forum i know of. thanks for all the support and encouragement over all those years. please don´t be mad at me, it just would be the wrong choice for ME to stick with a:m, i hope everyone can understand that.
  9. thefreshestever

    A:M fix for Mac OS "Mavericks"

    i don´t think the issue here is wether apple is developer friendly or not, the reason why a:m won´t run forever on a mac is that a:m is maintained and developed by one single person in his spare time. given those circumstances it is amazing how a:m has developed the last couple of years. but when you compare this development to other apps where several coders are working on it full time, well... you´ll see the difference. i´d rather pay more for a:m to be sure the money goes into development than paying just 79$ a year and don´t even know if it will run on my mac at all in the future. what if steffen gets hit by a bus tomorrow? i really hope that won´t happen, but then the pc-users would have to panic as well... i think there are several different options for hash here (investing money, advertise and raise the price, or make it free, open source, or sell it etc...), the way it´s been handled right now can´t possibly last forever. but that´s not my decision to make, i just have to consider my options. right now it seems a:ms future is quite foggy, and i need something to rely on.
  10. thefreshestever

    A:M fix for Mac OS "Mavericks"

  11. thefreshestever

    A:M fix for Mac OS "Mavericks"

    the first part of that post is really good news
  12. thefreshestever

    A:M fix for Mac OS "Mavericks"

    easy for you windowsy people to say
  13. thefreshestever

    A:M fix for Mac OS "Mavericks"

    that´s true, nobody said anything else... but that doesn´t solve the problem that the day will come when a:m won´t work on newer mac OS anymore.
  14. thefreshestever

    A:M fix for Mac OS "Mavericks"

    it is a dealbreaker for me, too... i refuse to work in windows just because of a:m. as far as i understand the code CAN be updated, but it´s a money and manpower issue. a:m has been running on some sort of a shell on a mac so far, and was never properly coded for the mac. i don´t think we are supposed to talk about that here, but to me it seems unfair to all the mac users to let them just crash against a wall at some point. what if they are in the middle of an important project and then suddenly a:m stops working after a system update? either you invest money to guarantee it will work in the future, or you announce the bitter truth... for me that seem to be the only fair options. but since v16 is running on mavericks as you said, i guess it´s possible to make v18 run on it as well, in case it doesn´t do yet.
  15. thefreshestever

    A:M fix for Mac OS "Mavericks"

    i cant tell, dont have mavericks installed, but i also intend to.... but steffen added a "fix" for the menu dialogue issues in v18. it´s actually more of a workaround than a fix. whenever a menu is stuck, you can now press command "Q", to get out. that´s mainly for the dialogue boxes within a:m, such as the edit cp-weights menu, or the options menu, things like that. that menue then just simply closes, and you can try again, hopefully with more luck this time . this has been a pain in v17, because it happenend a lot, and one couldn´t use the workaround of hiding a:m and then go back to it, because you were really stuck in that menu. for the "save as", "import" menus and stuff it´s more convenient to use the old workaround, hide a:m and then go back to it, so the dialogue will remain open and be active after that. however, i don´t know if v18 even works on mavericks. steffen said he can´t really fix that dialogue issue, it would mean to re-code a:m completely for the mac, and that there are several system files on apples list of things they intend to neglect in the future that are necessary to run a:m in the first place... so it seems to be only a matter of time