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

fabian

Members
  • Content count

    1193
  • Joined

  • Last visited

Everything posted by fabian

  1. fabian

    Whats better then GZdoom.

    Sex.
  2. Update August 23, 2019: Crispy Doom 5.6.1 is released! Crispy Doom is a friendly fork of Chocolate Doom that provides a higher display resolution, removes the static limits of the Doom engine and offers further optional visual, tactical and physical enhancements while remaining entirely config file, savegame, netplay and demo compatible with the original. Crispy Doom 5.6.1 has been released on August 23, 2019. It is dedicated to hotfixing the bugs reported by the community after the 5.6 release. Please visit the Crispy Doom homepage for more information: https://github.com/fabiangreffrath/crispy-doom/releases Binaries for Windows (x86) are available here: https://github.com/fabiangreffrath/crispy-doom/releases/download/crispy-doom-5.6.1/crispy-doom-5.6.1-win32.zip Have a lot of fun! - Fabian
  3. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    Update August 23, 2019: Crispy Doom 5.6.1 is released! Crispy Doom is a friendly fork of Chocolate Doom that provides a higher display resolution, removes the static limits of the Doom engine and offers further optional visual, tactical and physical enhancements while remaining entirely config file, savegame, netplay and demo compatible with the original. Crispy Doom 5.6.1 has been released on August 23, 2019. It is dedicated to hotfixing the bugs reported by the community after the 5.6 release. Please visit the Crispy Doom homepage for more information: https://github.com/fabiangreffrath/crispy-doom/releases Binaries for Windows (x86) are available here: https://github.com/fabiangreffrath/crispy-doom/releases/download/crispy-doom-5.6.1/crispy-doom-5.6.1-win32.zip Have a lot of fun! - Fabian
  4. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    Sorry for not getting back to you earlier! I am afraid, there isn't much I can do about this. The feedback for playing with both uncapped framerate and vsync enabled is mostly "butter smooth" (also for me, though on Linux) - but there are always a few for which it lacks. The reason for this could be anywhere between your mouse's native resolution, your mouse driver or some setting, your Windows version, SDL or even the port itself - but I have no idea what exactly. @Zodomaniac has been working on completing the Crispness wiki page. Thanks for that! Sorry, but I have never used this feature myself. It is merely inherited from Chocolate Doom so I am referencing you to its documentation instead: https://www.chocolate-doom.org/wiki/index.php/GUS I have never felt it like that. Constructive criticism is always welcome!
  5. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    You may still read them from the automap. I understand the sheer possibility to have them visible all the time may be considered as cheating.
  6. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    @maxmanium and @ZeroMaster010 I fixed your issues in GIT, thanks for pointing them out!
  7. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    @ZeroMaster010 Sorry, I misunderstood you! I assumed that you wanted me to also disable even the non-desyncing cheat codes during demo recording. So, all you want me to disable is the "Show Player Coords: Always" option?
  8. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    Found and fixed! Thanks for your pointers. Apparently, this issue was hidden by 64-bit pointer size, because the Windows binaries are built as 32-bit and my Linux builds are all 64-bit (the pointer size determines the size of the vldoor_t and plat_t structs).
  9. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    Does anybody else get a crash when playing back this demo with SIGIL_COMPAT.wad?
  10. Fixed now in Crispy Doom, thanks for pointing this out!
  11. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    I have slept over this. Using IDMYPOS and IDDT is even possible with Vanilla DOOM.EXE when recording a demo. Nobody would ever notice... I don't want my port to be "worse" in this regard and have the turning-off of these cheats be considered a regression. I think it's already a fine line to cross that I have disabled the cheats that would inevitably cause desync. If you want to teach speed runners to play fair, I think castrating source ports if the wrong solution. Especially, since we are living in an open source world, people could easily just change one byte in the source code and have this reverted - and again, nobody would ever notice...
  12. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    Could you please send me your config? And a savegame of the moment when I have to press the USE key?
  13. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    I cannot reproduce this with 5.6, it simply doesn't crash when playing back the demo you attached. The framebuffer resolution will always be 640x400 (or 320x200, respectively), so this only affects the way it will be scaled on your screen. The widescreen rendering option in Crispy is still a pipe dream, not a single line of code has been written.
  14. Well, maybe this was the wrong reply to give a few years ago. As you can see, the project is still alive and active. However, I invite you to take any code you need from Crispy and to get more actively involved in the project as before.
  15. Thanks for checking. Please report back if you ever experience that crash again, Crispy must never crash. @Capellan No, there won't be any higher resolutions than 640x409 in Crispy.
  16. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    An episode selection menu for NRFTL is a feature since Crispy 1.0, but you need to provide the menu graphics lumps for that. The BFG Edition IWADs usually contain those. There is also some limited support for the all-in-one masterlevels.wad, but no menu or similar since this PWAD doesn't contain any more assets than the maps themselves.
  17. You probably used some pre-5.6 version then. It used to crash there and I applied the fix to the 5.6 release.
  18. fabian

    Things about Doom you just found out

    Crispy uses the item respawn sound if DSSECRET is not available.
  19. M8 crashed on you with Crispy 5.6?
  20. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    I am currently on a one week vacation with my family. No computer, just a phone. So you'll get some more detailed replies in about a week. @maxmanium This issue has been reported before but was fixed in the 5.6 release. Could you please make sure you are running the latest version?
  21. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    Yes, but it's still work in progress and far from finished: https://github.com/fabiangreffrath/crispy-doom/wiki/Crispness
  22. fabian

    sound stuttering and fps drops in gzdoom [SOLVED]

    Off-topic, but you should really try to use punctuation. It vastly helps the people who read your posts and try to help understand your issues.
  23. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    Alright. I'd like to keep the "Show Player Coordinates: Always" option functional, because it shows only very coarse coordinates, but helps mappers identify critical points in their maps which they can relate to editor coordinates. I can revert the IDMYPOS cheat back to the original Vanilla behavior, sure. I can make this and IDDT single-player only if this is more comfortable for you.
  24. fabian

    Crispy Doom 5.6.1 (Update: Aug 23, 2019)

    Does this also apply to the coarse coordinates in the automap or only the high resolution IDMYPOS coordinates?
×