I spent some time digging into the error log with my IBTC scene today.
There are tons of these, but they are just warnings. I don't notice any peformance problems in spite of a high RAM load. Most of them are very small: from 0 - 3 ms and, interestingly, mostly at frame -1, 0, or 1. So, right at the start of a clip, perhaps?
Curiously, I am experiencing performance problems on this PC right now and text that I type is being delayed appearing on screen. But it isn't my 6-clip and 3-shadow IBTC scene that is playing--it is the standard "Paint" scene that comes with iStripper and only has a single clip. My GPU really doesn't like motion backgrounds, it would seem. CPU usage (by vghd.exe) is only 9% and RAM is a paltry 300MB.
I just told iStripper to find a different scene. It chose The Penthouse Club and now I can type in real time again.
😊 I am banning Paint now.
Also just a warning. I had 7 of these each time the scene ran. This matches the 7 .png files that make up the scene: the background and 6 masks, each made from duplicates of the background image.
I opened each of them in GIMP and converted the sRGB profiles to GIMP's built-in profile. That did eliminate the warnings from the log. I will make sure to take this step with scenes that I create in the future, just as a best practice, but i don't see the need to revise my current scenes to replace the color profile. It doesn't seem to be causing any trouble. The Internet and
@TheEmu agree that it can be ignored.
Unknown node property "ambient"
Unknown node property "rotation"
These are just weird. The only place in this scene where the "ambient" property appears is the "light" node, and I know that's valid. "Rotation" spelled as the whole word, doesn't appear at all. I have used "rot" in clipSprites and I know that's valid, too.
i did a search to verify that "rot" isn't being used out of place anywhere, and it isn't. Also verifired that I didn't accidentally type "rotation" anywhere. That word does not exist in the file.