Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

antiriad

Members
  • Content count

    67
  • Joined

  • Last visited

About antiriad

  • Rank
    Mini-Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. antiriad

    Doom 3 - 16 Years Later: An LGR Retrospective

    I'm replaying it with dhewm3 (also MacOS is supported) https://dhewm3.org/ I take this opportunity for a question: has the Wulfen project for high resolution textures ever been completed? I downloaded an archive and it works, but some textures remain in low resolution. Thank you!
  2. antiriad

    Doom 3 - 16 Years Later: An LGR Retrospective

    Xbox. Not 360.
  3. SI6IL on my newly-build MS-DOS PC, in MBF 2.04: Playing it on that crt LG Flatron (that I got for free) is really a thing! 🤓
  4. antiriad

    Chocolate Doom

    I built choco v3 on Raspbian LITE getting a "no video device" error. At the end I gave up and I switched to "standard" Raspbian (with desktop manager). Removed all that educational junk, cleaned up a bit and installed SDL 2.0.5 hardware-accelerated from the official repository. I was able to build choco v3 and DoomRetro and they both run at full speed. I even installed Quakespasm and it's very fluid (~50fps without optimizations) in 1080p (OpenGL driver). I'm impressed.
  5. antiriad

    Chocolate Doom

    Chocolate-doom package in Raspbian Stretch Repository is 2.3.0 (SDL1 branch). I get a black screen (even with -geometry 640x480 -bpp 24) if in raspi-config I set the LEGACY (Videocore) driver. It is normal? Everything's OK if I enable one of the experimental OpenGL desktop driver, but since I don't use X11 (I'm on Raspbian Stretch LITE) I'd like to understand why I can't use LEGACY driver anymore. I've manually compiled 2.3.0 and I get the same results. It seems that things are becoming unnecessarily complicated on RPi for Raspbian Stretch Lite users (this is not a criticism to chocolate-doom, of course). Thanks
  6. antiriad

    Chocolate Doom

    Thank you very much!!! I'll try to compile latest (stable) version. ;)
  7. antiriad

    Chocolate Doom

    Hello and excuse me for my "newbie" question. I'd like to enjoy Chocolate-DOOM on Raspberry Pi 3 with Raspbian Stretch LITE (so, no X environment and no SDL2 acceleration out of the box). I can't precisely understand if the SDL2 branch is "the way to go" now on RPi (eventually I'll need to manually compile SDL 2.0.8 with hardware acceleration in framebuffer) or if I can install the SDL1 version and still have all the code updates in terms of gameplay. Another question is: what are dependancies for chocpkg and where can I find a command example to install Choco-DOOM on RPi? Thanks!
  8. antiriad

    DOOM Eternal Gameplay Reveal Impressions

    My impressions: overall, like DooM II, Eternal seems a bigger "more of the same" brother of the first chapter, and that's OK because DOOM 2016 was great. ;) I like the environments but this time my personal acceptable limit of "cartoon-style" was reached. I'll surely look for one of the alternative renders in the engine to make it darker and less colorful. I DON'T like the "new" design of: - Mancubus: in DOOM 2016 its reinterpreted style was "charismatic" as much as that of the Revenant. Maybe this new version is more faithful to the '90s, but aestetics evolve, and the final result seems to me a generic, homemade 3D render from some kind of GL_DOOM mod (sorry). - common Zombies: again, 2016 design was darker and more interesting IMHO. But I love that new Zombiemen! - Winged-imp: dunno why, but I really can't stand this one... I find it generic and out of context. - Baron of hell + Wolverine + flames? BURP. Don't get me wrong, I'm really picky here and my general feeling is positive on DOOM Eternal (I'll surely buy it on day one). But I still hope that Id Software will somehow polish this cartoon-style, and at the same time recover some very good DOOM 2016 monster design. Everything else: can't wait! :D
  9. antiriad

    Chocolate Doom

    Thank you, but I'm on Raspberry Pi (Raspbian Jessie). It's the same?
  10. antiriad

    Chocolate Doom

    Hello, on YouTube there is a video of Chocolate DOOM running with Don Allen's Timbres of Heaven Soundfont: I think it's great and I'd like to use it (I'm on my Raspberry Pi). I downloaded the 7zip archive that contains a .SF2 file, but I can't understand how to get it working with ChocoDOOM (ver2.3.0). Any hint? Thanks! :)
  11. Hi, I'm setting up a small BBS in my spare time (Mystic on RPi) and I will have a section dedicated to Classic DOOM. I have already customized a script that lists currently active chocolate-doom servers, now I'd like to add some other resources that could be somehow useful for vanilla DOOM or that have some kind of "historic" value. So I'm looking for TXTs (faqs, walkthroughs, ASCII, ANSIs etc.) that would be nice (or funny, or typical of 90's DOOM mania) to put in this section of the BBS (of course credited) like the "Unofficial DOOM Specs" mentioned in this page. Any hints? Thanks :)
  12. antiriad

    DOOM on Raspberry in 2016 ...which way?

    Maybe this could help: there is a Quake 1 port optimized for Raspberry that runs at 60fps@1080p even on a RPi 1B thanks to Open GLES. It's called Qurp and its source code is here: https://github.com/welford/qurp Maybe it could be of any help (I'm not a developer). Thanks
  13. antiriad

    DOOM on Raspberry in 2016 ...which way?

    Hi Rachel, I was going to point you in this thread on RPi forums when I read this great news: so does it take advantage of hardware acceleration? Does it run in pure CLI? Thank you very much for all your work (and that of dpJudas!)
  14. antiriad

    DOOM on Raspberry in 2016 ...which way?

    Thank you very much for your feedback. Latest stable release (SDL1 version) of Chocolate DOOM still runs very well on RPi, so IMHO it could have stayed in the Raspbian repository until V3 (SDL2). Really, it would be nice to have the opportunity to easily install Chocolate DOOM and ZDOOM on Raspberry via apt-get (from official Raspbian repository, custom repository, or even via a slimmed version of Retropie-Setup-like script). These two source ports run very well, but since installation is uncomfortable this leads many users to older ports, often without documentation. Which is a shame. ;D
×