32/64bit AB4.0b install

[aldred2]

Can somebody tell me how I can install AB4.0b into both 32bit and 64bit max on the same computer? I've tried all kinds of combinations of install, custom install and modify, but they just won't go in cleanly.

Thanks
Mark

[sitnisati]

Mark, you can't install both 32 and 64 bit under 64 bit windows. It's a limitation of windows installers - it can't install same application twice.
We are looing for a workaround.

In a day or two we are going to post plugin file packed in a zip file, primary for users that wants to easily deploy files
on network and do not want to mess with installers.

Regards,

Kresimir

[jrand]

In a day or two we are going to post plugin file packed in a zip file, primary for users that wants to easily deploy files
on network and do not want to mess with installers.

Regards,

Kresimir

The would be FANTASTIC! Thanks, Kresimir

[unexpected]

So what's up with the workaround???

With AfterBurn 3.2c it was possible to install it for both bit-versions, so why it's so different in 4.x?

Hard enough that we needed to update our FumeFX to 1.2 to have the same problem with choosing between x32 or x64.
But very annoying that we also have to buy an upgrade for AfterBurn now, because 3.2c isn't working with FumeFX 1.2.
And what for? To be limited to one Max BitVersion also?!

This can't be your intention. Please work on a solution and do it fast.

With regards
unexpected

[jrand]

Well because people were sick of waiting for Turbosquid to assemble the installers (the last round took around a month after the update was complete), also not sure if you noticed or not but the ffx 1.1 installers for max9 and max2009 were messed up. So Sitni Sati is making there own installers, of which I for one, am glad they are doing

Not sure about the ab 3.2c and ffx 1.2 issue, although AB 4.0 now uses the fusionworks engine instead of the old ab render engine, so both plugins will render simulatiously, as opposed to the prior afterburn would crash or throw errors.

Also note there is a manual install in the files section, which suits me just fine. If you have thirty machines to install across write up a quick batch file to install.

[unexpected]

Hello jrand,

thanks for the hint of the manual install-packkage in the files section. It looks interesting.
Don't solve the problem that you have to buy the AB4.x-Upgrade if you need to use FumeFX1.2 (because of the fixes), but maybe it will make it possible to use 32 AND 64 bit on the same computer. I will check it out.

[sitnisati]

Don't solve the problem that you have to buy the AB4.x-Upgrade if you need to use FumeFX1.2 (because of the fixes), but maybe it will make it possible to use 32 AND 64 bit on the same computer. I will check it out.

AfterBurn 3.2 is an obsolete version which means it's not supported anymore.
Now having both 32 bit /64 bit 3ds max and plug-ins with 3ds max released each year cost us developers a lot of time
to build, test and maintain and it would be simply impossible to support all old versions to work with new version of plugins and new versions of 3ds max and on new operating systems and to do this free of charge.
We try as much as possible to keep compatiility as long as possible, but sometimes we have
to break compatibility to be able to add new features.
With Afterburn 4 and FumeFX 1.2, we have added max script access to AFC and Gradient controls,
which caused a break in afterworks.dlu.

Best regards,

Kresimir Tkalcec

[unexpected]

and to do this free of charge

but sometimes we have to break compatibility to be able to add new features.

I understand that and I don't won't to slam your work.

But if you have two units working on different jobs at the same time and one unit is happy that needed things are fixed in FumeFX1.2, then it's very annoying if you realize that you can update only half of the renderfarm because of non-working AfterBurn which is used by the other unit. Or you have to upgrade AB which isn't an good option in the middle of a job. Maybe the changes between AB 3.2 and 4.0 are too big and you have to render the 3.2-pictures with 4.0 again and that isn't possible because of deadlines.

Maybe you can understand this uncomfortable situation. ...bad timing of our jobs having AB and Fume at the same time. :wink:

If unit 2 is done we will upgrade to AB4 to be save.

[sitnisati]

There is a difference between AfterBurn 3.2 and AfterBurn 4.0 rendering, so I do
not suggest that you update in the middle of the job.
However, with few tweaks, you can get your AfterBurn 4.0 rendering to fly using AB Shadow Map
in constrast to AfterBurn 3.2 - maybe it's worth to try it ?

Regards,

Kresimir