>Ok, I understand the GUI front end for NRL, but why bother with the DOS version of
>Nascar2? It would seem to me that you would get better performance with a Win95
>native app that could take advantage of all of the DirectX APIs (most noteably
>DirectDraw & Direct3D, as well as DirectInput for the upcoming force-feedback
>controls). Also, if I remember right, running an app in a DOS box lowers performance
>by about 25% from that of a true DOS session.
>Is Papyrus doing this to cover all the bases first, and then release a Win95 native
>version at a later date like ICR2?
>--
>Emory University Graduate School of Arts & Sciences
>Nascar Setups Page: http://userwww.service.emory.edu/~ebusch/
>Hawaii Network UserName: Buschwick
Well actually... We learned a lot from the ICR 2 for Win 95 project.
Win 95, even with DirectX causes a pretty big hit on frame rate when
compared to a native DOS app on the same system.
You need to understand that even though NCR 2 & NRL are "joined at the
hip" and are being done by the same company, they are 2 separate
projects. Bottom line, if a Win 95 version of NCR 2 could perform as
well as a DOS version, AND we felt comfortable that Win 95 was not too
big of a risk (in terms of getting NCR 2 done on time), NCR 2 would be
Win 95 native. However, neither of these factors is the real case (it
doesn't perform well, & it is a risk), so the NCR 2 DOS decision is
the right one at this point.
As for NRL, there is a lot more to NRL than NCR 2 to consider. We are
going to run this over someone else's data network which means that we
have to use standard protocols & O/S's. The online world has gone to
Win 95 & TCP/IP. If we are going to be able to "make a connection",
we have to go there too.
Ed Martin
Producer, Series Director
NASCAR Racing League
Papyrus / Sierra On-Line, Inc.