(req) A SkIndigo-like ...
-
... Maxwell plugin. One can dream, right?
-
yes...let's dream together...or with Pavol
-
lol. Come to think of it, a standalone "Skindigo-like" mats editor for Maxwell would perhaps be sufficient. I should add, also, there are things about the current Maxwell plugin I quite like. (Credit where credit is due.) The instancing tickbox is very handy, and the "auto mxm" function I absolutely love, as it enables you to use lo-rez textures while modelling. Helps a lot to keep filesize down.
But! The way SkIndigo enables you to use presets which you can tweak using only two sliders, is something I would like to see possible with Maxwell. A very intuitive and efficient way of working. Obviously I have no idea whether this is even possible with Maxwell.
-
I agree. Whaat made a wonderful plugin for Indigo.
I was hoping the Fryrender plugin would have a similar workflow...The thing that makes Whaats coding so good is the fact that he really approaches his stuff from a users end.
Kudos for that.It's a pitty Indigo hasn't got more Sky/multilight options.
-
@kwistenbiebel said:
The thing that makes Whaats coding so good is the fact that he really approaches his stuff from a users end.
Yes! That's it, indeed. With all due respect for NL, but they seem to do the opposite, in some regards.
-
May I suggest also a 'Skindigo like' approach for VrayforSketchup and some of the other render engines around ?
.......except for Podium, which already has a 'works like a charm' interface thanks to TBD. -
lol. I don't think that's gonna fly. Some developers like their apps to be hard to use, for some obscure reason.
No, seriously, it surprises me what horrible workflows (and bad docs) some apps have. The way I see it, if a "lone rider" like Whaat can provide a user-friendly gem like SkIndigo for free, then software companies should be able to do (at least) the same for the money we pay 'em (and let's not forget some apps are quite expensive!).
The same goes for tutorials and manuals. My favorite one ATM is the Maxwell manual.
I enjoy reading it, but I've noticed that it, for the most part, tells me what a feature does ... but NOT how to use it. -
I think the best piece of software is the one you don't need a manual for.
Coding should be K.I.S.S ('Keep It Simple Stupid')as a philosophy, just as it is in design.
It's not about what you can add to it, but what you can leave out of it and still have a full functional whole as a result.Less is more baby!
-
I agree. One can get going with SkIndigo after reading a one page tutorial.
Now, I don't mind putting in some effort - but some apps are just counter intuitive, IMO. You tried modo, right? I know I did. I still wake up at night, bathing in sweat, and clicking an imaginary mouse button.
I know, I know, I may just be plain stupid.That said, I watched Dan Ablan build a simple room in modo. Ablan's an experienced user, and clearly not as dumb as I am, but it still took him five times as long to build that room as it would take me doing it in SU.
A new release of SU doesn't need a lot of extra whistles and bells, just a couple, and MUCH better support of high poly models. Then it'd be perfect for it's job. Erm, IMO.
-
@unknownuser said:
A new release of SU doesn't need a lot of extra whistles and bells, just a couple, and MUCH better support of high poly models. Then it'd be perfect for it's job. Erm, IMO.
That's the frustrating part.
If Google would just fix the high polygon support and multi processor cabability I would be satisfied again for some years. The rest is bonus. -
Same here. Of course, people have been asking for these improvements for quite some time. If they're not in SU7 ... well, then we have the final verdict on Google's priorities.
How's C4D? Having fun with it?
-
@unknownuser said:
How's C4D? Having fun with it?
i feel nice with it
simple quick test http://img397.imageshack.us/img397/2334/nb021af8.jpg
with displ.map at floor-object(like vray's infinite plane) -
@kwistenbiebel said:
@unknownuser said:
A new release of SU doesn't need a lot of extra whistles and bells, just a couple, and MUCH better support of high poly models. Then it'd be perfect for it's job. Erm, IMO.
That's the frustrating part.
If Google would just fix the high polygon support and multi processor cabability I would be satisfied again for some years. The rest is bonus.I agree with the above, but another BIG thorn in my side is to be able to lock the toolbars and of course the shadow error. There are some other issues, but the above four are the main ones I think.
Advertisement