My last post in this thread: Prefix: Despite hesitations and 'let's form committees', the evidence is quite clear. The person who rigged Renda, either initially or after having been directed to fix deficiencies, has breached something (Copyright, EULA, whatever). After doing comparisons between Renda.cr2 and Victoria 3.cr2, there is no doubt in my mind that this is the case - way beyond reasonable doubt. 1. The Renda product should be immediately pulled from the Renderosity MarketPlace so that noone else can make purchases (id est: cover your assets!) 2. I feel sorry for the merchants working on Renda products and the customers who purchased anything related to Renda. They should be amply compensated/refunded in one way or another. End of story. When Daz3D learned of the Humvee issue, they immediately issued a statement to all that had the product, through email and pulled the product out of the catalog. That is responsible. 3. I don't feel sorry about this entire affair, for these reasons:

• Similarities in structure to V3 should have been a warning sign.
• When notified of deficiencies by those working on related products and then by merchants, Renderosity still went ahead and released it for commerical sale.
• As a 'flagship' product for Renderosity through RPublishing, extra-special care should have been warranted and taken to ensure a quality product void of legal issues. We've all taken hell over all of the work necessary to verify the authenticity/legality of our products in statements in the Readme.txt to filing 'rights to use' paperwork with BondWare. This breach is hypocritical.
• Whoever the product creator, the choice was ill-conceived. There seem to be any number of very capable and proven figure creators who inhabit Renderosity (Anton, for instance). Never send a boy to do a man's job.
• The real shock is the denial and hush-hush surrounding this. This product is selling for profit. When an automobile manufacturer hides deficiencies in its products that are uncovered, recalls ensue followed by investigations and sometimes guideline updates and mandates. Once in a great while, these deficiencies are openly acknowledged before public awareness, but many times it requires action on the part of others. This seems to be the case here.

Honesty and openness are the best policies. The facts are out there, let's fix the problem (not sweep it under a carpet).

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone