by pming » Thu Jul 14, 2016 5:03
Hiya!
I was talking with some folks over on the Doomsday Engine forum about the lack of DE information with regards to mapping for it...and that even the SLADE3 devs don't really know how/what DE handles so that they could develop, say, "compatibility" with DE (map-building wise). As it stands, DE is freaking *gorgeous* (IMHO), and with DED and XG (it's 'scripting lang' for adding goodies), it has the potential for SO-O much more!
Ahem. Anyhoo...during one of my chats, one or two folk have been trying to tell me that me using GZDB2 for DE mapping (I use either the jDOOM config for DOOM/2, or the pure Hexen in Hexen or Heretic in Heretic) is a loosing battle because "it (GZDB2) will never work well because it's built for GZDoom". I've tried to explain that it's the Config and Include stuff that it looks at, and I tried to write my own for Hexen and Heretic, but was having difficulty with Hexen in particular. That, as far as I know, there isn't anything really "Hard-Coded" into GZDB2 that is GZDoom specific and will automatically be assumed no matter what config you choose (like, say "Hexen in Hexen format"). Am I wrong in this assumption?
My main question(s) over there were more along the line of "suggestive questions"; e.g., "Man, it sure would be nice if DE had more support for mappers...", and "Hey, does anyone have a GZDB2 Config file for a 'jHexen' or 'jHeretic'?", etc. To my dismay, I'm getting either silence or a weird feeling of "Oh, you're one of those 'artistic' types who wants to make pretty maps for DE...sorry, we thought you were a programmer". It's almost like DE doesn't
want anyone to make maps for it.
Don't get me wrong, the folks over there in the DE forums are generally nice. I have never been yelled at, swore/cursed at, called 'stupid' or anything like that. It's just that the pure ambivalence with regards to working with/for the mapping community is so noticeable.
So...
Q1: Is GZDB2 "specific to GZDOOM" that non-GZDOOM mapping is not going to work?
Q2: Are there any plans to write (or figure out how to) a full-on "DE" config? Or separate ones (Hexen, Heretic, DOOM, DOOM2, etc)
Q3: Should I just give up on learning/mapping for DE until, say, the early 2020's, when there might be more 'artsy-fartsy-mappers' love? (ok, that last part sounded...weird...)
I'd LOVE to map for DE (Hexen and Heretic in particular), using GZDB2, with full DED access in-editor. It'd be even sweeter if it could 'read', say, "materials.ded" and then interpret that into a 'gl equivalent' for showing in the editor (like GLDEFS show up for GZDB2 DOOM2), and even better if we could also get approximations for color, dynamic lights (via ded), etc...like if you load up BeautifulDOOM into GZDB2...you can see all the glorious lights, glows, etc. I know, pie-in-the-sky, but hey...I can dream!
Thanks for ready this mini-novel! Sorry it's so long!
^_^
Paul L. Ming
Hiya!
I was talking with some folks over on the Doomsday Engine forum about the lack of DE information with regards to mapping for it...and that even the SLADE3 devs don't really know how/what DE handles so that they could develop, say, "compatibility" with DE (map-building wise). As it stands, DE is freaking *gorgeous* (IMHO), and with DED and XG (it's 'scripting lang' for adding goodies), it has the potential for SO-O much more!
Ahem. Anyhoo...during one of my chats, one or two folk have been trying to tell me that me using GZDB2 for DE mapping (I use either the jDOOM config for DOOM/2, or the pure Hexen in Hexen or Heretic in Heretic) is a loosing battle because "it (GZDB2) will never work well because it's built for GZDoom". I've tried to explain that it's the Config and Include stuff that it looks at, and I tried to write my own for Hexen and Heretic, but was having difficulty with Hexen in particular. That, as far as I know, there isn't anything really "Hard-Coded" into GZDB2 that is GZDoom specific and will automatically be assumed no matter what config you choose (like, say "Hexen in Hexen format"). Am I wrong in this assumption?
My main question(s) over there were more along the line of "suggestive questions"; e.g., "Man, it sure would be nice if DE had more support for mappers...", and "Hey, does anyone have a GZDB2 Config file for a 'jHexen' or 'jHeretic'?", etc. To my dismay, I'm getting either silence or a weird feeling of "Oh, you're one of those 'artistic' types who wants to make pretty maps for DE...sorry, we thought you were a programmer". It's almost like DE doesn't [i]want[/i] anyone to make maps for it. :shock:
Don't get me wrong, the folks over there in the DE forums are generally nice. I have never been yelled at, swore/cursed at, called 'stupid' or anything like that. It's just that the pure ambivalence with regards to working with/for the mapping community is so noticeable.
So...
[b]Q1: Is GZDB2 "specific to GZDOOM" that non-GZDOOM mapping is not going to work?[/b]
[b]Q2: Are there any plans to write (or figure out how to) a full-on "DE" config? Or separate ones (Hexen, Heretic, DOOM, DOOM2, etc)[/b]
[b]Q3: Should I just give up on learning/mapping for DE until, say, the early 2020's, when there might be more 'artsy-fartsy-mappers' love?[/b] (ok, that last part sounded...weird...)
I'd LOVE to map for DE (Hexen and Heretic in particular), using GZDB2, with full DED access in-editor. It'd be even sweeter if it could 'read', say, "materials.ded" and then interpret that into a 'gl equivalent' for showing in the editor (like GLDEFS show up for GZDB2 DOOM2), and even better if we could also get approximations for color, dynamic lights (via ded), etc...like if you load up BeautifulDOOM into GZDB2...you can see all the glorious lights, glows, etc. I know, pie-in-the-sky, but hey...I can dream!
Thanks for ready this mini-novel! Sorry it's so long! :oops:
^_^
Paul L. Ming