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


  • Content count

  • Joined

  • Last visited

About Jodwin

  • Rank
    Forum Staple

Recent Profile Visitors

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

Single Status Update

See all updates by Jodwin

  1. I was going to make a New year's speedmap late last night when Doom Builder crapped out on me when I tried to save the map, losing an hour of work. Hour's not a pretty big deal, but it was the first time I was able to get time for mapping since October. Then I found out that suddenly DB was no longer able to open any wad files all. I suspect it was because of particular system settings I had changed since last using DB, and which I can't take back because of other programs more important than DB. Mind you, I was still using Doom Builder 1 because it had been much, much better than Doom Builder 2.

    Then today I re-installed DB 2 to check if it would work and if it was worth anything at all. Sure, file operations for it worked. But when I tried to map, it's still as fucking horrible as ever:
    1) Why the fuck clicking void when you have selected something doesn't deselect the items?

    2) Why the fuck pressing insert to add vertex or line just puts the vertex where the cursor is instead of entering a place mode where you THEN click the target spot with the mouse (like in DB1)?

    3) Why the fuck linedefs try to snap to vertices when drawing if you aren't fully zoomed in? The whole snap-to thing when drawing fucking sucks.

    Okay, 1) and 3) were hidden in the settings, but I can't comprehend why the hell they were set on by default by begin with. Who the fuck wants linedefs stitching to vertices all the fucking time? Who wants to have selected items sticking around all the fucking time? But even if I could fix those, it doesn't help the most important issue which is THE INSERT BUTTON BEING FUCKING RETARDED, slowing mapping process a lot.

    There's no way I can map with a program that works in a completely illogical fashion compared to its predecessor, and with DB 1 no longer working for me, fuck this shit.

    1. Show previous comments  13 more
    2. 40oz


      I remember being not very interested in switching to DB2 for a while. I kinda had to force myself into getting used to it and now im glad i did.

    3. hervoheebo


      Funny, for me it was kinda the opposite. I was merrily building with DB1 and remembered that trailer a while back, went and checked the site and apparently DB2 had been released quite a while ago. Haven't looked back since. When I have to use other editors on less powerful computers (that can't run DB2) it feels almost alien.

    4. Megalyth


      DB1 has been giving me a few problems that I've not experienced before. This has only been since I reformatted and reinstalled everything. One theory is that now I'm running SP3 as opposed to SP2, which had possibly preserved my XP install in an older state more conducive to DB1's 3D mode, which is where the problems seem to be stemming from. Another is my primitive video card running much newer drivers than before the reformat. I've experienced dramatic compatibility shifts from one forceware to the next.

      Unfortunately, while DB2 is more stable, my PC is a tad too slow to run DB2 in the same capacity as DB1.