PP2014 Firefly Renders Hogging CPU - PLEASE HELP!

  • High key... well perhaps that's what I've been missing with my renders! I've been searching for a way to make them more realistic for ages! Please take into account that a lot of my latest pieces have been derived from each other, where I've used the same kind of effects to create bloom etc.

    Well, I can't really tell you the details of the renders themselves, as it's the same outcome with everything, no matter the project, which is why I made the point to explain that old projects that once worked fine now don't, without any adjustment whatsoever. I've tried a render in a scene with seven lights and I've tried a render with one. I've tried a render with minimal transparencies and a render with loads. This issue cannot be anything that is changeable by loading a different project, it is either within the software itself, with my hardware, which I've just tested or it's somewhere within my OS. Aside from that, I just don't know.

  • @Glen85 these are my high-quality firefly render settings. I have optimized them for speed and quality.

    0_1484621031904_Firefly settings.jpg

  • @ghostship Personally, I always reduce the min shading rate to 0 for final renders.

  • @matb There are two places you can adjust MSR. The other place is the object properties for each individual figure and prop. That setting has to be smaller than .2 to get any finer detail than my render settings will allow. Most figures and props are set to .2 so setting your MSR in your render settings smaller than .2 is doing nothing for your render.

  • Something is really off there, if your running hardware scans and it's all coming back normal, it's probably a software issue and something got borked along the way.

    The next time you do any render, check the Resource Monitor in the Task Manager. Make note of what's eating up your CPU and see if there's any unusual additional threads or one in particular that's causing the issue.

    Also, in your Poser preferences, try setting the rendering to a separate process, you can also lower your render threads to 6 or less and see what happens.

    If those settings don't change anything, just re-install the latest SR, when it asks you what to do with the preferences, let it create new ones and don't use the existing preferences.

  • @ghostship Oh really? Live and learn! :-)

  • Thank you for the advice, folks, much appreciated.

    My system monitor lists all CPU cores at 100% during the render and FFRender64.exe is the culprit every single time. Rendering has always been set as a separate process. I haven't looked at this in more depth yet, but I will and will report back.

    For now though, I do have an update which may shed some light onto this.

    The first render to actually complete in a long time has come out looking faceted, for want of a better term. Some of the surfaces appear crystallised, in a way. I deliberately scaled the render right down but kept all of the other settings the same as have worked before. This scene, with a character added and at a much larger scale, took less than 12hrs to complete before, and completed without these artefacts, but with the removal of the character and the downscaling, now took around 15hrs and had these artefacts.

    Might this be a good sign of what is going on?

    (Please ignore the exploding canvas print on the wall, that was a displacement map that shouldn't have been there and has since been upgraded).

    By the way, there is no reflection on the white plaster areas. In fact, the only reflections which should be visible within this scene are of the window and the bannister bracket.


  • Poser Ambassadors

    The default minimum MSR is 0.2

    Details are in the PoserPro manual. Lower part of page 515 and top of page 516.
    This will explain when the render settings will override the object settings.

    The manual says "per obj file", but actually the Min MSR is set per vertex group in its properties palette.

    If you want to go lower then the default 0.2, you have to lower that value in each vertex group concerned.

    Best regards, Tony

  • More to the point, why is FFRender64.exe killing my system and spewing out Frankenstein renders? Not to be pushy, but it has been a long time since I managed to make anything nice and the artist in me is sitting in a corner, rocking gently back and forth, muttering the song "They were pretty, oh so pretty..."

    With respect, can we gently ease our vessel back on course, please? Render settings, scene lighting and composition have nothing to do with what is going on here, as evidenced by the fact that this very scene now appears differently to the way it did before. Unfortunately, the original is gone, I discarded it because I didn't like my character's appearance in the scene, otherwise I would show a comparison. I shall look for another old project to use as a comparison in the meantime, to better illustrate the differences.

    Thanks for the input all the same, I don't mean to come across as pushy, I'm just quite desperate now.

  • You didn't mention how many threads your have it set for rendering. If you have it at 8, you're going to be using all four cores at 100%. Set it to six for 75% CPU usage, see if that changes anything. Or manually change the core count in Task Manager and let us know the results.

  • @vilters Thank you Tony!

  • @Glen85 Can you drop box the house scene to me and I'll do a test render with your settings in 2014 and Pro 11 for comparison.

  • @matb said in PP2014 Firefly Renders Hogging CPU - PLEASE HELP!:

    @Glen85 Can you drop box the house scene to me and I'll do a test render with your settings in 2014 and Pro 11 for comparison.

    And yes, totally feel you on this frustration, but there are some VERY knowledgeable guys here. I'm sure that they can work this through.

  • @johndoe641 Indeed I am, I'll reduce it and see how we get on, thank you. I was advised yonks ago to set it as such, and have been using it like this successfully for years, so maybe despite the tests, my CPU is frying or something.

    @matb Thank you for your kind offer! Unfortunately, the scene is not only well populated, making it pretty large in terms of data, but it also contains products from many different creators, and sharing it would be breaching their terms etc (or however you want to put it). The structure itself is based upon Home One by Maclean and I have placed countless items from other creators, both Poser-specific and general 3D models, as well as free items and a few of my own creation.

    Perhaps it might be an idea for someone to create a scene which they could legally share and send that to me instead, if they wouldn't mind? I don't really know what I'm doing on this end with regards to that. It's not essential, though, I'm sure that we'll get this sorted, one way or another.


    I have encountered another problem which may be related, figured I'd add it here.

    I have rigged up a television to use as a display for my PC, as it is much bigger than my monitor. However, it is quite a low resolution (1280X768) and has required me to sacrifice a lot of space on the screen. I've also been experiencing 'flickering', of sorts, whereby the display momentarily cuts out and then comes back. This happens more often than not, on Facebook, upon encountering a video on my timeline (not playing), and when switching Netflix to fullscreen. It appears as though the signal is lost for a moment (less than a second). It happens a LOT! I mean for every video I scroll past on Facebook, for example, it will happen at least twice (presumably once to change a resolution somewhere to fit the video, then again once I've gone past it to reset it to its standard state... just a guess).

    Well, I'm trying out another small render while I'm online and my display driver just shut off completely and left me with a blue screen (not BSOD, just a no signal screen). It wasn't until I used the bottom right button to switch to desktop (guessing where it was and clicking blind) that it came back on and gave me error messages that the display driver had crashed and recovered, that FFRender had crashed and that Poser had crashed.

    Might this be a GPU-based issue, or is this telly screwing everything up? If it's the latter, is there a way that I can get them to work together?

    GPU drivers have been updated in the last few days, but I should reiterate that I've been having problems for a long time now.

  • The GPU would definitely not affect a Firefly render, although I definitely think you're right to suspect a driver issue. That said, I'd be starting to look for a systemic problem such as a dying hard drive, or malware of some sort. I even contemplated an overheating CPU, although that surely would not cause rendering artefacts, it could certainly account for slowdowns IHMO.

  • Poser Ambassadors

    Many tvs default to 60htz, and they are actually 59. Try changing the refresh rate in the driver.

  • @shvrdavid Unless it's in Europe ;-)

  • @Glen85

    24 hours for render,my longest render has took me 13 hours in Poser and this has been large scene from Stonemason The Streets of Asia and applied there Snarly Snow script plus there has been 3 V4,this has been rendered on older X5670 OC to 4.2GHz

    Are you using SSS on floor,walls etc or are you using SSS only at V4,Genesis or other figure are you using IDL and if its possible can you post yours render settings please I would appreciated

    Are you using how many lights,do these lights have any alpha map applied or do they have applied any image map(HDR etc)?

    I don't think you have any infection,infection will cause other issues not only in Poser and usually you will see in Task Manager suspicious processes,which you will straight away recognize

    I will try to create simple scene for Poser 10 and earlier version,I've few props which I created and you can try how fast this will render on yours and will post my render settings,I would recommend to use D3D FireFly render settings

    Hope this helps


  • Poser Ambassadors

    @matb I have no idea what TV's report there, but I would guess that if they report wrong here, they do it there as well.

    The driver will list the options available, and there is usually on that is 1 htz lower that will stop the flickering.