[Code] Serious Engine v1.10 Open-sourced

[Rodzilla]

https://github.com/Croteam-official/Serious-Engine

[dragon99919]

[coding intensifies]

[Scratch]

Cool to finally see this come out!

[Discy]

Even more amazing than seeing the full code base of Serious Sam classic released is seeing Rodzilla post. What up?

[SLAwww]

A prophecy said he'd wake up on a day when sources are released.

[Discy]

I must've missed that particular passage.

I have a question, though. The latest patch release for TFE is 1.05 and TSE is 1.07. What's different in 1.10?

[dragon99919]

Originally Posted by Discy

I must've missed that particular passage.

I have a question, though. The latest patch release for TFE is 1.05 and TSE is 1.07. What's different in 1.10?

I think these are SLAwww's additions and fixes for SS:C on Steam (his username is present on github of the project).

[Discy]

If that's true, to what extent have SLAwww's additions been pushed? The OpenAL API he added is still very much beta at this point.

[dragon99919]

Idk, we have stuff like better resolutions, gameserver master and stuff like that. Also, it's github, code still can be updated. I actually just hope it works with modern versions of Visual Studio now, cause setting up the enviroment for the mods code back then was a real pain for me.

[Targ3t]

First Entroper now Rodzilla posted. Amazing!

[Scratch]

I actually made the base of this repo back in late 2012, and I also released the binaries for this 1.10 version a while ago. It's 1.07, with some changes in it to make it suitable for modern compilers, some old deprecated things removed (Gamespy, CD checks, etc), and some minor modernization in the engine itself

And before you ask - no, 1.10 is not network-compatible with 1.07 (nor Revolution).

[Gnaarwarian]

Good Job.

Imagine now what happened if somebody released Test 1 & Test 2 combined with this.

[SLAwww]

Originally Posted by Discy

The latest patch release for TFE is 1.05 and TSE is 1.07. What's different in 1.10?

There are several differences. The 64-bit problem is fixed on engine level, gamespy is replaced with custom master server code, several copyrighted parts had to be cut off (such as Exploration3D). 1.10 is very similar to 1.07, you can play 1.07 and 1.05 maps in it, but not mods (they need to be recompiled to be playable). Several improvements of the Steam version (such as display resolutions and OpenAL) are not included in 1.10. Unfortunately these improvements were made in a very kludgy fashion because I could not modify the engine library. But they can be added to 1.10 eventually, I guess. In fact, it will be much easier to add them, then it was with Steam SS1.

[dragon99919]

Cannot open include file: 'Engine/Classes/BaseEvents.h'

Either pure basic Visual Studio 2015 cannot simply compile it, or I'm probably really stupid and still need a tutorial how to set things up to make compilation possible. :v

[SLAwww]

You need either Visual Studio Professional or Visual Studio Community. The file BaseEvents.h is generated by compiling the file BaseEvents.es. You may try to manually compile it (RMB on file -> Compile). If this operation runs without errors, BaseEvents.h will be generated by ECC.

[dragon99919]

I do have Visual Studio Community, or at least... I think so... It's called Visual Studio Community 2015.



//edit

Hmm, that's strange.

I tried to build the EnitiesMP alone, and it seems that 'ecc' in console is not recognized as a command or program by my cmd. :v

This might be cause I use Windows 7 Home Premium, instead of let's say Professional or Ultimate?

[SLAwww]

Did you build the ECC first? Show me the log.

[dragon99919]

I tried to even build it alone and then...

1>------ Build started: Project: Ecc, Configuration: Debug Win32 ------
1>  Creating parser source
1>  ecc/parser.y contains 86 shift/reduce conflicts and 1 reduce/reduce conflict.
1>  Cannot find specified file.
1>  Cannot find specified directory.
1>  Creating scanner source
1>  flex: can't open Stuff\Serious-Engine-master\Sources\Ecc\\Scanner.cpp
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 1.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

//edit

While this is really funny, cause when I tried to compile all files from the source folder one-by-one - they do compile without any errors.

[Scratch]

You don't have bison, make sure those are in the tools folder

Edit: Or rather, let's make a more helpful post, you have to make sure that VS can find the bison and flex executables, check the ecc project properties executable paths if the Tools.Win32 folder is included

[SLAwww]

"Stuff\Serious-Engine-master\Sources\Ecc\\Scanner.cpp" is not a proper path. Press RMB on Scanner.l file, go to Custom build tab, then Command line -> <edit> -> Macros. Make sure your %(Root) and %(Directory) macros have proper values. %(Root) should have a drive letter with semicolon and a backslash, %(Directory) should contain a path to ECC project folder.

you have to make sure that VS can find the bison and flex executables

VS does find these, otherwise it would complain that "bison is not a command or program name".

[dragon99919]

//Scratch



Yep, they are there... I even copied them to System32 so whole CMD should see it anytime, anywhere, still getting exactly same error that you can see on my post above.

//SLAwww



As you can see I changed the macros, the file is placed there, and the compiler still cannot see it...

[SLAwww]

Spaces in the path are your problem. Remove them, and keep path as short as possible.

[dragon99919]

Originally Posted by Scratch

You don't have bison, make sure those are in the tools folder

Edit: Or rather, let's make a more helpful post, you have to make sure that VS can find the bison and flex executables, check the ecc project properties executable paths if the Tools.Win32 folder is included

Originally Posted by SLAwww

Spaces in the path are your problem. Remove them, and keep path as short as possible.

Yea, it works now, but another problem appears. xD

Now each time ECC works on .es files, it simply says that it "Stopped Working". Not really helpful polish error screenshot:



I would think that maybe someting went wrong with it's compilation, but first few files went just fine.

//edit

It seems it fails on BaseEvents.es, so I was wrong - it might be something with Ecc...

[SLAwww]

This is because your path is too long. Paths longer than 31 characters can cause such problems.

[dragon99919]

Okay, it works now!

Thanks, and sorry for being stupid!

//edit




Being proud cause that's probably the first thing I have ever coded. ;-;

[Zeo]

Glad to see this happening, finally !

[God Of Gaming]

It's great that the engine is finally out, I'm not sure what use can I make out of it though, I've pretty much moved all my focus to unreal engine 4... Guess I could try to make a source port for TFE/TSE, can't promise anything though, since I have no experience with engine programming...

[DamianTV]

Originally Posted by Target-UPnP

First Entroper now Rodzilla posted. Amazing!

Entroper and Rod arent the only ones that will crawl out of the wood work for this...

---

I probably would have been a bit mroe active if I could ever have gotten SS Classic to run on Win 7-64bit+...

Whats up y'all?

[PikaCommando]

What happened to the bumpmapping? Someone searched for it in the code but all traces are removed. Why hasn't it been fixed/added back?

[Discy]

Originally Posted by DamianTV

Entroper and Rod arent the only ones that will crawl out of the wood work for this...

---

I probably would have been a bit mroe active if I could ever have gotten SS Classic to run on Win 7-64bit+...

Whats up y'all?

Hey Damian, it's been too long. How is your life going?

Also, the classic Sam games have always worked on Windows 7 64 bit for me, not sure why it doesn't for you. The classic tools on the other hand haven't, but there have been fixes for that for a while.