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

fabian

Members
  • Content count

    1610
  • Joined

  • Last visited

About fabian

Recent Profile Visitors

2921 profile views
  1. fabian

    Crispy Doom 5.9.1 (Update: Sep 04, 2020)

    That's what I implemented today. Now you could name your demo files as you wish!
  2. fabian

    How can I work on my own Source Port? (not a joke)

    Yeah, because that's how coding works, right? *sigh* I have spent a couple of weeks this year to cleanly port WinMBF to 64-bit, the result is called Woof!. Maybe you should use that as your starting point and then add back the Fusion features that you are looking for.
  3. In general, I agree. However, for some unknown reason, Lee explicitly decided to load them last: https://github.com/fabiangreffrath/woof/blob/583e6d2196438bc8099abd41eeb2f844b519ba51/Source/d_main.c#L1742 Edit: I guess I figured it out. DEHACKED lumps are processed from last to first, so it actually makes sense to load "preloaded" DEH files last - their changes will be overridden by DEHACKED lumps included in WADs and DEH files loaded from the command line. WAD files, however, are loaded in order and thus override each other. Now, what happens with DEHACKED lumps in WAD files? If preloaded WAD files contain DEHECKED lumps, these will get processed last if the WAD files are loaded first. I guess that's what Lee wanted to avoid by loading "preloaded" WAD files last - this way makes sure that their embedded DEHACKED lumps will be processed first.
  4. Here is a rather vague explanation by Lee himself: https://github.com/fabiangreffrath/woof/blob/583e6d2196438bc8099abd41eeb2f844b519ba51/docs/options.txt#L361
  5. fabian

    Crispy Doom 5.9.1 (Update: Sep 04, 2020)

    That would crash the demo loop then. No, DEMO1 is almost certainly already a demo lump.
  6. fabian

    My favourite source port is a fridge...

    Seriously, what is this?
  7. fabian

    Crispy Doom 5.9.1 (Update: Sep 04, 2020)

    I could just rename the lump to DEMO1 internally for the very reasons you outlined above.
  8. fabian

    PrBoom+/UMAPINFO v 2.5.1.7

    Looks reasonable, could you please try this approach and report back?
  9. fabian

    Crispy Doom 5.9.1 (Update: Sep 04, 2020)

    Oh, this bug again! I should find a solution for this, it is getting annoying... Edii: It didn't crash for me because I loaded the demo as "~/armadosia_01.lmp", which M_ExtractFileBase() couldn't properly truncate to "armadosi". Thanks a lot @plums for the analysis! Edit 2: This could be a solution: --- a/src/doom/d_main.c +++ b/src/doom/d_main.c @@ -1842,6 +1842,18 @@ void D_DoomMain (void) if (D_AddFile(file)) { + char *name = lumpinfo[numlumps - 1]->name; + int i; + + // [crispy] check if the demo file name gets truncated to a lump name that is already present. + if (strncasecmp(name, "demo", 4) && + (i = W_CheckNumForNameFromTo(name, numlumps - 2, 0)) > -1) + { + I_Error("Demo lump name collision detected with lump \'%.8s\' from %s!\n" + "Please rename your demo file.", + lumpinfo[i]->name, W_WadNameForLump(lumpinfo[i])); + } + M_StringCopy(demolumpname, lumpinfo[numlumps - 1]->name, sizeof(demolumpname)); } That is, quit with an error message if the case is detected that a demo file name gets truncated to a lump name that is already present.
  10. Single-patched masked textures with a different height between the texture and the patch, yes.
  11. fabian

    Crispy Doom 5.9.1 (Update: Sep 04, 2020)

    Thanks, but they don't crash for me. I have just timedemo'd through 01 and 15s and they both finished just fine. Did you know that you could simply attach a ZIP archive to your reply?
  12. I have just added an "integer_scaling" option, but I found this feature obscure enough to hide it from the menu. You'll have to edit the config file to enable it. Also, it is now possible to bind the "use" action to a dedicated mouse button. Using by double-click is still available, but needs to get explicitly enabled in the "Input Methods" section of the "General" Options menu. (NB: You might have to rebind your mouse keys.)
  13. fabian

    Crispy Doom 5.9.1 (Update: Sep 04, 2020)

    Sure, I'll review any code submission. Oops, looks like an oversight. Should be pretty straightforward to add. I don't own any Apple hardware, but there is a wiki article describing in detail how to build Crispy on Mac Os: https://github.com/fabiangreffrath/crispy-doom/wiki/OS-X-Compilation-and-Installation-Guide
  14. fabian

    Questioning the stigma towards DOSBox

    Crispy Heretic is back for quite some time.
  15. I know and I am not even sure if it should get fixed...
×