I could confirm graphical anomalies on a few machines, but only with your project. You're including a DLL that uses a different DirectX version than Gamestudio. Theoretically this could work, but maybe the conflict between the two versions causes problems with some video drivers, or maybe theare's some other problem with that DLL.

Can you check out if you have the same problem when you remove that DLL from your project?

No, with other postprocessing projects, such as the shader postprocessing workshops, it does not happen here. But it's hard to tell because the effect is rare. It looks as if the data buffer on the 3D card jumps out of sync for one frame dependent on the content of the image. I'll check the problem in more detail in the next days.

If you have a _simple_ project where this problem happens too, please send it to the support. Maybe the reason is something in the shader code.

I just sent a small level to support. Hopefully this helps.

When will this be fixed?

After purchasing and putting Gstudio7 on my new computer I have this problem too(as in Slin's Photos). But it is random to an extent. It only happens on certain levels at a certain area all the time. As described here, it has to do with the new postproccessing commands, it affects the bloom, DOF, and heathaze shaders. The DOF and heathaze shaders are the recent ones just released as "Shade-C" in user contributions.

When I turn off all post processing, the problem goes away. It also seems to affect areas with more particles effects, I can even make it happen in areas it otherwise wouldn't using certain weapons that have more particle effects and sprites. And this seems to have a greater effect when the camera is moving fast. But it does happen when the camera is still. It also happens in fullscreen, just not as often.

Comp Specs:

Nvidia 8880 Ultra
Intel Core2 QX6850 Extreme @ 3.0Ghz
Windows Xp Media Center, latest updates
Latest Nvidia Drivers(Forceware 169.21)

After more testing, I noticed it's very widespread and appears in all my levels quite frequently. This is a pretty bad problem...

Yeah, it's still a large problem for me as well. I've been working on a postprocessing related project that I will need to submit in less than a month, and it appears this glitch will exist in my published project. Perhaps only for users with certain video cards, but still...

The 8800 series are very common though, and that is a problem.

I have already forwarded this problem to nVidia, but have no response yet. So I can't say when it will be fixed.

And I am assuming they will respond and fix it soon. Please update as soon as you fix it, it is a terrible thing to not be able to use any of the post processing updates for lite-c, this is why I converted to lite-c in the first place. Thanks.