[Engine] GLOOME / [WIP] Project 67 & Nocturne in Yellow

[Swordman]

Is it Project 67 still in progress? It looks really neat

[TerminusEst13]

Is it OK to use C++11-specific C++ code in GLOOME, such as std::shared_ptr? I understand zdoom is still built with Visual Studio 2005, but Graf Zahl apparently builds gzdoom using Visual Studio 2013. Perhaps we should consider requiring Visual Studio 2013/2015 or modern versions of gcc, and permit modern C++ code. This would increase the forkiness of GLOOME, but perhaps in a good way.

The reason I ask is that I'm working toward a pull request for stereoscopic 3D support in GLOOME, and I'm wondering if I really need to restrict myself to an ancient dialect of C++.

Ah, hell! Forgot to answer this, I'm sorry.
Please, go right ahead. It's perfectly fine. The entire point of this fork is for people to tweak, adjust, and change things as they want, thanks to the GPL license. If something big gets completed and a pull request is done, it'd certainly make our lives easier.

marrub's personal stance is also along the same lines (though the exact phrase was "i don't give a shit, fuck C++98, use anything from C++11 you want"), so we're interested in seeing where it goes.

Is it Project 67 still in progress? It looks really neat

No, unfortunately, marrub has decided to focus on other projects, which I guess makes Nocturne in Yellow and Nido Force instead the flagship titles.

[biospud]

Is it OK to use C++11-specific C++ code in GLOOME, such as std::shared_ptr?...I'm working toward a pull request for stereoscopic 3D support in GLOOME...

...Please, go right ahead. It's perfectly fine. The entire point of this fork is for people to tweak, adjust, and change things as they want, thanks to the GPL license. If something big gets completed and a pull request is done, it'd certainly make our lives easier...

Thanks TerminusEst13 for the feedback. I ended up using vanilla C++ for the pull request I created at https://github.com/marrub--/GLOOME/pull/18, which implements the basic infrastructure for stereoscopic 3D in GLOOME. I'd appreciate any feedback you or the other developers might have on the code I submitted.

[JunkerKun]

No, unfortunately, marrub has decided to focus on other projects, which I guess makes Nocturne in Yellow and Nido Force instead the flagship titles.

To what point is the engine done? I mean, are there any crucial game breaking bugs or is it safe to make a game using Gloome (mainly, is it safe to use 3D models exclusively)?

[Alekv]

Please tell me when will the new update GLOOME? the engine is updated rarely , it seems they are not engaged ..
I'd like to see in GLOOME at least part of the todo

And tell me whether in GLOOME everything new that is in GZDoom, such as :
http://zdoom.org/wiki/PickActor

[Alekv]

Tell me why does not work function in the acs ChangeFlag () ;?
ChangeFlag ( 0 , "NOGRAVITY", TRUE); Without the quotation marks " " does not compile .
function as it is performed , but the player still with gravity.

[Titan314]

I bellieve it is because you need the modified version of ACC to compile the Gloome extra features.

Speaking of it, could we get a compiled version of the modified ACC?

[jpalomo]

And tell me whether in GLOOME everything new that is in GZDoom, such as :
http://zdoom.org/wiki/PickActor

The new flags are actually from GLOOME. I renamed them and fixed a bug with them before backporting it to ZDoom. There is still an open pull request on GLOOME's repository to fix it. Marrub just needs to merge it.

[Alekv]

I bellieve it is because you need the modified version of ACC to compile the Gloome extra features.
Speaking of it, could we get a compiled version of the modified ACC?

Yes, I know , in my folder are files GZDB https://github.com/marrub--/GLOOME/tree/master/acs gdefs.acs, gspecial.acs .. Script compiled, but that feature is not working ChangeFlag . Maybe I did not prescribe the correct flags in acs or something?

The new flags are actually from GLOOME. I renamed them and fixed a bug with them before backporting it to ZDoom. There is still an open pull request on GLOOME's repository to fix it. Marrub just needs to merge it.

Very good , but I would like to see more updates GLOOME Beta Builds download . = (

[Titan314]

How hard would it be to make an in engine Half life style level transition? Sorta like this https://www.doomworld.com/vb/wads-mods/ ... ansitions/, Except allowing enemies to go between levels. The person that made the Half Life style level changes said that the engine needs sector serialisation and deserialisation between hub levels.

[GooberMan]

Or, in a bit more detail:

Sectors will need to be marked up in some fashion (UDMF properties!) as being serialised between different levels. I suppose the easiest thing to do would be to add entries to hub save data for each of these inter-level zones as you encounter new hub levels rather than trying to pre-calculate such things. It would need to treat things inside those sectors as belonging to that interzone rather than the original level. Saving the level state would save those interhub states. Loading the next hub level would load relevant interhub states and create the things for it. Players would probably need to be treated special I assume because they're treated special all the time.

It's quite open to abuse and doing it wrong if the sectors don't match correctly between hub levels, but I'm pretty sure that was the case in Half Life too.

[JunkerKun]

Hm... is there a way to enable stillbob? The console command doesn't seem to work.

[ibm5155]

I think in a manual solution for that.
Make some global HUGE vectors, storing the monsters position x,y,z, tids, health and who they were tracking.

It will require alot of work, but I belive it'll work (at least, if there's a way to store the monsters pointers...

========================================================
Well, if that counts, Spooky House of Jumpscares TC is going to be GLOOME compatible, but don't expect a near release, I'm trying to do a 90% TC, and some stuff that the devs made in the game maker tool, are a pain in the ass to be made in Doom .
But at least, The way things are being done will allow even newbies to expand the mod with almost zero acs touches (It will only require some changes into acs because each sector texture/Spawn tids are stored in acs).
Also I need to thanks alot _mental_ for making/finding the tools to rip the textures/sprites/sounds from it, without that, I would be still taking screenshots and ripping the áudio with audacity ;--;

[Marrub]

Oops, I forgot forums existed.

Hm... is there a way to enable stillbob? The console command doesn't seem to work.

Yes, you have to use some ACS to do it. The stillbob/movebob cvars are now just multipliers for the values set by ACS.
I may eventually add a cvar to disable that.

I bellieve it is because you need the modified version of ACC to compile the Gloome extra features.
Speaking of it, could we get a compiled version of the modified ACC?

I could definitely cross-compile our ACC version. Do note however that this isn't the cause of the error.
Of which I'm not exactly sure. That should work fine.

Very good , but I would like to see more updates GLOOME Beta Builds download . = (

I can't cross-compile GLOOME with my current setup, and it would take too much effort to get it working.
I'll go yell at TheZombieKiller to make some builds for me, since I know he has a proper environment for that.

No, unfortunately, marrub has decided to focus on other projects, which I guess makes Nocturne in Yellow and Nido Force instead the flagship titles.

To what point is the engine done? I mean, are there any crucial game breaking bugs or is it safe to make a game using Gloome (mainly, is it safe to use 3D models exclusively)?

Yeah, it should be fine. I don't currently know of any bugs.

[ibm5155]

I could compile some Windows builds if you guys want (I did it on the time when there wasn't an oficial build for gloome)
Zdoom/Gloome code is kinda short compared to the ones that I was playing this year (1gb of code ;--;)