Tue, Nov 26, 12:15 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Nov 21 4:12 am)



Subject: 1 day left this week. Any bets we don't see Final SR1?


Tashar59 ( ) posted Thu, 08 March 2007 at 9:35 PM · edited Tue, 23 July 2024 at 12:17 AM

Anyone think we'll get it tomorrow? Not that I'm in a hurry to get it. I'm using the stable pre-relase. I also won't make the same mistake and install the final SR until I have heard from the rest of you that knew there was a problem with the final in the first place.


thefixer ( ) posted Fri, 09 March 2007 at 1:47 AM

I posted another fault yesterday with rendering of boolean objects on hyperthreaded or multi core systems, basically it crashes [again!]
Apparently this is now fixed according to John Canver, it was him that used the above description of the fault that I sent in and the fix will be  **"part of the next update"
**He didn't actually say "When" that would be but he did leave me the impression that it would be soon!!

Injustice will be avenged.
Cofiwch Dryweryn.


iloco ( ) posted Fri, 09 March 2007 at 5:20 AM · edited Fri, 09 March 2007 at 5:22 AM

I was told last week it would be this week but have heard that many times before.........Soooooooo

ïÏøçö


PerfectN ( ) posted Fri, 09 March 2007 at 4:32 PM

Content Advisory! This message contains profanity

I left a complaint with Eon bitching about the memory problems and constant crashing and was told that "they are aware of the problem and will be addressing it with the next release and that THEY DIDN'T KNOW WHEN THAT WOULD BE."
He summed it up nicely with a "thanks for the input".
Ive gone back to using the version prior to the new release.
Funny enough though, I was trying to render a scene that kept constantly crashing on both the final release and the prior one. So I deleted object by object to see what was causing the crash. I never knew that there could be an object in a scened that could a) be rendered in preview but keep crashing in printing to disc modes.
..meh, who knew?


Tashar59 ( ) posted Fri, 09 March 2007 at 4:47 PM · edited Fri, 09 March 2007 at 4:51 PM

That pre release prior to the final was where all the problems started. You need to go back one more version. The second to last pre-release is the good one.

I didn't really think that the SR would be done that quick. Like I said let them take thier time and get it right. I have a working version.


iloco ( ) posted Fri, 09 March 2007 at 4:52 PM

What I dont understand is e-on took Vue 5 off the price list and market so people who do want a good version of vue can not have one and upgrade later if they wish to.
  Lot of things I will never understand but I do believe it is causing a lot of potienal customers to look else where for a landscape software.
   I have had good luck with tech responding back to me so got to give credit where its due. :)

ïÏøçö


thefixer ( ) posted Fri, 09 March 2007 at 5:03 PM

pre-release 288741 is the version that rocked, go back to that if you are able!

Injustice will be avenged.
Cofiwch Dryweryn.


PerfectN ( ) posted Fri, 09 March 2007 at 6:25 PM

Actually I was quite happy with the last release (not the final). Leave it to EOn to piss in my cornflakes.
And Im still a little but insensed that they want us to purchase the book for $55. Since the pre-release purchasers did a lot of their bug searches for them you would think they would ship out a book to us. The print cost plus shipping would MAYBE cost $12 - not only are they charging us - they are making a profit.


thefixer ( ) posted Sat, 10 March 2007 at 2:41 AM

Well I have to agree with that last point, a free manual should be the least that they offer IMO!

Injustice will be avenged.
Cofiwch Dryweryn.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.