Preferred scene only sets the preferred startup document, not the UI layout. The UI layout in on the Interface tab of the preferences. You can also use the UI dot's to store layouts for different tasks.

And I'm a bad nerd for not getting this stuff revved up and re-submitted to the Marketplace. Someday poser will get real particles and make this stuff obsolete. Until then ...

Increase the Depth for each of the sheets of rain. Select the Control for the Rain tool. The for the Depth control increase the Depth to someth8ing like .125 for the entire duration of the animation. That's most easily done with the graph tool. Open the graph and select all the keys for Depth and [Control] + Drag then up to fix the gap between the sheets of rain.

If you submit a Ticket on this please include the Poser log window. If the GPU grays out there should be an error in the log. Also once a render fails in GPU it needs to be reset and right now the only way is to exit Poser and Relaunch Poser. So launch Poser, render the offending scene and copy the text out of the log window. That will help us find if it's a bug in Cuda or the scene was just too big to fit on GPU memory.

I highly recommend creating a new runtime for all the stuff you create. You can mix it in with the included content but it will get messy. Just create a new folder on the most spacious hard drive you have then inside that folder create a folder named "runtime" From inside poser click the bookshelf icon with a (+) to add a new runtime. That will open a folder chooser window. Pick that runtime folder you just created.

Now you can add all the stuff you've customized to your own personal runtime.

Access denied is an operating system error. Poser's just repeating what Windows said.

1. Choose the render mode

2. Chose the output folder

3. Choose format

4. Check all 3 boxes for the old style behavior.

5. Render images is "Make Movie" does the same thing as the old make movie.

EXCEPT ... right now if you have audio in the scene it's not being added to the movie file as it should. That's a bug and we'll fix it.

Poser has always rendered the image sequence like this but it was done in a way hidden from view. SO now there's some stuff you can do easier. if you don't delete the images. you can re-render a portion of a render sequence and then use the Encode Images button to re-encode the movie.

If your render gets interrupted you can re-start the sequence render from where ever it left off.

Apple is creating a cache of the UI layout and it's corrupted. This affects quite a few applications. You'll need to delete that cache but it's in a hidden folder.

• Open Finder
  
• From top menu choose Go > Go to Folder ...
• Type or copy n' paste this:
• ~/Library/Saved Application State/com.Bondware.Poser.savedState
• Delete the entire contents of that folder:
  • data.data
  • window_1.data
  • windows.plist
    
• Launch Poser.

Two things may cause this. First is the background picture need's to be set to Auto-Fit. That's in the material room ...

Select the background Object and then check that box.

If you still get bars on the edges the aspect ratio of your scene needs to match the aspect of the background picture. From the top menu choose Render > Render Dimensions. Set at to Render to exact dimension and type in an a size that's the same as the aspect ration as your back ground.

It doesn't need to be the exact size of the background but just the same aspect. So if the original was 4096 x 2048 you can use 2048 x 1024.

The scene preview may still show blanking bars but when you render the image it will render with no blanking bars.

The clothes were probably modeled around an export of L'Homme which will bake his scale in the clothing then when the clothes are loaded the scale ends up doubled.

Always model clothing based on the original OBJ files not an export from the figure. Also the L'Homme included with Poser 13 has his hidden 105% scale removed so this won't happen to P13 l'Homme.

GTX 650 isn't supported. FireFly needs the CUDA Compute version of 5.2 or higher. Nvidia made the compute versions extra confusing. Sometimes a higher number card has a lower compute version.

Here's the source from Nvidia: https://developer.nvidia.com/cuda-gpus expand the heading "CUDA-Enabled GeForce and TITAN Products" and look for your GPU in the list.

You'll find weirdness like the GeForce 910M is a 5.2 compute and so it's supported. But, the 920M, 930M and 940M are compute 5.0 and won't work for SuperFly.

I run different versions of Poser all the time. It will work as long as they are whole versions apart. So yes, you can run P12 and P13 at the same time. I wouldn't try rendering in both at the same time though.

Being that a big part of my job is trying to break Poser I have 17 different installed versions of 3 major releases. Different versions of the same major release can be installed together they just can't be running at the same time.

I'm not going say a day. We've had to do a major architecture update to Mac to add Metal support for rendering. There was way more plumbing than anticipated to amek that work. Right now the Mac release in a top priority for us.

Both Poser 12 and 13 can install content directly from your purchase history on Renderosity and PoserSoftware.com. The included content is provided the same way. INstead of installing a bunck of zip files it's just one click to add the content.

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