That sure is  some improvment alright lol.

And the third one  from the top on your list, they only managed to answer 3 months before you posted it, and the one fourth from the top they only managed to answer 4 days before you posted it.

Not bad at all :)

Quote -

Quote - Plus Eon got hosed in that survey, becuase they listed every version of Vue known to man, instead of just saying Vue period, like they did for as an example for C4D or 3DMax.

You can blame that on Flak for telling me that the Vue option should be broke down by version like the Poser, Carrara and Bryce options were.  ;)

Guilty as charged on that one. Besides, E-on deserve to get hosed for having a different Vue flavour for every day of the month :D

Actually, I thought that there would be enough Vue respondants to create some interesting information on what versions/flavours of Vue that the poser/DS users tend to use when they choose to use Vue. I was sort of surprised that there weren't more Vue responses.

The reason I didn't bug Westonmi that C4D/Maya/3DSMax should also be split on version/flavour grounds like some of the others was because I didn't think there'd be enough users of those apps responding to produce any interesting information by splitting it up. At least it looks like I wasn't too far off on that count.

Sort of related.... A while back (Feb 8, 2009) I did a quick survey on what was being posted to some of the galleries at Rosity.

Bryce - 80
Poser - 493
Vue - 124
Rhino - 8
Carrara - 25
C4D - 54
Mojoworld - 8
Lightwave - 12
MixedMedium - 62
Photography - 525
Daz Studio - 201

Those are the numbers of pages of images posted in the various apps' galleries in the 45 days prior to when I made that list (using whatever the default settings are in user prefs).  While these numbers don't take into account how slow/fast it is to do something in a given app, the quality, whether they're wips or completed images, or anything beyond being just numbers of images posted, I think they provide another rough way to get an idea to what people are "using" at Rosity. (I can't emphasize rough enough)

edit - at the moment there are 66!!!! pages of 3dsmax and 18 in Maya.....

Just to echo what bruno said - the Vue 6 atmosphere's are sooo much better than the Vue 5 ones and Vue 7 is a bit better again.

Adobe Photoshop -  1  -
Bryce -                        2  -  80
Poser -                    15  -  493
Vue -                          6  -  124
Rhino -                     2  -  8
Carrara -                  2  -  25
C4D -                       3  -  54
Mojoworld -         0.3  -  8
Lightwave -             1 -  12
MixedMedium -          - 62
Photography -         2 - 525
Daz Studio -             2 - 201

Some more stats to play with :) The first number after the app is the number of pages of threads posted to that app's forum in the last 45 days. The second number is the number of pages of images posted in that app's gallery in the last 45 days. (using whatever the default settings are in user prefs.)

Photoshop didn't have a gallery (though its used in a lot of things in other galleries)  and "mixed medium" didn't have a forum, so no numbers for either of them in those categories.

Interesting that photography is bigger (numerically in terms of image posting)  here than poser and that Vue is #2 these days in the way of 3d app forum postings.

Yeap - depending on which "Vue6 program" I associate the .vue's with,  I can get either 7 or 6 to open the files.

That would certainly explain why when I find a .vue scene file in win explorer and do a right click "open with", I see Vue 6 Infinite listed twice and no sign of Vue7 in the available programs to open it with. I guess thats one of those oops moments lol.

RAR/split it up into 1MB chunks and email him one random chunk each day ;)

My Vue experience has sort of been at both ends of the spectrum.

My first Vue-ing was Vue 4 demo (I think). Back then I was a brycer and wanted to see what Vue was like after chatting with Thomas Krahn in rosity's chat room and seeing what he could do with it. The Vue 4 demo was so unstable, I uninstalled it straight away and stayed with bryce (the V4demo literally crashed as soon as I did anything).

V5i I got free with Lightwave and on my system it was on par with Daz Studio alpha for stability. Once again it was unusable so I went back to bryce 5. But to be fair, I did manage one commercial project using it - but it was more of a load terrain/dump ecosystem on it/ render sort of project, so nothing too complicated. By the end, the last update was more usable, but still pretty crashable for me, so nothing really got done in it bar that one project.

Vue 6i... I convinced myself that that one commerical V5i project could pay for the V6i update  and I'd be "cost neutral" even if V6i update was a dud. On the same computer that V5i was crash city, V6i was actually quite reasonable from the get-go. The pre-release, even with its bugs was soooo much more stable for me than any Vue, patched or non-patched, before - it was stable enough for me to actually do the things I wanted to try in it.

Then e-on redid the memory/resource managment in one of the early patches (maybe even one of the pre-release patches) and it got worse again. But then with more patches it slowly got better again, though it still seemed to fall over sooner with respect to memory usage issues than the first pre-release did. But.... recently my old vid card died and I had to replace it with another old vid card (went from ati->nvidia and more ram) and now Vue 6 is really quite nice - i.e. its stable and does what I expect it to do (and what its meant to do according to the manual with respect to error messages and things). The forced changing of the vid card made a big difference (even though Vue says it was happy and compatible with both old and newer cards).

So thats my story - luckily, for me, v6i ended well.

Attached Link: Humorix gallery - Gladiators image

When I've done cliff/ledge stuff, I tend to use a combination of lots of small terrains, symm lattices and rocks to get the shapes I'm after. Essentially I just build up what I want out of all these small elements - this works in bryce, so I reckon it will work fine in Vue when I get around to making a cavern or two later on. Its a lot of work to build things up this way, but it gives the best results/greatest control of any technique that I've tried.

My longest was about 180 hours for a 1000x800 (ish) pixel sort of image. Was playing around with trying to get smooth soft shadows out of vue in an interior scene and got a little carried away with AA.

"Finally, there will be one more surprise which I AM NOT letting out of the bag until it's set in Concrete."

Weeeell, if you're not going to say anything, then maybe we should make things up until you do :D

[start speculation]
A brand new feature where the 20 images that get the most... err ... lets call them points (all users and their clones are allowed to click a button on the gallery page to assign a point to an image) , are put onto a single page for all to see.  A point counts towards the point total for the image for one week after it was assigned..
[end speculation]

Hows that? :D

I've also run into this 1GB ceiling that only Vue seems to see on my xp32bit system. I can happily crank Bryce and Photoshop well beyond 1GB without any problems (bryce I can literally push up to 2GB and measure the point at which it will crash out).

Out of curiousity - do you have a dual channel ram setup on your motherboard - I do and am wondering if Vue is struggling with interpreting that.

And, thinking a bit more about this,  if you invert the uvmap template and use that as the transparency map, then you can have only the edges of the polygons that make up the geometry show up - true wireframe (as opposed to the solid wireframe that my post above would give you). You might need a pretty big uvmap template texture thingy  to do this with to get sharp edge lines, but then doesn't Vue have some sort of texture caching to allow it to work with really huge texture maps (seem to remember them talking about this in some of the v6i advertising).

edit - forgot that Vue does trans maps reversed to bryce - you may not need to invert it to get the wireframe look.

If the object is uvmapped, you could always texture the object with the uvmap (not coloured, just  the raw uvmap template) and render that.  As long as you're uvmap doesn't have overlapping parts of mesh/polys, it should give you pretty much what you want. I've used this technique in bryce a while back (years ago) and it worked ok.