@722 could you post a screen shot of the render setting you're using?

@peter_wade That illegal address error is a bug. We're currently hunting that one down. It would help us isolate the bug and make sure it's fixed if you could open a support ticket and attach the scene.

Please create a ticket here: https://support.posersoftware.com/

You can create a scene collection by using the File > Export > Save for sharing ...  That will create a zip file that included the scene and all the assets used by the scene. If the zip file is too big to attach to the support ticket we'll set up a link to send in the files.

This will help us make Poser better.

For a little background on GPU rendering: If a GPU render fails the device needs to be reset before Poser can render to it again. This requires Poser be restarted. If you're getting blank gray renders after a GPU render fails. Exit and restart poser to reset the GPU.

Scenes that are too big can cause this to happen. All the assets (textures and geometry) for a scene need to fit into the GPU memory all at once. GPU's can't do memory swapping the way a CPU can.That's why CPU renders have a much higher capacity for large scenes. That and most systems have much more main memory than dedicated GPU memory.

So how much GPU memory do you need? Roughly 2 GB for each figure in a scene. But, that's all subject to the exact figure. If you're using a character that has a bunch of 4K textures it will need more than 2 GB per figure. Clothes count as a figure too. Less than an actual figure but still probably 1 GB for each clothing item.

Reducing the bucket size and disabling progressive rendering on GPU will save about 200 MB on the GPU memory. So if the scene almost fits that may be enough to squeeze it in.

Other stuff running takes up some of the GPU memory too. If you're trying to maximize the GPU memory for a render close all the windows you're not using. Web browsers and anything the displays pictures will be the biggest RAM pigs. Rendering in the Render Queue will allow you to close Poser too. That will free up even more GPU memory.

What about dual GPU's? Yes but not what you were hoping for. The FireFly implementation of Cycles does use multiple GPUs. But, the entire scene must fit in each GPU's memory. So 2 8GB GPUs won't let you render a 16 GB scene. 8 GB will still be the limit.

@hornet3d The cycles warning about specular is this ...

Cycles want that connected a different way. FireFly doesn't care you can literally plug anything into anything else and it will happily render the impossible. Cycles and based on physical properties of the materials and gets offended when materials aren't based in reality.

Yes, if something causes a GPU render to fail, for any reason, Poser will need to be restarted to reset the GPU. Is one of those "Sawing off the branch you're standing on things" Poser can't reset the GPU while it's using it.

Anybody with CUDA errors. Please open a ticket at https://support.posersoftware.com/ and attache the scene as a zip created by the built in scene collection File > Export > Save for sharing ... command. If the scene is too big we'll provide you a way to send in larger attachments.

We looked into adaptive subdivision and it's not going to give you a replacement for micropolygon displacement. Things like displacement fuzz and grass just won't work because you'd need to subdivide the object till it had millions of polygons. And yeah I'd rather have a real time raytrace preview in the document window.

The exposure set to -1 is my bad. Some of the default scenes and the factory scene got shipped with the Post FX exposure set to -1. That will be fixed with the first service release. So change those to 0. Zero is no change in exposure and was supposed to be the default value.

The GTX 970 does work. I have 2 of them. It's possible there's something in that scene it doesn't like. First try rendering one of the included scene. That will eliminate some kind of hardware issue.

If a simple scene renders but not the scene you're having problems with it could be there's a material setup in that scene that's making the GPU unhappy. If this is the case we'd like to get that scene in the support system so we can track down the exact issue.

If it's just the one scene, go to https://support.posersoftware.com/ and create a support ticket. Use Poser 13's scene export (File > Export > Save for sharing ... ) that will create a scene complete zip file that can be attached to the ticket. If it's too big to attach we can provide an upload link for your scene. We can use that ti try and isolate the problem.

The best way to import geometries into Poser is an OBJ file. FBX is a container file and can contain any thing from a pose for a figure to a fully rigged and textured figure.

OBJ files only contain geometry. As to why the light wave isn't importing I don't without know what it is(n't) doing..Your best bet is OBJ anyway.

How to group materials together in the Group editor. Select the group you want to add too then Add > Material > [Whatever the material is]

It's technically possible to create a figure from a bunch of parented props but definitely not recommended. If you want to build a figure the setup room will probably be a necessity.  That said, here's how do do it the hard way.

In Hierarchy Editor (HE) parent the props in the order you want the figure to be.

On the Parameters for each object you need to set the order of rotation. On the Object properties palette check the option display in calculation order.

For each of the props you've parented together you need to sort the X, Y and Z rotations so the twist or long axis is first the primary bend is last

Drag and drop the rotation dials to the correct order.

An example rotation order for a knee on a human is Y, Z, X . The wheels of a car are going to be the same. A door would be Z, X, Y where Y opens the door

Select the root actor of your soon to be figure. On a human that's the hip for your car the body or chassis.

Once you have the object arranged and all the rotation orders set click the [Create Figure Button]

It will look like nothing happened. But a figure was just created in a special folder in the primary runtime.

In the figures category of the library look for a folder named "New Figures"

The figure you just created is in that folder.

Save your scene

Start a new scene and load the figure you created.

It will be a "Figure" but it's a long ways from working.

Fixing the joints to be where they should be is where you need the Joint Editor (JE)

The wheels probably won't roll straight. They will need their joint centers set so the center of the joint is there the wheel's hub is.

You can type in values or drag the green cross in the scene.

You'll need to setup how the joint bends. Being a machine this won't be as hard as a human.

There's a option on the figure actors called "Bend" you want that un-checked. That will make the actor rigid.

Save your new figure to the figure category of the library. Choose the option to create a new OBJ for the save.

That's the outline of the entire process and I probably lost you on the first line. But now you know where your going and there is a map. Just ask for directions along the way.

P.S. Everybody who uses F-Secure is having the same problem. It's not just your computer.

F-Secure is blocking sqlite_x64release.dll. That's why the interface won't stay set. That information is stored in a SQL data table. Without sqlite there is no data table. It's a miracle Poser launches at all missing such an important dll.The library uses data tables too.

This is a problem with F-Secure, not Poser. Especially if you've told it to exclude the files and it continues to false on it. That's a deal-breaker bug in F-Secure.

I've submitted the file in question to several multi-engine scanner sites. The only AV that giving false positives on sqlite_x64release.dll is F-Secure. Here's the results from jotti.org. Note only F-Secure is falling.

The extension value in Cycles IMageTexture node is doing exactly what it's supposed to. LaFemm's UV's extend across several UV spaces, "Tiled UVS". That's what the extension value does. It controls how the image is mapped across multiple UV spaces.

The Cycles documentation covers this better than the Poser manual. https://docs.blender.org/manual/en/latest/render/shader_nodes/textures/image.html

A walk designer can be created for any biped. You need a basic walk and as many blend styles are you want to create. I'll do at least a white paper on creating walk designers and probably an actual tutorial. There are several pieces that need to be in the right place for it to work.

The big change for P13 is that each supported figure is kept separate from all the rest of the figures. That was holding back the variety of figures we could support. Mostly because all the figures had to use the same basic walk. Now every supported figure gets own base walk and blends.

Does this mean non-bipedal figures an work. Probably. I haven't had time to actually try but it seems like it would work.

And Talking horses. Well any figure that has the needed speech morphs can have a viseme map created and used in talk designer. So if somebody makes speech morphs for a horse then we can make a horse talk.

Some tips for stuff that give cloth room indigestion. It really hates long narrow polygons. These are frequently used to create modeled in edges on cloth like a hem or piping.

It also hates sudden movements. T-pose to sitting in 1 frame. Act it out your self and see how long it takes you go from standing to sitting. Even if you just plop down it 1/2 to a full second. Give the cloth sim 30-60 frames to get in pose.

Non-manifold shapes. That's "T" shaped geometry. That's a patch pocket or modeled belt loops that connect to the underlying mesh. Leave the pocket un-welded from the base mesh and add it to the soft decorated group in the sim instead. Non-manifold geometry is a no-no in many modelers too.

This is a design limitation of the Animation palette. If you pick copy off the Edit menu it copies the current body part, not the entire frame. So, just the head or hip or whatever is selected in the pose window. The keyboard method is the only way to copy multiple frames. But, there's another keyboard trick which is much faster for making loops like walk cycles ...

Select the range of keys you want to duplicate. Then [Alt]+Drag them to the new location on the palette. Drop them where you want to loop your animation. Copied and pasted in one action.