Quake performance

Returning to Quake problems, aside for excessive RAM requirements it
also appears to have perorfmance problems on Neutirno. I have
PII-333/128Mb, Voodoo3500 AGP/16Mb, SB Live! which exceeds Quake
requirements (P266/64Mb) by a fair margin. Under Windows it indeed runs
perfectly on that machine, but on RTP I have somewhat choppy sound and
unstable frame rate. It feels like one is related to another. I mean, I
don’t know what is root reason - sound or video but it looks like the
other suffers too because they need to be syncronized.

  • igor

I can add to this, on Windows it works fine with resolutions up to
1600x1200, while it has problems with 640x480 on RTP. Too bad.

Igor Kovalenko wrote:

Returning to Quake problems, aside for excessive RAM requirements it
also appears to have perorfmance problems on Neutirno. I have
PII-333/128Mb, Voodoo3500 AGP/16Mb, SB Live! which exceeds Quake
requirements (P266/64Mb) by a fair margin. Under Windows it indeed runs
perfectly on that machine, but on RTP I have somewhat choppy sound and
unstable frame rate. It feels like one is related to another. I mean, I
don’t know what is root reason - sound or video but it looks like the
other suffers too because they need to be syncronized.

  • igor

Andrew <NOastuart@mira.netSPAM> skrev i
diskussionsgruppsmeddelandet:8t0gg9$4uf$1@inn.qnx.com

such reports are slightly disturbing aren’t they? surely the whole point
of
QNX RTP is that it outperforms windows by a mile, or am I missing
something?

cheers

andrew

As long as it is just the games that doesnt work better, I just dont care.
I downloaded the Doom demo, unaware that it only works on certain
videocards, and happily uninstalled it after discovering.
If I want to play, I got a nintendo for that, with a much bigger screen.

such reports are slightly disturbing aren’t they? surely the whole point of
QNX RTP is that it outperforms windows by a mile, or am I missing something?

cheers

andrew



“Igor Kovalenko” <kovalenko@home.com> wrote in message
news:39F37197.D54F9A50@home.com

I can add to this, on Windows it works fine with resolutions up to
1600x1200, while it has problems with 640x480 on RTP. Too bad.

Igor Kovalenko wrote:

Returning to Quake problems, aside for excessive RAM requirements it
also appears to have perorfmance problems on Neutirno. I have
PII-333/128Mb, Voodoo3500 AGP/16Mb, SB Live! which exceeds Quake
requirements (P266/64Mb) by a fair margin. Under Windows it indeed runs
perfectly on that machine, but on RTP I have somewhat choppy sound and
unstable frame rate. It feels like one is related to another. I mean, I
don’t know what is root reason - sound or video but it looks like the
other suffers too because they need to be syncronized.

  • igor

My concern is that poor gaming performance may indicate poor system
performance in some other areas of the operating system, which may also have
a performance impact on other software such as a web server for example.

Andrew

GuW <sm2vjx@hotmail.com> wrote in message news:8t0jkj$7kn$1@inn.qnx.com

Andrew <> NOastuart@mira.netSPAM> > skrev i
diskussionsgruppsmeddelandet:8t0gg9$4uf$> 1@inn.qnx.com> …
such reports are slightly disturbing aren’t they? surely the whole
point
of
QNX RTP is that it outperforms windows by a mile, or am I missing
something?

cheers

andrew


As long as it is just the games that doesnt work better, I just dont care.
I downloaded the Doom demo, unaware that it only works on certain
videocards, and happily uninstalled it after discovering.
If I want to play, I got a nintendo for that, with a much bigger screen.

You are great!

Well, your still going to be pageing to disk with all those
textures (there are a ton!) with 128 Megs.

You probably won’t get chop with more RAM. I play on a PII-400 with
256Megs, at 1024x768 full detail settings, with no problems frame rate
wise…same settings however with 128 megs causes swapping hell.

Problem is back to the swap file I’m afraid (which isn’t ready and is only
garunteed to work with gcc and friends…just happens to work with
Quake as well).

drempel




Igor Kovalenko <kovalenko@home.com> wrote:

I can add to this, on Windows it works fine with resolutions up to
1600x1200, while it has problems with 640x480 on RTP. Too bad.

Igor Kovalenko wrote:

Returning to Quake problems, aside for excessive RAM requirements it
also appears to have perorfmance problems on Neutirno. I have
PII-333/128Mb, Voodoo3500 AGP/16Mb, SB Live! which exceeds Quake
requirements (P266/64Mb) by a fair margin. Under Windows it indeed runs
perfectly on that machine, but on RTP I have somewhat choppy sound and
unstable frame rate. It feels like one is related to another. I mean, I
don’t know what is root reason - sound or video but it looks like the
other suffers too because they need to be syncronized.

  • igor

David Rempel wrote:

Well, your still going to be pageing to disk with all those
textures (there are a ton!) with 128 Megs.

You probably won’t get chop with more RAM. I play on a PII-400 with
256Megs, at 1024x768 full detail settings, with no problems frame rate
wise…same settings however with 128 megs causes swapping hell.

I played some more and it is really strange. Problems are worst when I
just start the game. First few seconds it hardly responds to controls
and names iof players entering sound like being pronounced by a speech
impaired. Then as you continue to struggle, frame rate stabilizes. Sound
might or might not stabilize. It always gets little better, but somtimes
remains chopped through the end. If you exit and restart quake, next
time it may behave in any way.

Also, problems do not really seem to be dependent on resolution. It
plays 1600x1200 with the same amount of problems as 640x480, so it is
not raw performance issue. One more thing: resolution 1600x1200 is
really screwed - I see only left 2/3 of screen.

Problem is back to the swap file I’m afraid (which isn’t ready and is only

You mean VM design? I’ve heard it will be redesigned, any idea when?

garunteed to work with gcc and friends…just happens to work with
Quake as well).

You should put some disclaimer somewhere, explaining that RAM
requirements are higher due to unfinished VM implementation. Otherwise
you’ll have quite a few people disappointed.

  • igor

Igor Kovalenko <kovalenko@home.com> wrote:

David Rempel wrote:

Well, your still going to be pageing to disk with all those
textures (there are a ton!) with 128 Megs.

You probably won’t get chop with more RAM. I play on a PII-400 with
256Megs, at 1024x768 full detail settings, with no problems frame rate
wise…same settings however with 128 megs causes swapping hell.


I played some more and it is really strange. Problems are worst when I
just start the game. First few seconds it hardly responds to controls
and names iof players entering sound like being pronounced by a speech
impaired. Then as you continue to struggle, frame rate stabilizes. Sound
might or might not stabilize. It always gets little better, but somtimes
remains chopped through the end. If you exit and restart quake, next
time it may behave in any way.

Hmmmm…I’ve seen something similar to this happen on SB128’s
(but it only seemed to happen on my machine…in a low memory, with game data
on the other side of a
a busy network connection scenario, other boxes in similar environments didn’t
show it) I’ll look into it.

Also, problems do not really seem to be dependent on resolution. It
plays 1600x1200 with the same amount of problems as 640x480, so it is
not raw performance issue. One more thing: resolution 1600x1200 is
really screwed - I see only left 2/3 of screen.

Yeah, should be fixed soon… (video mode is 640x480 fall back from errro
setting, Quake still thinks it’s in 1600x1200)

Problem is back to the swap file I’m afraid (which isn’t ready and is only

You mean VM design? I’ve heard it will be redesigned, any idea when?

No, I don’t know. Some one else would have to comment.

garunteed to work with gcc and friends…just happens to work with
Quake as well).


You should put some disclaimer somewhere, explaining that RAM
requirements are higher due to unfinished VM implementation. Otherwise
you’ll have quite a few people disappointed.

Probably a good idea…I’ll file a PR.

  • igor

drempel

Well I’ve played (tried to play?) Q3A on a PIII-400 with 128MB RAM under Win98
and it sucks rocks at all resolutions. I get the frame and sound “splotches”
that Igor’s talking about all the time no matter what lengths I try to go to.
However under RtP things sail right along with none of the problems I’ve seen
with Microschlock. So, file that one in the performance reports FWIW…

I’d like to think that RtP’s mission is to provide an alternative to
MicroSquishy bloatware and up the ante on “reliability” all the way around as
well. Apparently to MicroSchmuck, “Rock Solid Windows NT” means you get the
blue screen of death only once a week instead of once a day, and “Good Enough”
for realtime performance means “Don’t Count On It Working At All”. RtP’s still
young, give it some time to mature… It’s a developer’s O.S. to be sure, and
I for one envision a few of you guys putting out some pretty amazing stuff in
the future…

-Warren


“Andrew” <NOastuart@mira.netSPAM> wrote in message
news:8t0gg9$4uf$1@inn.qnx.com
| such reports are slightly disturbing aren’t they? surely the whole point of
| QNX RTP is that it outperforms windows by a mile, or am I missing something?
|
| cheers
|
| andrew
|
|
|
| “Igor Kovalenko” <kovalenko@home.com> wrote in message
| news:39F37197.D54F9A50@home.com
| > I can add to this, on Windows it works fine with resolutions up to
| > 1600x1200, while it has problems with 640x480 on RTP. Too bad.
| >
| > Igor Kovalenko wrote:
| > >
| > > Returning to Quake problems, aside for excessive RAM requirements it
| > > also appears to have perorfmance problems on Neutirno. I have
| > > PII-333/128Mb, Voodoo3500 AGP/16Mb, SB Live! which exceeds Quake
| > > requirements (P266/64Mb) by a fair margin. Under Windows it indeed runs
| > > perfectly on that machine, but on RTP I have somewhat choppy sound and
| > > unstable frame rate. It feels like one is related to another. I mean, I
| > > don’t know what is root reason - sound or video but it looks like the
| > > other suffers too because they need to be syncronized.
| > >
| > > - igor
|
|