I would love to see this engine go open source, community could expand it. I have seen so many projects thrive while going open source. The engine is "undead" as I read from another user, it would be great to boost some life back into this thing.

I am bouncing between GS3D, Godot, and Shiva3D. I prefer coding in GS3D, but see no point in starting a project that I will be at for years to have a ancient engine to finish it on. The experienced gained would be priceless of course. Although the experience could be gained in something else and still be applied in something current.

I know, I know use something else then. I am not insulting the engine, I quite enjoy it. I have been following GS3D for a few years now and am wondering why not either a) Actively develop it b) Open source it so it can live forever.

I am afraid if it takes too long, anyone who cares will be gone and if/when it gets open sourced or developed no one will give a hoot.

Maybe this should have been under Rants...? It is applicable to the future of the dieing engine.

It is not possible to release the full engine open source as it still contains code not originated by opGroup.
Those parts must be rewritten by someone

Well if there is a will, there is most definitely a way.

I completely understand what you are saying, and I am sure lot's of people would oblige, if open sourcing was an option.

Even stone aged A3 cannot be made open source pretty much due to the same reasons.

I bet you guys would love to get your hands on wed and med source , to dissect and evolve in to something better.

pity.

Maybe I should learn how to make plugins for SED/MED/WED...? Added functionality, I don't know enough about it all to know where that will lead, or what could be accomplished. My cousin and I have decided to use GS3D, for the simple reason of ease of use and a wealth of information, and hopefully when the time comes, experienced forum members still around to pick their brains.

I would love to be able to add custom functionality to MED and WED (and I'd share the results) but I don't understand how to build the stuff from the SDK with Visual Studio Community (2015).
If anyone could figure this out or jcl maybe even give a small tut/ instruction this would be amazing!

+1 ^^^^^

Yeah let's kick start this!!

Do not kickstart a product 'all but abandoned' by it's developers. I see you are new and haven't dealt with the apathy for the dev's, we have over these last few years. There are amazing start-up engine and great established engine your kickstart could help. LBGUI became the reason for the dev's to cancel the GUI expansion GED another third-party's work. Dev's probably won't pay for Savin's map editor would it be our new GED. <-- Pure assumption!
C# wrapper <- Us!
New physic <- Us!
New GUI <- Us!
Lite-C functions and explanations <- Us
Multiplayer tutorial <- One of Us and Georges kind pocket
More and more <- US

2 or 3 years of a update with bug fixes <- Dev's
My request for force joystick check 2 years+ to be added <- Dev's
and on and on

Mal

Yeah sorry I didn't mean that in the sense of a "kickstarter" project. You are 100% right I am new and yes, as far as this engine goes my spirit hasn't been crushed yet.

It's the exact reason I see so much community involvement and so much contributions (I have looked through many a AUM), that I believe some part of this engine should be open sourced or eliminate proprietary stuff and get it in the hands of the passionate people who could do something with it.

It's one thing to see a product go down hill and have no community to fall back on, but that is not the case here, you guys ROCK!! They have an oppurtunity to make this engine viable again...not "just a learning tool".