Klebnor opened this issue on Aug 25, 2010 · 29 posts
Klebnor posted Fri, 27 August 2010 at 1:01 PM
Quote - > Quote -
The problem is that products are not required to specify that they are usable in poser only. That would also be an acceptable approach.
I did not post this request in the poser forum (it was a request in the markeplace forum, not a rhetorical question) because I would fully expect the snarky condescending responses that were tacked on here, had it been posted there. Since it is in the proper forum, the responses are simply over sensitive reaction to one word ... which apparently hit a nerve.
As to the disclosure of all files in the readme.txt file, this is comparable to small print in a long contract.
Quote - Products are required to specify what is required to use them, furthermore they are put in software related categories.
The software related category is "Poser or DAZ". Unfortunately, this does not help with this issue as DAZ does not have the poser material room. I happen to use Carrara, which imports DAZ content (being a DAZ product) and has also been designed to use mat poses.
Quote - It isn't that your request is over the top, it's that you stated that not providing Poser Library MATS was due to laziness when some are simply purists who prefer to create their files based on how the software they are creating for is "supposed" to work.
I am perfectly willing to allow that the primary motivation for omitting mat poses may not be laziness. I should no longer be surprised by the poser universe, and yet I am, constantly. As a leisure user of 3d rendering software I find that my assumptions are frequently wrong. In the workday world that I inhabit most of the time, sellers of product fall over themselves to determine what users want so that they can provide it. This sort of customer focused marketing seems alien to the poser world.
If one had the mindset of a purist, I would think that one would be horrified to think that their product might be mistakenly purchased by one who couldn't use it. A purist would likely welcome a labeling scheme which clarified this aspect for the potential purchaser, wouldn't they?
Quote - No doubt you expected a reaction, you seem intelligent enough to know that using a derogatory remark in a "request" would get a reaction. Stating others are oversensitive is ridiculous, you no doubt knew exactly what reaction you would get - regardless of where you posted it.
Actually, I posed a request for consideration in the marketplace with no further agenda. It was the uninvited replies which ratcheted up my responses. I was perfectly content with the original response that it had been passed on. I will readily admit to rising to the bait when kicked.
Quote - Furthermore, a readme file's disclosure is only akin to small print in a contract if it has further restrictions, apples & oranges really. A listing of where the files are located is not required to describe a product.
I will put this down to differences in how one browses and purchases content. I have almost never opened a readme.txt file when purchasing a product. I am saddened at the thought that I will have to make this a routine part of what had been a pleasant pastime.
Quote - As I said, I do state if my products have mc6 files, and I know several others do that as well. But if the product is stated to be for Poser than stating that shouldn't be a requirement. If however it states usability in other software it should state that.
I suspect that this may be the final answer (if my request is even considered). As things stand now, it appears to be up to the vendor to qualify their product as usable by various software packages. The practices and methods of doing this don't seem terribly consistent. This is somewhat understandable when one factors in all the versions which might have to be qualified. I feel just as bad for a poser user who might buy a carrara shader package as it would be unusable to them.
To sum up ... I'm lazy, some vendors are lazy, and the world continues to spin on it's axis affording the splendor and pageantry of the changing seasons to all.
Cheers!
Lotus 123 ~ S-Render ~ OS/2 WARP ~ IBM 8088 / 4.77 Mhz ~ Hercules Ultima graphics, Hitachi 10 MB HDD, 64K RAM, 12 in diagonal CRT Monitor (16 colors / 60 Hz refresh rate), 240 Watt PS, Dual 1.44 MB Floppies, 2 button mouse input device. Beige horizontal case. I don't display my unit.