So...I can default everything in the Superfly render setting screen by just hitting "restore defaults." That works fine. But all of the presets that come with it seem to have been reversed! If I choose Ultra Quality (Caustics), it gives me 2 samples, a collection of 4s and 1s under individual sample rates, no depth of field, no caustics. If I choose Fast Preview, it goes up to 50 samples (!!), no branched path tracing, bucket size of 256, minimum 16 transparent bounces, etc...totally backwards from how it should be and how it used to be. Something ain't right. I haven't moved anything around, this is out of the box.

OMG, you're right.

I used "fast preview" last night and it took forever. (I'm not sure how long; I went to bed.) I never really noticed that the settings were really high. I just figured, it was Superfly, taking forever as usual.

Hello Minyassa,

Thank you for mentioning this.

I just tried this with build 272. I cannot confirm your findings.

When I choose the Ultra Quality I get the below, with 25 samples, etc.

Fast Preview preset is this, with 2 samples, etc.

Obviously one can discuss the presets and th naming. Should depth of Field be set for ver high quality? That is something one can argue about. However we cannot reproduce the error you mention here.

If the issue persists, I sugest you report it to the Poser support staff.

@ FVerbaas--I noticed that you have your video card selected, which would lead me to believe you are using GPU rendering. I'm not. Could that be the difference? Or maybe it's because I am using Windows 7 and things are starting to not be coded to take that into consideration...at any rate I will contact support because it is definitely not doing what yours is.

It's the opposite for me. Ultra Quality has 2 pixel samples, while Fast Preview has 50.

The results with CPU rendering for me at least) are the same.

Are you using the 'official' release (build 272) or the beta?

Anyway this suse is something for support.

I'm using Windows 10, and I get the same results whether I'm using CPU or GPU rendering.

Some of my settings are also off. Fast Preview shows Pixel Samples 50 with Branched Path Tracing unchecked which should be correct because manually rendering with similar settings is correct. My Ultra Quality nowhere matches FVerbaas.

I wonder if it matters if you saved your existing preferences? I tried to, but there were issues, so I did another install that nuked my preferences.

My saved Superfly preference presets are working correctly.

Most of my presets don't work at all. Fortunately, my saved ones work.

I'm having the same issue Red. The presets I've personally added, and saved, are working, but only 2 or 3 of the presets that come with PP11 are working correctly. The others all stay the same as the last preset chosen.

Luckily, I never use those, so for all I know, they've been "off" for a number of updates. Maybe it's time for the dev team to check them out for those who do use them regularly.

Well, I went exploring, as the Render Presets I saved are my presets, and not the ones that come with PP11. I wasn't sure where to look for those, but just found them, and they're all dated 9/13/19. If I had known about these, I would've saved this folder as well, but now it's too late.

The folder can be found in Runtime > prefs > RenderPresets > SuperFly.

mine weren't working after the previous update. there was a thread in the SM forum where others were having the problem so I checked mine. I never use them otherwise.

Ohh, I missed that thread, so it's not something new with the 11.2 update. I hope someone's already reported this for those who do use those SuperFly presets.

I usually don't use them anyway. I confess, I don't use Superfly much, though I'm trying to change my ways.

Seems like something that should be fixed, though not right now, since there's people who can't even open Poser. Choosing "Fast Draft" and having the render take days is enough to put someone off Superfly forever.

Update: The issue is reproduced and we found a possible cause.

Own render settings are added at the top of the list but it looks like the index of the choices of the standard items in the total list is not updated for them.

When testing I had no own preset defined so mine worked as expected.

The issue has been reported to the dev team.

Thank you all for bringing this to attention.

Oh good. Knowing it's been reported to the dev team, though it might take a while to fix, is at least a step in the right direction.

Once that's done, I'll be sure to save them when I save mine

Keep in mind that it is just the standard settings that get shifted. Your own settings should work as intended.

Yep, this is a carryover from SM. I've already reported it to new team. If you wanted to see the original post on the SM forum it's over here Superfly Render presets.

Miss B posted at 9:56AM Thu, 03 October 2019 - #4363401

Well, I went exploring, as the Render Presets I saved are my presets, and not the ones that come with PP11. I wasn't sure where to look for those, but just found them, and they're all dated 9/13/19. If I had known about these, I would've saved this folder as well, but now it's too late.

The folder can be found in Runtime > prefs > RenderPresets > SuperFly.

If you wish I can try to Pack you up the Presets from 11.1 it might fix the issue

gate posted at 12:57PM Thu, 03 October 2019 - #4365581

Miss B posted at 9:56AM Thu, 03 October 2019 - #4363401

Well, I went exploring, as the Render Presets I saved are my presets, and not the ones that come with PP11. I wasn't sure where to look for those, but just found them, and they're all dated 9/13/19. If I had known about these, I would've saved this folder as well, but now it's too late.

The folder can be found in Runtime > prefs > RenderPresets > SuperFly.

If you wish I can try to Pack you up the Presets from 11.1 it might fix the issue

Thanks for the offer, but I don't use the built in Poser SF presets, and didn't even know there was an issue with them, until I saw this thread.

There is no principal difference between standard presets and onse you save by yoursel. You can therefore move the standard preset file (.prp) from C:Program FilesPoser SoftwarePoser 11RuntimeprefsRenderPresetsSuperFly to C:Users\AppDataRoamingPoser Pro11RenderPresetsSuperFly

They are then all in the series that is loaded first so the indices are correct and you load the preset you want to load.

Do not delete the folder in the Runtime under Program Files. Poser is happy finding an empty folder but not sure how happy Poser is in not finding the folder at al. Better safe than sorry.

Hmmmm, I hadn't thought of trying that. I'll have to remember to try it once they get them working again, so at least I'll have good copies when I save mine for future updates.

Fix for this will be in tonight's beta build/download.

They DO work. It was just that the preference file loaded was not the one you clicked. This is the complete workaround Yuo have in fact made the standard ones your own ones.

Seems like fix should resolve issue without requiring the extra step.

yes but until it is fixed you can use this.

I've actually opened a .prp file using notepad, in particular, a file that is expressing erroneous preset numbers in Poser and found that the file does not reflect the numbers being displayed. Poser is either misinterpreting or oversampling those values. I shouldn't see any discrepancy between the Poser window and the .prp file.

This is my Medium Quality, both Poser and file in notepad.

FVerbaas posted at 1:10AM Sat, 05 October 2019 - #4365860

There is no principal difference between standard presets and onse you save by yoursel. You can therefore move the standard preset file (.prp) from C:Program FilesPoser SoftwarePoser 11RuntimeprefsRenderPresetsSuperFly to C:UsersAppDataRoamingPoser Pro11RenderPresetsSuperFly

They are then all in the series that is loaded first so the indices are correct and you load the preset you want to load.

Do not delete the folder in the Runtime under Program Files. Poser is happy finding an empty folder but not sure how happy Poser is in not finding the folder at al. Better safe than sorry.

OK, after updating to version .296, I tried this, and sure enough, now they're working, so something changed in Poser that messed them up in their usual Runtime > prefs folder.

Only thing I did, however, was to add the word SuperFly to the beginning of the name of each or they get mixed in with the ones I've saved over the years, because they list alphabetically. Now I see them as I used to see them, and they're all working just fine.

Yeah, it's not the files themselves at fault. As we discovered by the end of the original post at Smith Micro, Poser just has an issue reading the files from their default location. If you copy and paste them into the user RenderPresets folder they will load fine.