Hi All
In this letter we explain why we don’t want to work with Paralumino to develop new tools.
We really appreciate Brian J. Pohl as a very sincere and honest man who has done a lot of good things for EI and for us personally. Same time some things do stop further plug-ins development together. We personally see nothing offensive in formula “Brian does something wrong/bad” but if it’s not so - let moderator(s) just kill this thread, no probs.
1. Plug-ins ideas/themes
We really hate formula “what feature you would like..” (same as “what would you pay for.."). There is nothing more counter-productive. For all. If user answers - so he already hopes for something. What if it’s out of our abilities? Let’s explain him “we cannot do this?”. He would not like, sure. In other hand, developer becomes in situation like “you promised”. And it happens soooo momentary
although no one promise was given.
Ok, but how otherwise? Ideas should come from people/users, isn’t it? Very true. But not literally/directly. Need to see
what users do in their prjs, what are probs there etc. Nobody can “generate a good idea when he wants”, any idea comes as accumulation of experience. Developer must have a long memory.
Ok, examples:
a) some time ago Dave asked us about a shader “rounder of corners” kinda “bevels for existed objects”. We thought about this - but a shader seems not very suitable here. It’s more natural to have a “champher” plug-in for such purposes. Ok, some time later we considered a prj with shading artifacts. The reason was also bad corners/edges (a tons of polygons but inaccurate vertices normals). Another one user was interested how to achive rounded orners/edges with Encage. Another one - how with MrsBebel. Both ways are sometimes possible but it’s not what these plugins are intended for. So “champher” idea looks enough viable. But can we implement it? Time? What if it’s in modeler and not so actual as we guess?
b) Jens asked about “leather” shader. He showed photos and it’s very clear: actual fractal noises do not do what’s needed. They are “near” but they have not a some “harmony” of leather. Really interested. If modify existed fractal algorithm a little… so, maybe.. But who knows? It needs tons of experiments, maybe we cannot done this at all.
Please do NOT appreciate this as “hint”, “promise”, “teasing” etc. Just we really think: it’s affair of developer what
product to propose and when. There is a good user’s answer for “what would” questions: “Show me you product and explain its features. Then I will solve buy it or not”.
2. Featuring
“Paralumino plug-ins cannot be sold well because they have not enough features”. Be sure “enough features or not?” = absolute, 100% standard paranoya of any developer. But we are really interested: for what need to discuss this (subjective) opinion on public? “Our plugs are bad!!” - it should attract more customers? A new marketing style, huh?
Sometimes Brian is “too opened”
Ok, speaking seriously: Paralumino plug-ins are featured not worse than any EI plug we seen in previous 10 years. Paralumino plug-ins look quite decent compare to their analogs in other apps.
About “better Trestle”. There is a little story: engineers were asked why a tank model they created is so heavy/ugly. They answered: all was fine until one day boss said: “armor should be thicker”. Thicker armor - less speed. Thicker armor - need more powerful engine. More powerful engine - need to redesign all weapon. Finally all is worse, but armor is really thick - as boss said.
The goal of any engineering is a “balance”, not “more powerful”. For what we need to re-write a big piece of modeler as a plug-in? What’s so bad in mini-editor? Or maybe each text editor should have all from “Microsoft Word”? (oh, nooooo
) We really don’t want to waste months of time for a work that’s we estimate as unproductive/ineffective. Very and very often good, live ideas were killed by “more powerful”.
Another one prob is “user’s appetite” that has no limits. The “focus” of users’ attention jumps momentary from good “done things” (already clear and thus not interested) to “what whould be nice”. A “devaluation” effect comes very soon. That’s a very negative side of “public beta”, a final result looks “too small” compare to megatons of over-expectations. It was a very painful with Paralumino.
3. Pricing
This is very related with previous one. Be sure, every developer would be really happy to set less price to attract more users. But with “intensive featuring” there is no other way except of larger price (see “armor - speed” above). Otherwise it momentary becomes an amateurs work in sparse time.
And another one opinion: “In normal app every your plug-in should be a line of host’s menu” (often together with a portion of unhappy/irritating). Well, what to answer? That’s, undoubtedly, a reasonable opinion. That’s same (or even more) attractive for developers (a stable job is always better). However, we cannot hope for this in near EI future. That’s really large/huge work “to include this in host”. That’s a lot of related probs with support and others. And with all this it’s very possible host’s price will be bigger. And who knows will it be good or bad?. Remember how much you should pay for apps you talk about, their advanced renderers, network render places etc.
4. Positioning
We think a place of Paralumino plug-ins should be defined well and clear for all. If a thread about “hypopthetic modeler” is started (like 1.5 years ago) - so what are those plug-ins for? Why we need to duplicate things covered by other app? Why a user should pay for each single modeler’s function? So anyway our plan is to wait for Tesla and to see.
That’s all, gentlemen. Sorry for a long letter