Announcement

Collapse
No announcement yet.

OpenGL ES 2.0, GLSL Support For Open Doom 3

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

  • OpenGL ES 2.0, GLSL Support For Open Doom 3

    Phoronix: OpenGL ES 2.0, GLSL Support For Open Doom 3

    There's finally some open-source id Tech 4 / Doom 3 advancements to report on today. Oliver McFadden has released his new OpenGL ES 2.0 renderer with GLSL support for Doom 3...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    No point and click release to play the game yet?

    Comment


    • #3
      Too bad

      Too bad nobody is using this engine.

      Comment


      • #4
        Originally posted by uid313 View Post
        Too bad nobody is using this engine.
        Why should one?

        There are e.g. DarkPlaces, CrystalSpace, BlenderGameEngine, Torque, jMonkeyEngine, irrLicht, ShiVa, Linderdaum, ...
        (lots to find here: http://devmaster.net/devdb/engines)

        Those mostly also have some tools around them.
        iodoom3 does bring some with it but those don't work on Linux (or Mac) because they are MFC based.

        And worse:
        You don't get support by devs as they moved on to id tech 6.
        So you're stuck with people like you that also try to get in.

        And the first aid is missing.
        It's not like UDK, Unity3D, BGE, ... where you start a new project and have the basics or just insert some things following an easy tutorial, press play and everything works.
        No sample files. No base to build from.
        Just pure source code.

        Digging through iodoom3 for a university project is nice and I see a lot of potential.
        But other engines are already free and open and are far ahead.
        For gameDevs iodoom3 isn't currently an option.
        Maybe if we get the source updated, new features included and the asset- and work-pipeline flowing?
        (But why not use an engine that already has those features and tools and improve that?)



        Also: motorsep from "Kot in Action" ("Steel Storm") is trying to get into iodoom3.

        Comment

        Working...
        X