Combustion 4 Bugs

#1

We were suffering from Combustion`s bugs, and we were hoping that they would fix it with combustion 4…well, they didn’t…

#2

Well, I did download the demo of C4 yesterday and tryed it today. My main consern was using Maya .iff files. So I just loaded some rendered sequences and tryed to browse though the frames and it didnt crash as it used to.
Some nice new features like the resize operator is interesting.
I’ll try to test it well and give you my feedback.

#3

What were these bugs? No one can really help you if you don’t explain your problem. If you were to post a specfic bug list someone may be able to help you, or atleast provide some workarounds.

The resize operator is not a new operator, it was in version 3 and 2. Unless you are refering to another feature/operator.

-Eric
#4

It was there? What a shame, I didnt see it before:sad:

I just found out about when I read the New features of C4

[i]

  • Fast GBlur - optimized, high-quality blur filter with constant-speed
    rendering independent of blur radius
  • High Quality Resize includes Lanczos and Mitchell filter options
  • Capsules - organize your creative workspace by grouping multiple
    [/i]
#5

Sorry to say, but for a program made by one of the most legendary editing and compositing software developers I’d have to say - based on all my experiences so far (with combustion*) - it has been a huge dissapointment…

It seems discreet is making the same mistake as Microsoft does: They keep on adding new features, but seem to care less (?) about the reliability (affacted by these kind of bugs). Having these bugs isn’t even such a great luxory, because speed isn’t on combustion*'s side either. At least if, say, NUKE crashes… you’ll have it up and running in less than a few seconds.

I hope some day discreet manages to create a compositing package, for x86 Windows/Linux platform, that resembles it’s legendary flame*/flint* (even without HD I/O, it’d be great).

#6

Those filtering options were not available before, but the operator has been there.

-Eric

#7

That’s why I didnt find interesting to use the resize operator until I forgot it’s there, and after I started playing with Shake I was wondering why we dont have something like that in Combustion.

#8

Combustion only have bugs when you have wrong hardware.
try a different machine. maybe your problem is solved

#9

Toxik enter stage right?

#10

I’ve just ordered Combustion 4.0 and the currently playing with the trial version. I haven’t had any problems. I am running it on a 3.2GHz P4, 1GB RAM, 256MB Nvidia Quadro FX 3000 with the driver set to Combustion.

#11

Yes, they even have released specifications and screenshots of it recently (which can be found here: http://www4.discreet.com/toxik).

#12

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.