Hello again

I thought |I had better start a new thread with this one.

The issue I have is quite simple really:

1. I loaded a G2 figure
2. I deleted all the lights
3. I loaded a new light
4. I changed the light into an area light
5. A window appeared saying the below and it carried it on saying it LOL

Traceback (most recent call last):

File "/Applications/Poser Pro 2014/Runtime/Python/addons/Reality/init.py", line 732, in refreshRealityData

File "/Applications/Poser Pro 2014/Runtime/Python/addons/Reality/init.py", line 970, in updateSceneData

File "/Applications/Poser Pro 2014/Runtime/Python/addons/Reality/init.py", line 459, in hasLightChanged

File "/Applications/Poser Pro 2014/Runtime/Python/addons/Reality/init.py", line 362, in getLightData

KeyError: 4

For info, I no longer have PP2014 installed.

Any ideas?

I have found that PYC files have the path hard coded into them. That is the path to the file on the computer that they were compiled on not the path on the computer that they are run on.

At least I have found this in relation to some Wardrobe Wizard files, others may be similar.

PhilC posted at 5:59AM Tue, 24 November 2015 - #4240573

I have found that PYC files have the path hard coded into them. That is the path to the file on the computer that they were compiled on not the path on the computer that they are run on.

At least I have found this in relation to some Wardrobe Wizard files, others may be similar.

So this could be that I have not loaded the lights and indeed content to the default location favoured by the installer?

It is probably best to install the files as the writer of the program intended rather than to some other arbitrary location.

Which would mean that if you change file locations you will need to edit the PYC script to reflect those changes.

Hmm okay.

It just seems a bit short sighted of Smith Micro not to consider this issue.

The area light is a new function bundled with P11P.

As part of the installation process it gives you the option to install your content elsewhere.

Yet when you do the area lights stop working.

If this is the case then the installer should say that if you choose to install your content elsewhere then you can forget using area lights unless you start editing the scripts LOL.

Where would I find the pyc script for the lights so I can edit them

Thanks again for the help on this guys

I'm going to step in here even though I hate this fucking useless forum because i don't like to see SM maligned unfairly.

The advice you've been given above is nonsense.

Everything is installed in the right place. There is no .pyc script for the lights. You can't edit a .pyc script anyway.

The problem is that you've added the PP2014 runtime to your P11 installation, and the PP2014 runtime includes a (properly) installed version of the Reality addon that is incompatible with some of the new features in Poser 11, such as the new area lights. Reality is choking when trying to process a type of light it knows nothing about.

There is an update to Reality which makes it compatible with P11 on its way soon - you should have been notified about that. In the meantime, remove Reality from the PP2014 runtime, or don't link to that PP2014 runtime from within P11. Then get the updated Reality when it's available.

Malysse posted at 8:37PM Tue, 24 November 2015 - #4240721

I'm going to step in here even though I hate this fucking useless forum because i don't like to see SM maligned unfairly.

The advice you've been given above is nonsense.

Everything is installed in the right place. There is no .pyc script for the lights. You can't edit a .pyc script anyway.

The problem is that you've added the PP2014 runtime to your P11 installation, and the PP2014 runtime includes a (properly) installed version of the Reality addon that is incompatible with some of the new features in Poser 11, such as the new area lights. Reality is choking when trying to process a type of light it knows nothing about.

There is an update to Reality which makes it compatible with P11 on its way soon - you should have been notified about that. In the meantime, remove Reality from the PP2014 runtime, or don't link to that PP2014 runtime from within P11. Then get the updated Reality when it's available.

Hmm, makes sense. I'll pop over to the reality website and see when the next update is.

Thanks for the help albeit a little strongly worded LOL

Just by way of completing this thread it does appear that the reality issue was the problem. The files were located on my C drive in the old content folder. I've just manually removed then and the problem has gone.

With the benefit of hind sight It might have helped had I mentioned that I had reality installed so apologies for not doing so.

Thanks all once again.

I'm more curious as to why Pro11 is reading an addon installed in the 2014 runtime, or why Reality shows up under Render in Pro11. Shoot, it will even open if you click on it.

bevans84 posted at 5:23PM Wed, 25 November 2015 - #4240874

I'm more curious as to why Pro11 is reading an addon installed in the 2014 runtime, or why Reality shows up under Render in Pro11. Shoot, it will even open if you click on it.

From what I can gather it is because I had imported the 2014 runtime library into my Pro11 application.

You can add your 2014 runtime, just make sure you remove the "Python" folder. You will end up with duplicated and as with this case out dated scripts. You should add any add-ons such as Reality to the new location following the authors steps.

nerd posted at 7:52PM Wed, 25 November 2015 - #4240900

You can add your 2014 runtime, just make sure you remove the "Python" folder. You will end up with duplicated and as with this case out dated scripts. You should add any add-ons such as Reality to the new location following the authors steps.

Now, I didn't know that. I've just been through my old runtimes and deleted all the python folders LOL.

I had python folders going back to poser 8