shouted down now. I'm just wondering. For example, what if some new person came by and asked if he or she should consider purchasing Vue 6. (And I said, 'Yes," you'll love it!) Its gotten so that I'm afraid to try to offer any reasonable explanation for basically anything to do with e-on software, or with Vue 6. Its gotten pretty hard to try to answer any questions.

Yes we will quit when we get our version of vue 6 working as lots of others say it works. And NO I dont mean it in a hateful why but why can some have it their way and not want otherrs to have it when it don't work for us.    Is that to unreasonable to understand.

Help us get ours working and we will be as you and be enjoying soemthing as it is now we can not use as we did the prerelase and vue 5 inf.   Why is that so hard to understand that.

If its working for you then you have no reason to be upset.........

Instead of jumping into a thread and saying it  works for me so you dont  have a problem then help us instead of that kind of a reply and dont try to change us from doing scenes as we have in the past with vue 5 inf to doing other things we maynot like to do.    Is that asking to much.  to some I guess it is.

All I can say is - be patient. I know Vue costs money and should work well out of the box - I have no explanation to offer about the whole fiasco of things the final release version broken (and that were working in pre-release). The good news is that e-on is indeed working hard at fixing things. Software development is a difficult process. It is difficult to find a balance between taking the time to fix everything and releasing fixes to make customers and investors happy. There are a lot of little improvements between the beta versions and the final release - it is unfortunate these were eclipsed by the scale of things that got broken in the process. So... be patient... report issues when you are still having them... eventually, they will be fixed. Just looks at Vue 5 - it started as a very flaky version if I remember well, and turned out stable enough that I am still using it when Vue 6 breaks.

forester: If you care to look at some of my replies to potential purchasers of Vue6In [stephaniebt comes to mind] I have actually said on more than one occasion that Vue6Inf is the best bit of software I ever owned and that I would recommned to purchase, but I did however put a however in there in that it might or might not work well for her depending on how she uses it.

I am also on record at e-on tech support in praising the programme gushingly, and if my word isn't good enough then please ask John Canver, he will tell you I have!

That said, and this is the part that some don't seem to want to understand is, the praise I was giving was for the pre-release; since final release it has become a bag of spanners!
Sure I can still use it and I can bring maybe 1 poser character in before I get a resource message [that I didn't get before] and I have to constantly purge memory after ever move or rotation of that figure [again, I didn't before] so whatever you or others say "something definitely changed from pre-release to final" and those that don't accept that, well I don't know what to say!

Agiel I gree with you and think you see what some of us are up against and others are not.
   I can see you know there are problems and yes you are very right about  vue 5 being so flaxy and seeing the same from some it works and some it dont.
 Vue 4.5 pro was a mess untll we got the last update that fixed a big memory leak that shadowwind found and reported that all the tech and others had missed.
 Its a never ending cycle and will proably always be this way with new developings all the time.
  Just glad to see a few do believe a few of us are having reosouce andmemory issues that other beleive we don't have.   Thanks.

I won't deny something went south between pre-release and final version.

My first experience with the final version was this :

• I opened Vue
• added a terrain
• cleared altitudes
• opened the Browse button to final a bitmap to apply to my terrqain
• crashed

That was repeatable. And that was after waiting for the first update after the release.
And that thing has been working since the very early betas I have seen.

I'm with you forester...  It only took 9 minutes for a negative replies to start to fly.  

One of the problems that I see is if like me and vue 5i (that has allways worked for me without a problem no matter how big or small the scene or what I used in it) when a lot of other people where having problems I tried to help but I could not replicate the same faults people where having.

At the time as well as trying to replicate the faults other people where having I tried all day one day to crash vue5I but could not (and on less than 1gig of ram at the time)

In the end I was called a liar to shut up and go away. How do you think I felt about that!

The result is now I very rarely post or try to help anyone with there version of Vue, is that helping the vue community!

I understand peoples frustrations when vue or any program is not working as it should but sometimes just sometimes things do work right and maybe just because someone comes along and says "my version is working ok" that they should not be slamed straight away.

Wishing you all get working versions soon.
videodv.

Now that is being childess baiting others to see how long before they reply.  Havent anyone got more to do than pm or im to set these type of tricks up.
 I guess not, but at least the thread has turned into  one that some are using some common sense in where others have not.

You know its ironic that vue must have a curse on me because I been trying now for 7 hours to get some models uploaded to tech and keep getting timeouts with the uploads when I can upload to myown server with out any problems what so ever.     go figure....:(

If you think about it a minute, we need to hear both opinions.

It is a good thing to know wether something is an issue for everybody, or if it is working for some, or just behaving differently for others.

Every reports count to getting better clues on what is really happening.

It could he hardware related, or software, or an interference with a certain anti virus software... who knows ?

But we need to hear from everybody regardless it is working or not. 

It doesn't have to be in your face or even perceived that way. It is just necessary to know if an issue is happening for everybody. If it is not, we can focus on what makes some systems work and not others.

Agiel, opening the Browse button for a bitmap to apply on a terrain can cause a crash, but it can be fixed. I had to set my data execution settings to allow vue access, so it would stop windows from thinking there was a virus potential. Do you still have that problem? Or did it go away by itself?

I still have that problem ... and Vue is in the exception list of my anti-virus (PC Cillin).

I want everyone to know and hope they read it clearly that I have nothing against e-on or its tech support.   I just want what I paid for the same as others and a working version of Vue 6 Inf as advertised.
 If I am not mistaken it should at least be better than Vue 5 Inf being its suppose to be the state of the art software and a professional version.
 That said I think Agiel is correct in knowing both sides so we can find why it does work for others and not for some.
 If I were a beating man i'd say lots are having problems that are just sitting back because they don't want to voice their opinions because of how some will answer back.   Not unusual at all. :)

For those who have a good working version I say enjoy it and not let the ones like me and others interfere with your pleasure you should be getting from It.   I only wish I were in your shoes and not mine with the problems and then you would not see me replying to try and get mine fixed. :)
  

You know, as I recall, this "us and them" attitude started a few threads back when those of us with the problems were SHOUTED DOWN by the peeps that weren't having problems so to try and turn it around like this is rather unhelpful.

From what I'm reading from peeps that do want to try and sort it out is that it "seems" to be poser related and I'm beginning to get the suspicion that it might have to do with the Poser shader tree function [maybe].

@Peggy: If you'd taken the time to actually read my first response it was actually more positive than negative towards Vue6Inf. Despite the problems I still continue to try to work with it because I still think [once fixed] it rocks big time, for me it has taken over from Poser as my app. of choice which is no small compliment in itself let me tell you!

CobrayEye - I am having that crash as well when I try to open the file browser from Vue to look for a bitmap texture... but the file browser works fine to add an object to a collection.

To be honest - I am getting sick and tired of buggy  systems and software, be it in games that require patches the day they are released because they can't be installed somewhere else than C: or anti-virus that mistake healthy files for dangerous viruses and deletes them for you, and so on...

These days - I spend more time patching things up and looking for fixes online than actually using anything.

I am no luddite but I am seeing myself more and more going back to books, typewriters and crayons if it continues like that.

Agiel, what I mean and this worked for me is to go to the Data Execution Prevention Tab and make sure Vue 6 I is selected. The Date tab can be found be right clicking my computer and hitting properties. Then navigate to Advance, then settings under performance, and it is the 3rd tab called Data Execution Prevention. Make sure Vue 6 is selected for the choice turn on DEP for all programs and services except those I select. Reboot and try vue. It worked for me. If it doesn't work and vue crashes, open vue again and try again. It should work the 2nd time around for sure.

Oh, and I sometimes I feel that way too, but please don't lose hope. Things will get better. I really want to see more of your mythical fantasy renders.

Funny. I don't encounter major problems with VUE inf. No memory leaks, no crashes.
The VUE XStream in conjunction with 3ds max causes more problems and max crashes every now and then. But max crashes every now and then wether you use VUE or any other given plugin... ;-)

I've been application programmer for some years and I know, how hard it is, to program a software, that is mainly errorfree. Impossible? To be honest, we never published one, that was without known issues. Problem is, that an application running on one PC must not on another.
Problems depend on a lot of circumstances, like hardware and Operating system constellation as well as on other installed programs or packages.
Thats why software producers need us paying customers as beta-testers. :-)

CobraEye - Thanks for the details ... it didn't help. And thanks for the comments too. Maybe when I am done dealing with all of these problems, I will find time to do more pictures :)

Damn, I wonder why it worked on mine.

Well i didnt have many bugs or crashes, but I'm probably not "hardcore" enough, i guess i only use a very small bit of vue's potential and luckyly this bit is whats running stable.

Personally I am  very happy with vue 6, but i think its only as i only have it for a few weeks now and just played around a few hours here and there. And I'm still amazed as i come directly from vue 4 and the functions you may already know from vue 5 and dont notice is all new for me.

I'm feeling a bit ripped off when i wanted to install rendercow and wondered why i cant use it - took me quite some time to notice that i need to buy another 30 Euro module "just for network rendering". I can understand that they want money for building up a render farm with like 100 nodes, but this really annoyed me. I read the manual and it describes all stuff how to set it up, but it didnt mention a single word about that you need an extra module for extra money to use it.

But the best thing was when i opened up the new materials and thought like "Ah, paint - cool that they added this" and you select the material and it asks you to buy the materials from cornucopia now. THATS REALLY NASTY! Eon you mean old men, if you dont wanna include a material, then leave it out. I dont pay over 200 bucks for a software that always tells me like "Buy this now, buy that then". This is how these ringtone companies rip off teenagers, but no professional business behaviour. AT LEAST ONE DAMN MATERIAL SHOULD HAVE BEEN INCLUDED IN THAT CATEGORY. Then i could maybe have forgiven eon.

I already thought that i should maybe buy vue infinite, but why waste another 300 bucks? I already bought 3 extra modules and probably i buy infinite for much $$$ just to have infinite tell me what i could get if i buy xstream, eh?

I really feel a bit fooled, but still Vue 6 is my favorite rendering program. Its just delivered with a great "but..."

My 10 cents, i can really understand how you guys feel with having crashes and stuff not working on top of that.

it's not a bug, ist's a feature :-)
Just click the little "ghost" icon in the in the material- or atmosphere browser and you'll never see the cornucopia content again.
easy enough :-)

Quote -
But the best thing was when i opened up the new materials and thought like "Ah, paint - cool that they added this" and you select the material and it asks you to buy the materials from cornucopia now. THATS REALLY NASTY! Eon you mean old men, if you dont wanna include a material, then leave it out. I dont pay over 200 bucks for a software that always tells me like "Buy this now, buy that then". This is how these ringtone companies rip off teenagers, but no professional business behaviour. AT LEAST ONE DAMN MATERIAL SHOULD HAVE BEEN INCLUDED IN THAT CATEGORY. Then i could maybe have forgiven eon.

Quote - That said, and this is the part that some don't seem to want to understand is, the praise I was giving was for the pre-release; since final release it has become a bag of spanners!
Sure I can still use it and I can bring maybe 1 poser character in before I get a resource message [that I didn't get before] and I have to constantly purge memory after ever move or rotation of that figure [again, I didn't before] so whatever you or others say "something definitely changed from pre-release to final" and those that don't accept that, well I don't know what to say!

That's the problem - the code is not the same - windowsXP64 was the beta for Vista.  Saying things worked great in 64 but don't work in Vista is useless.  It don't tell us anything.  THE CODE CHANGED!!!  They went back to the same method (not the same exact code)  - but also made other changes.  THE CODE CHANGED!  It works better for some, worse for others.  To keep harping on the fact the it worked for you in the pre-release doesn't mean squat.  

I have faith that e-on will make it work.  Vue 4 was great, Vue 5 Infinite was awesome, I love Vue 6 Infinite even more.  I will willingly buy version 7 and go through this whole process again.   

Peggy: I have just received a response from John Canver at e-on and he explains some of the difference in it, something to do with them using Poser 6 SDK in the pre-release and now they're using the Poser 7 SDK, means diddly squat to me, maybe you can explain it to me if you'd be so kind.
Incidentally I'm not harping on about it, merely stating a fact that shouldn't be happening, it's like taking your car in for a new spark plug to find when you get it back the engine doesn't work anymore [Shrug].
I don't know why you need to get so cross about it, we all want it to work for everyone not just a few that might have more high end systems, as advertised.
You might say bitching and moaning about it doesn't help and that may be true, but neither does burying one's head in the sand!!

I have faith that e-on will make it work.  Vue 4 was great, Vue 5 Infinite was awesome, I love Vue 6 Infinite even more.  I will willingly buy version 7 and go through this whole process again.   
At last something we agree on!

haegerst, I agree with you 100% I didn't buy any part of a store when I bought Vue 4,5 but fouind it forced on me in vue 6.  Yes forced because I dint want it and dint ask for it.  All I want is Vue 6 and no strings attached.   Another of those behind the scens things we never saw the survey resuldts. :)
 We the customers don't mean doodly squat to some who re running the show....

Just give me vue 6 that works and I an many others will be happy campers. :)

lol.............I love to whin when I think I am right. :)

After the new update the store folders are deleted.

Actually that could very well explain a lot.

Vue doesn't load Poser scenes natively - it has to rely on libraries of tools provided by e-frontier through an SDK (software development kit).
 
This is basically how e-frontier provides access to Poser functions to outside software, like Vue.

So if you assume the pre-release was using the Poser 6 SDK and the final release was using Poser 7 SDK, you could expect things to behave differently as there may be changes between versions of the SDK that could not be expected by Vue.

Again.... give it some time.

The benefit of using the Poser 7 SDK will be a better integration with Poser 7. It's well worth waiting for.

Attached Link: http://www.cornucopia3d.com/newsletter/11/

The survey results have been published in the issue 11 of the Newsletter and are online as well.

Agiel: Is it possible then that I could get improved performance if I point Vue to Poser 7 instead of Poser 6? Or is it not as simple as that!!
I shall try it anyway, nothing to lose!!

I'd second that, agiel. We know that Vue has never been happy with less than syntax perfect pathing, and P7 introduced that virtual path function. No telling what mischief that alone can produce. Plus there's no telling what effect the new feature code is having.... Also, having the MSVC++ runtime installed is -good- idea. From past issues and work arounds I've dealt with, Vue's coders are developers working on dedicated development machines. And like a lot of coders, they assume the user has many of the same things on their system that they do....which usually is wrong. After I do a rebuild and reinstall of my OS, one of the first things I do is place Visual C++ 6 on it. My C coding is all but moribund, but the changes the app makes to the basic Windows OS seems to stabilize a lot of other applications. Including Vue. Others without hooks into the OS it doesn't affect one way or another.

agiel I dont get the newsletter anymore........Wonder why.
   The survey I was talking about is not in that link.     I meant the one which asked for having the store stuff showed in our vue collections that were just advertising gimmicks that a lot of us didnt want.
  If the last update removes it then I am very happy about not having to delete all that spam when I do a reinstall.  :)   good news indeed if that is the case. :)

thefixer I ahve found it makes no difference which poser you point it at.  I have poser 6 and 7 still installed as well as Vue 5 and Vue 6 so can try different experments before reporting to tech. :)

Peggy

Quote - That's the problem - the code is not the same - windowsXP64 was the beta for Vista.  Saying things worked great in 64 but don't work in Vista is useless. 

I agree, and even worse, Vista is the beta for a stable OS in the future. Maybe after the 2nd  Service Pack. I think almost a third of the Vista code is new. And partly erratic, as every new piece of software. For other 3d Applications, like 3ds max, Vista is not one of the supported OS now.

Quote - I have faith that e-on will make it work.  Vue 4 was great, Vue 5 Infinite was awesome, I love Vue 6 Infinite even more.  I will willingly buy version 7 and go through this whole process again.  

I totally agree as well.
Compared to 3ds max (I payed about $5000 for plus environmental plugins), VUE, although it  still has a few errors, is really great.
My max9 installations are crashing every now and then, VUE6 only once a day. Be positive! ;-)
Read the Autodesk max9 (10 times as expensive) newsgroup and you will hear the same protest songs as here. 
New Software is erratic. Thats a fact of life. If one can't accept it, he shouldn't buy it (brand new).

peace ;-)

DaleB - could you explain the above a bit more simply :blushing:  I usually see an error when Vue crashes to a  reference involving MS C++ runtime.

Thanks :)

I want to retract this statment because it was wrong.   STATEMENT:  We the customers don't mean doodly squat to some who re running the show...."

  I got carried away and after thinking about it we the customers do mean a lot to e-on and they re reading these threads even though they being quite.  I apologize for getting carried away and not thinking when typing so fast. :)

Awww, same goes for me i think. As i said before: Vue 6 is the best rendering app i got. I am probably just a bit frustrated as I cant afford the super version with all features any more. WHen i bought my last Vue (vue 4), there were no Pro, Infinite or Xstream versions, i paid 250 bucks and got neraly everything eon could offer. Now i feel like a poor bum as i cant access some cool advertised features. 

Bah, i will amke some money from selling really awesome vue stuff and then afford the XStream version and every single addon that is available.   :P

thefixer and iloco,

There's a new thread here called "BIG PROBLEM: FATAL ERRORS" which has some interesting tips and techniques as contributed by CobraEye, Peggy and Agiel which might be able to help you guys. Just thought it might help.

BTW, Peggy, Agiel and CobraEye, thanks again for helping to support our community by chipping in and helping others.

best, Chipp

Chipp: Thanx for the heads up, the problems I have aren't with rendering, if I can get there it renders beautifully every time, my problem is getting there without a crash.
Moving or rotating a Poser figure makes my resource drop to single figures and then I have to purge to get some back, then move the figure again, purge etc. It goes on like this until I get to the point where I want to render, then it renders terrific with lovely results.

As I've said many times, I love the app and it has taken over from Poser for me as my app of choice because of the lighting and rendering, I just wish I wouldn't have to piss about with purging all the time, if that was sorted I'd be a happy man!

I do appreciate you trying though!!

Chipp I have done all of those tips and tricks and never render a pic over 800 X 600 resolution since getting Vue 6 Inf.  I only use for hobby and pleasure of making what I call simple scenes.
  Not into animation at all.  Not into the professional end of it.      Just for fun for me. :)

I have had vue since version 4 and have tons of tutorials saved and on cds as well as all my saved html web pages to refer to.   I never turn down a tutorial or materials and things when I find them. :)
  Appreciate you trying to help but I done been through all you have mentioned. :)

Well guys, if your stuck for now until the next patch, you might saunter on over to Cornucopia and check out my new thread on Smoothing. If you don't already know about smoothing artifacts and how to get around them, you might find it helpful!

-Chipp

www.cornucopia3d.com/forum/viewtopic.php

Thanks chipp I am into trying to make a pic in Vue 5 inf for someone. :)   It still works for me so all is not lost. :)

Quote - DaleB - could you explain the above a bit more simply :blushing:  I usually see an error when Vue crashes to a  reference involving MS C++ runtime.

Thanks :)

 

Okaydokey! Developers tend to have a lot of stuff =not= on their systems, such as codecs, quicktime, games, etc, unless it related directly to the job they are doing. As a result, things like the system registry looks markedly different than what a general user would have. Dev machines tend to be as lean in add ons as possible, to provide the most resources for coding and debugging. If you search on the Microsoft sight, you should find links to the MS Visual C++ runtime distributable executable. This is the core dll set that Visual C++ uses in doing Windows manipulation of C++ code (there is also one for the Visual Basic runtime, but that -shouldn't- be needed). A lot of programs written in C++ on Windows makes calls that aren't included in the actual Windows program, but do exist in the runtime dll's. Without those dll's to talk with, those programs either default to things like basic Windows memory management (nuff said) and stack accessing, or simply won't initialize at all, throwing error messages if you're lucky. When you install those runtimes it changes things in the basic Windows environment; traceback functions are enabled, stack accessing gets a few more calls to use, just as an example. An error involving those runtimes could be generated by the app making a bad memory call. It could be a sign that the runtime is damaged in some way, and needs to be overwritten with a clean copy of itself, or updated to a later version. Or a lot of other reasons. If your crash mentions a specific function, write it down to add to any tech ticket you submit. That will give the developer a place to start backtracing from. Is that any clearer, or just a different color of mud....? :P

Ok, here's my take on this.  e-On is not a bad company.  Nor is Vue a bad product.  I just think this is how some intence graphic programs are.  They don't have the incoming cash like an Autodesk does...vue sells for hundreds...max/vix sell for thousands...and the numbers are better.

You just must be patient.  Stability usually comes within updates 1 and 2.  It'll get there.

And yes, I understand in day to day life, V6I is an expensive product...but in the world of 3d graphics programs, it's really quite inexpensive.

Got it DaleB - Thanks for the explanation :)

Sigh there's worse things in life thanbuggy software, liek getting up tight over it

2nd last release before final was MUCH better, but meh..I can wait a few weeks to it's fixed.
By comparison, Vue5I was dogs b****cks until about 6 months after release ;)

Vue, over all is miles better than other software cause it's FUN ot use , when it doesn't crash/screw up.

love one another, hugs, kisses!

"stop hitting me with them negative waves, Moriarity!"

;)