When I used Queue Manager with Poser 12.0.757 I got the following error message.  I reinstalled Poser & Queue Manager but the problem didn't go away. System: 
Windows 11 Pro
Intel  i5-11600 @ 2.80GHz
16 GB RAM
NVIDIA RTX2060 (Studio Driver 511.65)

Rendering normally or in the background works fine.  

I tried lodging a support ticket at posersoftware.com, but the support system doesn't seem to be working properly.

Any suggestions?  
oz

 

Are you sure that both computers have enough free place on their system drives?

𝒫𝒽𝓎𝓁

---

(っ◔◡◔)っ

👿 Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
👿 Mac Mini M2, Sequoia 15.2, 16GB, 500GB SSD
👿 Nas 10TB
👿 Poser 13 and soon 14 ❤️

Hi Y-Phil,

Not "both computers."  Poser & Queue Manager are on the same machine.  I simply wanted to a batch rendering of several scenes overnight.  I never had problems before.  And the disk drive has around 700 GB of free space.

oz

I got that too but life happened and I haven’t had time to look into it. I vaguely remember having issues quite a while ago too. Then it was 2 of the SF texture nodes that caused the problem, but I thought it had been fixed. I haven’t had time to check if it’s back or something different this time.

---

Available on Amazon for the Kindle E-Reader Monster of the North and The Shimmering Mage

Today I break my own personal record for the number of days for being alive.
Check out my store here or my free stuff here
I use Poser 13 and win 10

I've run a lot of Q12 renders (on Win7 machines) but have not seen this.  What is a .bom file?

Poser 12, in feet.  

OSes:  Win7Prox64, Win7Ultx64

Silo Pro 2.5.6 64bit, Vue Infinite 2014.7, Genetica 4.0 Studio, UV Mapper Pro, UV Layout Pro, PhotoImpact X3, GIF Animator 5

Oh and I forgot to mention that, depending on your use of your Windows PC, it's good to restart it, do not turn it of and on as it does not refreshes the resources. I've seen Poser 11/12 run almost half its normal speed if I let my PC unrestarted for 6 days or more, as besides  Poser, I'm using a program that's resource hungry (PyCharm)

𝒫𝒽𝓎𝓁

---

(っ◔◡◔)っ

👿 Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
👿 Mac Mini M2, Sequoia 15.2, 16GB, 500GB SSD
👿 Nas 10TB
👿 Poser 13 and soon 14 ❤️

From a Duck-Duck-Go search:  .bom is a "bill of materials" Mac OSX file.    Why would Queue on a Win11 machine be looking for a .bom?

Poser 12, in feet.  

OSes:  Win7Prox64, Win7Ultx64

Silo Pro 2.5.6 64bit, Vue Infinite 2014.7, Genetica 4.0 Studio, UV Mapper Pro, UV Layout Pro, PhotoImpact X3, GIF Animator 5

I've been using queue manager for months with no problem, until yesterday... I started experiencing the issue above ... How is it possible that this happens suddenly without any update to  Poser or queue manager? I did recently have a windows update(win10) could that have anything to do with it?

Has anyone found a fix or work-around for this?

Y'all have a great day.

I think the problem may have been with the size and/or content of the Poser file. QM can handle a simple render, but it failed for a Poser render with a 60MB pz3 file and a 105MB pmd file.  The log entries are:

...adding new Queue entry id 1
Queue Procs now available: 0
Launching FFRender for parsing...
C:\Program Files\Poser Software\Poser 12\FFRender64.exe "C:\Program Files\Poser Software\Poser 12" "C:\Users\Public\Documents\#########\2022- 3-12_17h47m11s.pz3" "C:\Users\wtang\AppData\Local\Temp\Queue Manager\12" "2000" "1600"
... FFRender launched
Parser process is ready to talk
SetRequestedFrame OK
Parser assets are ready.  Updating qTask with filenames.

Then the error message appears.

oz_tangles posted at 12:56 AM Sat, 12 March 2022 - #4435802

I think the problem may have been with the size and/or content of the Poser file. QM can handle a simple render, but it failed for a Poser render with a 60MB pz3 file and a 105MB pmd file. 

I checked a few of the PZ3s which I've used Queue to render;  several are bigger than yours (75MB, 132MB, etc).  So, file size might be a factor, but there must also be some other factor.  Why Queue is looking for a Mac OSX ".bom" file on your Win11 machine is a mystery to me.  My machines are Win7 64bit.

Poser 12, in feet.  

OSes:  Win7Prox64, Win7Ultx64

Silo Pro 2.5.6 64bit, Vue Infinite 2014.7, Genetica 4.0 Studio, UV Mapper Pro, UV Layout Pro, PhotoImpact X3, GIF Animator 5

I had a weird problem at end of 2021 where QM refused to transfer textures for part of Pp11 scene. It was not a very complex scene, the three imported FBX characters were just too much for my now-ageing twin GPU cards. Either I rendered locally as CPU-only, or I sent job to my Ryzen-7 network-render 'Box'. I tried everything I could think of, no go.

Put head-scratcher aside...

Three months along, sundry Win'10 updates, re-boots etc later, I'd worked down my 'ToDo' list to that problem, tried remote-rendering that scene again.

Ran perfectly...

Well, D'uh...