doomlegacy.sourceforge.net

Doom II is id Software's 1994 first-person shooter sequel to Doom, and you can still play it today by using a modern source port such as Doom Legacy. The practical path is: get the game data files from a legitimate copy of Doom II, install a source port, point the port at the data files, and launch. Doom Legacy is one such port; its site lists a current release, Doom Legacy 1.48.18 (rev1749), with binaries in the download area and a changelog in docs/whatsnew.html.

What Doom II is and how it differs from the original Doom

Doom II: Hell on Earth continues the story of the original Doom. It keeps the fast, sprite-based, first-person shooting of the first game and adds content rather than replacing the core formula. The well-known differences are:

• More and larger levels, including city-themed maps, rather than the original's three-episode structure.
• The super shotgun, a new weapon that becomes a staple of the arsenal.
• New monsters, such as the Hell knight, mancubus, revenant, and arch-vile, which change how encounters are fought.
• A single continuous campaign rather than episodes selected from a menu.

The original Doom and Doom II share the same underlying engine family, which is why the same source ports can usually run both.

Where to get Doom II and which files you need

Doom II is a commercial game, so the data files come from a copy you own. The files a source port needs are the game's WAD data files — principally DOOM2.WAD for Doom II. A source port is only the engine; it does not include the commercial game data.

In practice:

1. Obtain Doom II through a legitimate storefront or an owned copy, and install or extract it.
2. Locate DOOM2.WAD in the game's install folder.
3. Keep that file somewhere stable, since the source port will reference it.

If you only want to try a Doom-engine game without buying Doom II, free replacement WADs exist (for example Freedoom), but those are separate games' data, not Doom II itself.

What source ports are and why they matter

A source port is a re-implementation of the original game engine, built to run on modern operating systems and hardware. The original Doom II executable was written for DOS-era machines, so running it directly today is awkward. Source ports solve that by providing:

• Modern OS support (current Windows, Linux, and other platforms).
• Higher resolutions and widescreen, plus modern display and input handling.
• Bug fixes and quality-of-life features that the original engine lacked.
• Extended editing and gameplay features, which vary by port.

Ports differ in focus: some aim for strict demo compatibility, others for enhanced graphics, multiplayer, or modding. That is why there are many ports rather than one.

How Doom Legacy fits in

Doom Legacy is a source port engine for id Software's classic Doom games, and Doom II is among the games it is built to run. It is one option among several, not the only one.

From the Doom Legacy site, the current release is Doom Legacy 1.48.18 (rev1749), announced on 2025-07-17. The release notes state that it contains new gameplay and editing features and several bug fixes, with the full changelog in docs/whatsnew.html. Binaries and other packages are in the download area.

Choose Doom Legacy if you want a port that advertises ongoing gameplay and editing features and bug fixes. If your priority is something else — for example, a particular compatibility target or a specific modding workflow — compare ports on that dimension before committing, since feature sets differ.

Basic steps to launch Doom II through a source port

The general flow is the same for most ports, including Doom Legacy:

1. Get the port. Download the Doom Legacy package for your operating system from the download area on the Doom Legacy site, and extract it to a folder.
2. Place the game data. Put your DOOM2.WAD where the port can find it — commonly in the port's own folder, or in a folder you point the port to.
3. Launch the port. Start the Doom Legacy executable. Expect it to look for the WAD and either load it or ask you to select it.
4. Select Doom II. If the port presents a game or IWAD selection, choose Doom II so it uses DOOM2.WAD.
5. Verify. You should reach the Doom II title screen and be able to start a new game. If the port reports a missing WAD, recheck the file name and location.

Common snags

• Wrong WAD name or location. Ports look for exact file names such as DOOM2.WAD; a renamed or misplaced file will not be found.
• Using a port without game data. A source port alone will not run Doom II; the commercial WAD is required.
• Version mismatches with mods. If you load custom WADs or mods, check that they are compatible with the port version you installed; the changelog in docs/whatsnew.html is the place to confirm what changed.

Once the title screen loads, you are playing Doom II through a modern engine — and you can then explore the port's gameplay and editing features as your interest dictates.

Freedoom is a project that supplies all the content needed to form a complete, entirely free/libre game for the Doom engine. It is not a game engine itself: you still run it with a Doom engine (a source port), and Freedoom provides the replacement assets — levels, graphics, sounds, music, and monsters — so you can play without the original proprietary Doom game files. It is also designed to be compatible with most custom levels, music, graphics, and other mods made for the original Doom games.

What Freedoom actually provides

The Doom engine expects a game data file (commonly an IWAD) containing the assets that make up the game. Freedoom's role is to be that free/libre data set. The project's stated aim is to provide "all the content needed to form a complete, entirely free/libre game for the Doom engine."

That means Freedoom is best understood as a content replacement project, not an engine. The engine — the program that renders the world, handles input, and runs the game logic — comes from elsewhere. Freedoom fills in the art, audio, level, and monster content that the engine loads.

What it is not

• It is not a source port or engine you launch on its own.
• It is not a modification that requires the original Doom assets to work; the point is to avoid needing them.
• It is not a single fixed game — the project ships updates that add and revise levels, monsters, music, and visuals over time.

How it works with the Doom engine

The practical mechanism is straightforward: a Doom engine loads a game data file, and Freedoom supplies that file. Because the engine and the content are separate, Freedoom can be paired with engines that support the Doom data format.

The project also targets compatibility with the wider Doom ecosystem. Its own description says it is "designed to be compatible with most custom levels, music, graphics and other modifications ('mods') made for the original Doom games by Doom fans and artists over the decades." In practice, that means many community-made maps and mods built for the original games can be loaded alongside Freedoom's content.

A concrete example

Suppose you want to play a custom level pack made by a Doom fan years ago, but you do not have the original commercial game files. You would install a Doom engine, place Freedoom's data file where the engine expects the game data, and load the custom level pack on top. Freedoom supplies the base graphics, sounds, and monsters the level expects, while the custom pack supplies its own maps and any assets it includes.

This is also where compatibility caveats matter. The project's release notes show ongoing work on engine-level compatibility — for example, the 0.13.0 release (2024-01-29) lists "Improved vanilla compatibility," removal of Boom features, greatly reduced hall-of-mirrors effects, and fixes for visplane overflows, while noting that "savegame buffer overflow errors remain." Those notes are a useful signal: compatibility is actively maintained, but it is not absolute, and some edge cases persist.

What a release includes

Freedoom releases are substantial content updates. The 0.13.0 release notes describe changes across several areas, which gives a sense of what the project maintains:

The manual also gained French and Spanish translations in that release, and sections were added to highlight the project mandate and additional accessibility options.

When Freedoom is the right choice

Freedoom fits situations where you want to play Doom-engine content without relying on the original proprietary assets, or where you want a free/libre base for a Doom-engine game. It is a good match if:

• You want to run Doom-engine games or custom levels using freely licensed content.
• You are building or distributing something on the Doom engine and need a free/libre asset base.
• You want to play community mods and maps that were made for the original games, accepting that compatibility is broad but not guaranteed.

It is a weaker fit if you specifically need the exact original Doom assets, or if a particular mod depends on engine behaviors that Freedoom's compatibility work has not covered. The release notes are the place to check for known remaining issues before committing to a setup.

Getting started

The project's site provides the entry points you need: a Download page, a manual ("Read the Manual"), and pages for reporting issues and discussing the project on its forum or Discord. The site also links to related projects, including FreeDM, whose music is referenced in the 0.13.0 notes.

A practical path is:

1. Read the "What is Freedoom?" page to confirm the project matches what you want.
2. Download the current release from the Download page.
3. Follow the manual for setup, including how to pair Freedoom's data with a Doom engine.
4. Check the release notes for known compatibility issues relevant to the mods or levels you plan to use.

Because Freedoom is community-maintained and updated in releases, checking the latest project news before setting up is worthwhile — the 0.13.0 notes show that both content and compatibility change meaningfully between versions.

Yes. CC0 assets can be used in commercial games without paying royalties or crediting the creator. CC0 is a public-domain dedication: the creator has waived copyright and related rights to the fullest extent allowed by law. That means you can copy, modify, redistribute, and sell work built on those assets — including in a game you charge money for.

This article explains what CC0 actually covers, how it differs from other Creative Commons licenses, and how to bring CC0 assets into engines like Unreal and Unity and tools like Blender, Maya, and 3ds Max.

What CC0 actually means

CC0 is not a license in the traditional sense — it is a waiver. When a creator applies CC0 to their work, they give up their copyright and agree not to enforce related rights. You are free to:

• Use the asset in personal, educational, or commercial projects
• Modify, remix, and build derivative works
• Distribute the asset or your derivative as part of a larger project
• Do all of the above without attribution

There is no requirement to credit the creator, no share-alike clause forcing you to open-source your game, and no non-commercial restriction. For a studio shipping a paid title, that combination is unusually permissive.

One practical caveat: CC0 applies to the rights the creator holds. It cannot waive third-party rights the creator never owned. A scanned statue, a branded product, or a recognizable logo in a texture may still carry trademark or personality-rights issues. Treat CC0 as clearing copyright, not as clearing everything.

CC0 vs. other Creative Commons licenses

The differences matter most when you are choosing assets for a commercial build. The table below summarizes the common variants.

| License | Commercial use | Attribution required | Share-alike | Notes for games | |---|---|---|---|---|---| | CC0 | Yes | No | No | Closest to public domain; safest for closed-source commercial titles | | CC BY | Yes | Yes | No | Fine for commercial use, but you must credit — plan for a credits screen | | CC BY-SA | Yes | Yes | Yes | Derivatives may need to be shared under the same license; risky for proprietary code/assets | | CC BY-NC | No | Yes | No | Excludes commercial projects; avoid for any monetized game | | CC BY-ND | Yes | Yes | No | No derivatives — you cannot modify the asset, which limits integration |

If your goal is a commercial game with no legal overhead, CC0 is the simplest choice. CC BY is workable if you can maintain attribution. Avoid NC and ND for anything you intend to sell or heavily adapt.

How CC0 assets fit into game engines and pipelines

CC0 libraries typically provide HDRIs, PBR textures, and 3D models. Each type has a natural place in a game pipeline.

HDRIs

HDRIs are high-dynamic-range environment maps. In Unreal, they are commonly used for sky lighting via a Sky Light set to use an HDRI cubemap or a Sky Sphere material. In Unity, they feed the skybox and the environment lighting in the Lighting window. You can also use them as reflection probes or as the basis for image-based lighting in Blender, Maya, or 3ds Max for look development before export.

Textures

PBR texture sets usually ship as albedo (base color), roughness, metallic, normal, and sometimes ambient occlusion or height maps. These drop directly into Unreal's material system or Unity's Standard/URP/HDRP shaders. Keep the resolution appropriate: 4K textures are useful for hero assets, but 1K or 2K is often enough for background props and saves memory.

Models

Static meshes and props can be imported as FBX or OBJ. Check the scale and pivot before placing them in a level. If the asset was authored for offline rendering, it may have very high poly counts — decimate or LOD it before use in a real-time scene.

Practical steps for importing and adapting assets

1. Download and verify the license. Confirm the asset page states CC0. Save a screenshot or the license text alongside the file.
2. Organize by type. Keep HDRIs, textures, and models in separate folders. A consistent naming convention (for example, env_forest_01_4k.hdr) saves time later.
3. Import into your engine. In Unreal, drag the FBX into the Content Browser and set up materials. In Unity, import the FBX and assign a PBR material, then wire the texture maps to the correct slots.
4. Adapt scale and orientation. Real-world assets may be authored in meters or centimeters. Check against a reference cube of known size.
5. Optimize. Reduce texture resolution where it will not be seen up close, generate LODs for models, and bake lighting where appropriate.
6. Test in context. Place the asset in a representative scene and check lighting, reflections, and performance before committing it to the project.

What CC0 does not cover

CC0 clears copyright, but a few things still deserve a second look:

• Trademarks and logos. A texture containing a recognizable brand mark is not automatically safe to ship.
• Recognizable people or property. A model of a real person or a distinctive building may raise personality or property-rights questions.
• Third-party content inside the asset. If a creator included someone else's work without permission, the CC0 dedication does not fix that.

For most generic assets — rocks, foliage, generic furniture, abstract HDRIs — these concerns are minimal. For anything depicting a real brand, person, or landmark, verify independently.

Documenting asset sources for teams and clients

Even though CC0 requires no attribution, keeping records is good practice. It protects you if a client or publisher asks for provenance, and it helps when a team member needs to know where a file came from.

A simple tracking sheet works:

Store this alongside your project files. If you later combine CC0 assets with CC BY assets, the sheet makes it obvious which ones need credit.

Bottom line

CC0 assets are safe for commercial games, require no attribution, and impose no royalties or share-alike obligations. The main work is practical: verify the license, check for third-party rights, import and optimize the asset for your engine, and keep a record of where it came from. Do that, and a CC0 library becomes a legitimate, low-friction source for production assets in Unreal, Unity, Blender, Maya, and 3ds Max.

Short answer: free NZ Herald access gives you breaking news, headlines and a broad slice of daily reporting, while NZ Herald Premium is the paid layer that unlocks subscriber-only articles — typically opinion, analysis, in-depth explainers and selected business, politics and lifestyle features. If you mainly skim headlines and breaking stories, free access may be enough. If you want to read the full argument, the data behind a story or a columnist's take, Premium is the part you'd be paying for.

How the two tiers generally work

Most large news sites, including nzherald.co.nz, operate on a mixed model: some content is open to everyone, and some sits behind a paywall marked as Premium. The exact mechanics can change, but the practical pattern is consistent.

Free NZ Herald news

• Breaking news and live updates, so you can follow major events as they happen.
• Headlines, summaries and a large amount of general reporting across NZ, sport, business, entertainment and travel.
• Basic browsing of section front pages, which lets you see what's being covered even if you can't open every article.

NZ Herald Premium

• Subscriber-only articles, usually flagged with a "Premium" label before you click.
• Opinion and columns, where writers argue a position rather than just report facts.
• Analysis and explainers that go deeper into politics, business, tax, housing and the economy.
• Selected long-form features, reviews and lifestyle pieces, such as travel and beauty coverage.

A useful way to think about it: free access tells you what happened; Premium is often where you find why it matters and what it means for you.

What kinds of content typically sit behind Premium

Based on how the site labels its own sections, Premium content clusters around a few areas:

This is a general pattern, not a fixed rule — any individual article can fall on either side, so check the label on the story you actually want to read.

How paywalls and metering usually behave

News sites commonly use one of two approaches, or a mix:

1. A hard paywall — the article is locked from the first visit, and you see only a preview.
2. Metering — you get a set number of free articles per month, then hit a limit.

Either way, the practical steps are the same:

• Look for a "Premium" tag next to the headline before clicking.
• If you hit a wall, note whether it's a per-article lock or a monthly limit.
• Check whether the same story is summarised elsewhere on the free site, which sometimes happens with breaking news.

Deciding whether Premium is worth it for you

Rather than asking "is it good?", match it to your habits.

Free access is probably enough if you:

• Check headlines a few times a day and rarely read past the first few paragraphs.
• Follow breaking news and sport results more than analysis.
• Only occasionally want a columnist's opinion.

Premium is more likely to earn its cost if you:

• Read opinion and analysis regularly, not just news.
• Follow politics, business, tax or housing policy closely.
• Want explainers that put a story in context rather than just reporting it.
• Value long-form features, reviews or travel and lifestyle writing.

A simple test: over one week, count how many times you click an article and find it locked. If that number is high and the locked pieces are the ones you actually wanted, Premium is doing real work for you.

What to check before subscribing

Before you commit, confirm these details on the site itself, since terms and prices change:

• Trial conditions — length, whether a card is required, and when billing starts.
• Price and billing cycle — weekly, monthly or annual, and whether it renews automatically.
• Cancellation terms — how to cancel and whether you keep access until the end of the period.
• Device and account access — whether one subscription covers phone, tablet and desktop, and how many people can use it.
• What's included — whether Premium covers all sections or only some, and whether any bundled products (such as a magazine or newsletter) come with it.

Because pricing and offers are set by the publisher and can change, treat any figure you see as current only at the moment you check it.

A quick decision template

Fill this in honestly:

1. How many days a week do I read NZ news? ___
2. How often do I want opinion or analysis, not just headlines? ___
3. How many Premium articles did I try to open last month? ___
4. Would I rather pay for depth, or stay with free headlines? ___

If your answers lean toward frequent reading and a real appetite for analysis, Premium is the tier built for you. If you're mostly a headline scanner, the free experience covers most of what you need — and you can always subscribe later when a specific story makes the case for you.

Cascadeur is a 3D animation tool for character animation, mocap cleanup, AI motion generation, and editing, and the only reliable place to get it is the official site at cascadeur.com. Start from the download entry on that site, then use the "Start trial" link on the Plans page if you want to test the paid tiers before committing. The site lists Plans and a trial but does not publish prices or system requirements on the pages captured here, so treat those as things to confirm on the official pages rather than assume.

Where to Get the Installer

Go to cascadeur.com and use the download link on the site itself. Avoid third-party mirrors, repacked installers, or file-sharing links — animation software is a common target for bundled malware, and a mirror will not give you a legitimate license or update path.

The homepage presents two relevant entry points:

• A Try for free action, which is the fastest route to a working install.
• A Plans page (cascadeur.com/plans) with a Start trial link (cascadeur.com/plans#trial) if you want to evaluate paid functionality.

The site does not state which operating systems the installer supports, so check the download page for the platform list before you start. If you need Windows, macOS, or Linux specifically, confirm it there rather than assuming all three are covered.

What You Get After Installing

Once running, Cascadeur covers a specific set of animation tasks. Knowing these up front tells you whether the download is worth your time:

It also ships tools aimed at mocap cleanup — fixing foot sliding, knee pops, and geometry penetration — plus previz and animation editing workflows.

File Compatibility Before You Commit

Cascadeur works with .FBX, .DAE, .GLB/.GLTF, and .USD files. If your pipeline already exports one of these, integration is straightforward. If your character assets live in a format outside this list, plan a conversion step before importing, or the download will not get you far.

First Steps After Install

1. Launch the application and create or sign into an account if prompted.
2. Start a trial or free session through the entry you chose on the Plans page.
3. Import a character file in FBX, DAE, GLB/GLTF, or USD.
4. Use drag-and-drop rigging to generate a skeleton for a humanoid or quadruped.
5. Test one feature end to end — for example, AutoPosing on a single pose, or Inbetweening between two keyframes — to confirm the install is functional before building a full workflow.

Common Snags

• Download fails or stalls. Retry from the official site; corporate networks and some browsers block large installers. Try a different browser or network.
• Installer errors on launch. Confirm your OS version against the download page, since the captured pages do not list requirements.
• Import rejects your file. Check the extension against the supported list above; a format that looks similar (for example, an older FBX variant) may still need re-export.
• Trial or plan confusion. The Plans page is the authoritative source for what each tier includes and what the trial covers. The site does not publish pricing in the material available here, so read the Plans page directly rather than relying on secondhand summaries.

Is It Worth Downloading

Download Cascadeur if you need AI-assisted keyframe animation, mocap cleanup, or retargeting between characters with different skeletons, and your assets are in FBX, DAE, GLB/GLTF, or USD. Skip it if your pipeline depends on a format outside that list or you need confirmed system requirements before installing — in that case, check the official download and Plans pages first, since those details are not published in the source material here.