Hi guys!
Does anyone have any info about the possibility of using Vue7XStream for cinema4d R11 in 64b , on mac/OSX platform ?
I did already ask at Cornucopia, and looks like we’ll might have a chance with Vue8 ?
It’s not that I can’t use c4d in 64bit and comp after the Vue standalone pass, but…
Anyone?
I wouldn’t hold my breath… But, if they do decide to port Vue to native cocoa code on the mac, I hope they take the opportunity to completely rewrite Vue from the ground up, on all platforms.
This software is capable of creating beautiful imagery, but I find the work flow to be absolutely horrible.
Things that are pissing me off about Vue:
Terrain editor… worst written tool in cg history (team that up with the crappy “proxy view” you get in the editor… well, let’s just say I avoid using Vue terrains whenever I can)
Ecosystem painter: indiscriminately paint 50 trees on a landscape that totals 50,000,000 polys and Vue renders like a sloth… but, paint using an ecosystem material… 70,000 instances totally 3 billion polys, and render times are cut by 75%. WTF???
/end rant
back on topic, I hope they do port to 64bit osx and rewrite the core, but one thing that is not gonna happen, which has happened in the past, is I’m not gonna be buying that upgrade until all fronts have posted MASSIVE improvements in stability.
I do have to give E-on credit however, since 7.2 is certainly a massive improvement over 7… so at least their bug fixes now actually fix bugs:) The only crashes I’ve had in the last week have probably been my fault. The days of “WTF?!? All I did was hit SAVE… now it’s crashed and all my files have corrupted” seem to be behind us (crossing fingers/knocking on wood).
kvb
I would love to have a 64bit version of Vue as well for the Mac as others that are well written like C4D and even Modo take better advantage of all the CPU and memory. However, as most say, that is not likely until version 8, if even then.
In terms of it crashing a corrupting your files, that should not be happening. I have never had a crash on any software, such as Vue, C4D, Poser Pro, etc. that damaged a file. Yes, I have had crashes at times, but the files always were OK, unless of course it was the first time saving. Do you know what caused them to be corrupt? I just have never seen this out of all the times I have used 3D software or most any other program.
I have Vue files become unopenable after a crash during a save, and 3ds max is notorious for this.
2 cents
Be prepared Jeff, you’re first corrupted file is on it’s way. Stock up on four leaf clovers and replace all your furniture with wood furniture:D The cat’s out of the bag now, don’t let sleep under the ladder, man:D
But in all seriousness, yes, Vue had(has?) a bad habit of corrupting files. Mostly with v6 xstream when working xstream side in c4d. If Vue crashed, or it crashed c4d, it would commonly corrupt not only my vue files but also the .bak files and even the c4d files they were linked to.
The problem was so bad that one time, I had opened a whole bunch of files in xstream, subsequently closing most of them. After a while I got a crash with an xstream file open. Later I discovered that every last file I had opened during that session was corrupted by the crash. So I went to get really drunk with some friends, got a call that my friend died earlier that day, then got in a fight with my fiance and she ripped my favorite shirt. So, yeah… good thing they nipped that bug in the butt, cuz it was turning out to be a real doozy. :eek:
Seriously though, I have never heard of this as a rule as usually there is something else going on with the hardware/software that causes this. NOTE: I can certainly understand if you were replacing a file with the same file name during a save and this happened, but there is no reason whatsoever this should happen with a different file name. That is why I always do directories of each image/project and save many revisions. The OS and whatever application it is, regardless of Mac/Windows or software should NEVER be damaging any files not in use at the time of the save. Certainly, your “.bak” and others should be just fine unless they were in use as I state and that should not be the case unless you had those open too.
I am not saying you don’t have a problem, only I have never heard of this in any support forum or even a general computer tech forum in terms of the general issue that you say happens. Otherwise, thousands of computer users would have all their files being damaged for no reason at all when their software crashes. Like I said, if the file is in use or being replaced then yes, possible, but never out of that context.
Just remember, this is Vue we’re talking about here:) Even identical machines can have wildly different results as far as stability. And just because it hasn’t shown up on any support forums doesn’t mean I’m the only one it’s happened to. Chances are those people went directly to E-on tech support with it, a private forum.
But you’re right, it shouldn’t be happening with ANY software.
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.