I put a work-in-progress image in that other thread but here's a completed one. This is a 20-image story, the first 12 are up in my gallery already https://www.renderosity.com/users/ChromeStar/gallery , I'm posting the rest 3 per day. This particular image is #14, so sneak peek for tomorrow.

The developers could say for sure, but "no binary for GPU" sure sounds like hardware that is not supported and not going to work. Hopefully the regular non-Optix option works.

It's a laptop so upgrading the GPU is not feasible without replacing the computer.

Hmm, the GPU is 10 years old. The docs say "OptiX-accelerated raytracing requires Nvidia RTX or Turing GPU, or newer." And the K3100M is Kepler, not Turing. So you might be out of luck for Optix.

Restart Poser, then pick the non-Optix GPU option. Does it work? Note that it will not work if you already got an Optix error and did not restart Poser, you need to restart Poser to clear the error.

Does CPU rendering work in P13? If so, that clarifies the issue is GPU-related and not a more general problem with the scene.

All gray seems suspicious. If you look in the upper right, is there an icon there with a dialog bubble? Click it to see the log. Is there a CUDA error? If you do have one, you'll need to close Poser and re-open it. Sometimes the skinning mode seems to be an issue here: select each figure, go on the menu to Figure, change it to Unimesh. Could also be an issue with a particular shader, the log might give a hint about which one.

It looks like it's just on the character's skin, so probably a shader problem. Can you post a picture of the material for the character, for the arm, face, or neck?

Ok, spoke to support. It looks like RedPhantom's idea was spot on. Support noted there were no facet groups in the .obj file (which would be lines starting with "g") that I sent them. And Poser needs those to assign the geometry to the figure's body parts in the scene.

However when I did some additional looking around (thought I would compare the .cr2 file to see if it had any hints), I found there was another copy of the .obj file by the same name in the Characters folder. So I guess initially it pulled the one from Characters because it was in the same folder as the .cr2 file, but on reloading it went for the one in the Geometries folder, and that's what failed. I copied the one from Characters over the one in the Geometries folder and it worked correctly.

Good thoughts. The pose camera centers in the middle of everything. There is a red selection circle around the middle of the scene (which should be the middle of the carousel), but it's too small. If I increase the scale, all the parented stuff gets bigger and moves up, and the red circle grows, but nothing new appears.

The list files script tells me "Runtime\Geometries\Anniemation\Carousel\Carousel Complete.obj" got loaded, which looks correct. There is also a "Carousel Complete2.obj" in the same geometries folder, but Carousel Complete.obj is the one referenced in the .cr2 file.

What other diagnostics have we got hiding in there? I ran printGeomStats and it says this, which seems problematic:

Carousel 2
     Body     no geometry
     CenterOfMass      360 polys          324 verts
     GoalCenterOfMass      360 polys          324 verts
     base     no geometry
     poles     no geometry
     auras     no geometry
     emitters     no geometry
     lights     no geometry
Carousel 2 totals --> 720 polys      648 verts

I'm sure there is supposed to be some geometry for those parts. But that seems to indicate the problem is loading the geometry rather than some kind of display, position, or scaling issue.

None of the eyes are greyed out.

I didn't hide any whole figure. I mean, I hid the girl's toes to prevent pokethrough, but that shouldn't do it. I'll try a restart.

I'm so behind on even downloading all the items I have bought. But I thought I'd at least try these out. I did give it a materials upgrade from the original PoserSurface concrete.

Since this is the last release of 13, it probably doesn't make sense for the release notes to still say "This is an Early Access release" but....

Poser 13.3.680 - 2024-03-08
--------------------------------
- Talk Designer: Transcript correctly clears out previous supplemental text when loading a text file. #2323 (App), #472 (Beta)
- Talk Designer: Updated default Viseme mappings so all Cartoon Characters work. #2328 (App), #473 (Beta)

Poser 13.3.669 - 2024-02-29
--------------------------------
- Fixed issue with Vicky 4 pmd not injecting external morphs. #2309 (App)
- On the Mac: fixed Crash when renaming a figure from the hierarchy panel. #2294 (App)
- Replaced current Lip Sync tech with Rhubarb Lip Sync. #2308 (App)
- Fixed 'Install from Zip Archive' to be case insensitive on .ZIP suffix. #2311 (App)
- Scenes sent to Render Queue correctly recognize the adaptive sampling setting. #2297 (App)
- Scenes with HSV node no longer ignored in Render Queue and Render in Background. #2292 (App)
- Normal maps correctly rendering when using PoserSurface root. #2276 (App)
- Replacing figures or props now gives warning message saving to the library when file compression/uncompression doesn't match. #2301 (App)
- Corrected Simple Color node so that it no longer creates invalid results in the cg shader code. #2286  (App)
- Corrected Joint center going into a confused state in the Joint Editor. #2318 (App)

It's been very slow loading poses for me, and I'm not afraid of the registry, so I took a look. It won't let me delete the BAM entry for Poser though. I also note that the linked page says "entries older than 7 days are removed when Windows boots" and that's not actually true (at least in Windows 11). Unless there is another entry I'm not seeing currently, because I just got back from a week-long trip and nothing has been used in that time.

I notice for FTH, though, that there is a key "ExclusionList" and wonder if it could be excluded there if it's a problem.

ChromeStar posted at 3:52 PM Mon, 5 February 2024 - #4481278

That's procedural? Very nicely done. I don't suppose you'd like to share?

Sharing is caring: Knit-Procedural-Red.mt5.

odf posted at 5:05 PM Sun, 4 February 2024 - #4481250

Thanks! I was trying to make my procedural knit pattern look better in closeups by using bump, displacement and subsurface scattering together. I'm not a material room wiz, but I think it turned out quite nice.

Regarding the ends, I would think the squareness that Y-Phil mentions (and I agree) could be addressed with a transmap (so it's simply not square) or add a map that overlays or replaces the ends of the pattern, e.g., a horizonal line across the weave to imply a hem.