Any utility that assists in the creation of mods, assets, etc, go here. For example: Ultimate Doom Builder, Slade, WadSmoosh, Oblige, etc.
Forum rules The Projects forums are ONLY for YOUR PROJECTS! If you are asking questions about a project, either find that project's thread, or start a thread in the General section instead.
esselfortium wrote:Bug report: The right-click options on a patch in the texture1 editor don't seem to work. When right-clicking on a patch image in the texture preview, the only menu option that has any effect is Add Patch. The others don't do anything from that menu, though they work fine from the buttons on the upper right or from the Patch submenu in the Texture menu up top.
While testing this I found another bug: the patch-selection highlight outline disappears when the "Send selected patch(es) back/forward" options are used.
Works for me, I'm guessing you don't have the patch selected first . Patches deselecting when moved back/forward is a bug though.
esselfortium wrote:The inconsistency is in the patch browser: it seems to be the only 'picker' in Slade that doesn't allow you to use the arrow keys and pgup/pgdn to move the selection around, and also doesn't allow you to type in a letter or two to skip to the next matching item in the list.
Heh I thought I had implemented keyboard control for the browser. Guess I forgot
esselfortium wrote:In addition to hoping to see a fix for that, my feature request is to allow for quicker patch duplication using a nice keyboard shortcut from Photoshop: if holding down the alt key while using the arrow keys to move the selected patch(es) around, it will create a duplicate and move that duplicate rather than the original.
BTW, sirjuddington didn't mention it, but he has already implemented that alt-arrow duplication feature and it can be found in the latest SVN build; as well as typing letters to jump to a patch in the patch browser.
sirjuddington wrote:Heh, well actually since that screenshot I've changed it so the hilight is an outline but selection is filled. Still subject to change, of course http://slade.mancubus.net/dev/3/s3me_ui9.png
should be controllable at least by cvars, for performance reasons
disposable_username2 wrote:2 bugs with r1043,windows xp sp3
1.in-place lump rename ignores "force uppercase" setting
2.if soundfont is configured and auto-play is on, select d_runnin in doom2.wad, press and hold Down key ->windows error box "slade.exe error" blah blah...
It does this when trying to set a color range after clearing the translations list.
That one, however, I've never gotten.
NeuralStunner wrote:* Which I love, by the way. Only things that'd make it better (aside from not crashing ):
Source/destination palette selectors, handy if you're translating across palettes or forgot to set the correct one beforehand.
The ability to scroll the previewer through selected graphics when multiple ones are being retranslated, so you know how they'll all look.
Working with initially truecolor graphics (paletting them first), and outputting truecolor or a modified PNG palette if applicable.
I guess I can put that on the suggestion list. I hate working with UI so I'll leave it up to Simon.
disposable_username2 wrote:
disposable_username2 wrote:2 bugs with r1043,windows xp sp3
1.in-place lump rename ignores "force uppercase" setting
2.if soundfont is configured and auto-play is on, select d_runnin in doom2.wad, press and hold Down key ->windows error box "slade.exe error" blah blah...
bump. reproduced with r1061
1. Fixed.
2. Seems that is a problem with the MIDI player.
It does this when trying to set a color range after clearing the translations list.
That one, however, I've never gotten.
OK, more detailed steps:
Select a graphic and a working palette.
Open the remap window.
Use the [-] button next to the "Translation Ranges" list until the list is empty.
Select a source palette range, any will do.
Under "Target Range Type", choose "Colour Gradient".
Pick either the start or end color under "Target Range", pick some color.
It should crash now.
Note that choosing palette range to palette range simply does nothing, neither harmful nor useful.
A case of "don't do that" probably, but sometimes I'm wanting to clear the trnslation lsit and start over, and I forget the extra step of putting a new list item back in. It could either give a warning when trying to work with a nonexistent remap, or force the list to always have at least a "0:0=0:0" in it.
I'm finally getting round to trying this. It seems very nice, very slick. Easy to use, well laid out etc. I can see me using this more and more as I get used to it.
One thing I'd like to change, when I load an IWAD (this is one that I created, not an original Id IWAD) and try to make a change to it, when I try to save, a message pops up saying "ERROR: IWAD saving disabled". Is this a user configurable option? If it is I can't find it so I'd appreciate if someone could tell me where it is. If it isn't, then it makes creating and editing a personal IWAD difficult (I got around it by opening up the WAD in a HEX editor and changing the header from IWAD to PWAD).
Enjay wrote:One thing I'd like to change, when I load an IWAD (this is one that I created, not an original Id IWAD) and try to make a change to it, when I try to save, a message pops up saying "ERROR: IWAD saving disabled". Is this a user configurable option?
Yes. You need to change the iwad_lock option in slade.cfg.
Enjay's question has kind of poked at a sore spot of mine.
I really think that these config-only options (short of the layout ones, of course) should still have a palce in the options window. If needed, put them under an Advanced category, with whatever warning seems sufficient.
It's a lot less hassle than editing the cfg directly and restarting, plus it's a lot less option obfustication, which I am borderline militant about.