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

fabian

Members
  • Content count

    1230
  • Joined

  • Last visited

Everything posted by fabian

  1. In general you are right, but my specific case is simpler: I'd like to suggest some map modifications to the Freedoom project. And instead of the usual manual and error-prone changelog (i.e. replace Thing X by Thing Y, increase light by Z, ...) I'd like to submit a machine-generated but human-readable diff between both maps, i.e. before vs. after. I got used to submitting source code patches to open-source projects and find that submitting a binary file with some accompanying text just feels wrong. :)
  2. I am looking for a tool that can dump the complete set of properties of all things, lines, etc. in a WAD map in a human-readable format and in a reproducable way. I want to use it to spot the difference between two (not too different) WAD maps using e.g. "diff -u".
  3. fabian

    Release clean up

    This is really an important question that needs to be clarified! For example, I'd really like to implement some changes to Map05 which were discussed elsewhere in this forum and which would make the level IMHO much less frustrating, but hesitate do to so because I don't want to step on the original author's/maintainer's toes.
  4. Hi, I am currently looking for (a MegaWAD with) some short levels. Nothing too hard, just some fun to kill some time and keep me entertained for, say, 5-10 minutes. Something like the first dozen levels of Scythe!
  5. As the subject suggests, I wonder which PWADs would be accepted for Compet-N demos if it was established today. I believe, e.g. Scythe and DTWID would be good candidates. On the other hand I wonder why Icarus and Eternal Doom were not added back then (but then I believe that had to do with "TeamTNT have sold their souls" ;) ).
  6. It seems the same questions has already been discussed there before: http://webcache.googleusercontent.com/search?q=cache:aUUG_xYItKEJ:www.doom.com.hr/forum/viewtopic.php%3Ff%3D12%26t%3D104+&cd=11&hl=de&ct=clnk&client=iceweasel-a The suggestions were pretty much the same as here!
  7. Any chance to get the list of PWADs accepted in Compet-N updated or extended?
  8. The reason why it worked with "-file doom1.wad av.wad" (in *that* order) should be that av.wad contains a TEXTURE1 lump based on doom2.wad's that re-overrides doom1.wad's one. However, in recent builds of prboom-plus it should work in any order.
  9. Yes, but Final Doom are IWADs, not PWADs. Sorry, In my initial post I should have asked "what PWADs in addition to the four official IWADs". By the way, I think the new "official family member" NERVE.WAD would be another obvious candidate. Apropos, Final Doom, how about Plutonia 2? I am not sure if this is relevant. Memento Mori was an obvious candidate back then (and maybe is still by today's standards), but according to its own MM.TXT file it was designed with *multiplayer* in mind. Maybe you are right. I remember I have once seen a video on Youtube with someone playing through the whole of Scythe in a matter of just a few minutes. There is really not much space left for competition. Maybe Scythe 2 would fit better? I am not sure if vanilla compatibility should still be a criterion; removed limits or even Boom compatibility should be alright. The WADs should just not be port-specific, IMHO (like, e.g. Knee-Deep in ZDoom).
  10. fabian

    Loading doom1 as a PWAD

    This exact use case, i.e. using doom1.wad as a resource PWAD for doom2.wad, is possible in recent PrBoom+ test releases. I implemented this by making sure that doom1.wad does not override the currently used IWAD's TEXTURE1 and PNAMES lumps.
  11. fabian

    Converting .lmp's to video?

    As has been mentioned before, you can use "prboom-plus -timedemo demo.lmp -viddump demo.mp4" to convert demo.lmp in to a demo.mp4 video. However, with prboom-plus' standard configuration you'll need additional tools for that, i.e. oggenc2, x264 and mkvmux. Or you change the configuration to use ffmpeg for all three encoding steps, as has also been mentioned before.
  12. fabian

    Source ports render Doom aspect-fov improperly

    Thank you very much for this insightful comparison! Both these ports have been derived from BOOM, so maybe it is unfair to compare them against vanilla. Do you know how they compare against the original BOOM.EXE in dosbox?
  13. fabian

    PrBoom-Plus, ver. 2.5.1.4

    It's not *that* simple. :p The problem is that the empty line is already eaten by the string parser deh_procStrings(), which has been called because of the "[STRINGS]" directive in the first line of that file. Since it cannot parse that empty line it returns to ProcessDehFile(), which reads the *next* line and expects another directive like "[STRINGS]" there (i.e. one of deh_blocks[i].key) but finds "E1TEXT = [...]" and thus fails for the rest of that file. We need to tell ProcessDehFile() that if it does not find a valid directive in the current line, it should pass that same line again to the last valid deh_proc*() parser (i.e. one of deh_blocks[i].fptr()) or fail if there wasn't one bvefore (i.e. comments at the beginning of a file).
  14. fabian

    PrBoom-Plus, ver. 2.5.1.4

    Nevertheless, would you accept a patch, though?
  15. fabian

    PrBoom-Plus, ver. 2.5.1.4

    The concatenation of the lines ending with a backslash isn't the problem, prboom-plus already does this properly. The blank lines that interrupt the [STRINGS] block are the problem here.
  16. fabian

    PrBoom-Plus, ver. 2.5.1.4

    o_O Great, thanks!
  17. fabian

    PrBoom-Plus, ver. 2.5.1.4

    Gosh, I was just going to play that WAD myself. Could you maybe either provide a fixed version of that BEX file or make prboom-plus's file parser more tolerant against the formatting mistakes found in it, please?
  18. fabian

    PrBoom-Plus, ver. 2.5.1.4

    I guess he is talking about the fix found here: http://www.doomworld.com/pageofdoom/lostdoom.html
  19. fabian

    Current state and future of WinMBF?

    Even if you decide not to apply any of the patches , I believe you should at least release the current state in SVN to the public. It contains so many features that clearly add value over the current 2.03 Build 2 release, e.g. video scaling and aspect ration fixing. Though I believe you should at least apply crash-videomode.patch, which fixes a crash introduced by the WinMBF change set. The other crash-*, security-* and portability-* patches are minimal-intrusive and could turn out interesting as well.
  20. fabian

    Palette change

    Damn, yes, I wrote some C-Code using libjpeg for that... :/
  21. fabian

    Palette change

    Alright, I somehow managed to recreate the palette from the image posted in http://www.doomworld.com/vb/post/1007754. (Please feel free to ask for the code if you are interested.) It is available here: http://greffrath.com/~fabian/moddedpalette06.zip If you're asking me, it's looking plain great. It gives the game a fresh new feeling without changing its visual appearance too much away from Doom.
  22. fabian

    Palette change

    Unfortunately, that download link is broken. Does someone still have this PWAD with the changed palette available somewhere? I'd love to check it out myself and see how Freedoom looks with it.
  23. fabian

    freedoom and free content source ports

    Well, it's not that complicated: Get prboom-plus from SVN and run "./configure --disable-nonfree-graphics"
  24. fabian

    Rock/Metal Songs That Fit Doom

    I think the music should be of the same area when DOOM was released, i.e. early 90s. I'd like to add Samael - Into the Pentagram to the list.
  25. To answer my own question, I have supplied the following patch to the corresponding bug [1] in prboom-plus' bug tracker on sourceforge:--- a/src/w_wad.c +++ b/src/w_wad.c @@ -253,6 +253,12 @@ static void W_AddFile(wadfile_info_t *wa } strncpy (lump_p->name, fileinfo->name, 8); lump_p->source = wadfile->src; // Ty 08/29/98 + + // IWAD file used as recource PWAD must not override TEXTURE1 or PNAMES + if (wadfile->src != source_iwad && !strncmp(header.identification,"IWAD",4) && + (!strnicmp(fileinfo->name,"TEXTURE1",8) || + !strnicmp(fileinfo->name,"PNAMES",6))) + strncpy (lump_p->name, "-IGNORE-", 8); } free(fileinfo2free); // killough It prevents IWADs that are not used as *the* current IWAD from overriding the current IWAD's TEXTURE1/2 and PNAMES lumps. I admit it is a bit hackish, but it works for the decribed use case: "prboom-plus -iwad freedoom.wad -file doom1.wad" works as expected. Furthermore, PWADs that supply their own TEXTURE1/2 lumps for a reason are still allowed to do so (but for additional IWADs this is usually wrong). It fails, however, for IWADs that declare themselves as PWADs like CHEX.WAD or DOOM.WAD and DOOM2.WAD from the Doom 3 BFG Edition. A more clean solution would be to introduce the aforementioned cummulative TEXTURE and PNAMES lumps, but that is bexond the scope of my approach. [1] http://sourceforge.net/tracker/?func=detail&aid=3603569&group_id=148658&atid=772946
×