Hi: I just picked up the most recent 3D world mag (North American). They have a screen shot for the Vue 6 contest they have going on. It looks like the interface is completely changed. Does anyone know of other screenshots available?  Curious.

No but, if the code is completely new, one can expect the interface to be a bit different. I hope that this time they will have tested it properly. The existing interface still has problems such as the fact that in some colour entry boxes, you can copy the colour but not paste it.

Phantast, what do you mean, "if the code is completely new "? At the e-on software website page about Vue 6, I saw where it says; "Vue 6 is based on an entirely redesigned internal architecture, and will provide enhanced functionality in all aspects of the program."  But I didn't see that the code was going to be entirely new. 

Am I missing something?

Ahhh...now this sounds good. After many years of using Vue, I could never get use to the "fixed" GUI. Apart from that, even though it looked pretty it also looked toyish and because it was graphically heavy that is probably part of the reason it was hardly customizable.
Artists want to be able to customise the GUI to fit their workflow...not customize their workflow to fit the GUI.
Just look at C4D or Modo to see how customizable a GUI should be.

Cheers (with everything crossed in the hope E-on finally allow the artist flexibility within their working enviroment lol)

How long till we are supposed to be hearing something about V6? A couple of weeks?

Well, if you can entirely redesign the internal architecture while preserving legacy code, I stand corrected. Maybe I should have toned down the word "completely" ... 

Quote - How long till we are supposed to be hearing something about V6? A couple of weeks?

Hi,

At Siggraph mate, it will all be revealed.

Cheers
Jon

If you've developed well structured code that separates the development into different layer and if the different layers are designed to communicate in clearly defined ways then this is quite possible.

Say you have a data layer, computation layer and presentation layer for example.  Say the data layer has separate parts to handle objects, textures and animation data.  You may have coded your app so that it runs nice and quick but to do that you uncompress all the images used in textures and keep the uncompressed data in memory.  If users start using lots of very high res images that crash your app by forcing it into disc swapping all the time.  What you might do then is change the part of the data storage to a slightly slower but more memory efficient approach that only uncompresses an image when it is being used.  As your code that uses the image still sends back the same data you can still use the same code for everything else.  This is a good thing as it saves on development time and thus keeps the cost of the end product down or lets you add extra features.

Of course this approach isn't always the best one.  If you need to write really fast code you may have to sacrifice ellegance.  I've had to do that a couple of times but if you can get a 2000% speed increase on a crucial part of a project it may be a sacrifice your prepared to make.

Quote - > Quote - How long till we are supposed to be hearing something about V6? A couple of weeks?

Hi,

At Siggraph mate, it will all be revealed.

Cheers
Jon

Can't wait to see what they are offering! Paul

Hi,

You and me both mate. Personally I would like to see some actually modelling tools this time around.  Something where you can edit the actual poly's of models etc.

Cheers
Jon

Anyone have a scan of that ad?  I can't get that mag over here unless I subscribe to it.  :crying:

Sorry. I don't have a scanner. You could try their website. They may have it in their reviews section. http://www.computerarts.co.uk/3dworld

hunting it down

In the 'Cars' issue? 

Quote - Personally I would like to see some actually modelling tools this time around.  Something where you can edit the actual poly's of models etc.

I would be against that. It would make the program more cumbersome, less stable, and wouldn't be as good as a dedicated modeler. You might as well ask for it to include Photoshop touch-up abilities as well

It doesn't need to be cumbersome if executed properly.

And anyway I am just saying what I would like to see. At the end of the day we will get what we get. A built in modeller is something that would have helped me emmensly in the past.

Thanks
Jon

I have Vue 4 and Vue 5 Easel...Do you all think I should invest for the Vue 6 Cross grade...I don't do animation yet but maybe someday...Opions please...

I have to agree with Phantast - leave modelling to modelling packages.  The tools Vue has (primitives, booleans and metablobs etc) are very useful but Vue should stick to what it is good at.

Also adding modelling features would simulateously open them up to reviews comparing them to modellers and into annoying the makers of modelling packages who might be less inclined to support Vue importing their formats in future.

Now there are some features buried in Vue's python functions that would allow anyone who wanted to to develope a modelling package that worked with Vue or to integrate one they already had sitting around.  That would be a big task for anyone who chose to take it on and I'm not sure if there would be much of a market for it either.

Quote - hunting it down

In the 'Cars' issue? 

I think it is the one before that. It just came out in Canada last week. Hope that helps.

Patience :) SIGGRAPH is here - e-on will unveil Vue 6 in more details any days now.