Is Version Cue worth having?

We are looking to upgrade our existing Adobe packages. We only really use InDesign and Photoshop (Illustrator is not used very often) and we already have upgraded to Acrobat 6. I don't use GoLive at all (preferring Dreamweaver).

So I can either upgrade just Indesign and Photoshop as separate products (and not get Version Cue) or go for the basic CS upgrade and get get Version Cue.

As I won't use Illustrator that often, it makes VersionCue seem expensive, unless it is useful. There are 3 of us in our office, and we do work on the same projects at different times.

As yet, I haven't read if Version Cue is genuinely useful, or a bit of a gimmick. Any thoughts?

No it's really not anything to spend any money on or use period.

It just adds confusion and complications to your workflow.

Good working logic voids the need for version cue even if it wasn't crazy and unimportant.

Adobe would have been better server if it built some more features that are helpful tools and make sure the new versions work properly and bug free.

At this point, I might agree with Joe. I like the idea behind it, but it's problematic, there really aren't any good tutorials to walk you through how it could really be used, and if you have an efficient workflow process already, you may spend more time and energy trying to figure out how to migrate that process to VC. That's exactly where I am right now - determined to give it a try, but getting quite frustrated.
I'd say that the (relatively) low traffic in this forum is testament that probably only a small percentage of CS users have figured out how to put VC to good use.

I'm in a small <10 person package design company, as both a production designer and IT guy, and I've been responsible for our installation of CS since June.

It's been a little bit of a hassle switching to Version Cue, but I think it is totally worth it. The ability to easily view other versions of the same file is incredible, and the comments per version directly help with invoicing and billing of projects.

It is quite a bit different though that more established workflows. We've run into some problems here and there, and I totally agree that there are some really quirky undocumented, or at least not discussed features. Like, for example, a lot of people say that it's super annoying that you can only browse the files via a program's open dialog. This isn't true, but it should be.

The webdav access to each project you create is really nice, especially for doing disk packs (sending files to vendors and the like) because you can drag-and-drop within the version cue file system. But this is a very dangerous feature, becaue if you change things within the webdav interface, it can have horrible effects on your file structure and history.

It really is a trial and error process, and I fully support both the adoption and further development of Version Cue. But I do so with the word of caution because it is _Really_ easy to screw up things.

-Erin Sparling