• Advertisement
Sign in to follow this  

Free Universal Game Engine (FUGE)

This topic is 1002 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

What is this:

Hello my name is Anthony, and I just recently joined this forum. My intention is to share with you a free 2D OpenGL game engine that I made in C++. It utilizes Lua as its scripting language, and uses a similar GUI as Unity, to ease the transition. The scripting is very well documented inside the program, but currently it is in a very early version, so it doesn't have much to offer. I'd love to cooperate with game dev(s) that would provide their input to me on how to improve my game engine (make it easier, add functions etc) to reach more audience. This is certainly not meant as a competition, it is intended to be a free alternative to the expensive game engines of today. The biggest pro is that there are no obligations for commercial release of your product/game (no payment or credit required to be given to me). You can read more about it, if you're interested, on my reddit post: https://www.reddit.com/r/gamedev/comments/3e2et5/free_universal_game_engine_fuge/

FAQ is there as well

 

Links:

- Download: https://bitbucket.org/junakovic-a/free-universal-game-engine-fuge

- Facebook Fan Page: https://www.facebook.com/pages/Free-Universal-Game-Engine-FUGE/1500585353565305

 

To request functionalities, help, bug report or anything, just contact me here, or on Facebook, or anywhere. I'll be more than happy to respond.

Share this post


Link to post
Share on other sites
Advertisement

Hi.

 

It would be good to have some examples packed with distro.

 

I see there's a lot of functions that must be called to destroy native objects (font/text/etc).

It would be good to make native objects garbage-collectable. Functions that destroy large native objects might be still there, to faster release/destroy big native data allocated by that object (like texture planes, vertex buffers, etc). But it shouldn't be mandatory to call. You're making things complicate on script side.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement