I am encountering some strange problems with PHC Nykta on the 01Sculp zone that I have never seen happen before inside Poser's Material Room.

After loading my character and the Nykta hair into my scene normally, I applied the PHC #18 texture to the hair and went into the Material Room to edit the shader. On the 01Sculp zone, the nodes and PoserSurface palette are inaccessible, as can be seen in my attached screencapture.

Material Room screencapture

By using my scroll wheel, it sometimes toggles between the PoserSurface palette and the two nodes that are attached, but other times it does not. I have checked the other colour options and all of them do the same thing for the 01Sculp zone. However, checking the base Nykta, this issue does not happen.

I have tried closing Poser and restarting it. I tried downloading the .zip for the hair texture and reloading the files. I tried creating a new document and only loading the hair and applying the PHC shader. I tried dragging the PoserSurface node downwards in the Material Room in attempt to get everything to display at the same time. I have also tried deleting the two nodes and reattaching them manually, but as soon as I leave 01Sculp and go to a different zone, upon returning to 01Sculp the problem is back. None of these solutions worked.

I am using Poser Pro 2014 version 10.0.5.28925.

Any help of fixing the problem or an explanation of what is going on would be greatly appreciated!

Is this the only content that is giving you a problem? Which OS are you currently running? And where have you installed your content? The questions may not have any bearing on your issue, but the app is not behaving as it should for a reason and we need to gather more information before offering a solution. Also, do you have the latest SR installed? If not, I would recommend downloading it from SM; there may be a fix for this problem already.

Yes, the problem is only occurring with this specific PHC texture add-on and it is only happening to Nykta. I have loaded several other hairs that I have the PHC add-on for an all of them behave normally. I have never seen this sort of screen in the Material Room before.

I am running Windows 7 64-bit Ultimate edition and my content is all installed in external Runtimes on a partition on my hard-drive. The PHC add-ons are in the same Runtime as the Nykta base product. Comparing the version number on SM's page and the version number of my Poser, yes I am running the most recent SR.

Sounds like you're doing everything correctly. Either one of two things come to mind, a corrupted file or a vendor error which was never caught be the beta testers. If it is an inherent problem from the source, then many other users would be experiencing the same issue. That would be easy determine from others reporting back to the vendor. Try downloading the files again just in case there was a corruption if you are able. Otherwise, contact the vendor for assistance.

I have already downloaded the .zip file from my account, extracted the files and replaced them all in my Runtime. When this didn't work, I contacted the vendor and she had a look at her files and wasn't encountering the problem with her textures. So those two, a corrupted file or vendor error, can be ruled out since I already took measures to rule those out before I posted a topic on the forum. It was Peggy's suggestion that I posted a topic on the forum, since she didn't know what could be causing the problem and her files checked out. (She sent me a screencap to show me.)

It's all very frustrating, with it only happening to this PHC pack and the base product behaves normally, and the strange behaviour making the nodes inaccessible so it's not something I can really work around. Unless I want to be remaking the nodes for that zone every time I want to make a simple change.

Tomorrow I will check on my second computer if the problem happens there as well. Right now, it is 2:37AM and my second system is in dire need of updating before I can check anything.

I encountered a system failure on my second desktop so I am having to fix that before I can check if Poser on that machine has the same problem with the Material Room.

I should be able to check it today or tomorrow, but in the meantime, if anyone has encountered a problem like this or has some suggestions of what else I could try to fix it, it would be appreciated.

After getting my secondary system back online, I have opened Poser and added V4 and the Nykta hair and I have encountered the same problem with the malfunctioning Material Room on the 01Sculp zone. The version of Poser on my secondary machine is the same that is on my primary machine, 10.0.5.28925.

So, if anyone has any ideas about what is causing this problem or a way to fix it, I would appreciate it. There is nothing else I can think of trying or that I haven't tried already.

Thank you.

Can you copy the material itself to another object, such as the Poser single sided square? Then perhaps copy it back and see if that makes any difference. Or even save the material out on its own, just as a mt5,

Maybe even take a look at the model's cr2 after the materials have loaded, see if you can spot anything weird about that particular body part.

Other than that, I got nothin'.

If I copy and paste from the 01Sculp zone and paste onto the hi-res square, then the Material Room displays normally; the PoserSurface and the two nodes are visible on the same screen. Likewise if I paste the nodes onto the pyramid primitive. When I copy and paste them back onto the Nykta hair in 01Sculp where they belong, the Material Room displays incorrectly - the way it appears in my screencapture.

To look at the model's cr2 file and the texture is applied... I have no idea what is normal and what isn't in those files. Also, I don't understand how looking at the cr2 file will reveal anything when the model with its base textures behaves normally. It is only when I apply the PHC textures to the Nykta hair that the 01Sculp zone displays incorrectly in the Material Room.

I wondered if the material surface showed any obvious differences between when the material is applied and when it ain't. Just a wild stab in the dark, so to speak.

I will try applying the PHC to Nykta, save it out to get the cr2 and then compare it side by side with the original. I won't have any better idea of what I'm looking at, but comparing side by side, I will spot any differences.

If nothing shows up, I'll just live with it. It could be worse: it could be a terribly complex shader that would be a nightmare to recreate every time I wanted to make some changes to it.

I just tried looking at the cr2 file in Poser File Editor, comparing Nykta with the PHC texture applied and the original file, but it is as I said previously: I don't understand what I am looking at, or even know what I am looking for. To me, the cr2 files look the same. I have tried everything I can think of, it happens on two of my machines running Poser Pro 2014, with the most current SR, Peggy/P3D-Art has never seen this before and 01Sculp behaves normally for her, and so far no one on the forum has come forward having this problem themselves...

I'll just live with it, and hope the problem never happens on something with a more complex shader.

Hope this problem is solved for you by now .. Since we both looked at it and it is not my PHC expansion causing this .. It is developed on Mac in PP2014 and tested in Windows

Just curious cause of course I hope it is solved so you can fully enjoy this product ..!!

No, unfortunately the problem is still there and I have no idea what is causing it. I think it's just me being 'special' that I can get this problem on both of my machines, running the same version of Poser, with the same content, the same Windows Ultimate 64-bit.

It doesn't matter though. It is easy enough to delete the nodes and recreate them every time I want to make some adjustments to the Diffuse colour to darken the textures up a little bit. It's an awesome product though, and this little niggle isn't going to stop me from using PHC on Nykta. Even if I have to wrestle nodes into submission! ;)

I am still hopeful that someone, somewhere will either know what is causing this problem or someone else is having the problem as well. Right now, I'm just living with it and hoping it doesn't appear anywhere else.