Dramatic? That's staggering! Good work, guys. Presumably performance
will again increase with the 3d chipsets once you start coding for them
(Creative Labs' 3dBlaster etc). Time to figure out more textures -
realistic clouds, dynamic skid marks etc :)
Mike.
>Quoting rickgenter from a message in rec.autos.simulators
> ri>Path:
>Rick,
>WOW, that is great news! Will it be possible to update Nascar for
this
>optimization? Or even a NEW version of Nascar with this added
improvement?
>I'd be more than happy to pay for that type of frame rate increase. :)
>Andy
So, can we expect an update for NASCAR Racing with this new texture mapper, or
is this already the case with the NASCAR Racing for Macintosh/Windows??
Harald
It will be in NASCAR Racing for Windows. I believe we are planning to do
an update to the DOS version at the same time, so it should be in there as
well.
Rick Genter
Technical Lead, IndyCar Racing II/NASCAR Racing for Macintosh/Windows
Papyrus Design Group, Inc.
That's a good group to look down on. It sounded like you were blasting
someone for not upgrading, rather than flaming, though.
->Unless you have the minimum or recommended processor for a given
->program...dont insult the developers/product.
I didn't. The owner of the computer mentioned above did.
... Two writes don't make a novel.
->(Robert Berus Jr) writes:
->>
->>Unless you have some money to hand out to everyone, don't insult
->people
->>for the computer they have.
->>
->>
->>So...you're advocating that folks without enough 'horsepower' to run
->Nascar start flaming PAPYRUS?? What nonsense!
No I'm not...I'm saying don't insult people for their computer. Where did
I say anything about flaming Papyrus?
... Everybody is ignorant, only on different subjects.
->*previous* computer was an Apple IIe!)
Exactly...someone who understands....I had an Applie IIc....still sittin'
in the box. <g>
Oh...I just started playing NASCAR last night....a great game...I'm still
in the wreck anything and everything stage, so Bristol is a fun track. <g>
... If I were here more often, I wouldn't be gone so much.
You may be slightly missing the point. I have read a post earlier regarding F1GP2 where someone was
"flaming" Microprose and suggesting that they would be "selling out" if they didn't spend ages
tightening code and/or compromising the detail so that the game would run on a 486. Personally I
just spend quite a lot of money on a Pentium so that I COULD enjoy these games in full detail. I
have no problem with games being made to run on so called low-end equipment, I just hate to think a
product could have been better but was hobbled to allow less powerful machines to run it.
If you can run F1GP2 in low res with no detail on a Morphy Richards toaster, I'm delighted - as
long as I can enjoy it in full SVGA light-sourced, texture-mapped, full detail splendour. Voila,
we're both happy.
Cheers!
John
> >>As for hardware you need the equivalent of a low end Silicon Graphics
> >>workstation. That equates to a high end Pentium, very high end (p120 with
> >>16MB). (I know comparing a high end pentium to low end SGI system is a vile
> >>and despicable insult to SGI and I apologize to SGI for it).
> >No true,
> >I am running NASCAR on a 90 MHz Pentium and it runs just fine. I know several
> >people running NASCAR on a 486DX4-100 with 16 MB of RAM and it too runs fine. The
> >video card is the big one to watch out for as well. I would recommend an ATI Mach
> >64 PRO Turbo, or an accelerated S3!
> The big burden is when it comes to SVGA mode. If you up the res., the amount
> of texturing is going up by a factor of four and this part of the game represents
> the greatest hit on the CPU.
> If you want a benchmark, I've tried it on a Dell P133 with 16 Mb RAM, 512Kb
> burst cache, #9 Motion card ( which gets a rating of '1' in WC3 ) and you
> _still_ have to turn off track texturing in SVGA mode to get 25 fps.
> Let's hope that F1GP2's SVGA mode is a little kinder on the old CPU -
> Crammond has written virtually all of the code in assembly with efficiency
> as his main aim.
> Fraser
>>>>I have a 486/33 and it sucks. I love Nascar Racing but I
> >>As for hardware you need the equivalent of a low end Silicon Graphics
> >>workstation. That equates to a high end Pentium, very high end (p120 with
> >>16MB). (I know comparing a high end pentium to low end SGI system is a vile
> >>and despicable insult to SGI and I apologize to SGI for it).
> >No true,
> >I am running NASCAR on a 90 MHz Pentium and it runs just fine. I know several
> >people running NASCAR on a 486DX4-100 with 16 MB of RAM and it too runs fine. The
> >video card is the big one to watch out for as well. I would recommend an ATI Mach
> >64 PRO Turbo, or an accelerated S3!
> The big burden is when it comes to SVGA mode. If you up the res., the amount
> of texturing is going up by a factor of four and this part of the game represents
> the greatest hit on the CPU.
> If you want a benchmark, I've tried it on a Dell P133 with 16 Mb RAM, 512Kb
> burst cache, #9 Motion card ( which gets a rating of '1' in WC3 ) and you
> _still_ have to turn off track texturing in SVGA mode to get 25 fps.
> Let's hope that F1GP2's SVGA mode is a little kinder on the old CPU -
> Crammond has written virtually all of the code in assembly with efficiency
> as his main aim.
> Fraser
>>>>I have a 486/33 and it sucks. I love Nascar Racing but I
>> >>As for hardware you need the equivalent of a low end Silicon Graphics
>> >>workstation. That equates to a high end Pentium, very high end (p120
>with
>> >>16MB). (I know comparing a high end pentium to low end SGI system is
a
>vile
>> >>and despicable insult to SGI and I apologize to SGI for it).
>> >No true,
>> >I am running NASCAR on a 90 MHz Pentium and it runs just fine. I know
>several
>> >people running NASCAR on a 486DX4-100 with 16 MB of RAM and it too
runs
>fine. The
>> >video card is the big one to watch out for as well. I would recommend
an
>ATI Mach
>> >64 PRO Turbo, or an accelerated S3!
>> The big burden is when it comes to SVGA mode. If you up the res., the
>amount
>> of texturing is going up by a factor of four and this part of the game
>represents
>> the greatest hit on the CPU.
>> If you want a benchmark, I've tried it on a Dell P133 with 16 Mb RAM,
512Kb
>> burst cache, #9 Motion card ( which gets a rating of '1' in WC3 ) and
you
>> _still_ have to turn off track texturing in SVGA mode to get 25 fps.
>> Let's hope that F1GP2's SVGA mode is a little kinder on the old CPU -
>> Crammond has written virtually all of the code in assembly with
efficiency
>> as his main aim.
>> Fraser
