Hi every one, I make my self clear from the beginning. I not going to write this post with any intention to offend or to make someone feel bad.
In the past few days I’ve been a little un active in the forum. (yes i have low activity, 90 post so far) But i was reading some old posts, and the answers of some users were lame. When somebody asks for a professional advice by just saying “nice!” it only cheers up but thats it, in the bottom newbies are that newbies willing to improve, and but just saying “nice”, “good job” it’s not a expected answer. They want them you, professional user to correct them, to give conclusive explanations of methods, good examples like Fernando and Micha do.
If you are going to just explain parameters, buttons and scenes add images, add screenshots, make things more clear. If you pro users are going to take some of your time to answer newbies forum posts, do it well, help people in trouble, don’t confuse them worse.
*Sorry for my bad english if i missed speell something.
*Sorry if this is not the place to post this, did’nt found where.
To be sure, I wasn’t sure how to take some of your other posts, its difficult to always be sure the tone perceived by the reader is the same as what is intended by the writer. I always try to assume everyone has the best intentions (unless its obvious that they don’t).
Anway, you are right again, at least in principle. I’m not new to rendering (Alias Wavefront 6 and up), but relatively new to rhino and v-ray.
The difficulty I have is often due to differences in terminology and the UI, and less often, the individual capabilities of the software. Not to mention time and tight deadlines. So to say “check your _____” is often all that is needed and much appreciated.
However, for someone new to rendering, there’s a lot that is now done with just a click of a button. If that is the only experience you have then there is no way to know what is happenning behind the scenes. One also needs a decent understanding of theory. One of the best ways to get that understanding is by doing and by experimenting, which I believe is the spirit behind many replies.
Sometimes, I think that some people really just want to click a button, but perhaps this isn’t the right package for them. Personally, I like to tweak things, but finding the right balance is tricky.
But I do agree that more informed critiques, some outside links, book recommendations, and general advice about theory and what it means to the software is really helpful, and often lacking in some of these posts.
Saying “nice!” is always welcome, but additionally such an approach as you suggest would also go along way not only in helping others but also to advance the software in return. Even the pros can learn something new…
Alrami
I was refering to some answers of some users with barely 5 posts confusing others, and telling lies about things that aren’t that way.
More than accusing someone mi inttention was to encourage the “free help”, to be a better help, saying by that, that if you as “expert” or “newbie” user answer questions with the most truth possible basing it in treu facts and not in suppositions. To put screenshot to explain, not just go and say: “nice but missing some reflections”, i mean reflection where? how to? propose…do i get my self clear?
I’m not angry, jelous or something, my concern is that before posting do it in the most complete way, with conclusive answers, not everybody knows whats in the others head..so…
ok, without meaning or taking any offense either, I take exception to one thing:
Using this forum is not just for hobby purposes, it is actually the preferred and recommended means of tech support by ASGvis.
I appreciate that the team is busy on the next release, but I also see a recent trend that there are more and more unanswered questions. (If the question has already been answered many times over, then a quick “do a search” or “see sticky ___” should be plenty.)
The previous level of support (and the image quality), which was timely and excellent, was one of the reasons I went with vray for rhino.
Critiques certainly don’t fall under support tasks, but to be sure, they could really help everyone learn the software better, and lead to improved feedback, bug resolution, etc.
And indeed, encouragement, no matter how small is always a great thing!
