Maybe I jumped the gun in buying the upgrade to infinite 2015 from 2011 I have just spent a week and 40+ hours fighting with importing and rendering poser content after watching plenty of tutorials from previous versions and making a sqillion adjustments here and there-atmospheres, lighting you name it,

shadows are all wrong, bumps are all over the show, it renders black, the resolution is not right even if I bump it up high as, shall I go on-you get the picture

I am not going to raise a support issue with them as the last time I tried 4 years ago it  took 3 months for a reply and it was worth bantha poodo when I got it.

I tried updating NVidia drivers, I have done everything I think I can try so now because my name is not George lucas or james Cameron the can shove their precious program where 3d wont render!!!!!!! 

About Poser Import, I opened a ticket, and they'll take care about that.

I underestand your frustration, same here. I've been away from Vue since release 10 and have sworn to never come back. Well, I've been tempted. "faster rendering" and "better Antialiasing" did it. I just don't see it. I see all those nice but grainy Vue renders in the gallery here and I wonder how the hell are they doing it. My vue renders allways look like post coulored B/W pictures. Photometric doesn't look even close to photoreal.

The best vue pics I've seen are all exported in Maya via Vue Xstream I guess rendering with Mental Ray. Vue seems useless on a single home maschine. I am hoping on some service releases, but I'm not over all optimistic. Vue is a nice environment app, but the render is cra... not useful. I pray for an Octane plug-in.

I am saving for a machine to do octane justice and thought vue2015 looked like a useful in between solution but no,  I feel ripped off.

I have had very good luck in bringing in people from DAZ as OBJs. I find Vue 2015 Infinite faster and smoother than previous versions. Also, so far no crashes. You can configure OBJs of people beautifully.

New build fixing the Poser import problem, but antialiasing is messed up now. We need an Octane bridge, because Vue's renderer is just simply ... ahm ... "cattle feces". ;) I am seriousley contemplaining a refund.

My renders in Vue are fine. I don't have problems. What settings do you use and what issues do you have?

My renders in Vue are fine. I don't have problems. What settings do you use and what issues do you have?

Changing the antialiasing settings in the user render settings, are not applied, until you've restarted Vue. Sometimes the picture is rendered as it should until the post render menue pops up. At that point the antialiasing is removed. Why ever. I am loosing patience with that App. I am usingVue since vers.4 and the renderer has allways been a PITA. With the new 2015, nothing has improved as they promised. I am mostley mad at myself for trusting their promos and being tempted again. Now I wish, I would have resisted. :(

My renders in Vue are fine. I don't have problems. What settings do you use and what issues do you have?

Changing the antialiasing settings in the user render settings, are not applied, until you've restarted Vue. Sometimes the picture is rendered as it should until the post render menue pops up. At that point the antialiasing is removed. Why ever. I am loosing patience with that App. I am usingVue since vers.4 and the renderer has allways been a PITA. With the new 2015, nothing has improved as they promised. I am mostley mad at myself for trusting their promos and being tempted again. Now I wish, I would have resisted. :(

Now I can't reproduce it anymore, but I cannot load a Poser figure into an empty environment mapping scene. One weirdness disappears, another one pops up.

New build fixing the Poser import problem, but antialiasing is messed up now. We need an Octane bridge, because Vue's renderer is just simply ... ahm ... "cattle feces". ;) I am seriousley contemplaining a refund.

I wouldn't call the Vue renderer that at all, not at all. It's a pretty good renderer, but yes it can be troublesome. An Octane brigde for Vue? Would that even work. I don't see Octane render all the stuff Vue can throw at it, not at current. It just wouldn't work..... unless you create a network of GPU's with lot's of memory for the GPU's. Vue is not only CPU intensive when rendering, but also eats memory, we all know that. Using octane with Vue would be limited.

I've seen Vue stuff rendered with Octane, some have done it, I think there even were posts about in the forum. It left, me let's say, underwhelmed and unimpressed.

As you concluded, you most likely shouldn't have bought Vue 2015 at this stage. I always wait first for the reports to come in about the new Vue. You know what? There's a huge lack of reports and images of the Vue 2015, making me think it's not that good as E-On claims it to be. I had no intention of buying it and so far that intention has not changed. Normally we even see this dead forum flooded with posts about the new version, but since that isn't happening at all, it's safe to assume Vue 2015 is one to skip..... I'll wait and see if others can change my mind in time to come when they release their experiences with Vue 2015. So far, it hasn't been that positive.

quote: "... As you concluded, you most likely shouldn't have bought Vue 2015 at this stage. ..."

It was cheaper ;)

Some comments above...
Octane is GPU and Cuda Core.  Just go get yerself a GPX 780 with 2300 cuda cores and Octane will run like a raped ape.
Vue and Poser need CPU cores, the more the merrier, and the faster the better.

They do not mix. 

VRam is not all that much, so don't get sucked into the Titan that has the same cuda cores and double the vrarm.

Been there/done that.  Just trying to share. 

What exactly is your problem with Vue?  Its easy to see the frustration but hard to decipher why because I find Vue 2015 Infinite incredibly stable - like Zero crashes and I have been hammering for a week now with test scenes and animation renders. Large ecosystem and figure animation scenes.  I animate "worlds" rather than make perspective sets so really like the stability and speed improvements.  Vue 2015 is far more robust than prior releases.  With respect to importing figures, most rendering systems will require some material and texture adjustments. Because Vue focuses on the macro (outdoor environment scale scenes) imported objects have texture layers merged  and maps compressed - where you find it common for Poser to have a 4mb tex file, Vue and other engines will require far smaller since its rendered in combination all the other textures in the scene.  Often too, its optimal to group and weld objects prior to import (search tips on Vue optimization).  Also merge clothes to figure.   For this reason I will get better consistency by using the texture atlas to merge Poser or DAZ texture layers to a single texture map per obj, or 1 per figure group.  Animate if necessary and export as animated Collada (dae) retaining groups, textures and keyframes.  

I thought Vue 2015 was more stable than previous versions until it crashed every time I would put in a scene exported as an Obj from DAZ. Oddly enough I could bring it into Vue 11.5. Then if I opened the 11.5 scene in 2015, it was ok. I did open a ticket and sent them the files. Also, when using photometric atmos, the main camera window was do dark that I couldn't see what I was doing.  Then, if you want to render a small section of an image, it sort of seems useless. It was fine in prior versions. I did use Vue 2014, but went back to 11.5. My system is win 7 64 bit with 64 GB memory and is only 2 years old.  I'm on my iPad so I can't put down more specs, but it is fast and was custom built.  It is a good system.

I am beginning to wonder with all the valied experiences people are having whether Vue is just not really picky about configuration and other programs. I have used Vue infinite since about 2002 and it seems we all have different issues and experiences. 

I did post my issues on the maintenance forum and am awaiting answers. I would like to use this new version, but I seem to waste so much time that I keep going back to my Vue 11.5 so I can get work done. 

I must say I am frustrated.

I've been telling people that for years. Aside from rendercow issues, I've never had the problems people talk about vis a vis stability. I also run my CG programs on a dedicated box and allow -no- social media, tool bars, web games, or the like to ever touch metal in it. I also make sure the OS is stable before loading up my various programs. Even the load order makes a difference, depending on program version. On your problem Paula, it -sounds- like the .obj format issue that has been around forever. DAZ is doing something that the 2015 obj importer doesn't support; 11.5 either does support it, or it simply strips it out of the equation, since it doesn't recognize it. The next most likely is DS is adding something to the format that it uses, 11.5 ignores, and 2015 is aware of just enough to dislike. Probably something associated with the genesis part of the figure.

* On your problem Paula, it -sounds- like the .obj format issue that has been around forever. DAZ is doing something that the 2015 obj importer doesn't support; 11.5 either does support it, or it simply strips it out of the equation, since it doesn't recognize it. The next most likely is DS is adding something to the format that it uses, 11.5 ignores, and 2015 is aware of just enough to dislike. Probably*

 The idea makes sense, but then why would some OBJs export and import properly and others not? The export settings are all the same. So far, G2F figures have imported properly into 2015. What hasn't are large scenes like canal city. I prefer to do all my work in Vue (rearranging parts of a scene, eliminating, etc.) other than with figures which have to be done in DAZ. I did send in a ticket on this to e-on.

Again as with any tool in your 3d pipeline, you really should optimize the mesh for import.  Vue prefers triangles over quads, 1 tex layer per group and decimated to less than 100k polys.  It WILL accommodate a complex Poser figure non-optimized but it cant handle too many before your scene will crawl.  However if you optimize the figures as you would for a game engine, you can add many more figures to a Vue scene.  
If you use content from a lot of sources and need to a tool that offers the greatest level of flexibility and capability to optimize figures in your pipeline, consider using Ultimate Unwrap 3d by Brad Bolthouse.  Its brilliant. simple yet effective and its become the indispensable swiss army knife in my 3d toolkit.

Again as with any tool in your 3d pipeline, you really should optimize the mesh for import.  Vue prefers triangles over quads, 1 tex layer per group and decimated to less than 100k polys.  It WILL accommodate a complex Poser figure non-optimized but it cant handle too many before your scene will crawl.  However if you optimize the figures as you would for a game engine, you can add many more figures to a Vue scene.  
If you use content from a lot of sources and need to a tool that offers the greatest level of flexibility and capability to optimize figures in your pipeline, consider using Ultimate Unwrap 3d by Brad Bolthouse.  Its brilliant. simple yet effective and its become the indispensable swiss army knife in my 3d toolkit.

* On your problem Paula, it -sounds- like the .obj format issue that has been around forever. DAZ is doing something that the 2015 obj importer doesn't support; 11.5 either does support it, or it simply strips it out of the equation, since it doesn't recognize it. The next most likely is DS is adding something to the format that it uses, 11.5 ignores, and 2015 is aware of just enough to dislike. Probably*

 The idea makes sense, but then why would some OBJs export and import properly and others not? The export settings are all the same. So far, G2F figures have imported properly into 2015. What hasn't are large scenes like canal city. I prefer to do all my work in Vue (rearranging parts of a scene, eliminating, etc.) other than with figures which have to be done in DAZ. I did send in a ticket on this to e-on.

Well, .obj is the old Wavefront file format that Lightwave initially made a default. But the standard is so old, that it was never properly defined and closed. Kind of like Blu-ray; that standard is still incomplete so people can bolt on just about anything....which is why BD is such a pita. If you don't permit your player to be online for uncontrolled flashes of the firmware, you are going to have problems. In .obj's case, the format was expanded over the years, so the initial format is basically correct, but there has been things added. You can look at a 1990's .obj and a 2014 .obj in a text editor and see differences in format. How well a program does accepting it falls to how well the parser is written. In .obj's case, a lot of them are written to ignore the lw specific tweaks inserted over the years, unless it was one to fix an issue. The basic format is highly portable; its when you deal with the Lw specific tweaks that things get messy. Each program has its own parser, and how they interpret things can get pretty ugly... And that looks like a neat utility, dreamcutter. I may have to give it a spin.....

It would be interesting to know if parameters were changed in the importer fo r Vue infinite 2015. I didn't start importing a lot of obj so until I was using  Vue 11. While I still preferred a certain 11.5 build, I could import all into Vue 12. Since you both seem to know a lot more than I do about obj geometry, could changing the DAZ export settings make a difference? 

Not using DS so I can't say for sure, but if there are multiple options for export, then it could very fix the issue. It would depend on what the problem actually is.

About Poser Import, I opened a ticket, and they'll take care about that.

I underestand your frustration, same here. I've been away from Vue since release 10 and have sworn to never come back. Well, I've been tempted. "faster rendering" and "better Antialiasing" did it. I just don't see it. I see all those nice but grainy Vue renders in the gallery here and I wonder how the hell are they doing it. My vue renders allways look like post coulored B/W pictures. Photometric doesn't look even close to photoreal.

The best vue pics I've seen are all exported in Maya via Vue Xstream I guess rendering with Mental Ray. Vue seems useless on a single home maschine. I am hoping on some service releases, but I'm not over all optimistic. Vue is a nice environment app, but the render is cra... not useful. I pray for an Octane plug-in.

along with more power theres usually more to do and settings to get right. There are some threads at cornucopia3d about render settings and usually the folks there are happy to assist, esp the folks who do the beautifull jawdroppers. If you havent already try posting for render advice etc in the forums. If your renders arent looking well then check the specs too as far as card etc. I have 2014 and yes some atmos dont work as they should but then I havent had the time between work and school to research it. Up until I started with Vue and Maya my software was easy and intuitive but wasnt really powerfull. Ive decided that ive a long way to go to learn. Ive dealt with Eon and Cornucopia for years and even tho at times you end up asking a few times they will give the help you need. Keep at it and good luck

:)

Vue's GoZ bridge broke my DAZStudio GoZ bridge. Man, I'm going to hate this fing e-on*ware company.