Low:  1% point light for candle, etc.  1% infinite for night scenes.

High:  2500 to 3000 infinite light for volumetric godrays, and for an undersea scene with volumetric water, I have a floater bot with a pencil-tight green spotlight beam at 50,000 surrounded by an amber spot beam at 150,000.

As far as I know, you will need to strip the geometry from the .pp2 file.  There are small utility programs for this.  Vanishing Point had Geometry Stripper.  EvilInnocence (makers of the CrossDresser clothes-fitting program have Object Extractor.  Dimension 3D had EmbGeom.

It is possible to manually edit the .pp2 file, but it's easier/faster to use one of those geometry-stripping utilities.

Dawn and Dusk relax in Cafe' L'Homme.   P12 Superfly render, lots of mesh lighting.

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.

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?

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

Yeah, what @RedPhantom said;  I was only showing that you can use more than one, as many as you can scrounge together.  If doing a single render, only one remote (aka "slave") will be engaged.  Multiple remotes are great if you're running a batch list of promo renders, or if you're rendering an animation.  A singleton render will *not* be distributed among multiple slaves;  I have asked for this capability to be added since Poser Pro 2010.

No need to install any runtime or content on the slave computer(s);  when the master computer sends a render job off to the network, it sends the selected frame of the scene, along with all OBJs and texturing JPGs.  So, the master machine's Queue supplies everything needed to the slave PC's Queue.  When the slave's FFRender64 finishes the render, it returns the result -including any separate passes needed- to the master.

P.S.     The colored lines in my diagram represent Cat6+ (aethernet) cables.

@shante:     Both computers need to be in the same network;  this means the Cat (aethernet) cables are plugged into the same router (or network switch).  If the router/modem your internet service provided doesn't have an available aethernet (Cat cable) port, you can connect the computers to an unmanaged network switch (they're not expensive), then connect the switch to the router.

Along with the P12 installer, you should also have a Queue Manager installer.  If the master computer is Mac and the slave is Windows (or vice versa), you'll need to download the Queue installer for the slave's OS.  Run the Queue Manager installer -not the Poser installer- on the second (slave) machine, the one which you intend to use for rendering.

  The first time you launch Queue, your firewall will challenge you for permission for Queue;  be sure to allow it.  The first time you send a render job from your master machine (the one with Poser installed) to the slave/rendercow/remote, the slave's firewall will challenge you for permission for FFRender64;  be sure to allow it.  You can install Queue on as many computers as you want.

In the render settings, set Mesh Light Samples to zero and render again;  perhaps the building has ceiling light panels which have ambient (or translucent) cranked up.  If there are no lights "on", then in preview, you could use a camera to scan the ceiling for bright areas.

For those who may be experimenting with developing a ghost material, I think that transparency is not going be satisfactory.  Bagginsbill's ghost material from some years back uses refraction;  that is what I'm using.  It will only "see" the forward-facing polys.   This allows you to move the camera or re-pose the doll and still get the desired effect, whereas a transmap would only work for a fixed perspective.

I also added in lightcasting (look at the ground beneath the fire sprite, and the metal tabletop under the green wireframe sci-fi girl).  If you use @SamTherapy's method, you could render the background with a blue point light to compensate.

Render settings will need to allow for plenty of transmission bounces so that the refraction can reach back to the camera.  If the doll's mouth is closed, apply the invisible MT5 to the inner mouth parts;  that will reduce the number of transmission bounces needed.  I set transmission bounces high, like 64, since the render engine will only use as many bounces as needed to complete the raytracing path anyway.

This may not be relevant to your current problem, but it  is good to bear in mind:

Poser needs network permission because Poser, the render engine (FFRender64,) and Queue Manager are separate EXEs;  even though they are communicating within your computer, Windows considers that as a network connection.

I don't have a script, but I have ghost materials amongst my freebies.  It has materials for both Firefly and Superfly.  Examples:

Eddy's post in another thread suggests that the P11 networking problem was introduced by a Win10 update.

My Win7 machines can still do networked P11/Q11 rendering just fine.  I think that Eddy has pinpointed the introduction of the problem:

Inspired_Art posted at 3:12 PM Tue, 21 September 2021 - #4427822

 Networking did work up until I believe it was Windows 10 Build 1609.. after that it was, and still is, completely broken. 

There hasn't been any recent update/change to P11 and Q11.