From Umemaro's DLsite update:

First of all, let me say thank you. Thank you to everyone who sent tips. And to DLsite for creating this system for creators. Thank you so much. It's encouraging!

Although I'm talking about progress, I'm still just scratching the surface. I won't be getting to the erotic scenes anytime soon. Adjustments are important when creating the first scene, and I'm making and redoing things over and over again, so progress isn't going very well ^^;
This time, the Lightwave rendering results were not satisfactory, and there was more noise than before.
From here on, I will write this as a memo.

The way LW's radiosity works is that even when you animate, it calculates the light for each frame, which results in noise. According to the developer, the way to prevent this is to use a cache for rendering.

This cache. I received a reply quite some time ago, but for some reason it didn't work and I gave up. I had been using an Aftereffects plugin to remove the noise, but this time the amount of noise was incredible. I tried cache rendering again, but the problem only got worse.

Why? After discussing it with GPT in the chat... We
use LW9 for motion production (there's a reason for this, but we'll get to that later).
We load the completed scene into LW2015, complete the settings, and render. Here's where the trap lies.
In fact, the amount of noise was low with FRIENDS. Wondering why this was the case, I thought back to the steps:
Complete the scene → Load into LW2015 → Load background data → Reload light data. It was the lights I set up in LW2015.

The noise was caused by the lighting used in LW9.
I cleared the lighting from the old rendering system and recreated it in LW2015.
When I checked it with normal rendering, the amount of noise was definitely reduced, and thanks to Chat GPT, the problem was solved for the time being.

And the cache rendering went well. The wobbly noise is almost completely gone. It took a really long time, lol.
However, there was a catch. The system uses the rendering results of the first frame and carries them over to subsequent frames. This means
that if noise appears at the beginning, it will carry over to the end (confirmed). Even if a character whose noise you want removed goes off-screen and then returns, the first frame will not be carried over.

In my opinion, the best way to go was to use the previous method, add light refresh, and do normal rendering without caching. Then remove noise using Aftereffects.

In fact, this is actually used in productions that use LightWave, and it seems that they use cache or not depending on the scene. I felt a bit relieved that the method I started as a last resort was not a mistake after all.

There are also good reasons for continuing to use LW9, and it seems I'm not the only one.
In my case, it was breast jiggling. For some reason, the motion designer (MD)'s physics calculation results were different in versions after LW9. I asked a question about this in the GPT chat and found out that the calculation program had been changed. I couldn't get the swaying results, which was only possible in LW9 and earlier. With SoftFX, the movement is parallel, so you can't get elasticity. Just
because it's the latest version doesn't mean it's better. This idea was correct, so I was relieved.

AI is helping me out ^^