Page 2058 of 2906 FirstFirst ... 2053205620572058205920602063 ... LastLast
Results 30,856 to 30,870 of 43577

Click here to go to the first staff post in this thread.
Thread: The Star Citizen Thread v5

  1. #30856
    I'm an amateur here, so take everything with a pinch of salt.

    CE is not one large drill like the one they used for the channel tunnel. It is a tradesman's bag full of tools like a hammer, a hand drill, a micrometer, a chisel, several screwdrivers and spanners, etc

    So if CE 3.7 had all these tools and CiG changed the micrometer and the chisel but left the rest... And LY took the 3.7 toolbag and have left it more or less alone but added some Whitworth sockets and a pair of snipe nosed pliers...

    The upshot is that most of the toolbag is still the same, with a couple of additions from both sides that they need to check for interoperability?

    I think it is getting fractious in here because everyone (I'll admit it was my thought), has been getting hung up on the old "50% modified" quote from Brian C?

    Something largely based on CE 3.7 being flipped to work with something else largely based on CE 3.7 is nowhere near the pain of going from CE 3.7 to Unreal 4?

    Just trying to calm the waters a little, although I do reserve the right to be wrong!

  2. #30857
    So Ben, you are telling me that the whole 50% CE changes to make "star engine" was ? So now Star engine is just a simple mod that can be copy pasted on any version of cry engine, whether it has modifications of its own or not ?
    If this is the case, did it really took 2 years for CIG to be able to make just a simple engine mod ?

    all the money spent on just a mod ?

  3. #30858
    Originally Posted by Hi-Ban View Post (Source)
    They are still running StarEngine. Didn't you read Ben's post from some days ago? He wrote a very easy to understand buffet analogy. I assume you missed that post.
    Still a lot easier than switching from, lets say, Havok to UE4.
    You ppl. are really something you know that.......and I figure that itīs pointless to have reasonable conversation with "you" any more.....the CULT is simply that the CULT and itīs making me sick how deep you people are ready to go into the brainwashing and butkissing from anything that comes out from CIG.....

  4. #30859
    Originally Posted by 1500 View Post (Source)
    So we are back to CIG only changing for the network code that can't be used to make the MMO and will have to be made by CIG anyway.
    Amazon Game Studios is developing a MMO using the Lumberyard engine. It's called "New World".
    Just sayin'...

    Originally Posted by Zyll Goliath View Post (Source)
    You ppl. are really something you know that.......and I figure that itīs pointless to have reasonable conversation with "you" any more.....the CULT is simply that the CULT and itīs making me sick how deep you people are ready to go into the brainwashing and butkissing from anything that comes out from CIG.....
    Dude chill out, i just directed you to a post in which Ben explains it in an easy to understand way.

  5. #30860
    Originally Posted by Remus View Post (Source)
    So Ben, you are telling me that the whole 50% CE changes to make "star engine" was ? So now Star engine is just a simple mod that can be copy pasted on any version of cry engine, whether it has modifications of its own or not ?
    If this is the case, did it really took 2 years for CIG to be able to make just a simple engine mod ?

    all the money spent on just a mod ?
    This makes all the talk about reworks even worse as it suggests that a ton of time has been burned on assets rather than a functioning game.

  6. #30861
    Originally Posted by 1500 View Post (Source)
    So you are saying that Starengine didn't diverge from Cryengine.
    No. Good god, man, no.

    StarEngine diverged from CryEngine at 3.7
    LY and CE diverged from one another at 3.8
    So, because 3.7 is less that 3.8, StarEngine's changes are as compatible with CryEngine as they are with Lumberyard.

    If they'd diverged at 3.7, and StarEngine was based on 3.8, then StarEngine would be based on code that wasn't the same, and there'd be problems.

    If you stay with CE, or you switch to LY, taking later updates takes work because of StarEngine's differences. Which is why my quote from yesteryear about not just doing big merges.

  7. #30862
    Originally Posted by Hi-Ban View Post (Source)
    Amazon Game Studios is developing a MMO using the Lumberyard engine. It's called "New World".
    Just sayin'...



    Dude chill out, i just directed you to a post in which Ben explains it in an easy to understand way.
    Ohh I am chill no worries....I also directed you here:https://forums.robertsspaceindustrie...game-engine/p1 and ask you what changed your mind after a year but you dodge that bullet and play on "stooge"card instead....

  8. #30863
    Originally Posted by Hi-Ban View Post (Source)
    Amazon Game Studios is developing a MMO using the Lumberyard engine. It's called "New World".
    Just sayin'....
    I try to avoid feeling like I'm playing the man and not the ball... New World is, by the looks of the advert on the Amazon page:

    "About the Product
    New World is a massively multiplayer, open-ended sandbox game that allows you to carve your own destiny with other players in a living, hostile, cursed land.
    How you play, what you do, and whom you work with or against is up to you.
    Live on your own amidst the supernatural terrors or join with others to build thriving civilizations.
    In this evolving world that transforms with the changing of the seasons, weather, and time of day, the only limit is your own ambition.
    When you register, you will become a New World Insider and receive news updates. The release date and pricing for New World have not been set.

    Actually, with the bolded emphasis mine, I am beginning to see why a supporter of SC would think New World is an interesting product. The whole "We haven't got any gameplay specifics nailed down yet and we are pre-alpha, but trust us it will be great" is resonant.

  9. #30864
    Originally Posted by Tuub t Tute View Post (Source)
    I'm an amateur here, so take everything with a pinch of salt.

    CE is not one large drill like the one they used for the channel tunnel. It is a tradesman's bag full of tools like a hammer, a hand drill, a micrometer, a chisel, several screwdrivers and spanners, etc

    So if CE 3.7 had all these tools and CiG changed the micrometer and the chisel but left the rest... And LY took the 3.7 toolbag and have left it more or less alone but added some Whitworth sockets and a pair of snipe nosed pliers...

    The upshot is that most of the toolbag is still the same, with a couple of additions from both sides that they need to check for interoperability?

    I think it is getting fractious in here because everyone (I'll admit it was my thought), has been getting hung up on the old "50% modified" quote from Brian C?

    Something largely based on CE 3.7 being flipped to work with something else largely based on CE 3.7 is nowhere near the pain of going from CE 3.7 to Unreal 4?

    Just trying to calm the waters a little, although I do reserve the right to be wrong!
    Pretty much this. LY is a changed CE, and from a functional point of view there are 3 types of changes:
    Functions added
    Functions taken away
    Functions doing something different

    Functions added isn't a problem: they maybe something you can use later (Like non-pants networking) but they not going to break something just by existing.
    Functions taken away might be a problem, but it's generally not something you do unless you are really sure you don't need it: Maybe CE supports Pentium II processors and LY doesn't, that sort of thing. What I'd expect is they would go through and optimise when they're getting closer to release (whenever that is).
    Functions doing something different would be a problem, but as I've said before they would have to be morons to do that because it gives LY a steeper learning curve for existing CE developers, which defeats the point of the exercise. And Amazon don't appear to be morons.

    So, it's not really a problem.

    What we probably do have is some duplication, with SC using CIGs pants netcode when there's much better code sitting unused in LY, but that doesn't hold up switching to LY: It just means they've wasted time and money (nothing new there then) but will have an easier job in the future.

    SC has a lulzbucket full of problems, but LY isn't one of them.

  10. #30865
    Originally Posted by Remus View Post (Source)
    So Ben, you are telling me that the whole 50% CE changes to make "star engine" was ? So now Star engine is just a simple mod that can be copy pasted on any version of cry engine, whether it has modifications of its own or not ?
    If this is the case, did it really took 2 years for CIG to be able to make just a simple engine mod ?

    all the money spent on just a mod ?
    Any codebase can be expressed as a set of differences from another one. It's what gets put in patches, it's what gets stored in version control systems.
    All of CIGs changes relative to CE 3.7 can be wrapped up like that, even though there's a lot of them.
    You can apply those changes to anything else that has identical code to CE 3.7.
    Since LY did not make any changes until 3.8, you can apply the changes to pre-3.8 Lumberyard. Note that I don't know what Amazon will actually do with the version numbers, but there'll be a point in their versioning system that lines up with CE 3.8.

  11. #30866
    Originally Posted by Zyll Goliath View Post (Source)
    Ohh I am chill no worries....I also directed you here:https://forums.robertsspaceindustrie...game-engine/p1 and ask you what changed your mind after a year but you dodge that bullet and play on "stooge"card instead....
    Honestly, i missed that thread.

  12. #30867
    Soooooooooooooooooooooo...does this mean the game comes sooner?

  13. #30868
    Originally Posted by Ben Parry View Post (Source)
    No. Good god, man, no.

    StarEngine diverged from CryEngine at 3.7
    LY and CE diverged from one another at 3.8
    So, because 3.7 is less that 3.8, StarEngine's changes are as compatible with CryEngine as they are with Lumberyard. But, you just said doing this would be a ton of trouble and a ton of work ?

    If they'd diverged at 3.7, and StarEngine was based on 3.8, then StarEngine would be based on code that wasn't the same, and there'd be problems.
    LY 3.8> Starengine 3.7, as you said different codes means a lot of problems. But somehow this doesn't apply to LY because ?

    If you stay with CE, or you switch to LY, taking later updates takes work because of StarEngine's differences. LY is an update by deffinition since it is an upgrade from CE 3.7Which is why my quote from yesteryear about not just doing big merges. this last sentence makes no sence in my eyes, someone care to translate ?
    I'm even more confused.

    - - - Updated - - -

    Originally Posted by Ben Parry View Post (Source)
    Any codebase can be expressed as a set of differences from another one. It's what gets put in patches, it's what gets stored in version control systems.
    All of CIGs changes relative to CE 3.7 can be wrapped up like that, even though there's a lot of them.
    You can apply those changes to anything else that has identical code to CE 3.7.
    Since LY did not make any changes until 3.8, you can apply the changes to pre-3.8 Lumberyardexcept there is NO pre 3.8 for Lumberyard, as per their site LY is a fork of CE 3.8.1 and nothing before that. Note that I don't know what Amazon will actually do with the version numbers, but there'll be a point in their versioning system that lines up with CE 3.8.

    I'm starting to believe that you don't know Lumberyard Ben.

  14. #30869
    Originally Posted by Ben Parry View Post (Source)
    No. Good god, man, no.

    StarEngine diverged from CryEngine at 3.7
    LY and CE diverged from one another at 3.8
    So, because 3.7 is less that 3.8, StarEngine's changes are as compatible with CryEngine as they are with Lumberyard.

    If they'd diverged at 3.7, and StarEngine was based on 3.8, then StarEngine would be based on code that wasn't the same, and there'd be problems.

    If you stay with CE, or you switch to LY, taking later updates takes work because of StarEngine's differences. Which is why my quote from yesteryear about not just doing big merges.
    So CIG just went "ctrl C" from Cryengine 3.7 and then "ctrl V" into Lumberyard 3.7 (legacy support in Lumberyard 3.8) bringing over all the Starengine features. If CIG want any of the Lumberyard 3.8 features that will be extra work.

    Am I understanding that right?

  15. #30870
    Originally Posted by Remus View Post (Source)
    I'm even more confused.

    - - - Updated - - -




    I'm starting to believe that you don't know Lumberyard Ben.
    Basically, 3.7 + (Monkeys pounding on keyboards) = old StarEngine
    3.7 + (3.8 stuff from Crytek) + (stuff from Amazon) = Lumberyard, so
    3.7 + (3.8 stuff from Crytek) + (stuff from Amazon) + (Monkeys pounding on keyboards) = new StarEngine.
    the (3.8 stuff from Crytek) and the (stuff from Amazon) might not be used, but I doubt they break anything.