Cry engine 2 -> cry Engine 3 possible switch

[strook]

 

so guys you could call me game guru

as the cry engines are compatible, we could rewrite the cryengine 1 interface headers as layer between the mod and cryengine 3.
then you'll have got an cry engine 3 game, you need just to implement all the new features.

and, at least we would get rid of the installation and crysis game key problem.

what do you think about it?

this could be my christmas present for ya if you let me work on it.

note i have already made a opengl engine with the ogre engine work together, and worked aon a project working with the irrlicht engine and the ogre engine.

gluing engines would nothing new to me also.


cheers

[ELH_KillThemALL]

None. © KingLeerUK

[strook]

hmmmm i think the engine is missing.

the cry engine 3 sdk is also an mod engine developmet kit unlike i was told.

so you modified the GameDll folder...

i think the headers will be mostly compatible, there too.

so we could write an compatibility layer, and use the .cpp files for the sdk3 headers, to get it run on cry engine 3.

what do you think about that?

game would fall back to an alpha version, then, but i think we could get a real player base as we would engage the problem converting to cryengine3, and we woud maybe get rid of the key problem, if that no more exists on cry engine 3.

after that we could replace or rewrite the contents of the cpp files to match the cryengine3 ones. i think it would be mostly a copy&paste.

[=CJW= Bin Fish]

As it was explained before it would not be a cut and paste job.

Lots of the underlying textures etc are from the native crysis games.

A shift to engine3 would mean making these from scratch and then a full alpha rebuild.

No one wants this.

[strook]

if that is the problem... just include the crysis stuff into the mod to ensure compatibility.

there could be just an file search tag be made to look into the backwards compatible dirs if some stuff isn't found.

it has never been easy to shift up, i think the community wants it.

[=CJW= Bin Fish]

Then I would suggest you go make this post in the 'join the team' section and get in contact with the dev's directly.

Would get you some feedback much quicker.

[strook]

it's already on the way... got integer on skype and starting a discussion about it

[(TLL)CapperDeluxe]

minor corrections first: Cryengine 1 is FarCry, Cryengine 2 is Crysis Wars

Such a switch was briefly talked about months ago with the response being somewhere around the lines of: not anytime soon because to do so would mean a very long period of not having new features.

[KingLeerUK]

Beyond the large technical hurdles involved in such a switch there are other non-technical considerations that weigh heavily over things.

[strook]

well i am not part of a dev team yet and would like to do it.
you can leave me apart by doing this until it's done.

i had a chat with sesambrot and he said that we must get the bug with the serial number away if we want to have
a bigger community on long term.

this could maybe only happen with cryengine 3.

so as this is anyway a free commmunity project, get me involved and i'll try whatever i can to convert this to make it
cryengine 3 compatible.

we could have a hybrid version maybe that loads the old dll (cryengine 2) if it detects crysis wars, and the new dll if it detects
crysis 3.

i am sure we find a solution.

[Sesambrot]

I'd appreciate it, if you didn't put words in my mouth, I never said that!
What I did say is that this serial-issue has been around for a very long time now, and while we all understand how painfully annoying it is, we can't do anything to fix it, and that we might not have the issue if we ported the game to ce3.
Anyways, I also told you that in order to properly port this mod to ce3 we would probably need a second dev-team that focused solely on doing that properly, or we'd have to halt beta-development for a couple of months or even years in order to convert everything we need.

The kind of patchjob you keep suggesting doesn't sound all that great to me, but in any case, moving to a different engine also requires extensive testing of each and every little feature of the game, to see if something broke in the process.
I'm not a coder, but as far as I understand it we rely not only on the assets that come with Crysis Wars but also on the engine code of which we don't know yet if it is in ce3 also. On top of that I'm pretty sure we wouldn't be allowed to just copy 'n' paste every asset/texture we use, over to ce3...

[strook]

I'd appreciate it, if you didn't put words in my mouth, I never said that!
What I did say is that this serial-issue has been around for a very long time now, and while we all understand how painfully annoying it is, we can't do anything to fix it, and that we might not have the issue if we ported the game to ce3.

well, i'm not sure about that, right now i have read that there is an engine sdk and an mod sdk for 3...
i have to inform me a bit more. but nevermind, do you know "teekesselchen"? that is if someone says something it 'll be modified by everyone who hears it , and if there is a chain of herarers which tell it to each other, something quite strange comes out. in other words nevermind

Anyways, I also told you that in order to properly port this mod to ce3 we would probably need a second dev-team that focused solely on doing that properly, or we'd have to halt beta-development for a couple of months or even years in order to convert everything we need.

ya i'll do my best to attract mod developers. i have some contacts, maybe (if they'll find the time...).

The kind of patchjob you keep suggesting doesn't sound all that great to me, but in any case, moving to a different engine also requires extensive testing of each and every little feature of the game, to see if something broke in the process.
I'm not a coder, but as far as I understand it we rely not only on the assets that come with Crysis Wars but also on the engine code of which we don't know yet if it is in ce3 also.

see below, but i think, again, too we need to update if we want prevent that the the project dies. i don't suppose that the update process won't be a easy thing, but i think we have to engage it now.

On top of that I'm pretty sure we wouldn't be allowed to just copy 'n' paste every asset/texture we use, over to ce3...

ya i think that's the main problem.
as i usually was developing for open source, we used usually the GPL or compatible licenses.
i think we could leave it to the player like this we continue cryengine 2 support in parralel as i update my
files to the newest version. If i have any usuable output, we continue support for both engines.
this preceeds FOR US that the player must have a registered crysis wars version have installed, also it lets us use temporarily, as long as we need the old assets and they aren't replaced by new ones, them. if the player decides to go not using the crysis wars key and is using the not free assets without buying the key, it will be then not up to us. the only thing we need to do, is to tell the player that he needs the key. what he makes from it is up to him, and we are out. of course to get rid of the key, we had to replace all the assets sometime... 

[strook]

hmmm i think to be shure we should ask for the key untill we replaced all the content when starting the cryengine 3 part of the game.

[Mitchpate]

It has nothing to do with actual keys as much as it does the licensing associated with the games themselves.  You can't just copy-paste assets from one game into another, it creates all sorts of copyright issues.  Not to mention size issues as the mod would require several GB worth of textures that the core game wouldn't have.

For this to be done it would have to be done right.  I won't pretend to speak for the MWLL team but I'm pretty sure if/when they do this they want it done properly.  No offense, but it sounds like you want to jackleg the conversion and I'm pretty sure they don't want to do that.

[strook]

mitchpate: read properly, then retype.