hborre posted at 1:25PM Fri, 01 January 2016 - #4246733

As was posted, you need to save a copy of G2F back to the Poser library to generate the necessary obj file. Only then will you find the file in the Poser geometries folder of your Genesis 2 runtime.

I may have misunderstood this. I took at as though there was an assumption I hadn't installed G2 into poser which I had so I ignored it.

I still don't know how to "load G2 via DSON into Poser" then.

I have however made progress...I think..not thoroughly tested and I need to go out for a bit on a family mission.

I loaded the modified G2 figure into poser from the library.

I then selected, File > export > wavefront object ans saved it.

I then deleted the modified G2 figure and loaded the base G2 figure.

I then went to Figure > load full body morph, named the file and navigated to the saved .obj file loading it in.

The dial appeared and the base G2 figure responded to adjustment when I turned the dial to 1 and appears to work perfectly.

Thanks all for your help.

Hopefully this is sorted now, let you know if not.

Jules53757 posted at 12:43PM Fri, 01 January 2016 - #4246723

You load G2 via DSON into Poser and then save the figure to a library of your needs. Then you have to look into the CR2 to find the name and the location of that obj file.

As you can see from the above screenshot all I have are dson, .py and poser content files.

I've opened them all just now in notepad and none point to a .obj I can see?

Thanks Paolo,

I have installed Blender and I am working through the video tutorial you have made. I am stuck already however in that I am trying to import the Genesis 2 wavefront object and cannot find it anywhere. It is not in the following locations:

This looks promising but nothing there appears to be a .obj??

Do I need to create the .obj first?

WandW posted at 8:27AM Wed, 30 December 2015 - #4246317

marvlin posted at 10:12PM Tue, 29 December 2015 - #4246280

Just out of interest. Where do you get the M4 shape from?

DAZ... http://www.daz3d.com/michael-4-for-genesis-2-male

Hmm, that's odd as I already own this but don't see the M4 shape. I've just been looking through through the files before install and there is nothing in the poserCF. Does the M4 shape work in poser? If so where would I find it?

WandW posted at 11:23PM Tue, 29 December 2015 - #4246249

I don't have any M4 mats converted to work on Genesis 2, but I do have the M4 shape and UVs for the shape. I dialed in the shape and loaded the UVs and put him in the Grantham Suit, saved him to the Library, and he loads fine clothed.

I'm using Poser 11 with the last beta version of the DSON importer, 1.1.3.49 (the current release version is newer, but gives a distorted leg mesh on Genesis 2 Female), and the latest version of Genesis 2 Starter Essentials...

Just out of interest. Where do you get the M4 shape from?

Okeedoke.

I've just had to resort to clothing the characters in the scene and saving the scene as a separate file then calling that up to get the job done for now.

I'm only using the M4 and V4 textures because I was using the older generation characters when I started this story and now I want to use the G2 generation clothing as it just looks better especially on the blokes without those massive shoulders all the M4 mens clothes seem to have.

I was able to create clones of the M4 and V4 characters out of genesis 2 male and females but they just didn't look right without the original textures I was using as they were quite distinctive.

Once I have completed this story I will use genesis materials and this should stop being a problem.

Hi WandW, I'm afraid that didn't work. The error still persists.

Haha, stumped you with this one LOL

Just so you know I have now tried the following and it is definitely something about the UV mapping and using M4 textures that is conflicting here.

I've just loaded a clean Genesis 2 male then added the UV mapping, textures than the G2 clothes and the same error occurred.

I then loaded a clean Genesis 2 male then added the G2 clothes and it saved to the Library without problems.

I Then used the same Genesis 2 figure still loaded into the pose screen still wearing the same clothes that had save to the library without trouble and tried again.

I UV mapped the figure and added the M4 textures then tried to save.

This time when I tried to save it to the library I got this error code.

Anyone know what it means?

3DFineries posted at 9:50AM Thu, 24 December 2015 - #4245392

Here's the settings I use for final renders & I never have issues with my final renders.

Try these settings on the light:

And try these render settings:

Hi 3D fineries,

Thanks for that. Just tried those settings and so far no artefacts.

Also, big thanks to EldritchCellar. I found alot of the info you posted very useful.

Regards

Martyn

Hi EldritchCellar, I have indeed tried disabling AO and the artefacts still occurred.

I'll try what you say and report back

nerd posted at 7:52PM Wed, 25 November 2015 - #4240900

You can add your 2014 runtime, just make sure you remove the "Python" folder. You will end up with duplicated and as with this case out dated scripts. You should add any add-ons such as Reality to the new location following the authors steps.

Now, I didn't know that. I've just been through my old runtimes and deleted all the python folders LOL.

I had python folders going back to poser 8

bevans84 posted at 5:23PM Wed, 25 November 2015 - #4240874

I'm more curious as to why Pro11 is reading an addon installed in the 2014 runtime, or why Reality shows up under Render in Pro11. Shoot, it will even open if you click on it.

From what I can gather it is because I had imported the 2014 runtime library into my Pro11 application.

Just by way of completing this thread it does appear that the reality issue was the problem. The files were located on my C drive in the old content folder. I've just manually removed then and the problem has gone.

With the benefit of hind sight It might have helped had I mentioned that I had reality installed so apologies for not doing so.

Thanks all once again.

Malysse posted at 8:37PM Tue, 24 November 2015 - #4240721

I'm going to step in here even though I hate this fucking useless forum because i don't like to see SM maligned unfairly.

The advice you've been given above is nonsense.

Everything is installed in the right place. There is no .pyc script for the lights. You can't edit a .pyc script anyway.

The problem is that you've added the PP2014 runtime to your P11 installation, and the PP2014 runtime includes a (properly) installed version of the Reality addon that is incompatible with some of the new features in Poser 11, such as the new area lights. Reality is choking when trying to process a type of light it knows nothing about.

There is an update to Reality which makes it compatible with P11 on its way soon - you should have been notified about that. In the meantime, remove Reality from the PP2014 runtime, or don't link to that PP2014 runtime from within P11. Then get the updated Reality when it's available.

Hmm, makes sense. I'll pop over to the reality website and see when the next update is.

Thanks for the help albeit a little strongly worded LOL

Hmm okay.

It just seems a bit short sighted of Smith Micro not to consider this issue.

The area light is a new function bundled with P11P.

As part of the installation process it gives you the option to install your content elsewhere.

Yet when you do the area lights stop working.

If this is the case then the installer should say that if you choose to install your content elsewhere then you can forget using area lights unless you start editing the scripts LOL.

Where would I find the pyc script for the lights so I can edit them

Thanks again for the help on this guys