Finally version 13.3.686 has fixed this problem for me. Hooray!

blackbonner posted at 2:49 PM Thu, 8 February 2024 - #4481366

I can confirm that problem.
I re-created the morph, exported it into my main library, deleted the V4.2, loaded her again.
The morph from the library is getting loaded, the dial shows up, but it's not working at all.

By the way, thanks to everyone that has read and contributed to this thread.

I was convinced it was something due to my ancient runtime or some of the tweaking I had done somewhere.

Yes, please submit a support ticket. I'll try to grab it when it comes in since I've already been trying to figure this one out.

Thanks. It's already being looked into.

What I would do first is Spawn a full body morph for the figure. This should take the shape from the magnets and create an actual morph so that you don't need the magnets any longer.

Sorry, I've failed to explain myself correctly. I deform the body part with a magnet and then spawn a morph target. That MT is what I export using the export morph injection option and then load from the pose library.

Thank you all for your comments. Here's an illustrated version to make things clearer:

On P13 I load V4 from an outside runtime and using a magnet I create a chest MT I'll call "horn". Then export it as a morph injection to the poses folder of that same runtime.

P13 creates .pz2 and a .pmd files as seen on the folder on Windows Explorer.

Then on P12 I load V4 and go to the poses library...

...and load "Horn". It works.

Back on P13 I delete the V4 and load a new V4 and then load the Horn pose...

...and while the dial appears it has zero effect on the figure.

It's not that P12 injections for V4 don't work on P13, injections created on P13 also don't work. They all work fine on P11.

And when I try the same with M4 I find no problem at all.

I keep thinking there's something wrong with my setup because otherwise a lot of other people should have had this problem. I guess I'll have to submit a ticket.

 So ... do you have the runtime folder that you saved your morph injections into set as an external runtime folder in Poser 13? That might be the issue.

Both the figures and the morph injections are on the same runtime, an external one added to the P13 library. Otherwise I wouldn't be able to load the injection from the library.

The only OTHER thing that I could think of is, if the morph injections rely on Victoria 4.2 morph packages, do you also have the runtimes that contain Victoria 4.2 and all her morphs included as external runtimes for Poser 13?

They don't, they are MTs created with magnets inside Poser.

That puts my mind at rest. I'll follow your advice, thank you very much!

Thank you. I've tried those values but the noise keeps appearing U_U

I have tried tweaking every setting, even to the point of not just turning off the lighst but deleting them just in case their mere existence was the cause. All I get is some difference in the noises's "seed".

My point is I've seen around a lot of renders done with mesh lights and none showed this noise nor anybody mentioned finding this problem. Does it happen only to me? Is there some kind of weird incompatibility between Poser Pro 2014 and my motherboard and/or OS? Then why it happens in Poser 11 too? It makes me mad because besides that fact mesh lights behave wonderfully. Look at those soft shadows.

Thanks but I think that's not the problem. This is the result using a sphere. In the first example I used a cube but I've come across the same noise using a single sided square also.

Apparently P11's Firfely engine is NOT the same from PP2014. Rendering with the same settings with indirect light creates artifacts in P11 that doesn't appear on PP2014.

Thank you very VERY much!

The .bum is a strange, poser exclusive format. When a texture that uses it is loaded in Poser 5 (and, I guess, P6) it's plugged into a special "gradient bump" node, different from the standard bump plug, as it doesn't behave as an average b/w bump map.

In fact when I switched from P4 to P5 I had no problem loading P4 metarials. They just didn't look so good as P5 ones.

I don't think the problem is P6 being unable to load P4 materials, as it has the "gradient bump" node too.

I've been playing with CREditor and the problem seems to be CR2 store the full path for the "visible" textures (runtime/textures/etc) but for "invisible" ones it just stores the file name. Somehow this isn't a problem for P5 (as I usually store color and bump textures in the same folder) but for P6 it is.

Thanks for your help. I hadn't found that thread. Anyway my problem is different, as P6 has no problem finding the geometry and the "visible" textures (located in the same runtime as the ones it doesn't find).

I added the P4 runtime the way the manual (and several threads here) says, going to the upper level on the library and clicking the "+". In fact I've removed and added the runtime to make sure it was correctly added.

I've tried using CorrectReference, but it keeps happening the same thing.

I've got a similar problem. The weird thing is P7 has no trouble finding the obj files, nor any texture that is displayed in preview mode. But somehow it can't find the non visible ones (bump, displacement, anyone on a cartoon or outline displayed element...)