Just as an update, Ive now tried on 3 different systems with 3 different video cards, all same results, and not just with my code, also with the several tutorials i ran as reference.

Before Update, they run wonderfully

After update, terrible shearing/horizontal lines.

Did you try redefining the triplebuffer to a double? If that doesn't fix it then could you post a pic so we could see exactly what these lines look like? I have experienced another "lines" problem since the latest update. After my system has been on for a while, and when running a 3dGS app, there are thick black or white lines all over the place, bad flicker, and other weirdness. If I play a non-3DGS game, after this, it affects it, as well. Perhaps this is what you've been describing? The triplebuffer/refresh shearing problem is an entirely different looking anomaly.

Hello,

First, let me say thank you for you replies!

I tried the triple buffer a couple weeks ago, unfortunately to no avail. The distortion does not show in other 3d applications. Taking a screenshot is near impossible though...i took about 5 and failed to capture it, as its only when moving the screen. It resembles clipping, and comes off the nearby structures, whatever type they may be.

Thank you again

Quote:

---

i took about 5 and failed to capture it

---

I had the same issue with 6.31. I also found it nearly impossible to capture via screenshot because the anomally never shows in them.
Only happened in A6. Never had the issue in 5.5 or any other software.

Zeroframe, sounds like your describing exactly the issue I have at hand. Did you ever get it resolved?

Thank you!

I had to bump the monitor's refresh rate to 80HZ from 65.
The problem became much less noticeable.
I reloaded my video drivers, reinstalled dx9 also.
I ended up going back to A5.5 anyway for the time being due to other anomallies
with a6 like **ahem** collision.
Good luck!

Thats good to know..I'll have to give that yet another go much sooner than I was planning!
Couldn't find that in the documentation, so this helps!

It's under enable_polycollision. It also says that setting it to 0 disables the physics engine, but I've been told that that is not the case. I haven't enabled physics in a while so I can't confirm that. Old collision is supposed to be removed one day, but that won't be for a long time, I'm sure. The c_instructions will be required if you use octree levels. Hijack over.

@destro55: Have you tried a video capture? I'm not sure if it'll pick it up with that, but you can try out Fraps.

Thanks OB, your triple buffer pointer fixed it for me,
Cheers.