This just started the other day... poser renders great, but if i sent renders to the queue the only things that render are smartprops- oddly it renders them as though the figure is completely invisible. it just makes the figures vanish and renders the props.

This is happening in both Poser Pro 2014, and Poser 11... just started the other day.

Also why is this happening. As you can see from the pic the new version of poser is borking the eye textures when it renders. Both of these have render settings at maximum.

I've done a gob of Queue rendering in Pro 2014 GameDev and P11Pro. I haven't seen figures disappearing in either.

The eye problem may be the same root issue or maybe something else. I'll run some tests.

Interesting that Queue wasn't doing that before, but now it is - and it sounds like some files aren't getting received. Queue and Poser need network permission to work.

Are you doing the Queue rendering on a single machine, that is, one computer functioning both as master and doing all of the rendering, or are you using remote networked machines to do some/all of the rendering?

This is all on one machine. Not getting any errors it is attempting to render it just won't render figures anymore lol, just props. I'm on Windows 10 but it was working fine a week ago I've had Windows 10 for a couple months.

Yeah just did a test render queue of 2 renders just M4 standing there, nothing else in the scene. it's spitting out completely blank images.

This is pretty devastating to my work :(((

Have you run any windows updates between when it was working and not? The other thing to look at is corrupted drivers. I've been plagued by that before. Windows reports working fine, but it lies! I don't know Win10, but there should be a way to check for Windows corrupt core files. There always has been anyway, SFC /Scannow or something like that. Good luck. I hate when things are working, then suddenly stop for no reason.

My nvidia driver may be to blame. i'm in the trenches right now it's all out war getting this driver updated- have to do a full purge first the installation keeps failing

You might want to roll back the nvidia driver via the Windows Device Manger (under graphic card name Properties). I think the most recent Nvidia driver might be buggy.... it happens...

I also can't use the Start Button anymore, or right click icons on the task bar. started recently as well, i'll try to rollback. i uninstalled nvidia, rebooted and reinstalled, still failed driver installation and queue manager still can't render anything correctly.

rollback didn't help. this is insane i don't understand how everything broke down when all i did differently was to install poser 11 lol... i'm gonna take it into the shop and see if they can get the drivers working and get my start button working again. then maybe i'll get lucky and be able to render again.

This is what I'm getting in Poser 11 so far. The render queue bug happens in Poser Pro 2014 as well.

Does it render normally outside the Render Queue?

Yep. Which is why I think Nvidia may not be to blame for this one. Could there be a setting somewhere that got switched?

Also did you check your Windows Event logs for errors? If you still can't use the start button, try restarting your pc in safe mode, then look at the Windows Event logs. It'll look ugly because things will be in lousy screen resolution but once back out of safe mode you'll be back in your preferred settings. It's possible there was a Windows update. Today is Patch Tuesday for Windows machines *scratch this line. I'm wrong on today being a windows patch.

The weird thing is start button shut off 2 weeks before this render queue stuff broke down. They might be related but seems a stretch. I don't understand how it's possible for queue manager to crank out renders that aren't identical to the same render in the software. And this is happening on two versions of poser.

I sent a support ticket in with picture to smith micro, hopefully they will have a solution

If you are having troubles with your Start button and other windows only items, your windows install may be corrupted. Do a system core file check. Search google for windows 10 scannow or whatever it is in this version. It doesn't take long. The other thing to watch out for is your hard drive. Failing drives can cause problems like this even if the drive is new. Had similar problems with a new SSD drive. It worked, but then corrupted files, then worked, then corrupted until I reinstalled over and over again. Finally, sent back to manufacturer and the new drive never has had the problems. It will make you crazy.

I'm just confused how it would relate only to queue manager and not to poser itself.

And if Windows is corrupt I wonder why it took a few months for any of this to come up... Ugh

Now this is interesting- the tech from Smith Micro had me save the scene with the collectSceneInventory script, then open the scene from there and try QM again. This time Queue manager rendered everything correctly!

So for some reason the instructions and pathways describing the CHARACTERS is not getting passed to queue manager from Poser, but the PROPS information is passed and rendered just fine.

OK! long thread but in case anyone else runs into this i want to clarify. The issue was PERMISSIONS on my content folder (my runtimes). probably what happened is some little Windows 10 update changed permissions or tightened security on my SSD.

So i've set allow Full Control for all users on my runtimes and that should solve it.

Ah, that makes sense. I had that permissions issue on Poser 10 in Windows 7 (silly UAC issue too). On the start button, that's something different. Maybe a user permission got goofed up somewhere.... that would explain the taskbar issue too.

Darkworld: Queue is a separate executable, so to talk to Poser both programs need firewall permissions. Both need read/write permissions for certain folders.

You had those permissions originally, but Win10 changed them without asking. Win10 updates itself without asking, making whatever changes MicroSoft sees fit.

The problem is not with Queue, nor with nVidia; Win10 is your problem. It may make other changes in the future which will cause problems.

Kazam's issue with UAC probably involved having a runtime in ProgramFiles; you should not put a runtime in ProgramFiles if using Vista or newer Windows.

I had heard the most recent Microsoft Win10 update sadly reset a lot of settings back to default so the update got pulled. Still haven't updated to Win10.

I'm wishing I hadn't updated to Win10. :(