Anyone want a QUAKE LIVE invite?


Recommended Posts

Well the engine used for COD4 is based on the COD2 engine, which way way back was slightly based on the Q3 engine.

But no, COD4 isn't really based on the Q3 engine at all, maybe it has some old similar code from COD2.

Actually, it is. IW has used the Quake engine as the underlying coding structure through their games, even Call of Duty 4 shares similar coding methods and file structure.

BUT, it has nothing to do with the graphics or gameplay, that is up to the developers to form and shape.

Actually, it is. IW has used the Quake engine as the underlying coding structure through their games, even Call of Duty 4 shares similar coding methods and file structure.

BUT, it has nothing to do with the graphics or gameplay, that is up to the developers to form and shape.

yup, same engine, different textures and some tweaked coding.

More than "some" tweaking, it'd be fairer to say that the engine borrows heavily from Q3's engine structure and design than anything else. I mean, Valve's source engine is based on the Half-life 1 engine, which is based on the Quake 2 engine, but you wouldn't say Source == Quake 2 outrightly.

At the end of the day, it doesn't really matter, Quake live is just as fast-paced and crazy as Quake 3 was back in the day. I should know, I suck at it!

Actually, it is. IW has used the Quake engine as the underlying coding structure through their games, even Call of Duty 4 shares similar coding methods and file structure.

BUT, it has nothing to do with the graphics or gameplay, that is up to the developers to form and shape.

Well thats what I figured, because I know the config setups are organized are very similar to Quake 3. But I really don't think the engine is based on the Q3 engine whatsoever.

Even when you look at the doom and quake engine, their file structure is pretty similar and things like cvars, etc. Although the engines are completely different.

IMO, I think it just has more to do with the developers being trained with the Q3 engine, maybe it makes it easier for them to structure the coding like Q3, idk.

The same commands work, the same tweaks work, and the same odd engine glitches exist. In quake 3, its optimal to max your fps to 125, its an odd thing, but many old schoolers will agree, it enables you to make jumps that normally you cant.

The engine seems to run the same, just that really its bigger textures and different ai and other tweaks. But other than that, the engine really still seems quite similar to the quake3 game still.

I havent played this back since 2000. Quake Con was awesome back then.

Does this version allow for Rocket Arena settings?

Whoa, settle down there tiger.

Quake 3 was and is an average hyper-shooter which only had its looks going for it back in the good old day, in my opinion. I am just afraid that when you take away the looks all you are left with is a pretty meh shooter. And don't lecture me on games, specially not with you being 14 years old, I played games before you were even born.

My age doesn't mean anything, and you should know that being how old you are. You say it like graphics means alot. It's not like we're toying with an engine equivalent to Doom's or Aleph One. This is a fully 3D and stable first person shooter. It's engine is no different from the Source engine save for its prettiness and physics. Its textures are now the equivalent to what we've seen in 2004. I'm afraid you seem to think that this shooter has absolutely no graphical value to it whatsoever.

It's about the gameplay not the graphics. And your opinion about an "average hyper shooter" is an opinion and nothing else. I recall Quake3 being used in plenty of tournaments and events, equal to that of UT.

My age doesn't mean anything, and you should know that being how old you are. You say it like graphics means alot. It's not like we're toying with an engine equivalent to Doom's or Aleph One. This is a fully 3D and stable first person shooter. It's engine is no different from the Source engine save for its prettiness and physics. It's models are now the equivilant to what we've seen in 2004. I'm afraid you seem to think that this shooter has absolutely no graphical value to it whatsoever.

It's about the gameplay not the graphics. And your opinion about an "average hyper shooter" is an opinion and nothing else. I recall Quake3 being used in plenty of tournaments and events, equal to that of UT.

Wait, are you comparing it to the Source engine and then just listing the things it doesn't feature, plus you even list two of the biggest aspects of the Source engine, pathetic :rofl:

I can't take the rest of your post serious after a comparison like that. ( Not that your post made any sense in the first place, damn :| )

It's a great game with almost near perfect online coding and hit detection.

It pits players against each other, in an equal setting, in a world with set physics to it. those who learn those physics, can become a neo sort of in the game, moving quickly from place to place, and even knowing where to track others. It really is a game of sort of learning and skill to it, which makes it great for those with a competitive nature.

Wait, are you comparing it to the Source engine and then just listing the things it doesn't feature, plus you even list two of the biggest aspects of the Source engine, pathetic :rofl:

I can't take the rest of your post serious after a comparison like that. ( Not that your post made any sense in the first place, damn :| )

..

I listed the only two things that are superior about the Source engine, thus (sadly) attempting to prove how the Source engine is simply superior in those two areas, and Quake 3 is the same thing minus a little bit on both.

Physics in Quake 3 don't matter as much as they do in Half Life 2. For instance, if you strip away the gravity gun and the ragdolls, you end up without a need for such a complex physics engine like Havoc. Quake's physics would then fit perfectly in its place.

On the other hand, you're left with the graphics. A graphics engine only plays a part in functionality to a certain point. You can only utilize the graphics to differentiate between, for example, two different enemies, or two different guns. Once you hit that point, the development of shaders and textures become virtually pointless other than to serve as eye candy. Of course, this is not entirely true seeing as Crysis takes advantage of destructable structures and hiding in grass, and Splinter Cell hides in the shadows. But if you're smart enough, you see my point. And plus, this isn't a Crysis type of shooter.

I should have revised before I posted, that was a silly comparison. So let me take that sentence out and let's see if you can read it.

My age doesn't mean anything, and you should know that being how old you are. You say it like graphics means alot. It's not like we're toying with an engine equal to Doom's or Aleph One. This is a fully 3D and stable first person shooter. Its textures are now the equivalent to what we've seen in 2004. I'm afraid you seem to think that this shooter has absolutely no graphical value to it whatsoever.

It's about the gameplay not the graphics. And your opinion about an "average hyper shooter" is an opinion and nothing else. I recall Quake3 being used in plenty of tournaments and events, equal to that of UT.

Edited by Recon415

It's back up, but my invites are gone, I was only able to give 1 of the 5 out =\

Sorry guys, particularly Blindlabel013, PricklyPoo and shakey who all literally missed out on it by a few seconds (The time between me going to the invite section and pasting their emails to the time QL went down).

If my invites return, those 3 will be the first in line.

EDIT: That was quick! You guys got your invites after all. So did Jase.

1 invite left! Next POSTER gets it!

..

I listed the only two things that are superior about the Source engine, thus (sadly) attempting to prove how the Source engine is simply superior in those two areas, and Quake 3 is the same thing minus a little bit on both.

Physics in Quake 3 don't matter as much as they do in Half Life 2. For instance, if you strip away the gravity gun and the ragdolls, you end up without a need for such a complex physics engine like Havoc. Quake's physics would then fit perfectly in its place.

On the other hand, you're left with the graphics. A graphics engine only plays a part in functionality to a certain point. You can only utilize the graphics to differentiate between, for example, two different enemies, or two different guns. Once you hit that point, the development of shaders and textures become virtually pointless other than to serve as eye candy. Of course, this is not entirely true seeing as Crysis takes advantage of destructable structures and hiding in grass, and Splinter Cell hides in the shadows. But if you're smart enough, you see my point. And plus, this isn't a Crysis type of shooter.

I should have revised before I posted, that was a silly comparison. So let me take that sentence out and let's see if you can read it.

I'm sorry but your posts are a joke. I don't think I've seen such daft arguments in my whole life? You constantly just strip away features from engines and they say "There, now you are left with the Quake engine". Yes, take engine graphics engine and remove features, you are basically going to end up with a simple 3D engine. That's how engines evolve today, by adding features and improving the graphical side of the engine by the use of advanced effects, improving textures, mimicking real-life effects etc. There's a reason why big companies like AMD ( ATi ) and nVidia pumps out out GPUs every other month and people actually buy them. There's a reason why new consoles are launched every few years, there is a reason why games are constantly pushing the envelope on the graphical side - Because people actually care. Gameplay and graphics go hand in hand, like it or not. Also, you need to reword that entire post to make me read it, I had people approaching me on messenger laughing at the post because it sounds like it's written by a seagull.

The above was aimed at FPS / TPS games mostly because they are the games trying to create user immersion by getting close to realistic looks.

And just to make it perfectly clear, I can play games with older graphics engine. My concerns about this game was the fact that I never really got into the "Quake" gameplay and combined with inferior graphics, I wasn't sure whether I'd like it or not.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      596
    2. 2
      +Edouard
      188
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!