QUOTE(Sum Square Stories @ Jan 16 2011, 11:35 PM)
I so didn't want to write another response to this thread.
" It's a beta. That's short for "we're telling you up front it can't possibly be working right yet." It's absolutely not an official version that's regarded as ready-to-go. Once you start using a beta, you're saying you want to be a tester with all the dangers and hardships that go with that. It's asking for trouble. "
Even if it was the final v16 it still is and would be there, it wasn't a bug it was a programed in check, limit, restriction (whatever). The first public release of the 16beta of netrender should have mentioned it in the release notes. If it was part of the earlier versions the buyers should have either known it or been informed since it would cause issues otherwise. I think some of those who checked this thread had the previous version of netrender and if they did they either weren't aware of this restriction or didn't say anything if it did exist before. I suspect it was added to the v16 netrender though for the reasons I brought up. I was the first (no guarantee) and maybe only person trying to use it with under 1900mB but that 1900mB was an intentional choice that was added not a bug to be discovered and fixed. I don't have a problem with that choice in how it has been implemented either, just that it wasn't documented at all. I wasn't miffed at having a problem I was miffed (partially) because it wasn't a problem but a lack of communication. I've used AM since v9.5 and I've used other betas before. I gave my specs early but it wasn't looked at until over 30 posts later. The assumptions (on all sides) in the end were the main problem that were chronicled here.
I think this is enough talked about it... you will encounter such things in future too. We all have to live with it. If every situation would be tested before Final versions and if every problem would be solved, the forums would not be filled with questions, the software would cost MUCH more (even Maya and other software in that pricerange is not bugfree... you can find many user and non-user-caused problems in the forums around there too...
I know it is frustrating sometimes, but you have to see it from the other users point of view too.
We all want to help and we are (as you) not able to look into the code (and even if, it is hard to find errors in 100.000 lines of code (or whatever A:M has)...).
So we try to find out what is going on with our possibilities. That is what a community is about.
MOST problems in any forum are user caused... often just something like setting one of 20 checkboxes wrong, or going a slightly other route of opening a window, a menu, etc. can result in VERY different behaviour with stable or less stable situations... we don't know how much you know and even if we dont know if you just did overlook something that can easily be overlooked... or if we overlooked something... and since you are another person than us you overlookd other stuff than us. Maybe less, maybe more who knows?
Getting angry about questions if you wanna solve a problem is not helpful for you and for us. Even so I can very well understand why it is frustrating for you (I had this situations too) think about it the other way round: The angrier and the more annoyed you react to one of the people trying to help (even so it may not be helpful) the less other people will answer. Because no one likes to be the next to be shouted at when trying to help.
The best way of reacting to this is giving short answers like "see post #15" or just ignoring it.
It is not that anybody think you are stupid... Many people just dont read the whole conversations (which is understandable since many are very textheavy) have the knowledge or just can't see if it is a usererror or a problem with the programm especially in situations like this where most people dont have these problems...
I will not comment on the RAM amount too much: I think systems with less than 2 GB of RAM are not really well built for doing 3d-work. Laptops are less suited too.
I can see why you want to use anything you got, but how large are you projects? Does it really make that much of a difference? If you are having very large projects,
buy a little bit more of RAM (it is quiet inexpensive these days...) or even better: Built you own computer just for rendering.
The following is not sololy addressed for you, this is for any user reading it:
It is more inexpensive today than it was anytime before to get a good system running. I recommend an AMD-system because it really gives a great ratio between money / performance. You can get a good system for 400 Dollars today that will outperform any one or two year old laptop by far...
Yes I know: It is less money but it is still money but think of this: Do you bicycle as a hobby? How much is a good bike? Do you climb as a hobby? How much is the equipment for that? Do you ride a motorbike? How much was that, how much is the gas for it? Hobbies are expensive... In comparision to other hobbies A:M is quite inexpensive... even with the equipment needed and if you do it for a living you should be able to afford the hardware or you shouldn't do it professional...
And more important: How much is your time? I tend to see my freetime as I would get payed for it. It is very valueable... So it may be worth spending a few bugs to get more from it on the long run, don't you think? Getting rid of frustrating hours of waiting must be worth a few dollars, isn't it?
I hope you will not run into such frustrating things in future but I would bet money on it that you will. It is part of the game. Noone can prevent you from it and it is very likely not the fault of anybody else, at least not fully. Try to stay calm about it. It is better for you, your heart and better for everyone around and I am very sure that finding the answers is a good feeling if you had to work for it. It is what makes the stuff more valueable at least (and not only) for the feel of it. And that is what it is all about, isn't it?