A xStream user told me she has problems opening the vob files I created in Infinite. I could imagine that lower versions can't read files created in higher versions, but this is the other way round and it's just weird. She said she has this problem frequently with objects from various sources. We are both using Version 6, so it can't be version-related. I've no idea where this problem comes from and what to do about it. Any suggestions?

Quote - We are both using Version 6, so it can't be version-related.

It still might be, as you need to compare the full build number as there can be problems using content saved with a higher build number with a lower build number (this is the source of many problems with C3D content).

Also without knowing what the errors are, another possibility is that the VOBs depend on content you have but your friend doesn't.

Not a version problem at all. I have had the same issue with someone else i wanted to use for a BETA tester for my models i never released due to the lack of a beta tester. I run 6 Infinite, and she runs XStream. Same builds (or both most up to date builds anyway) XStream is buggy as a sewer rat.

Quote -
another possibility is that the VOBs depend on content you have but your friend doesn't.

It's content I made myself, my Gladioli sold here in the marketplace.
I will ask her to check the build number.

@Trepz: I could betatest your models in Studio Pro and Infinite if you are still looking for a tester ;)

I had the same problem with the same lady as you Paul !!

BTW, I could also beta test for you if you needed a 2nd opinion :)

Yer all talking about me here :p

I might as well spill the built number in here so you all know ;)

I'm running version 6.05-04 Build 289768. I've got all the patches and fixes (which I might add is far from fixing everything).
There.

And the error I get is a read error. xStream simply tells me that it is unable to read the .vob and that's it. No further messages or anything.
I rarely buy .vob files for this reason, but when I do I can usually open them.
It's all down to random as it seems. Just like most things with xStream.

C.

I also asked in the Cornucopia forum, they don't seem to have any idea at all about how to solve this problem.
But I think I can offer you a kind of workaround, check your PNs ;)

Thanks Sabine...I appreciate your help :)
And no one ever seems to know why xStream acts the way it does...it's almost as if it was built by aliens from another planet :p

C.

Oh Ms. Modestnevercomestotheforum thinks we're talking about her...:D WELL WE ARE SO THERE:D If e-on doesent know the problem, then i dont think it is going to be ficed any time soon(;

-Paul

Oh, e-on is going to hear about this problem from me, I can guarantee you that.
I've already found and reported another bug. Given that the Gladioli are my first Vue product and now I've noticed two bugs already this is slightly alarming. It makes my enthusiasm for Vue cool down quite a lot.

Well, good luck in your endevors, If a few bugs scare ya then Vue certainly isnt for you:D

Quote - ... I'm running version 6.05-04 Build 289768. I've got all the patches and fixes (which I might add is far from fixing everything).

The latest XStream is 6.60 - Build 292711 (it's about 2 months old). It's always a good idea to check the Eon website for updates rather than relying on the check that Vue does (which is known to miss things).

Now we need to know the Infinite build number to check against.

My current Infinite build is 292711. But I made these objects some time ago with the previous build. However, vendors can't be expected to update their products every time a new build is released. The software should be able to read older files correctly, especially as they use no "exotic" settings or features.