@HartyBart I'm afraid my initial suggestion of loading a light pose file to change just the depthMapSize attribute was doomed to the failure I originally suspected. Applying such a pose, with only a single light and none of the usual parameters immediately deletes all of the other lights in the scene and loses all of the default parameters and other configuration of the named light.

DON'T TRY THIS AT HOME.

The paradigm that the Poser devs envisioned for lights was never to be able to add additional lighting via pose file, only complete replacement with a preset light configuration was imagined and rigorously implemented. Thus, the only way to make such a change will currently be to save a pose with all of the current scene lights, have a script parse it line by line, identifying the light to be changed (easier if you just want to do it to all the lights) and doing a replace of a line which just starts with whitespace and the word depthMapSize, followed by digits. A grep string would look like

^\s*depthMapSize \d+\n

if you want to do a grep type replacement, then the search and replace strings would be:

^(\s+depthMapSize )\d+(\n)

and

\11024\2

or variants thereof.

I have written a more-or-less full parser for Poser library files, but it's certainly not required just to modify such specifically defined lines.

I should also note that apart from purging all of the lights except one from the scene, my little light pose file also removed all parameters and STILL failed to set the depthMapSize in the Properties tab to 1024, so it may be all or nothing. I will try extracting the lights from my saved scene file and see if I can reinstate them with changed depthMapSize.

[Edited due to the frustrating removal of all backslashes from posts. Trying double backslashes]

---

My ShareCG Stuff

Verbosity: Profusely promulgating Graham's number epics of complete and utter verbiage by the metric monkey barrel.