Nice

FrankT posted at 5:38AM Fri, 27 November 2015 - #4241098

Bear in mind that if your site is not mobile friendly it will negatively affect your Google search ranking

http://googlewebmastercentral.blogspot.co.uk/2015/04/faqs-april-21st-mobile-friendly.html

Sure - but that does not mean exclusivly mobile. Either case - mobile friendly or not the current site isnt gatting a great search rank. Its got a PR of 5/10 and this chart reflects that http://traffic.alexa.com/graph?o=lt&y=t&b=ffffff&n=666666&f=999999&p=4e8cff&r=1y&t=2&z=30&c=1&h=150&w=340&u=renderosity.com

I appreciate the awsome administration at Renderosity. All the people and products are great, but I see the infrastructure is limiting oppertunties. Poser users are PC users right? I always shop for content on my installed system not on a tablet. These are good front page design goals, but they need to be suited for the dominate platform of the visitors. It appears the site is attempting to be optimized for mobile. I believe in time data may reveal its not achieving that objective with the inconsistant mini-panels. Its way too distracting and cumbersome to scroll. However I could be wrong, maybe the site demographics prefer it. I also hate jump-cut videos and really have a hard time following so it may be a generational thing and the target audience prefers it this way.

Me too. I spend the day roasting the bird ~ so by the time its ready I've inhaled enough. Then when everyone is snoozing off the turkey-hydate, I will sneak off and create a scene. Then when its rendering I'll make a leftover sandwich with all the trimmings.

I also experience this. It was never great to search the product catalog here, but now its hopeless.

Any reason ajax cant be employed by the gallery to save the form data in the event there was a failure in submission? Its really a pain to submit art here and I gave up.

Tnats expected however something isnt right.  That is a popular GPU and it should work fine. If you are using Windows default GeForce drivers try the Geforce/com factory drivers  - or the other way around.  You should see no conflicts or hardware errors in the Windows device manager.  

In a fast system with many CPU's render using Hyperview and use render cow instances... even better use a hypervisor to launch multiple cow instances.  Modern hypervisors like VMWare are hardware assisted on current CPU/Motherboards and use 1% cpu cycles at most for overhead.  They can pass GPU and RAM resources so you can set up windows or linux wine system "images" with optimal configurations and load them as hot and ready render cows and launch them at with a button on your hypervisor control panel.  The added benefit is enhanced backup, security and the easiest way to create and test optimal system software configurations. 

yes... Vue runs in wine, fine.

No hardware openGL mode is compatible, or just the "shader 4 " will not work?  The only performance loss really is in the User Interface, renders will be very close to the same on a fast system.  I believe only anti-aliasing is the only render task that can be passed to teh GPU and it needs to be enabled, only in Vue 11 or later.

Thanks for sharing..very helpful.

Thanks for your interest.  The link to the Pacific Pig video:  https://youtu.be/WyBDfAfbUIQ  .  The scene further inspired me to make it a video game... so I made this teaser for "P-40 Killzone, Gauntlet of Boom" and am preparing the game which should be ready for the the 4th of July. https://www.youtube.com/watch?v=6iYjA8pj22U

Here is a sample of various animation render Vue 2015 modes to compare, HDR, Photo, NPR and Vue Multi-Pass with G-Buffer layering to see fx effects and alpha quality).  https://www.youtube.com/watch?v=WyBDfAfbUIQ  The scene is 8M+ Polys and oodles of textures run on a 16gb amdfx.  900 frames, rendered in Ultra on a 10 rendercow farm takes less than 10 hours.  Before AVX this would have taken well over 20+ hours,

Oh... and pardon the crappy pig animation.  It was tossed in to test the Poser import.

Animation Rendered in Vue 2015 "P40- KillZOne" a short scenic animation with original score : https://youtu.be/aTpdwYOPzdE

The entire scene is made from standard Vue content and props including the Flak 88 gun, Curtis P-40, Mitsubisi Zero, Police Man, China Junk, Plumeria Tree, Coconut Tree, and the  Barnyard Grass Bundle.

In my experimentation while more stable and fast, Vue 2015 has more firm RAM needs and really does not like going to virtual disk. I doubt Vue would even perform well at all at 4GB now.  In massive Vue scenes, you will want to decimate and merge clothing mesh and textures so your figures are a single layer mesh and texture.  I am doing this as a course of routine now in all my Vue scenes, because even when I plan them small ~ the scenes always start to grow and grow and GROW.  
 Used to have to export Poser to DS or a 3d utility like UUW3D to do this but the new Poser 2014 Game Edition makes it a snap and does it well. 

When importing un-merged DAZ (.dae export) or Poser figures when the textures dont look right, you usually have a layer that came in with wrong aplha/transparency setting.  Click on the suspect group and examine the material.  Open the color graphs and see how its linked to aplha and what channel transparency is.  Most times just sliding trans to 100% and back to zero will fix the glitch.  Other times you need to rewire the links in the graph or rebuild the material from the material editor UI.
If your textures and cloth/body were pre-merged you might only have one material to tweak, if at all.

" I don't know it you use Poser with Vue, but they (once again) have bungled the Poser import. "

Seems to me they could really do away with the issue if they move FBX import into the Artist line.