[Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
-
- Posts: 561
- Joined: Fri Aug 09, 2013 12:13 pm
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
No, at least not right away. Pulsar was intended to be a minimum-change derivative of GZDoom that would gradually evolve if I gained the time and skill to do so.
Pulsar was always a maybe thing, and probably would have ended up providing only what was necessary for Ascension Revolution. I'm even more hesitant to start work on Pulsar now that GLOOME is here and Revolution might not happen.
Pulsar was always a maybe thing, and probably would have ended up providing only what was necessary for Ascension Revolution. I'm even more hesitant to start work on Pulsar now that GLOOME is here and Revolution might not happen.
-
- Posts: 142
- Joined: Thu Apr 03, 2014 10:25 am
- Graphics Processor: nVidia (Modern GZDoom)
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
GAMEINFO lets you set a startup screen type. To quote the page itself...ibm5155 wrote: I just wanted to add an heretic like loading screen, I think I'll just need to change the Game = Doom to Game = Heretic (and also, change alot of stuff inside of Heretic config...
This is the part that makes confuse to me, I still couldn't found how to load that ascii animation, is that hardcoded on the binary code or on the engine.pk3?
You'll also need to supply an ANSI screen lump called "LOADING" to use as the background; it's set up the exact same way as ENDOOM. Unfortunately, the only limitation is that you cannot change where the loading bars are placed.STARTUPTYPE = "<game name>"
Allows to choose the startup screen will be displayed. Valid values are Doom (text), Heretic, Hexen and Strife. This overrides the game default.
(BTW you don't need several iwads for different languages, the LANGUAGE lump lets you set translations for every string and picks which one to use depending on the user's system language)
-
- Posts: 98
- Joined: Wed Jul 02, 2014 7:52 pm
- Location: CA
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
Pretty rad man. Get excite.
-
-
- Posts: 1198
- Joined: Tue Feb 26, 2013 2:48 pm
- Preferred Pronouns: No Preference
- Operating System Version (Optional): Arch Linux
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
This might actually be trivial to implement as a GAMEINFO property. I'll see about adding that.TehRealSalt wrote:Unfortunately, the only limitation is that you cannot change where the loading bars are placed.
Why is this needed? I really want to know what people want of ConsoleCommand that couldn't be done by adding new functions.XCVG wrote:-Implementation of the controversial ConsoleCommand function and possibly some other insecure or unsafe functions.
Indeed this is already doable with the GameInfo block in MAPINFO now.ZDWH wrote:-Ditch aspect ratio correction across the board (it looks like this can be made configurable now)
Code: Select all
gameinfo
{
pixelratio = 1.0
}
-
-
- Posts: 17934
- Joined: Fri Jul 06, 2007 3:22 pm
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
Instead of implementing ConsoleCommand and using ConsoleCommand("foobar blah blah") in a script, why not implement foobar as an ACS command doing the same thing as the foobar console command, and having Foobar(blah, blah) in a script?XCVG wrote:-Implementation of the controversial ConsoleCommand function and possibly some other insecure or unsafe functions.
-
- Posts: 313
- Joined: Tue Jul 02, 2013 7:26 pm
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
Would it be possible to start merging the feature suggestions with GLOOME?
-
- Posts: 561
- Joined: Fri Aug 09, 2013 12:13 pm
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
It's a stopgap measure more than anything. Implementing foobar may be fairly trivial, but implementing foobar, foo, bar, tbar, xbar, mybar, yourbar, etc is less so. Implementing that one functions provides immediate access to a lot of capabilities that may or may not be slowly implemented over time. I understand why it hasn't been done for ZDoom, but it's assumed that a game dev is not going to do something malicious- or will do it anyway.Gez wrote:Instead of implementing ConsoleCommand and using ConsoleCommand("foobar blah blah") in a script, why not implement foobar as an ACS command doing the same thing as the foobar console command, and having Foobar(blah, blah) in a script?XCVG wrote:-Implementation of the controversial ConsoleCommand function and possibly some other insecure or unsafe functions.
See the above. Nothing, but those functions may or may not be added and we may have to wait a while to get them, whereas ConsoleCommand gives us a lot of capability right out of the gate.Marrub wrote:Why is this needed? I really want to know what people want of ConsoleCommand that couldn't be done by adding new functions.XCVG wrote:-Implementation of the controversial ConsoleCommand function and possibly some other insecure or unsafe functions.
I don't think this affects the HUD or models, though it's been a while since I've looked at it.Marrub wrote:Indeed this is already doable with the GameInfo block in MAPINFO now.ZDWH wrote:-Ditch aspect ratio correction across the board (it looks like this can be made configurable now)Code: Select all
gameinfo { pixelratio = 1.0 }
-
-
- Posts: 1198
- Joined: Tue Feb 26, 2013 2:48 pm
- Preferred Pronouns: No Preference
- Operating System Version (Optional): Arch Linux
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
I'm pretty sure it doesn't affect models, but I did make it stretch view sprites accordingly. It can look pretty funny if extremely stretched.XCVG wrote:I don't think this affects the HUD or models, though it's been a while since I've looked at it.
If you're making your own fork, you don't have to wait on anyone but yourself.XCVG wrote:Implementing that one functions provides immediate access to a lot of capabilities that may or may not be slowly implemented over time.
Which ones? I do have quite a few feature requests in my todo right now.Raziel236 wrote:Would it be possible to start merging the feature suggestions with GLOOME?
-
- Posts: 561
- Joined: Fri Aug 09, 2013 12:13 pm
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
Actually, the main reason I wanted to implement this was because I knew I wouldn't have the time or skill to implement a lot of functions, at least not right away. But it looks like you're already working on some of the more advanced stuff I had in mind.Marrub wrote:If you're making your own fork, you don't have to wait on anyone but yourself.XCVG wrote:Implementing that one functions provides immediate access to a lot of capabilities that may or may not be slowly implemented over time.
-
- Posts: 282
- Joined: Thu Apr 02, 2015 8:42 pm
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
Thank you and your team for this, Term - this is what I feel will be the ultimate platform for my Weavel game I was planning to use Metroid Dreadnought as a base on! The thing is that I do not understand DECORATE very well, along with having a little bit of ACS in terms of line specials, sector specials, and creating events based on triggers. I will learn as much as I can within my free time to do this!
-
- Posts: 313
- Joined: Tue Jul 02, 2013 7:26 pm
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
Raziel236 wrote:Would it be possible to start merging the feature suggestions with GLOOME?
Meant the ZDoom suggestions.Marrub wrote:Which ones? I do have quite a few feature requests in my todo right now.
-
-
- Posts: 1198
- Joined: Tue Feb 26, 2013 2:48 pm
- Preferred Pronouns: No Preference
- Operating System Version (Optional): Arch Linux
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
Well, yeah, but any in particular? I can't just add every single feature suggestion.Raziel236 wrote:Raziel236 wrote:Would it be possible to start merging the feature suggestions with GLOOME?Meant the ZDoom suggestions.Marrub wrote:Which ones? I do have quite a few feature requests in my todo right now.
-
- Posts: 2119
- Joined: Thu May 02, 2013 1:27 am
- Operating System Version (Optional): Windows 10
- Graphics Processor: nVidia with Vulkan support
- Location: Brazil
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
Specially (sp?) because people have suggested ConsoleCommand (*pukes*) in the past, so adding all feature suggestions in both the Closed Feature Suggestions and Feature Suggestions forums would be dangerous.
There's also other possibly dangerous suggestions in there.
There's also other possibly dangerous suggestions in there.
-
- Posts: 313
- Joined: Tue Jul 02, 2013 7:26 pm
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
No no just meant that any suggested for ZDoom could be considered for GLOOME, especially rejected ones.
-
- Posts: 1927
- Joined: Thu Jun 12, 2014 3:16 pm
- Location: Anywhere.
Re: [Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow
Whoa, I love the look of Nocturne in Yellow, nice work, man!