I'm a whore so I'm posting this here too.

http://www.youtube.com/watch?v=Ge2GWnhGA_M

I generally upload videos to my youtube account with major revisions. I'm posting updates constantly in this thread. Read through that if you want.
http://www.modacity.net/forums/showthread.php?25132-I-bring-thee-not-simple-rearrangements-but-a-whole-new-world-of-possibilities&p=646432#post646432
Engine is java + opengl + lwjgl based.

Going to get drunk now.


Edited by Not Inferno on Jun 1, 2013 at 10:35 AM

So, you're working on a new engine?

your one error is using java. other than that, you should adjust the lighting; areas in shadow do not get that dark.

nvm,
Edited by OrangeJuice on Jun 1, 2013 at 01:23 PM

I was gonna say some things about java's many bottlenecks, but I haven't used java 7 yet...
Edited by OrangeJuice on Jun 1, 2013 at 01:28 PM

If he hands out this only for smart people.. Then you are in trouble..

I'm gay IRL so it's k.

Also, BR BR BR HUE HUE HUE MORDEKAISER ES NUMERO UNO

I have an XDK, nobody ever comes after me

EDIT>v They're all over the "What's your Halo CE battle station" topic v<
EDIT>v And nobody will come after you, Devon. People post themselves using XDKs all over Scenyx, even Alpha hardware versions. v<

EDIT>v No, no no! A tiny net is a death sentence. v<

EDIT>v ...... v<
Edited by OrangeJuice on Jun 1, 2013 at 02:11 PM

I wonder what ever happened to JWOW's custom engine

In that case, learn to read before say anything..

*ignores stupid trolls*

...so you're making your own new game, but you can import Halo assets into it?
What can you import, exactly? MAP files? Tags? Shaders? or...?

Can't wait to give it a try

^ He's just building an engine, not a game apparently.

Anyway, this looks awesome. I just hope it doesn't get cancelled like a lot of open-source engines have been.

Yes, it will scare the ignorant away.

Good riddance, I say.

1. No, it really isn't. Artstyle's slightly worse.
2. Gameplay's... meh.
3. HEK is... seriously meh.
4. It's only on Vista.

about the possibility of a new engine:
i personally would love to see a more efficient, and better graphically inclined engine.
i would love support for common programming languages, especially how common java is.
i would love to see the possibility of new lighting and shaders, especially cryengine quality (doubtful).
i'd love to see more efficient rendering and data usage, especially removing the low map compiling size limit.
and for anybody who is too dumb to switch engines, or is worried it would split the players, stupid people will always be stupid, and just use the "only use it for SP" bullshut excuse people use for Open Sauce.

I'd like to point out the engine will be open source.

Also, my engine already has client side hit detection and projectile simulation. I also have spread synchronization and modular actor property simulation implemented. (in simple terms, all objects in the game sync in MP). And I have script synchronization planned for a later date.

Making maps is easy and the lighting model is dynamic so no radiosity, this also allows for fluid day night cycles. Post processing can be applied by layer (IE you can apply HDR or bloom or whatever you want and it will only affect the game world not the HUD)

Also the engine will be on a large scale of graphical qualities, the minimum setting being a netbook compatibility mode with basically just simple diffuse rendering.

In reference to your reply to my comment requesting documentation on scripting. I was wondering if you were going to go into extreme detail about the scripts and their functions, as well as the engines limitations. I have some more questions too.

Are you planning on making 12D like HEK? If so, are you going to:
- Allow for 44100hz weapon sounds?
- Stereo sounds?
- A less fussy compilation tool?
- Keep the sapien/graphical editor fly cam the same as it is?*
- Live updates when you modify shaders in guerilla/meta editor?
- Allow for more than just .jms imports?

If not, would you be able to take these ideas into consideration for meta/graphical editors
- Everything I mentioned above.

* If keeping the original sapien flycam with the WASDRF controls isn't what you have in mind, can you make it a switch between for people who do prefer the WASDRF? It's my personal preference, and maybe a lot of others have the same preference.

Personally I would love to be able to instantly spawn in the level to test things in sapien.

Here's some of the stuff in the engine

-Simple BSP importing
-BSP is imported with .obj and a collision mesh can be the same model
-Dynamic lighting, so there is no 50hr radiosity
-Working physics engine
-Optimized garbage collection
-UV animations

Really cool man and it's great to see you back in town.

This account is new but this guy is not.

Better known as DMT Inferno

Or the guy who made snowtrap.

Yeah I'm the guy that did all the scripting and tagging for Yoyorast Island 2 and I made a few other maps and what not.



- Sound uses flac. (Thank flibit for that)
- Stereo, yes.
- Compilation is done on runtime. Longer loads and file sizes but easier development and the ability to download files needed for mods :P. Also allows a server to rearrange weapon spawns (like forge). IE the game only uses tags and source files, it doesn't need a map cache.
- Shader editing is currently done in a text file but I will have a visual editor later.
- Engine uses 2 formats for models. OBJ for static meshes, TBJ for skeletal meshes. TAF is for animations. TBJ and TAF are my own formats I created and I have an exporter for 3dsmax. I will provide specifications for people to create exporters for other programs if they want.

On my rig (i7-920) deathisland loads in about 2-3 seconds. With all the weapons models and animations for Halo, maybe 9 - 10 seconds. On a lower end rig maybe 20 seconds tops. Of course I've still got lots of optimization to do. My code is filled with //TODO: FIX THIS OPTIMIZE THIS

:P

Shader math is pretty simple. It's about as flexible as Unreal Engine 3 shaders. Though I don't have support for cubemaps yet. Not sure if I will or not.

12D Client / Server comes to a total of nearly 15,000 lines so it's a lot of stuff to work through.
Edited by Not Inferno on Jun 4, 2013 at 06:43 PM
Edited by Not Inferno on Jun 4, 2013 at 06:45 PM

Standard specular reflections. You can also color the specular map if you want to use an RGB texture for it :P I tend to stick with using the alpha channel of the diffuse texture as specular.
Edited by Not Inferno on Jun 4, 2013 at 06:49 PM

I am really excited for this engine now. Is it being designed around the original Halo limitations with more being allowed? Or is it completely custom and tailored to allow Halo-ish effects to take place?

I'm well aware. I want to know if he's designing it specifically for Halo content or other game content as well.

What I'm referring to is he going to take ideas from other game engines as well. Such as the Biotics and stories tailored to who you are in the Mass Effect series. Or even the giant, fun as hell sandbox environments like GTA.

These engines were tailored to support the developers wants for the games. I know what I'm talking about here; the developers modify the source code of the engine to suit it to their liking. Hence why I'm thinking of the different games.

Ui tag format and renderer is slowly taking shape. Just need to start writing console commands since the buttons on Ui will simply send console commands to change setting, join servers, load maps, send chat messages, and etc.

http://inferno.codebrainshideout.net/Images/dat%20ui.png

Do you want to get Mangenkyos help for the UI? Or someone else? Mainly because the UI at the moment isn't amazing; unless it's supposed to look like a 2 minute job.

It is a 2 minute job.

What I'm demonstrating is that the code is there to make it work. I'll make it pretty later.

Good :) I can't wait to see this looking pretty. Good luck mate!