Terrain Engine
hi,
i''ve finished my first stable alpha release of my terrain subsystem its at - http://www.geocities.com/chicoze2/ch3dterrain0.03.zip
it uses full-mesh CLOD and height based texturing
hope you like it.... if you can , post here the performance at which 1)Pixel Error 2)Tri nº (average...) 3) Comp specs if possible
thanks in advance, ChicoZe
With this pixel error at 4.0 (default) it ran at only about 25-30 FPS. With pixel error as low as possible I got about 80 FPS
My computer specs:
TBird 1Ghz
256mb
GeForce2Mx
Keep up the good work!
/MindWipe
"If it doesn''t fit, force it; if it breaks, it needed replacement anyway."
My computer specs:
TBird 1Ghz
256mb
GeForce2Mx
Keep up the good work!
/MindWipe
"If it doesn''t fit, force it; if it breaks, it needed replacement anyway."
It ran ~12fps with 12462 tris, default pixel error, on a Duron 700 w/ Geforce2.
streampark
http://www.geocities.com/streampark - WayOut Engine v00.2
''That''s it man, game over man, game over'' - Aliens
brb
streampark
http://www.geocities.com/streampark - WayOut Engine v00.2
''That''s it man, game over man, game over'' - Aliens
brb
http://www.geocities.com/chicoze2/chicos3d.html
New release and screenshots - almost twice as fast
thanks , chicoze
New release and screenshots - almost twice as fast
thanks , chicoze
Tried the updated version and got these results:
pixel error 1.0 - 4.0 100fps (flickering display)
pixel error above 4.0 300 - 600fps!! (badly flickering)
System spec:
athlon 1.4ghz, 256DDR, Geforce2 MX400, WindowsXP pro.
Everthing worked fine just flickered like a bitch!
Edited by - newframe on January 5, 2002 9:34:43 PM
pixel error 1.0 - 4.0 100fps (flickering display)
pixel error above 4.0 300 - 600fps!! (badly flickering)
System spec:
athlon 1.4ghz, 256DDR, Geforce2 MX400, WindowsXP pro.
Everthing worked fine just flickered like a bitch!
Edited by - newframe on January 5, 2002 9:34:43 PM
Overall it''s good work, but:
1) Even with the pixel error set to 1.0 there is noticeable popping. Could this be a problem with the metric you''re using?
2) For the love of God, why does pressing ESC not get me out of the program???
1) Even with the pixel error set to 1.0 there is noticeable popping. Could this be a problem with the metric you''re using?
2) For the love of God, why does pressing ESC not get me out of the program???
case WM_KEYDOWN: switch (wParam) { case VK_ESCAPE: PostQuitMessage(WM_QUIT); break; }break;
hi,
i''ve posted on the webpage a new release of the executables that (almost) fixes the popping problem. Its strange why it flickers on your comps cos in mine it runs solid...but my comp is a little odd for todys times(oldoldold)...
thanks for the help and the responses so far...
ps: could you describe the flickering better? (does the text disappear?)
chico
i''ve posted on the webpage a new release of the executables that (almost) fixes the popping problem. Its strange why it flickers on your comps cos in mine it runs solid...but my comp is a little odd for todys times(oldoldold)...
thanks for the help and the responses so far...
ps: could you describe the flickering better? (does the text disappear?)
chico
quote:Original post by chicoze
ps: could you describe the flickering better? (does the text disappear?)
chico
I''ve just tried the newer version of execs and still have the flickering. I tried under XP then ME and still the same.
The text does not flicker.
Landscape only seems to flicker when framerate goes above about 200.0fps (changing my monitor refresh rate makes no difference)
The flickering is best described as the entire landscape occasionally not being rendered for the odd frame -
hope this helps
(if I get time I''ll have a look at the source...)
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement