I have been trying to export a vob and get errors and crashes when trying to export as a obj or 3ds file.
Anyone tryed to export using Vue 6 Final yet. :(

Hadn't tried it but just did for you:

obj started then stopped at 36.5%

3ds started hardly at all, no percentage showing.

neither would go any further, had to cancel but didn't get a crash!

Shame so much stuff don't work with Vue 6 Inf as advertised to be in the final. :(    What else we going to find wrong......................?

Yep, I noticed that Monsoon has noticed some issues too!
There seems to be more and more peeps starting to see issues now!

I'm not really using it much now until the fix comes out, shame really 'cos I was using the pre-release every day and doing some BIG scenes with it too!

No problems here>>>>>>>>>>>>>runs to hide now :) Tried both 3ds & obj.

I will try some more models tomorrow. :)  Thanks.

Did you people check Save colored maps and bump maps as jpg when exporting.
 If I do this I crash.

I can export if I dont make these settings but when I bring model into poser it does not have an textures. :(

I tried both .bmps & jpgs & no crash - however importing into Carrara the .obj was willy nilly - 1 time textures there, and  another item no. 

Hmmmmmmmmm I got to find why I can not export when setting to add color jpgs . :(

If I dont click on add a color map or bump I can export and obj.  If I select these two boxes I get a crash.   Any ideas what may be happening or what files are involved that I may replace for this odd behaviour.

thefixer have you tryed exporting any more.
  I did a clean install of vue 6 and still get errors when exporting.   If I dont check the color maps I can export but end up with a plain jane obj with no textures.

 I can export with Vue 5 inf and check maps and have no problem exporting same obj.
   What I dont understand is some dont have a problem.   I would like to narrow down where my problem is. :(

New info & a possible clue.  I dumped poser6 today & just have Poser7 on my machine now.  Now I can't export at all :blink:  I don't know what this would have to do with P7 but it appears it does.  All was fine until I loaded P7 - cripes.

I can't post a tech ticket because there DB is fubared :cursing:

WOW! Something else a bit off with our new and improved VUE6F?

Sarcasm aside...@ iloco...what exactly are you trying to export to .vob? If it's a Poser import, since  I own most of their store...geeee, wouldn't a nice 60' Plasma TV look better here in my playroom?...LOL...I could try and replicate it for you?

Steve

Just realized upon returning here that Poser doesn't really have a store 8*)...but what I meant was I do have most everything from DAZ and RDNA (pre--cutie/G2 days) so I could help you out there.

I did import  Transponds' Western Church from RDNA and tried to export it....maps checked...and VUE6F locked up on me. Checking  in 5I now...

Worked like a charm in 5I...in less than two minutes I imported the same item, saved it out as a .3ds and had it reloaded!

This is working with POSER 6...

Steve

@Iloco: Haven't tried again, I'll see if I can today without those things ticked. I'll let you know!

@Iloco Confirmed, if I export without colour or bump maps then there isn't an issue, as soon as I select them again it doesn't want to know!

Lets face it, Vue has never been great at exporting...and when it did, UV's/textures were usually screwed and the mesh triangulated to kingdom come. This bug is no surprise to me, but then I never export from Vue as it just doesn't meet the mark.

Ceers

Thanks thefixer and dlk30341 for now confirming it may be a poser 7 and vue 6 problem.

spider1313 we are having an export issue out of Vue 6 final using saved vob to export.
I can export with vue 5 inf and dont hve the crashes I am getting with vue 6 Final. :)
  
 I had not thought about it but looks like dlk30341 may have narrowed it down to a poser 7 and Vue 6 final problem now.  Now to see if e-on can confirm and see if its a poser 7 or Vue 6 problem.

 Cheers you are 100% right about Vue and its export problems.  But  everyone wants to blame it on something else so I got tired trying to get anysone to help solve the problem and make it better at exporting. :)
 I dont export that much but when I try a feature and Vue crashes I like to know why is why I am keeping at it on this problem. :)

 Why so many things get by beta testers is what I have yet to understand...........?

WEll its a shame the data base is as screwed upl.   This is so agravating when can't post a bug report because of a messed up dataa base.   I am wondering if they thought to save a backup................Hmm
 I thought Vue 5 was bad but I dont think it can leave up to what is going on now.......

I sure hope they get us a good patch so can start making pics instead of beta testing a final release. :)

Actually Iloco, I was using Poser6
I do have 7 but Vue points at 6 for the minute because it doesn't do Poser 7 imports that well!!

Yes thefixer it is seeing the poser 7 installed someway I think.   I also have poser 6 still installed use till I am 100% sure poser bugs have been fixed in poser 7..     It just being installed tells me there is a conflict with it and vue.   I also have vue pointed to poser 6.

As dlk 30341 has said after installing Poser 7 I am now quite sure the export thing is related to the install of Poser 7 being on out computer.

If they would fix the data base so can post to tech at e-on I will report and see what they have to say.  Seems get one thing fixed and get two to take its place........ very annoying. :(

The ones who have reported no problems I bet don't have Poser 7 installed. :)

Hmm! good point Iloco.

I got a gopod reply back from tech support on this problem and they were able to confirm the problem.

This is a good example of it works for me so it should for you that we hear so much.  Some dont have the vue setup as with us with problems like are we using the same build, do we have the same version of poser installed and do we have the same SR1 installed as well. 

 Here is reply from tech support:

QUOTE:   Hi William,

I was able to reproduce the error. This should be fixed in the new update.

Since you opened two reports on this issue, I have taken the liberty of closing the other one. This one contained the information I needed to reproduce the error.

Best regards.