3DGE Source Fork - 1.36C released!

[Corbin]

3DGE Source Port Announcement
+++++++++++++++++++++++++++|


I want to note that I have started a fork of EDGE called hyper3DGE, or just 3DGE. We have opened a project site at SF (). We are a team of 3 people who originally invested this for HT, but after the demise of EDGE we decided to continue its legacy for everyone.

We released the first binary of the fork today, which has a few minor additions ported from an abandoned branch of Edge into 1.35. It's nothing too major, but I thought I'd list it here anyway. You are better off using Andy's version most likely if you are building a project.

The release notes are on the SF page itself. Let us know what you think. We hope to expand EDGE into new territory and gain some new source port end users. Cheers Andy for letting me create threads here for this.

If you are interested in developing you are more than welcome (encouraged, even) to join the development of this source port.


Also - I will only be releasing Win32 stuff for the time being (if anyone wants to do the Linux stuff I'll be more than happy to pass that along).

EDIT: NEW VERSION

[Tragos]

Corbin will never let Edge die.... Or Corbin might die? LOL

If you get all of this working I may just come back to Edge! Goodluck.

[deathbringer]

Any chance of portals on lower textures? I think I asked about it ages ago, in fact it might already be in XD.

It'd be good because you could build a whole detailed building you could even walk on the roof of, with a "sticking up block" "of portal" in the doorway that woud let you see inside, which would be built elsewhere on the map and also detailed and fancy.

[Corbin]

1.36.2 has been released!

http://sourceforge.net/projects/edge2/f ... ries/1.36/

Good news here is that we decided to leave 1.32 and continue with what Andy released in 1.35 final. Saying this, we now have full compatibility with EDGE mods should you decide to give this a test run.


++
CHANGELOG
(April 2011)++

+ FULL Compatibility with 1.35 final (mods will work!)

+ MD3 Support! Syntax is the same as MD2, with the
exception - lump/file name should be xMD3 instead
of xMD2 (where 'x' is the name).
Limitations: single-mesh support only, working on
full support.

+ Removed customizable stuff in styles.ddf due to
a clean working copy from EDGE 1.35 final. Will
be restored (and fixed!) in 1.36.3.

+ 3DGE now uses the wadfile 'edge2.wad'. This is to
avoid confusion in the future with the EDGE
wadfile.

+ Went ahead and included the doom_ddf folder from
EDGE 1.35 since people complained about downloading
them separately.

+ Removed DLL's associated with 0.35d. Now only one DLL is necessary (SDL).

[Nickster]

I've been lurking for quite a long while and have to say this interests me greatly.
Keep up the good work.

[Karnizero]

Incredible but true. Downloading...

And meanwhile, reading all your list of features.


Bat I have a quastion, my little Corbin: you call it "3DGE" or "hyper3DGE", but the Sourceforge web page says "EDGE 2", and Andrew is already developing a project called EDGE2, time before you even though about your "3DGE" engine (if we can call it "engine"), so isn't it a bit confusing, at least for those who know little about Andrew new secret engine?


Nah, good work, i will be testing it as soon as i can, and tell give you some good feedback.

[EDIT]

Ok downloaded, but i couldnt test it.
It asks for libgcc_s_dw2-1.dll which i didnt have, but downloaded from internet.
Now asks for libgcc_s_dw2-1.dll, which i don't have, and i don't want (i can't) to install MinGW. Any solution (i.e. send me the .dll
libstdc++-6.dll)?

[Corbin]

[Karnizero]

It works now with all your dlls.


Are the decals working or not? I changed the player_punch attk "PUFF=PUFF" by "DECAL=PUFF", but game console complains about it, saying that such instruction doesn't exists.


Also I noticed that the executable is using the caleb's face as icon. I would recommend to change it for a more appropriate one


As final question: why 3DGE is asking my windows to unblock the incoming net packets for it? This is, why 3DGE needs to access internet when i execute it?

[andrewj]

[Corbin]

[Karnizero]

[Corbin]

Another (very) small update, I released , which includes a new DDF function (scream_sound in THINGS for falling long distances, from Hexen), and a fix for the ability to customize menu and console graphics in styles.ddf. I was working on some stuff left over from Andy, but it's not included yet. Big features are still not finished, should be in the next package.

++
Changelog:
(June 2011)++

+ DDF Additions: Added SCREAM_SOUND for the player
when they fall long distances, ala Hexen. Use this in
THINGS.ddf.

+ Customizable styles.ddf (namely, background.image)
has been added back and fixed (console image now
sizes correctly). Commented-out switches are available
in Styles.ddf.

+ Bumped edge2.wad version number

+ Released Source.

+ Minor cleanups

[Karnizero]

[Corbin]

[Karnizero]

[Corbin]

I might make that a user defined option actually.

New release coming soon, with a few [very] interesting features, such as post processing effects and splitscreen support. Also, a few small fixes left from EDGE and 3DGE.

I'm also working on a wiki to update the DDF, RTS, and COAL documentation stuff. I was originally going to use a format similar to Lobo's guide but I decided a wiki might be easier.

[Tragos]

I watched your video that showcased the split screen feature. I commend your efforts! It appears that the 2nd player does not trigger events/monsters despite being able to interact with them.

Is split-screen a serious feature you plan to implement? Or is the beginning of actual multiplayer support for edge?

[Corbin]

To be fair Andrew did a lot of the work on this, but I plan on changing the orientation, and I'm in the process of creating a control scheme, and making splitscreen a dedicated menu. I am fixing the rest of the bugs with it as well.

I'm also working on a few other things I mentioned, but it's merely learning where to stick the code, not neccesarily how I need to write it.

The LAN/etc multiplayer stuff is being worked on internally alongside the splitscreen, the majority being by a network programmer, while I'm adding a few things on the SP side. I'm mostly interested in the OpenGL aspects and what I can do to enhance it. Also, things like a customizable inventory and whatnot are really fun, though they are very challenging.

It's really interesting working on this because a lot of it is trial and error. Almost 90% of the code I work on fails on build time, but it's helping me learn the engine (which is a good thing). I have a lot of hit and miss, but I am grasping the concept and where Andy put stuff and how it's working. It's a little different from the other DOOM engines but I'm slowly learning.

[Corbin]

Another update, I released , which includes a new parameter for testing the splitscreen in the engine (-splitscreen at runtime). This version was actually completed weeks ago but I decided to release something now rather than making you all wait for the planned stuff to surface. So, new parameter, and the HUD will have a bit of garbage over it because this release didn't fix the postprocessing problems I had at the time. Also, this version gives you very limited control of Player 2 (with only the mouse to use for moving, opening, and shooting) as I didn't finish the key mapping. This was what Ajapted helped me do so be sure to give him kudos!

++
Changelog:
(July 2011)++

+ New runtime Parameter -splitscreen, for testing ONLY. See below.

+ Bugfixes and optimizations

- HUD may occasionally glitch with garbage, working on new things
in source that were not completed at the time of this test.
HUD will glitch out in splitscreen as well.

- New Paramter -splitscreen is heavily bugged, no
input support for player 2 (only the mouse for basic controls), makes
playing very impractical. Mostly to test the mode on
numerous systems with weak configurations, especially
the GPU side. This version only has verticle splitscreen - the
next release will give you an option to scissor vertically
or horizontally. Keep in mind that there are also AI problems in
certain situations where they won't recognize either player, which
is fixed for the next release. I know I should have just included
these fixes but this version was out last month and I forgot to
make an update here about it first.

I was going to release an even newer version that actually has postprocessing fixed (as of yesterday) but I held off - I was able to gain an extra arm in the OpenGL department so we're in the process of making a topology for rendering improvements and other really cool effects. But, for now, something else to play with while you wait! Hopefully the next release will have very basic Internet support also!

If it complains about missing an additional dll (vfw32) let me know. If you get fed up with the splitscreen I would recommend using the last version as it's a bit less buggy. Also, screen wipes might act up and "miss" the last texture before wiping, which is expected for now. Just have fun!

[Nickster]

How will RTS scripting be effected by the split-screen changes?
Will the other player completely break them?

[Corbin]

[Corbin]

I'm on the brink of releasing a maintanence update. The update will fix the menus and console, reduce the filesize of the executable, and fix splitscreen for a horizontal scissor rather than a verticle.

Aside from that, I'm still working away at the heavier features and I'm actively thinking about hosting it all on SF rather than my own server, so it can be more open to changes and stuff.

There are still things that I'm grappling with (how everything potentially ties into the DDF system, etc). For instance, I think I have the inventory code from Heretic down (I had to rewrite it a bit), but beyond that I only have vague ideas on getting it to talk to DDF and whatnot. It does seem a little more complicated because EDGE does rely on things like RTS, DDF, COAL - which isn't the same convention as most other DOOM ports. So, for brand new stuff like inventory, it turned out a bit more challenging than I first thought.

Anyways, look for the maintanence update here in a few days.

[Corbin]

Anyone not willing to test out the last build? Need feedback before I start rolling out the final.

[Nickster]

[Corbin]

[Nickster]

[Corbin]

[Nickster]

[Corbin]

I will see what I can do, thanks for that. Is it only the BENEFIT that we're worried about with the players? Want to be sure it's not any other part of the code that could be affected.

-edit-
I found the piece of code that I'm sure controls it, RAD_ActBenefitPlayers, so I'll just do some adjusting and see what I can come up with.

[Corbin]

Sorry guys - this is taking a bit longer than usual. I've found a few more bugs I want to fix first.

In running some model format tests, I noticed that the rendering system might be slightly out-of-order when it comes to multiple alpha channel surfaces. There is interference, which is mostly noticeable on models (MD2 or MD3 format) with transparent surfaces/planes (such as, for instance, trees that render leaves with alpha surfaces). Revolving around the model, some surfaces show up while others get cut out. Currently looking into ways I can possibly fix this.

Sorry if I ramble on, I know you'd like to see an update but I'd rather have things fixed for the final release of 1.36 so I can start all the experimental stuff next.

EDIT: NEW VERSION