[noseman]

I am talking about the C4D plugin.
You are out of excuses NL.
Sorry Tyrone but the "patience" attitude doesn't help me any more.

WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN

[Rochr]

I second that.

This thing passed ridiculous a long time ago. You can´t expect people to wait forever while you play around with webpages, MXM pages and whatnot.
How about putting the pages and the Studio aside, and bring the plugins up to par. It certainly would be about god damn time.

[Eric Lagman]

I doubt the same guy that does the web pages does the writes code for the cd plugin But regardless I would not consider this a 1.0 release at all. There are way too many workflow issues. I had to move a project that I was working on that had a bunch of custom mxm with textures to another computer. Talk about a nightmare to go in and adjust the path of all the mxm, then go into the tags and point them to the new location of the mxm. The save project needs to take the mxm's into account somehow. I feel like I spend most of my time creating paths to textures over and over In the material editor and in the plugin tags.

[Tyrone Marshall]

I am talking about the C4D plugin.
You are out of excuses NL.
Sorry Tyrone but the "patience" attitude doesn't help me any more.

WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN
WE WANT OUR WOKING PLUGIN

Have you ever written software before? Development takes time. It will be ready when its ready. The same for a lot of software developers.

[Rochr]

Development takes time. It will be ready when its ready. The same for a lot of software developers.

Of course. You get no argument from me there.
But fixing issues such as texture tags(time consuming tripple tagging) and better camera tools, allowing multiple cameras wouldn´t exactly be rocket science. After all, 1.0 had these features. Why take away features that worked well?

Sadly, reverting to the previous version and add the ability to render out highres would actually be an improvement over what we have today.

And a few words here from NL wouldn´t be such a bad thing. It would at least show that they know we exist.

[seco7]

Have you ever written software before? Development takes time. It will be ready when its ready. The same for a lot of software developers.

Seriously, how many years does it take to write a plugin? And not just some plugin, but a vital piece of your product. How about use your contacts at NL to get an actual update or atleast "I checked and someone is working on it right now, full time, full effort".

[noseman]

Have you ever written software before? Development takes time. It will be ready when its ready. The same for a lot of software developers.

It is definately NOT about writting software, it's about customer relationships.
This product is STILL not final, and my money is still in their hands.

Your argument is TOTALY wrong because it has nothing to do with the actual problem. This plugin was supposed to be ready on February 2005. The delay has NOTHING to do with software development as a task, but it's caused by NL's greed. Their desparate need to get the money has turned them from a team of talented programmers to a bunch of rude crooks.

Do yourself a favor and don't spoil your excellent reputation by standing up for these people.

[liquidlight]

Thanks noseman! You´re absolutely right.
I don´t think that statements form NL will bring us closer to the desired plugin. I´m sure they´re working on it but just can´t get along with certain issues regarding C4D or just put more effort in many other projects.

Development takes time. It will be ready when its ready. The same for a lot of software developers.

That´s true. Development takes time but NL is sellling MR and the connectivity plugins as working software. Just have a look on the website, and you´ll find out that NL is offering the plugin without any limitations.

[sidenimjay]

is anyone taking into account that this plugin may NOT be being written by a programmer at NL?

there is an sdk out there.....and people are writing pulgins using it. not every plugin is written by NL, or by extremely knowledgeable programmers. the sdk was only released about a month or so ago and there are some very MAJOR changes to the way the code works, especially where mxm is concerned. further it has been more than a year since anyone has had the chance to use the maxwell sdk, takes a bit to refresh the memory especially when the code can be some 3000+ lines long.

perhaps people are yelling at the wrong list of programmers.....programers have feelings too.....but they hold the key so i would advise against being overly rude or perhaps they wont be generous, especially if they arent being paid to make the plugin

i wrote the houdini plugin in my SPARE time of which there is very little. i am not being paid and dont have to release it, but i want the houdini community to embrace maxwell and vice-versa, not to mention for my own purposes of using the two together.

perhaps i am wrong about the C4D plugin, maybe it is written by NL....perhaps they owe it to those who bought maxwell....but if its just a simple person as myself that is learning the sdks of two packages it can take a bit of time.

just food for thought...

[zoetropeuk]

is anyone taking into account that this plugin may NOT be being written by a programmer at NL?

there is an sdk out there.....and people are writing pulgins using it. not every plugin is written by NL, or by extremely knowledgeable programmers. the sdk was only released about a month or so ago and there are some very MAJOR changes to the way the code works, especially where mxm is concerned. further it has been more than a year since anyone has had the chance to use the maxwell sdk, takes a bit to refresh the memory especially when the code can be some 3000+ lines long.

perhaps people are yelling at the wrong list of programmers.....programers have feelings too.....but they hold the key so i would advise against being overly rude or perhaps they wont be generous, especially if they arent being paid to make the plugin

i wrote the houdini plugin in my SPARE time of which there is very little. i am not being paid and dont have to release it, but i want the houdini community to embrace maxwell and vice-versa, not to mention for my own purposes of using the two together.

perhaps i am wrong about the C4D plugin, maybe it is written by NL....perhaps they owe it to those who bought maxwell....but if its just a simple person as myself that is learning the sdks of two packages it can take a bit of time.

just food for thought...

Damn, the excuses from Next Limit supporters are just get more lame all the time. Next Limit sold Maxwell Render to the majority of C4D users based on the promise of a working plug-in. It is Next Limits legal responsibility to provide this or offer a full refund.

I don't care if a bunch of blind monkeys are programming it as long as it's what's promised. And if the C4D plug-in developer isn't a part of Next Limit than this is utterly disgraceful and Next Limit need to PAY someone to do it. If I was told that the plug-in was to be developed by some stranger in his spare time then I would have spent my $495 on strippers and beer.

PS I've emailed Next Limit on numerous occassions requesting updates for the OS X SDK status and I've NEVER had a single reply

Matt

[Rochr]

Next Limit sold Maxwell Render to the majority of C4D users based on the promise of a working plug-in. It is Next Limits legal responsibility to provide this or offer a full refund.

My thoughts exactly.

[sidenimjay]

let me start by saying ,pardon me for my "lame excuse" and for being a supporter instead of a basher, i understand now that support is not needed. i must have missed the part of the purchase agreement that stated NL had any obligations to provide any plugins for any package let alone all the 3d apps in the world.
foolishly, i thought the stated goal was that they were going to make a 3d standalone renderer called maxwell.

furthermore, i am now aware that there is no point in trying to help people that cant program, and arent as adventurous as we blind monkeys that foolishly waste our time to make our own plugins and offer them to the general public, understand the nature of the beast.....

besides, seeing how there are no other ways to render in maxwell other than through a plugin, my eyes are open now to see that it is much better that every 3d app in the world work with maxwell before we get really useless things like dislpacement and camera motion blur.

Dammit get busy NL, stop wasting your time on useless programming on the core engine!

so please bash away, im sure it will eventualy reach those deaf ears

thanks for the enlightenment

[Rochr]

...i understand now that support is not needed. i must have missed the part of the purchase agreement that stated NL had any obligations to provide any plugins for any package let alone all the 3d apps in the world.
foolishly, i thought the stated goal was that they were going to make a 3d standalone renderer called maxwell.

Oh, support is very much needed, but it´s non existant. At least from NL´s part. I think i´ve recieved 1 answer from their technical support, but that was a very long time ago.

And no, Maxwell was initially sold as a fully featured plugin for several applications. The standalone popped up out of nowhere much later on, at the same time they decided to re-write the engine.
Too bad no one seem to have a copy of NL´s old webpage. Some people would need a reminder on what product was actually sold at that time.

Personally i have absolutely zero use of a standalone renderer, nor did i buy or payed for one. I payed for a plugin, and that´s what i expect NL to deliver.
Better yet, separate the core from the rest, and sell Maxwell as two separate products, Plugin and Studio. That way, the plugins would hopefully get some attention, and i wouldn´t need to waste harddrive space on Studio.

[sidenimjay]

rochr,

sorry for the confusion on support, it is desperately needed from NL. the support i was refering to is "my" support or any end users support for NL and the programmers there, now NL certainly doesnt need that.

i have no use nor desire for 3d studio max, and as far as the alpha stage of maxwell that i bought into back towards the end of 2004 , was and always has been a command line renderer with the intention of having an sdk that would allow for any plugin to be written.

first they had a small list of programs that inflated to include a huge number of programs, most of which were added because someone mentioned they could make the port. houdini was on their list due to the fact the guy that made the real flow port said he would do it, but was only available after i took the initiative. NLs first mistake was to inform the
general public what programs would be supported without having an sdk ready or the plugins in hand

this is soley from my memory banks , which seem to fail a bit more the older i get, but as an animator at Sony at the time, i recall looking for a standalone renderer in as much as renderman is, only better for rendering global illumination. maxwell was offering all of that and nothing more.

but maybe i am wrong.....

anyway im out on this one......i have things to render and clients to please

[Rochr]

A misunderstanding from my part about the support issue then. Sorry about that.
Yeah, you´re probably right, but problem is that when people are meat with nothing but silence from NL´s part, they grow tired of trying to help out. Perfectly understandable.
And i don´t believe anyone is blaming the programmers here, only NL and their poor customer relations.

You may be right about Maxwells history as well. You obviously bought it at an early stage. However, the deal at the time i made my purchase (june -05), was a fully featured plugin. If there would´ve been anything about a standalone, i would never have bought it.
Guess i´ve learned my lesson. It was certainly the first and last time i bought beta software, and definitely the last time i bought anything from Next Limit Technologies.