rec.autos.simulators

I have updated my graphics demo a little.  I have added a "track",
lighting and have added some code to get some of the capibilities of the
graphics card and use them as fully as possible (I am still learning at
this point!).

Currently it is still attempting to render the whole of the track with
only the clipping in directx removing unwanted polygons.  I havent
decided on a culling technique yet, but it will be sorted out soon.

It will be slow on everything but the latest systems (due to the whole
track being rendered), what I want to know is that it works on all
decent graphics cards.  Its a little bigger this time because of the
track (1.7 meg)

here it is - http://www.racesimcentral.net/

Thanks for the help guys,
Ash

http://www.racesimcentral.net/

Well Ash, you've done it. Fails to load here "Error getting Direct3D".

Like I said before, not sure, but could be I'm still on DirectX8.0a. I'm a
bit hesitant to load Dx8.1 while still using the V3 (these upgrades are
historically very hard to back out of). You think that would be a "safe"
thing to try?

Jan.
=---
"Pay attention when I'm talking to you boy!" -Foghorn Leghorn.

<snip>
<snip>

System: P4-1.5GHz, 256 megs DDR RAM, WinXP Home, GeForce 2 MX-400 64
megs (is that a "decent" card these days...?)

44fps running in a window (800x600), 31fps in full-screen mode
(1024x768).

Very nice - other than the clipping problems you mentioned, I can't see
anything wrong (though I'd like to try an 800x600 full-screen mode, as
that's what I generally drive in).

Am looking forward to the next installment - this could give Racer a
run for its money in time!

--
"After all, a mere thousand yards... such a harmless little knoll,
really" - Raymond Mays on Shelsley Walsh.

The GPL Scrapyard: bits 'n' bobs at http://www.hillclimbfan.f2s.com

--
Biz

"Don't touch that please, your primitive intellect wouldn't understand
alloys and compositions and,......things with molecular structures,....and
the....." - Ash

Ah yes, thanks for trying it out Jan.  That is definitely a directx
version problem.  I have moved to Directx 8.1 recently (I found the joy
of directx debug levels ;)).  It will not work at all if 8.1 isnt
installed.  I havent had any problems at all with 8.1, however I am
using a geforce, probably the most standard card at the minute.  I
wouldnt upgrade to 8.1 on my account, its not worthwhile at the minute,
tis only (not that) pretty graphics.  Hopefully in the future i will
give you a genuine reason to upgrade directx :)

All the best,
Ash

Thanks for the positive comments David :)

I was pretty sure that fullscreen is 800x600, I will have to create a
small setup program to select your res and fullscreen / windowed.  I am
not sure why it isnt faster in fullscreen, but I am just learning about
the intricacies of direct3d - there is probably something I am not
setting correctly for fullscreen mode to take advantage of all the hardware.

I will try not to disappoint in future releases :)

All the best,
Ash

http://www.siroccoracing.com

Driving along the road, I get 160-200 fps. When I enter the grassy area the
number drops to 30! Apart from that it looks just fine.

Athlon T-Bird 1266, 256 MB SD-Ram, Win2kPro, Kyro 2 w/ 64 clocked at 175.

/Jens

<snip>

Came out at 1024x768 on my machine, and as I only have a 15" monitor
(lack of space) details are a little small. A res selector would be
fantastic.

--
"After all, a mere thousand yards... such a harmless little knoll,
really" - Raymond Mays on Shelsley Walsh.

The GPL Scrapyard: bits 'n' bobs at http://www.hillclimbfan.f2s.com

Very odd indeed, thats a very high FPS - alot higher than my Geforce 2
(or 3), but the FPS doesnt really vary for me on the grass, I dont
understand why it would, its only a big rectangle with a few polys,
should be simple to render.  You have me confused Jens :)

I will try to figure out why it might happen on the Kyro

All the best,
Ash

http://www.siroccoracing.com