Attached Link: Light FIle

Hi, I ran some files through the Merchant Utility and it came up with an error on all of my light files saying that 'This file contained paths that should be enclosed in quotes (spaces in path)'. The only paths I can see are those relating to the camera.obj. Now the thing is this file was created directly in Poser 6, without any external editing by myself, so surely any path should be correct. I added the quote either side of the obj reference, but still the same error. Does anyone know why this is showing as an error? Is the Merchant Utility at fault or is it Poser 6? I need to make sure that this is brought to the attention of the RMP testers, because I'd hate for this to generate a fail on my latest product. . Thanks in anticipation Steve

Follow Predatron on Facebook www.facebook.com/Predatron3D or go to www.predatron.co.uk

The only reason the path would have spaces in, is if it's an absolute path.

Just edit the problems paths and turn them into relative paths, i.e. starting with ":Runtime".

they have relative paths. Poser generated this code first,
objFileGeom 0 0 :Runtime:geometries:Camera:Camera.obj
I tried it with both quotes and without, still comes up with an error in the Merchant Utility. It is an error in MU, as these files have been tested in both P5 and P6 with no problems.
Seems it's getting confuse by the inclusion of the two zeros and the spaces before the frist colon. So as far as I'm concerned the actually lt2 file hasn't anything wrong with it.
Cheers
Steve

Follow Predatron on Facebook www.facebook.com/Predatron3D or go to www.predatron.co.uk

That's odd.  The format for objFileGeom is indeed:

objFileGeom 0 0

Possibly the creator of Merchant Utility missed this?  For the sake of argument, have you tried a test by removing the '0 0' to see how MU responds?

Robert

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone

Missed the zip when posting first time.

The problem is with the name of the depthMapSize channels for the lights.
The string "Map Size" is the name of that channel in each of the lights.
If you replace it with "GetStringRes(1028,29)" (no quotes), then the utility doesn't complain.
Alternatively putting quotes around the name string also cures the problem.

You might also want to use the GetStringRes(1028, ...) forms of the names for some of the other channels.

The main gripe was that these files work in Poser 5/6 as is, and there were initially created in Poser, so why is there a need to make sure that any errors found by the MU should be set in stone. I would never have found that error, if indeed it can actually be classed as one. Thanks for highlighting this though, I have had a few explanations as to why.

Follow Predatron on Facebook www.facebook.com/Predatron3D or go to www.predatron.co.uk

It's a known issue with the merchant utility. It misreports on light files (camera files too, maybe.)

You can contact laetia to see if she will be making an update, but be aware she's no longer part of the testing team here - she's busy working on her own stuff ;-)

---

"you are terrifying
and strange and beautiful
something not everyone knows how to love." - Warsan Shire

It's not an error in the file, (Poser wrote it), so it's a bug in the utility, because that was the only dial where a space in it's name would cause the error report.

I had to resort to deleting lines from the file until the message went away (it only became obvious when I was left with a few lines in the light block)