Jeeez, calm down cowboy.aoktar wrote:Document is updated. I think you are underestimating the work behind of plugin and you don't have any idea how hard to inject a mix material system to C4D. I can't see any any good reason for this topic. You can make a post about a specific bug/problem and try to help us to fix it. And i may not think to add features like Node Editor, scatter, volume object, material stacking, etc... I didn't have to add these with extra works of months.
So you lock the thread with yet another passionately irrational stream of words, which are mostly about something completely different than the issues at hand.
Why these emotional retorts devoid of relevance?
Is it, A - some irresistible impulse to whine about your feelz, or B - just whatever bit of inanity that pops into your head?
You do realize I haven’t said a single word about the amount of work put in, or how hard/easy something is?
So, regarding your first three words, which also happens to be for how long focus on something relevant is maintained;
Okay, but still pretty far from complete, for instance all of the examples I provided are still missing.
And since you bring attention to Mix Materials I feel inclined to say something about it as well.
As the huge workflow killer and project clutterer it is, it's by far the most annoying thing about Octane. I've always thought of it as some cheap excuse for a proper material system,
my first thought being “oh, they've copied the worst part of vray”
Add to that the inexplicable extra step of having to first choose octane/image texture before loading a texture, finishing it off by adding a separate texture manager with less functionality.
“Having { x ∈ ℝ│3 ≤ x ≤ ∞ } materials to represent 1 material is a glorious idea!” is a famous quote by No One Ever.
There was only silence following your previous meltdown, so here comes another chance
to answer the following, and preferably without getting all bent out of shape.
- “If, as you say, certain parts of the plugin is considered "free add-ons" then why, like in "why dear god, why?" isn't the core of the plugin finished before any add-on?”
Do you consider the following good business practice?
- Regularly leaving customers without help for weeks, or just abandon unsolved topics (which to be fair seems like modus operandi at Otoy)
Spend five minutes browsing the forum and you find an equal amount of examples.
- Mostly blame the customer, regardless of the issue
- “Is it the official position of Otoy that certain features of the plugin are "free add-ons which should be paid or individual plugins", and If so, can we get a clear statement which those features are?”
So why am I so upset?
For over a month I’ve spent countless hours working around problems, re-render, at times even being unable to use Octane, due to a flawed licensing system.
Here’s some of the problems, without the details as they're already expanded upon elsewhere.
- Documentation - Incomplete
- Save scene with assets - Broken
- Network rendering - Broken
- Network animation rendering - Broken
- Network rendering slaves ip config - Broken
- Save image from live view - Broken
- Opening network render options from live viewer - Broken
- Unchecked checkboxes check themselves, or the other way around
- Licence system - Broken
Otoy, do you understand that there’s a problem here, or do I have to find myself both time and crayons to explain it further?
