Announcement

Collapse

Discord link fixed!

FYI for anyone who was having trouble using https://discord.quakeone.com that link is now fixed!
See more
See less

A Framerate Comparison of Engines

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Dr Labman
    replied
    :d

    Leave a comment:


  • scar3crow
    replied
    Labman - Your host was giving me problems with the dl at the time of testing, I will try again when I return home Sunday, expect to see results come Sunday night EST.

    Leave a comment:


  • Dr Labman
    replied
    No QMB framerate?

    I wouldn't mind seeing how it does

    Leave a comment:


  • Baker
    replied
    Originally posted by scar3crow
    Oh and with Romi's rtlights, that scene looks better and runs a lot faster Baker. Keep in mind DP is an ahead of its time engine that is fully backwards compatible.
    Agreed. It can make even the normal maps look a lot better without doing anything but playing with the control panel. It is an outstanding engine.

    Leave a comment:


  • scar3crow
    replied
    Baker - yes, and in that default settings all dlight entities are dynamically casting all of the lights, so everytime an entity fires a weapon or a grenade explodes, in that region all of the lighting is being recompiled, so thats even more the case for DP ; )

    Forcing vsync off netted GLPro a lot more fps as did TQ148, so its roughly of the same rank as FitzQuake now, but did little for any other engine. DP still looks the best, and runs 3rd best.

    Oh and with Romi's rtlights, that scene looks better and runs a lot faster Baker. Keep in mind DP is an ahead of its time engine that is fully backwards compatible.

    Leave a comment:


  • Sajt
    replied
    Or if you have a 1337 card like my geforce 7800 gtx

    Leave a comment:


  • Baker
    replied
    I might add that you shouldn't turn all the graphics doohickeys on, heh :d

    If you turn on a reasonable number of graphics doohickeys on, everything looks a lot better and things run smooth.

    Leave a comment:


  • Baker
    replied
    Originally posted by Sajt
    Well the point was that the engine(s) with the *most* graphic doohickeys and goodies was scoring the highest framerate as well
    Yeah but Scrarecrow, was using the default settings.

    What happens when you start turning the graphic doohickeys on?

    Leave a comment:


  • Sajt
    replied
    Well the point was that the engine(s) with the *most* graphic doohickeys and goodies was scoring the highest framerate as well

    Leave a comment:


  • golden_boy
    replied
    These measurements don't mean all too much.
    The differences are probably due to the details of the enhanced graphics stuff in the different clients and the standard settings not really being comparable.

    even 55 fps is enough to enjoy quake. use what you like ppl.

    peace.

    Leave a comment:


  • CheapAlert
    replied
    i've never had a prob with running glquake on every single video card i've ever used tbh (from the powervr pcx2 from 96 to the radeon i have now). You've got to have a lot of bad luck to make it crash like that.

    well the only horrible glquake problems i ever ran to was the s3 prosavage onboard laptop chipset, it just is slow but that's it.

    Leave a comment:


  • Baker
    replied
    Originally posted by CheapAlert
    That's like the #1 most common problem behind GLquake and ports, 2nd most common problem is lacking a 3d accellerated card, and that's not so common in this decade.
    Yeah, I am so glad that is improving in the graphics card department.

    Dell used to ... and maybe still does ... ship out computers with the Intel Extreme Graphics Controller. It runs Quake 3 fine, but not Quake (black screens) and it is indicated that Quake is known to not work on the Intel page. My computer was one of them. Then you ask yourself ... "Should I buy a graphics card when Quake is the only game I have that doesn't run?"

    Fortunately, 3D accelerators are become prevalent and every laptop I've bought has run GL Quake just fine.

    (It wasn't the OpenGl32.dll, that does this error, but that file sure is annoying, isn't it.)

    Leave a comment:


  • CheapAlert
    replied
    Originally posted by Baker
    Also, some players have computers that can only run software builds.
    Sucks to be them then, because in this day and age a 2ghz is average and a VERY decent computer is very affordable, hell even beggable if you're persuasive enough. lol

    Originally posted by Baker
    I've always wondered why Quake is so likely to have trouble with people's video cards whereas things like Quake 3 are not.
    maybe because THEY DIDN'T DELETE THE OPENGL32.DLL LOCATED IN THE QUAKE FOLDER AS THE INSTRUCTIONS SAY? That's like the #1 most common problem behind GLquake and ports, 2nd most common problem is lacking a 3d accellerated card, and that's not so common in this decade.

    Leave a comment:


  • Baker
    replied
    Originally posted by scar3crow
    Qrack really should allocate 32megs of ram automatically for the sake of modern levels BTW.
    I think Rook did this and the later removed the feature for some important reason.

    Miscellaneous stuff:

    Also, some players have computers that can only run software builds.

    I've always wondered why Quake is so likely to have trouble with people's video cards whereas things like Quake 3 are not.

    JoeQuake/QRack/Tremor, all being JQ-based, are the only engines where I can alt-tab into and out of it without my display getting messed up with my GeForce2.

    Leave a comment:


  • Sajt
    replied

    Leave a comment:

Working...
X