Strange 3D visual error [screenshot example inside]

Author

Message

billy777

22

Years of Service

User Offline

Joined: 9th Jan 2003

Location:

Posted: 3rd Jun 2004 03:33 Edited at: 3rd Jun 2004 03:46

Link

I've gotten this error before - please see screenshots below...

error #1
jagged lines around the edges of two objects intersecting

error #2
It basically occurs when you have one object behind another object and move the camera away. The object behind becomes visible through the front object.

What im trying to do is have random scattered pools of water throughout my landscape. So... I place a box(texture with water) beneath my matrix and randomly set my matrix height to dip down into my water object - providing pools of water throughout my landscape - however - as you can see it doesnt work cleanly - since the pools have extremely jagged edges and when the camera looks at the ground from a distance it gets really screwy. (even showing through places it shouldnt even show water)

Does anyone have any ideas on how to correct this error? Ive tried a few things - but not sure what to do.

Thanks

Back to top

Profile PM

DARKGuy

21

Years of Service

User Offline

Joined: 28th Nov 2003

Location:

Posted: 3rd Jun 2004 08:18

Link

A trick that works very good, is to make everything small, EVERYTHING, so for example, if the matrix was 1000 units big, make it 100 units small, and scale and move everythign in relation to that, it's just avoiding using big numbers for distances, or else you'll get that error. Isn't an error really, it's caused by the Z Buffer

...

Try that

:: Pentium 300 Mhz, 8Mb video card, 64Mb RAM, 5 gb & 1.6 gb HD's, W98SE, Sound Blaster AWE 32 ::

Back to top

Profile PM Email

Lukas W

21

Years of Service

User Offline

Joined: 5th Sep 2003

Location: Sweden

Posted: 3rd Jun 2004 14:06

Link

I also used to get this problem, but with the 'set camera range' command it got fixed!

so now I usually use 'set camera range 5, 10000'
and it doesn't get screwed.

but you could use 10 instead of 5, it will be better, only the objects are dissapearing too soon infront of the camera, so I suggest you to use 5.

Thief 3 : Deadly Shadows, The BEST game in the WORLD!

Back to top

Profile PM Email

David T

Retired Moderator

22

Years of Service

User Offline

Joined: 27th Aug 2002

Location: England

Posted: 3rd Jun 2004 15:22

Link

I had the problem when matrices intercepted each other - as already suggested setting set camera range to something like 5,xxxx fixes it.

Two strings walk into a bar. I'll have a pint says the first$%ASLDJ09920D"$"$D. Excuse my friend says the second, he isn't null terminated.

Back to top

Profile PM Email Website

Phaelax

DBPro Master

22

Years of Service

User Offline

Joined: 16th Apr 2003

Location: Metropia

Posted: 3rd Jun 2004 16:45

Link

oooo, looks like an rts to me. Got a theme set in mind?

"eureka" - Archimedes

Back to top

Profile PM Email Website

billy777

22

Years of Service

User Offline

Joined: 9th Jan 2003

Location:

Posted: 3rd Jun 2004 18:25

Link

Thanks for the quick response people. However I already have my camera at 5,10000 - i will try 10 and possibly making everything really small - see if that works.

Yes - You're right.Its a space strategy. You can see some more info and screenshots here...

http://www.lasthalfofdarkness.com/darkgalaxy

Back to top

Profile PM

DARKGuy

21

Years of Service

User Offline

Joined: 28th Nov 2003

Location:

Posted: 4th Jun 2004 06:30 Edited at: 4th Jun 2004 06:43

Link

Use one of those two methods..if you make everything small and put a high value in the first parameter of set camera range...