Vanishing point for camera matching: any chance it's been tuned up to function?

Question

I've been trying to use the VP tool in CS5 to do some camera matching work for 3dsMax. The potential is huge - it is really intuitive and fast to set up in Photoshop, but the exports never seem to work right. The cameras do not line up properly when loaded into Max, or the planes are all over the place (upside down etc) and it only seems to export one grid, no matter how many I've made in VP.
It's a great tool for quick fixes inside Photoshop, but exports seem largely useless right now - so wondering if this is something that is getting a tune-up for CS6, or has anyone figured out how to get something more functional out of CS5?
/b

Answer 1

I should have been more clear: the *expot to 3ds* funcion does not work as designed. I agree VP works well within Photoshop, but why have an export option at all if it is not meant to be useful in other 3D programs?  In any case, reference measures are not critical to the process as long as things are kept consistent, and in fact you can enter a base measure in VP too (although it's of limited value without knowing what the units of measure are, or being able to adjust them).
I'm aware of Syntheyes and the tools within Max, but VP offers a very simple and effective way to do this if only it could output a 3DS that actually matched what you see in Photoshop. Clearly it's able to generate the required data to make it work within there - it really just looks like somethign with the export/conversion rather than the core algorithms etc.
/b