All posts relating to Maxwell Render 1.x
By ajlynn
#226534
My old MXS files still work... have you tried the previous version of the plugin with 8.5 and MX 15.?
By shnerp
#226537
Still waiting for the email..
Anyone out there try the xsi plugin yet?
Is it even released?

Steve.
User avatar
By michaelplogue
#226557
Rochr wrote:
lllab wrote:there are several programming reason why support for older c4d version is difficult and problematic for 3rd party engines. to not support 8.5 is not realy nls fault. 9.6 is the earliest version which can be supported in a usefull way.

cheers
stefan
Funny that the last version worked with 8.5.
It would be a completely different story if this would´ve been Maxwell V2, but it´s still an 1x update.

I stick to my opinion about the cash.
I'm going to have to side with Rochr on this one. Even though I don't use C4d, whatever was supported with 1.0 should be supported throughout the 1.x releases. If I were in the c4d 8.x users shoes, I'd be pretty pissed as well. Basically, they are forcing early buyers of MW to spend even more money to upgrade their 3d applications because they took so long to come out with updates. Bad form NL..... Really bad form!
User avatar
By michaelplogue
#226563
[double posting] :oops:
Last edited by michaelplogue on Thu May 24, 2007 12:47 am, edited 1 time in total.
By big K
#226565
you have to consider that many c4d users (like me) demand a better plugin and integration and this might only be possible with cinema 9.6 and higher.

but i agree that a basic plugin should be available for older versions, so that people are able to use their software.

michael
User avatar
By Axe
#226566
Note also that Rhino 3 is no longer supported. I was basically forced to upgrade to Rhino 4 to continue to use Maxwell.

Not good form, but I can understand if there's significant changes to the host application that make it no longer compatible with older versions. Luckily the upgrade cost for my version of Rhino wasn't prohibitive, but I'd be upset if I had to pay $$$$ to upgrade more complex applications such as Max.
By lllab
#226569
well i have the development of vrayforc4d
my c4d programmers told me there are many problems with the c4d sdk prior to 9.6. we also cannot support older version reliable. so i understand when nl has to skip older c4d version to make the c4d plugin better.

cheers
stefan

edit: yes the idea of keeping an optional simple plugin that is more backward compatible is probably the nicest way, thats true.
User avatar
By MetinSeven_com
#226577
Anyone tested if Maxwell and the Max plug-in is truly 64-bit? In the Max 9 64-bit plug-in I can't increase the memory spinner beyond 2048 and the main 64-bit Maxwell suite installs itself in the x86 folder.
User avatar
By Rochr
#226601
lllab wrote:well i have the development of vrayforc4d
my c4d programmers told me there are many problems with the c4d sdk prior to 9.6. we also cannot support older version reliable. so i understand when nl has to skip older c4d version to make the c4d plugin better.
Fair enough, but at the time i bought Maxwell, 8.5 wasn´t old.

Next Limit stalls, and the customers have to pay extra for it. Nice...


Btw, thanks for the support Michael. Appreciated.
Last edited by Rochr on Thu May 24, 2007 1:27 am, edited 1 time in total.
By lllab
#226609
well yes i understand your concerns. i just wanted to point out what could be. (at least for vray it is)
cheers
stefan
By ajlynn
#226693
Ummm... anybody actually using the Cinema for OSX plugin? Mine just crashes...
User avatar
By dd_
#226820
if people bought maxwell early when it supported 8.5 then imho they should get a simple plugin that would atleast get them into the studio. its not thier fault there was delays, the other solution is a refund as they cant supply what was initially on offer to them. many of my clients are still using c4d 8.5 so there are still loads of users out there that dont wish to upgrade their c4ds.
User avatar
By dzowada
#226831
MetinSeven_com wrote:Anyone tested if Maxwell and the Max plug-in is truly 64-bit? In the Max 9 64-bit plug-in I can't increase the memory spinner beyond 2048 and the main 64-bit Maxwell suite installs itself in the x86 folder.
Yep, 64bit.

The spinner seems to mean NOTHING.

Check out:

http://www.maxwellrender.com/forum/view ... hp?t=22955
User avatar
By Mihnea Balta
#226856
32-bit DLLs can't be loaded in 64-bit applications so since the plug-in loads, it's 64-bit. :)

If you're talking about the "Max Physical Memory" spinner in the global render options, that's only for the "use hard disk" option. I'm sorry that the name is misleading (and that it's not automatically grayed out when "Use Harddisk" is off), but it doesn't affect normal rendering in any way.
User avatar
By Kabe
#226873
big K wrote: i agree that a basic plugin should be available for older versions, so that people are able to use their software.
Well, in a way it is available:
The old plugin works fine with the new Studio afaik.

NL also had to support R10, and at some point you have to choose.

I said literally years ago, that sticking with 8.5 is quite an limitation when it
comes to support an external renderer. They are not crowded with people
doing the Cinema plugin - and compared with the Maya plugin it's still a bit
basic.

If they would stick with 8.5, a lot of development capacity would have been
wasted to write code for the bin. Nobody likes to do that.

Kabe

> .\maxwell.exe -benchwell -nowait -priority:[…]

render engines and Maxwell

You could be right about AI, but actually I prefe[…]