EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
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.
Got a cool project idea but nothing else? Put it in the project ideas thread instead!
Projects for any Doom-based engine are perfectly acceptable here too.
Please read the full rules for more details.
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.
Got a cool project idea but nothing else? Put it in the project ideas thread instead!
Projects for any Doom-based engine are perfectly acceptable here too.
Please read the full rules for more details.
-
- Posts: 1467
- Joined: Sun Mar 14, 2010 2:52 am
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
A quick question: Is transparency broken in the recent build?
Been trying it out with various mods and there is zero transparency.
Been trying it out with various mods and there is zero transparency.
-
- Posts: 447
- Joined: Wed Aug 15, 2012 3:41 pm
- Location: California
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
Some things to check:
What is the value of r_oldblend if you type it in the console (should be 1)? And also check r_transfix.
Transparency in images? What format are the images in?
If r_oldblend is not at 1, try setting that and restarting EDGE. If it is, set it to 0 and restart. Let me know the results, also screenshots are welcome as well.
What is the value of r_oldblend if you type it in the console (should be 1)? And also check r_transfix.
Transparency in images? What format are the images in?
If r_oldblend is not at 1, try setting that and restarting EDGE. If it is, set it to 0 and restart. Let me know the results, also screenshots are welcome as well.
-
- Posts: 1467
- Joined: Sun Mar 14, 2010 2:52 am
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
Apears to be everything, no transparency in sight. I'll try the console command.
EDIT: r_oldblend WAS set to 0. How come it isn't set to 1 by default? And how about adding it to video options menu. Or should it be screen options.
EDIT: r_oldblend WAS set to 0. How come it isn't set to 1 by default? And how about adding it to video options menu. Or should it be screen options.
-
- Posts: 282
- Joined: Thu Apr 02, 2015 8:42 pm
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
Completely off topic, but does anyone know where to get royalty - free chess piece MD2/MD3 models, and how would I go about implementing them into 3DGE? I found an old reference wad from when Andrew was the developer but as far as I know, that was for previous versions dating back to 1.23 -1.36F. Please, would like help for a Hexen-style map I'm experimenting with, and models would be the most efficient assets to use in a scripted environment. Thank you!
-
- Posts: 447
- Joined: Wed Aug 15, 2012 3:41 pm
- Location: California
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
Are you asking about a 3D model tutorial? I've actually been working on one, and also has documentation on GL3-only features such as specular and normal mapping.
As for those, find them in any format - I've also been cooking up a 3D model conversion tutorial. I'm sure it will also apply to other ports, at least logically speaking, mostly for GZDoom.
Just a quick note: releasing EDGE 2.1.0 RC2 shortly which has a host of bug fixes, and changes DDF on-disk semantics slightly (all DDF folders will now reside in a folder called /base/).
For those of you that found COAL complicated, look up any QuakeC tutorial - the generalized idea is the same. Also, I'm really trying to put work into the existing COAL docs on the EdgeWiki. What exactly if you don't mind, is overly complicated? In the same vein, any suggestions to make it easier to read/comprehend? Because we are in light talks with complimenting the existing DDF/RTS into COAL.
Feedback welcome
As for those, find them in any format - I've also been cooking up a 3D model conversion tutorial. I'm sure it will also apply to other ports, at least logically speaking, mostly for GZDoom.
Just a quick note: releasing EDGE 2.1.0 RC2 shortly which has a host of bug fixes, and changes DDF on-disk semantics slightly (all DDF folders will now reside in a folder called /base/).
For those of you that found COAL complicated, look up any QuakeC tutorial - the generalized idea is the same. Also, I'm really trying to put work into the existing COAL docs on the EdgeWiki. What exactly if you don't mind, is overly complicated? In the same vein, any suggestions to make it easier to read/comprehend? Because we are in light talks with complimenting the existing DDF/RTS into COAL.
Feedback welcome
-
- Posts: 1467
- Joined: Sun Mar 14, 2010 2:52 am
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
THING commands ARMOUR_CLASS, ARMOUR_PROTECTION, etc appear to be broken. I am trying to make an armour item that protects against "missiles" (projectiles) while ignoring everything else. Something that should be 100% doable with those commands at your disposal but no matter what combination of commands I use in whatever order, it just will not work. I do remeber it working fine a while back, so I'm not sure if something happened between versions. Tested and not working with v2.1.0pre-242-gc9e8a01 and v2.1.0-RC1-93-g12c3a0307
-
- Posts: 447
- Joined: Wed Aug 15, 2012 3:41 pm
- Location: California
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
Hey everyone, getting back into coding again after a bit of a hiatus (issues in personal life like dating, job change, etc).
Also, need to know - it’s becoming more difficult to retain different rendering paths in EDGE with regards to OpenGL, and debugging the stuff that breaks in between different paths is also very difficult to diagnose and fix.
Thinking about going to at least OpenGL 3 and being done with that stuff - however, are there any users that are still using cards that only work with GL 1.1 or GL 2? Because if not I’d like to just move forward and make GL 3.0 a requirement, but I don’t want to do it if this will make existing users unable to use the engine. Maybe I should take a poll. So if everyone can get back to me on that I’d appreciate it!
The existing ports like DC and soon-to-be-released VitaEDGE will stay on their respective paths for reasons (1.2 for DC and 2.0 for Vita).
Sorry about that, some stuff changed which broke others so I reverted back to the previous innards which fixes that stuff. I’ll upload that devbuild tonight for you.CeeJay wrote:THING commands ARMOUR_CLASS, ARMOUR_PROTECTION, etc appear to be broken. I am trying to make an armour item that protects against "missiles" (projectiles) while ignoring everything else. Something that should be 100% doable with those commands at your disposal but no matter what combination of commands I use in whatever order, it just will not work. I do remeber it working fine a while back, so I'm not sure if something happened between versions. Tested and not working with v2.1.0pre-242-gc9e8a01 and v2.1.0-RC1-93-g12c3a0307
Also, need to know - it’s becoming more difficult to retain different rendering paths in EDGE with regards to OpenGL, and debugging the stuff that breaks in between different paths is also very difficult to diagnose and fix.
Thinking about going to at least OpenGL 3 and being done with that stuff - however, are there any users that are still using cards that only work with GL 1.1 or GL 2? Because if not I’d like to just move forward and make GL 3.0 a requirement, but I don’t want to do it if this will make existing users unable to use the engine. Maybe I should take a poll. So if everyone can get back to me on that I’d appreciate it!
The existing ports like DC and soon-to-be-released VitaEDGE will stay on their respective paths for reasons (1.2 for DC and 2.0 for Vita).
-
-
- Posts: 17934
- Joined: Fri Jul 06, 2007 3:22 pm
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
There's survey code in GZDoom which you could borrow; it'd be more exhaustive than forum replies.
It was put in there for pretty much the same reason.
It was put in there for pretty much the same reason.
-
- Vintage GZDoom Developer
- Posts: 3150
- Joined: Fri Apr 23, 2004 3:51 am
- Location: Spain
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
Or just look at the results of the survey.
-
- Posts: 13793
- Joined: Tue Jan 13, 2004 1:31 pm
- Preferred Pronouns: She/Her
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
GZDoom's audience would be fairly different from EDGE's and the results of the survey would likely have significant enough differences that Coraline should run an EDGE survey.
-
- Posts: 447
- Joined: Wed Aug 15, 2012 3:41 pm
- Location: California
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
Just to be clear, we are talking about a forum survey right?Rachael wrote:GZDoom's audience would be fairly different from EDGE's and the results of the survey would likely have significant enough differences that Coraline should run an EDGE survey.
-
- Lead GZDoom+Raze Developer
- Posts: 49183
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
No, this sounds like an actual engine-side survey, like GZDoom has done last year. Which is actually the only way to get useful data.
We never explicitly tested this but some number crunching I did to evaluate the feasiblity of dropping Direct3D backend support for the software renderer yielded numbers between 0.2 and 0.3% running such old hardware. The survey showed zero legacy graphics cards from AMD or NVidia (these would have been flagged), so all these users that may still have OpenGL 1.x are on lowest end Intel chipsets that are totally worthless for running anything hardware accelerated. I don't think you'd lose anybody dropping support for this.
GL 2 still has a minor user share (GZDoom showed a bit less than 3% last year, but GL 1.x may be considered irrelevant these days, unless you really want to service the last 5 holdouts on such toaster systems.Coraline wrote: Thinking about going to at least OpenGL 3 and being done with that stuff - however, are there any users that are still using cards that only work with GL 1.1 or GL 2? Because if not I’d like to just move forward and make GL 3.0 a requirement, but I don’t want to do it if this will make existing users unable to use the engine. Maybe I should take a poll. So if everyone can get back to me on that I’d appreciate it!
We never explicitly tested this but some number crunching I did to evaluate the feasiblity of dropping Direct3D backend support for the software renderer yielded numbers between 0.2 and 0.3% running such old hardware. The survey showed zero legacy graphics cards from AMD or NVidia (these would have been flagged), so all these users that may still have OpenGL 1.x are on lowest end Intel chipsets that are totally worthless for running anything hardware accelerated. I don't think you'd lose anybody dropping support for this.
-
- Posts: 447
- Joined: Wed Aug 15, 2012 3:41 pm
- Location: California
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
I'll have to look into that - having an engine-side survey sounds pretty useful. Especially if it means I can drop all of the crazy mixed-mode OpenGL EDGE currently uses.Graf Zahl wrote:No, this sounds like an actual engine-side survey, like GZDoom has done last year. Which is actually the only way to get useful data.
GL 2 still has a minor user share (GZDoom showed a bit less than 3% last year, but GL 1.x may be considered irrelevant these days, unless you really want to service the last 5 holdouts on such toaster systems.Coraline wrote: Thinking about going to at least OpenGL 3 and being done with that stuff - however, are there any users that are still using cards that only work with GL 1.1 or GL 2? Because if not I’d like to just move forward and make GL 3.0 a requirement, but I don’t want to do it if this will make existing users unable to use the engine. Maybe I should take a poll. So if everyone can get back to me on that I’d appreciate it!
We never explicitly tested this but some number crunching I did to evaluate the feasiblity of dropping Direct3D backend support for the software renderer yielded numbers between 0.2 and 0.3% running such old hardware. The survey showed zero legacy graphics cards from AMD or NVidia (these would have been flagged), so all these users that may still have OpenGL 1.x are on lowest end Intel chipsets that are totally worthless for running anything hardware accelerated. I don't think you'd lose anybody dropping support for this.
Still experiencing framerates that dip into the high 40's, mid 50's on my AMD RX580. Curiously, any modern Intel HD IGP (even on my Surface Pro 2015 with the Iris 640 and Latitude E7450 with the HD 5500) runs EDGE at a perfect 60FPS! This has to be an ATi driver issue - I thought it might be a monitor refresh rate case, but it isn't so. My Arcade desktop (which sports a lower-end Nvidia GTX 680) runs it well above 60FPS. I have to find out if there's some sort of GL implementation that either isn't supported or has weird hacks that bogs shit down with. Tried with and without the Andrenaline drivers and even tweaked all of the settings for EDGE on the driver level. Some weird shit. . .
If anyone has a newer ATI card I humbly beg you to run EDGE, even if you don't have any intention of keeping the port and delete it 2 seconds after you are finished. When the game starts, type in 'idinfo' for the FPS counter. I’ll even take reports from GZDoom users if anyone has trouble hitting 60FPS.
At this point - I can't tell if this has anything to do with SDL2, our interpolation/vsync code, or ATI's drivers. Attempting to run it through CodeXL with my current card is a nightmare and doesn't do much good. No point in running it on my Intel IGP machines nor my nVidia as those function just fine.
@Graf, any advice?
I dropped a new build into the DRDTeam for the 64-bit version of EDGE (will drop x86 when I get the chance). This should fix your issues - if it doesn't, please let me know. Remember your x64 processor needs to support AVX or EDGE will crash (anyone know how to detect AVX? Should I use SDL_Bool and weave it into i_x86 from ZDoom)?CeeJay wrote:THING commands ARMOUR_CLASS, ARMOUR_PROTECTION, etc appear to be broken. I am trying to make an armour item that protects against "missiles" (projectiles) while ignoring everything else. Something that should be 100% doable with those commands at your disposal but no matter what combination of commands I use in whatever order, it just will not work. I do remeber it working fine a while back, so I'm not sure if something happened between versions. Tested and not working with v2.1.0pre-242-gc9e8a01 and v2.1.0-RC1-93-g12c3a0307
-
- Lead GZDoom+Raze Developer
- Posts: 49183
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
Sorry, but Sourceforge and their messed up Javascripted download interface is giving me trouble.Coraline wrote: @Graf, any advice?
I think you really should consider putting the downloads on Github instead, it's far more user friendly and doesn't try to shove ads down the downloader's throat.
-
- Posts: 447
- Joined: Wed Aug 15, 2012 3:41 pm
- Location: California
Re: EDGE 2.1.0 Discussion [RC-1 Released on 10.3.2018]
It’s uploaded to the DRDTeam.