Actually, I reported these things on Doomworld on 23rd of August, and most of them still bother me. I'm sorry if some of these points were reported in this forum. But I know for sure, that some weren't. So I repost it all here, so just they, well, stay afloat. I removed some points which were probably my personal bugs (I changed my computer and my OS since then, so some things started workign correctly).

Drawing a line from some other line and drawing a new sector. I don't know how people usually do it, but when I needed to draw a line in DB1 I pressed ins, and a starting vertex would stick to the mouse cursor. Then I'd put the vertex where I wanted it to be and started drawing. In DB2 the vertex in this case would be draw right away on the map. This is actually EXTREMELY annoying, because when you need to draw a line from some other line, you have to switch to Verttices mode, put the vertex on the line, then switch to Lines and draw the line from where you need.
It's the same when you start drawing a sector withing another sector. In DB2 I have to point the mouse cursor to the place where I want to start and then press Ins, because the vertex is drawn on the map. Really, annoying.

ACS editor bug. There's a serious bug with 'replace all' function in script editor. When you try to replace something with something else, that contains the original string, the function will loop and start repeating the process of replacing until the program crashes. For example:
1. you command to find and replace light_fade(1,255,3.0); with light_fade(1,255,3.0); light_fade(2,255,3.0);
2. the program replaces light_fade(1,255,3.0); with 'light_fade(1,255,3.0); light_fade(2,255,3.0); (probably)
3. then the program tries to replace newly created light_fade(1,255,3.0); again and again and so on...
And you can't stop it, until it all freezes. I mean, like, completely.
Or, to be honest, I don't know what it does, because as soon as you press OK to find and replace, the whole thing freezes. But I think my guess is correct, as nothing like this happens with normal replacement, where new string doesn't contain the original one.

Vertex stitching. In DB1 the process of vertex stitching was considered as an action. Which means that when you pasted something, and some vertex stitched, you could just press Ctrl-Z to cancel that stitching. In DB2 this way you will cancel the whole pasting. Which means you have to turn off 'merge geometry' before you paste something bit like this, and I really don't like it.

Quick recent wads opening. Before I used to pressing Alt-F-1 to open the latest previously edited wad. Now the wads that were edited and are remembered are not bound to number keys. The same is about closing the wad, you can't do it in DB2 with Alt-F-C. That's not good. Some would say it's nothing, but, you know, that's one of the main reasons why I stopped using OpenOffice and came back to MicrosoftOffice (similarly to this case, in OpenOffice recently used documents are inside sub-menu and can't be opened with Alt-F-1).

Uploading resources. Will we ever be able to upload new resources in the wad through DB2? I mean, DeepSea can import textures in the wad being edited, as far as I know... Being able to add wads or directories is good, but not enough. And how about editing some lumps, like Decorate?

Gravity on/off in Visual Mode. There's a little bug connected to using shortcuts: if you press G to turn on/off gravity in Visual Mode, it at the same time turns on/off snap-to-grid. I think that controls in different modes shouldn't overlap.

Make brightness gradient. How the hell does this function work? Does it at all?

And finally: light level editing. If memory serves, in DB1 in Sectors mode you could select a sector and use Ctrl-PgUp/PgDn to increase/decrease light level. That's what we NEED in DB2. First of all, having to switch to the other mode just to edit light sucks. Second, if you select many sectors in Brightness Mode and start editing their light, you know what it does? It makes the lightness of all selected sectors to THE SAME. I.e. it ruins the lighting in the map. And the problem is, at first you may not even notice it. And you surely know, that sometimes it's extremely necessary to just increase or decrease lightning of many sectors equally, but keep their light levels different.

Press Ctrl-D instead of Insert.


IIRC Codeimp said several times that DB will not get any resource managing functions. There are already a bunch of well working tools for that anyways


Works fine for me. You probably expect it to do something it doesn't. It does not create any geometry for you. You'll have to select multiple sectors and it will graduate the light level between the first and the last sector between all the other selected sectors.

Can't say anything about your other points right now.

I am surprised that there is still someone who is not using r1233. Much has been improved since r1157.
http://doombuilder.svn.sourceforge.net/ ... /?view=log


This works very well, indeed. If you have a string of adjoining sectors, give the first sector a low brightness value. Then give the last sector a high brightness value. You just have to pay attention to how the sectors are selected. If you want the sectors to increase in brightness evenly, then they must all be in sequence from 1 to xx when selected. Then click on the gradient icon and done, ie.:



Height gradients work in a similar manner.



Hit F5, then Controls. Here are all the shortcut keys. Most are different from DB1.
I find it handy to have a printed version in front of me
http://www.sendspace.com/file/at0dk3
I have bound 2 or 3 to different keys from the defaults.

My mistake, people. I probably should've explained to you, that I've actually been mapping and modding for Doom for a long time and that I am not an idiot.

Make brightness gradient doesn't work in my DB2. I tried, it actually did nothing.

Light editing. Kappes Buur, you really think I can't look into controls menu?. DB2 DOES NOT HAVE any other means of brightness editing apart from make brightness gradient, brightness mode and increase/decrease brightness in Visual mode. Which, I repeat, sucks. I want to be able to edit light level in Sectors mode.



OK, that's useful, thanks. It still is a stupid and unnecessary change. But at least the function hasn't been lost.


All the other points are still relevant.

Works fine for me in both 1157 and SVN. Both the menu button and the hotkey.

It may be my personal bug, that's not especially important. The absense of light level controlling function in Sectors Mode, however, is.

Some of this has been fixed and/or added. Consider the other things declined or not reproducible.