Ozone is a killer

[kromekat]

Sav - I feel your pain - I have no idea how to resolve the issue though I am afraid.

You haven't got any backups from an earlier stage then? - it's well worth having Cinema save at least one or two, so that you always have the previous pair saved for such an eventuality. :/

Hope you can rectify the problem though.

Adam

[hentsteph]

I've had several of these proplems and everytime I had to start over... now I put Ozone 3 as the last element in my scene and make very little changes after :shrug:

[Rantin Al]

Was there any possibility of a rescued file in the bug reporter folder?

If the Merge File command doesn't achieve anything, I'd say the file is corrupt and you are stuffed.

The horse has bolted but it is a sore lesson in using Save Incremental every half hour or so. :shrug:

Sorry, Alan.

[boxy]

Thanks guys. I usually make regular incremental saves but y'know, haven't slept for about 48 hours so I guess the old grey matter let me down there :) Guess I can only start again and accept the consequences for being late. Cheers anyway
Boxy

[kromekat]

Have Cinema do it for you automatically from now on! :)

Adam

[boxy]

Thanks Al, it actually crashed while I was saving my first incremental file so though there was one in bug report, it too wouldn't open, so good old Ozone managed to corrupt 2 files at once :S
Thanks Adam I agree, its a must now :)
Cheers
Sav

[ooo]

Thanks for the warning, and I feel very sorry for you. I really hope there will be a satisfying bugfix soon :shrug:

odo

[Per-Anders]

If it's working as a plugin then remove Ozone from your plugins folder before starting up Cinema and attempting to open the file. Unless it's competely screwed up the file structure the file itself should open correctly now with just a ? where Ozone would have been, resave under a different name.

[boxy]

Thanks guys. Guess I have to put it down to a learning experience and move on. It is just frustrating because I love the plug in, but that is clearly not acceptable that it destroys ones work when in a tight deadline situation :)
Per I tried that but just got an error message saying 'unable to position in file', so I guess the fie is corrupted.
Cheers
Boxy

[ThePriest]

Ozone - XStream - are both notorious for saving 0byte dead files.
I can physically make it crash very easily and I've sent files to E-on
with no joy. Not a single update has fixed this easy to achieve crash.

[boxy]

Well I guess I have been spoiled, but never before have i come across an app that destroys work. I guess the only way I can do my part to fix it is to keep letting them know.
Cheers
Boxy

[kromekat]

It's quite remarkable how eon have managed to find their software in the hands of people like ILM I think, because the whole Vue line seems to have been bug ridden for years - I have never come across so much instability in an app.
XStream is completely unusable in my opinion, and although I have suceeded in creating final images with Vue Infinte 6 on it's own, it has generally been with a great deal of persistance because of random, and often hugely destructive crashes, that have also managed to take my entire Mac OS down and required forced shutdowns - thats quite an achievement by any developers standards! :(

I guess it could be argued that what Vue is capable of achieving is so good, that it should be expected that it would have some issues, but even as I write that, ...I don't believe it one bit!!

:/
Adam

[Shademaster]

You could let Cinema make Backup copies every so often, it will create a *scenefile.BAK* file. Hope that helps!

[boxy]

It will help :) Thanks. I do find it quite astonishing that such serious bugs have never been addressed, I'm no programmer, but I imagine being able to safely save a file is a basic priority :S
Anyway I guess this isn't an eon forum so I will shut up now :D
Cheers
Boxy

[ThePriest]

It's not my intention to give E-On a bad name, they've
got a very powerful tool with huge potential, that's prone to crashing.

Max was the same a few years ago and its popularity certainly didn't
wane. Perhaps we as Cinema users are somewhat spoiled by our
sturdy application.

@kromekat

I can see how ILM might have used it - Limited choices!
And when you do get Vue to play nice, it's simple to use and very powerful..

We speak of these big fx and production companies as though
the CG God's would have granted them only crash free software,
where as in reality I'm sure they suffer the same woe's
as the individual artist does.

[rsquires]

I am sorry but I don't see how a company can do business when it's product is woeful. I bought Ozone and had it crash consistently when trying to use the spectral rendering. This is the only reason I bought it as the skies are incredibly realistic, although admittedly this does produce a big render time penalty. But I could live with that if it didn't crash cinema and just freeze it for no reason. I tried to report the problem but their support is designed to be as unhelpful as possible. If you have ever used an eon product you will know what I mean. There is no friendly forum with representatives from the company actively helping out the community of users, like many of the apps I use. Silo is a good example of that where support and tips are always readily available. So I have given up on it until such time as a fix surfaces. Which galls me when I paid good money for what is essentially a dud.

grrrr rant over

back to work

rich

[kromekat]

@kromekat

I can see how ILM might have used it - Limited choices!
And when you do get Vue to play nice, it's simple to use and very powerful..

We speak of these big fx and production companies as though
the CG God's would have granted them only crash free software,
where as in reality I'm sure they suffer the same woe's
as the individual artist does.

I agree, but when the software proves SO unreliable, it's surprising that a company with such a huge software resource (ie: bespoke tools, or custom enhancements of primary pakages) would risk the delays to their workflow on tight deadlines!

I guess they might just have been lucky the week or so they used it on Pirates II!? ;)

Don't get me wrong - these are potentially great tools, I just don't see how they can release them in these states, when the overall experience seems to be that they are not only unreliable, but potentially dangerous to exisiting files.

:/
Adam

[AdamT]

I agree, but when the software proves SO unreliable, it's surprising that a company with such a huge software resource (ie: bespoke tools, or custom enhancements of primary pakages) would risk the delays to their workflow on tight deadlines!

I guess they might just have been lucky the week or so they used it on Pirates II!? ;)

Don't get me wrong - these are potentially great tools, I just don't see how they can release them in these states, when the overall experience seems to be that they are not only unreliable, but potentially dangerous to exisiting files.

:/
Adam
My guess (and it's nothing but) is that they had at least one e-on programmer on hand doing TD work for them during production.

[rsquires]

Hi guys

just thought I'd keep you in the loop so to speak:


The e-on software support technician responded:
Hi Richard,

We've fixed these random freeze. They were indeed caused by locking mechanisms between threads. We successfully rendered a variety of scenes with the fix and no lock occured.
The next update, which should be released soon, will include this fix as well as a few others. Thanks for your patience.

Best regards.
Ben Lewald

Let's hope the update comes soon

regards

rich

[hentsteph]

That would be a well worth update...

[MikeS369]

I had the same thing happen to me while demoing Ozone a couple of years ago. Check your file and see what size it is. Ozone completely wiped out all my data and there was no way to recover it. I won't even look at Ozone anymore.

[Triker]

This thread has saved me a lot of headaches, as I was going to buy Ozone 3. If, and when, it ever works properly I am ready to give it a try.

Vue 6.5 has been pretty stable for me and I really like the skies it produces, so for now I'll just render them out as HDRi and use them in C4D that way.

Sorry for all the suffering the early adapters have to go through, but it helps others make business decisions.

I did the pre-order deal for Vray for C4D and have much more confidence in that product launch. Hard to believe a couple of folks can do a better job of software launch than a large corporation. IMO it says something about integrity vs greed.

[ooo]

Hi guys

just thought I'd keep you in the loop so to speak:


The e-on software support technician responded:
Hi Richard,

We've fixed these random freeze. They were indeed caused by locking mechanisms between threads. We successfully rendered a variety of scenes with the fix and no lock occured.
The next update, which should be released soon, will include this fix as well as a few others. Thanks for your patience.

Best regards.
Ben Lewald

Let's hope the update comes soon

regards

rich

Thanks for the headsup Rich!
This gives me at least some hope for the usability of Ozone. Nevertheless they should have fixed this before release.

odo

[boxy]

Thanks for the heads up. It will be great when its stopped crashing :)
Cheers
Boxy

[CGTalk Moderation]

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.