Yes, it does.

That's an excellent question. Unfortunately, I don't know the answer myself. But I would try different ones. I don't remember which versions of Poser/Vue it was, but in one of them, I had to use an older one.

I'm pretty sure I was importing Poser 11 pro into Vue 10, using the standard Poser import. Just make sure the SKD you're using is the latest.

Greymom posted at 8:30AM Fri, 25 January 2019 - #4341337

gillbrooks posted at 12:45PM Thu, 06 December 2018 - #4341322

Why the need for alternatives? I'm using 2015 Infinite and had already decided to stop there as the upgrades, to me seemed pointless. Mostly new features that I don't need or use. Just because it's now subscription only doesn't mean that you can't continue to create in your current version. As they have stated, it's yours, you own it - the licence to use it at very least. The only possible problem may occur if at some future point, your new OS won't support it. Although for me, I would like to continue using Win 8.1 untill I falls off me perch.

The whole point being, why change just because you can't get the shiny, new "latest" version? If it works, why change ??

I agree, I decided to set a couple of machines up for hardware dual boot (Win 7/Win 10 with two physical drives so I just swap plugs), and others Win7 only (Win 10 compatibility a bit iffy). Hoping to keep VUE 2015, Plant Factory, Carrara, and probably Bryce, running on Win 7 (on machines built from cheap surplus server parts) for years to come. When I am running Win7 there will be no connection to the internet for those machines. The money for hardware was already spent, and I had extra copies of Win7, so why not?

In the meantime, I will see what develops.

2015 "works" in Win 10. I put works in parenthesis due to the bug mentioned in my previous post. Pretty sure i had the same bug with Win 7,although it's possible I didn't buy 2015 until after I upgraded to 10. In any case, according to E-on, 2015 is compatible with 10.

gillbrooks posted at 8:17AM Fri, 25 January 2019 - #4341322

Why the need for alternatives? I'm using 2015 Infinite and had already decided to stop there as the upgrades, to me seemed pointless. Mostly new features that I don't need or use. Just because it's now subscription only doesn't mean that you can't continue to create in your current version. As they have stated, it's yours, you own it - the licence to use it at very least. The only possible problem may occur if at some future point, your new OS won't support it. Although for me, I would like to continue using Win 8.1 untill I falls off me perch.

The whole point being, why change just because you can't get the shiny, new "latest" version? If it works, why change ??

For me, it's because I have a random bug that deletes all the texture maps and/or makes them ignore lighting. It's an issue that E-on was made aware of relativity early on when 2015 was released. I was not,in fact, the first (or second) to report the bug. E-on either was unable to, or couldn't be bothered to, fix it. The only current cure is to delete the Vue 2015 folder in Local/Apps/Roaming and redo all your preferences. And resign yourself to the fact that unless you had recently saved the file under a different name, however many hours of work you've put into this scene have been wasted. It's obviously not a minor bug that can just be ignored.

I had intended on upgrading to 2016 after Christmas, only to find that E-On changed pricing so that instead of $595 to own the software outright, I could instead pay $795 for a single year. Unless I can find someone who is willing to sell me 2016, I'm done with Vue.

And for the record, I'm not blindly opposed to a subscription model. In fact, that's how i finally managed to score Photoshop. The difference being that Photoshop costs $11 a month and I can install it on any two computers (and in fact, can bounce it back and forth between computers so long as I only have it on two computers at any given time).

Correction to my post. $700 a year, not a month. Still outrageous. I'm hoping to find a copy of 2016 to pick up somewhere. If not, I'm done with Vue. Does anybody have any suggestions for software with similar capabilities?

I don't mind a reasonably priced monthly plan, but to get the same function as Infinite, instead of paying $598 to own the software outright, I can pay over $700 for ONE MONTH. what puts the frosting on the cake is the fact that my only reason for upgrading from 2015 is that there is a bug that makes it damn near unusable. And it's a bug that Vue was made aware of shortly after it's release by a few other users with the same problem. If I can't find a copy I can buy outright through a 3rd party vendor, I'm done with Vue. I've used it faithfully since 3.5.

Sorry. I was at work. Yes, 2012. As usual with Poser imports, you can expect some fudging with materials. Also, if you're trying to get a good volumetric atmosphere effect, you might have to enlarge the scale. Some end results: https://www.renderosity.com/mod/gallery/welcome-to-the-jungle-/2326101/ https://www.renderosity.com/mod/gallery/comes-the-dawn/2368034/

I used Pro 2015 with Vue 10. It imports as well as can be expected.

I've been avoiding the genesis stuff completely, assuming that it wouldn't import correctly into Vue. Am I understanding you correctly in that you can if you turn off subdiv?

I'm having the same issue with textures in 2015. If I save a scene, on reloading many of the bitmaps for the textures don't load.

I've used Vue since 5. Never had this issue before.

You should be able to adjust the shadows in the perimeters of the lights. I never do a straight Poser import. The materials almost always need 'fudging.'

I suggest you do your posing in poser, then import them into Vue. Vue has a substantially better render engine then the native renderer in Poser. Most people who use both programs do it this way.

So is Skinvue worth it, in your opinion? I've thought about it, but I can get pretty decent skin textures just fiddling with the material options. Of course, sometimes it can be time comsuming depending on the model and what lighting I'm using.

The problem with objects is, as you said, that you have to include the maps. Unless I'm doing it completely wrong (or Daz has an import option that compresses maps), you end up using a crapload of hard drive space.

The other option is to manually direct Vue to each map as it looks for it. That's a bit of a pain in the neck, but if you save the object as a VOB when you finish fussing with the materials, you'll only have to do it once. I recommend doing this with any import as it seems to reduce the resources that Vue uses.