Slashdot Mirror


Too Human No Longer an Unreal 3 Title?

1up is reporting that Silicon Knights, makers of Eternal Darkness and the upcoming Too Human, may have decided to drop the Unreal 3 Engine from Too Human. The company is reportedly having big problems getting Epic's powerful product to work well with their title on the 360. The plan is now that they will be crafting their own rendering systems for use with the game.

17 of 50 comments (clear)

  1. Industry rumer is by rsilvergun · · Score: 4, Funny

    they're switching to the DNF engine.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  2. Woah by bcat24 · · Score: 3, Funny

    That's just unreal! No, wait, it's not Unreal anymore! That's unreal! Aaahh, I'm so confused!

    1. Re:Woah by andrewman327 · · Score: 2, Funny

      Come on now, I'm sure most /.ers have studyed De Morgans Laws. !(!real) == real. This story is real!

      --
      Information wants a fueled airplane waiting at the hangar and no one gets hurt.
    2. Re:Woah by bradkittenbrink · · Score: 3, Funny

      Wouldn't DeMorgan's laws imply something more like !(Un && real) => !Un || !real. Since I agree with you that the story is real, I guess this means that it must be !Un.

      umm, yeah...

    3. Re:Woah by andrewman327 · · Score: 2, Funny

      In GP I established that Un = !. Therefore your assertion that the story is !Un&&real means that it is real and it is not false. Although I thought that || was or and that only xor implies mutual exclusivity.

      --
      Information wants a fueled airplane waiting at the hangar and no one gets hurt.
    4. Re:Woah by bradkittenbrink · · Score: 2, Funny

      My point was that DeMorgan's laws don't apply to constructions like !real, only to conjunctions or disjunctions. The rest of my post was facetious. In fact, all of my post was facetious.

  3. I don't understand... by __aaclcg7560 · · Score: 2, Funny

    Is the Unreal 3 engine too UNREAListic to be too human?

  4. PlayStation - GameCube - X360 - ? by CaseyB · · Score: 4, Funny

    They've already blamed the platform for the failure to complete this title more than once.

    It's like that old saying: Give up on one platform, shame on the platform.

    Give up on 3 platforms ... give up ... Can't give up again!

  5. NDH Syndrome by RingDev · · Score: 4, Insightful

    Not Designed Here syndrome. It can usually be averted by reviewing investments in 3rd party solutions, acquiring new 3rd party solutions, or by planning from the start to use an in house solution.

    At this point, it will likely mean project failure. The organization's core capability is making games, not game engines. Not only is there the huge scope of creating the engine, testing, debugging, and optimizing, but there is the legal liability in it also. If their engine designers have been staring at Unreal3 engine code for the last 6 months, and now decide to create their own engine, what is the likelihood that they will borrow either code or concepts from the Unreal engine? That could turn around and bite them hard in a trade secrets and copy right lawsuit.

    -Rick

    --
    "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
    1. Re:NDH Syndrome by MindStalker · · Score: 4, Insightful

      Exactly, I think they'd be better off obtaining permission to highly modify the UnReal engine. No reason to completly scrap usable code you've already licensed.

  6. Drop an engine and write own renderer. by El_Muerte_TDS · · Score: 3, Informative

    Then what about the rest of the engine. A game engine is more than just whatever you put on the screen. If you drop a complete engine you'll also have to implement the rest. Switching an engine is a bad idea when you already did a lot for the game. Dropping an engine and rolling your own is just plain stupid.

  7. Here's a Stat I'd like to know by Kardall · · Score: 4, Interesting
    From people in the industry using UE3, how many of you have had problems developing it for each console? What were the problems experienced? How did you overcome them or did you?

    If a company like Silicon Knights has issues with something, and decides near the end of their products pre-release lifespan, to scrap the backbone of the game and redo it, then there has to be either something very wrong with the Engine, or the platform.

    It's not a light decision. That will set a game back by a huge amount of time, probably inconceivable at this point, because doing their own renderer will take time in and of itself. Then they'll have to adapt everything that they've done to it. Perhaps, they'll just take parts of the Unreal Engine 3 with them, and keep some of the basics? I dunno. Seems kinda weak to say this at the end.

    1. Re:Here's a Stat I'd like to know by Anonymous Coward · · Score: 2, Interesting

      As a games programmer who has been using UE3 for some time now I can say that this decision doesn't surprise me at all. The performance of UE3 on 360 is pretty bad and a lot of people where I work are getting pissed off with that and with Epic's attitude to licensees. People might point to GoW as an example of a UE3 game running well on 360 but in recent months Epic have been scaling back their lighting pipeline just to get GoW to run at 30 fps. You can absolutely forget about running at 60 fps. There are some very nice things about UE3, but there are a lot of question marks about its performance. It isn't helped of course by the nature of the hardware and the fact that UE3 is a PC-centric engine. It would be possible for SK to just rewrite the renderer and keep the rest of the engine. At this stage in development that seems a lot more sensible than a complete engine change, but I guess it depends how much leeway they have with their publisher. :-) We are considering rewriting the renderer as well and will probably make a decision on that within the next month.

  8. Lame excuse by hollismb · · Score: 2, Insightful

    Perhaps they should talk to UBISoft, because, if I'm not mistaken, both Splinter Cell: Double Agent, and Rainbow Six: Vegas run on the Unreal engine on the 360.

    1. Re:Lame excuse by Traiklin · · Score: 3, Insightful

      or better yet, talk to Epic themselves.

      I hear they have a game coming out on the 360, didn't sound like it was giving them much problems using the Unreal engine 3 for it either.

  9. What about Mass Effect? by dgg3565 · · Score: 3, Interesting

    Bioware's Mass Effect is running on Unreal 3 and I certainly haven't heard anything out of them on this. In fact, I cam across one post on the ME forum where one of he developers was just talking about how one of their guys had squeezed out more preformance on the E3 demo by doing an optimization pass. It seems like everyone and their grandmother is using UE 3 at this point and yet not a peep out of any other dev team. And it isn't like Unreal is a new engine with neophyte coders behind it. This is a third generation engine that is built on a code base that has been used in titles from here to Timbuktu. Something seems fishy here.

  10. Not as bad as it sounds by Rayonic · · Score: 3, Interesting

    IIRC, Too Human was running on a custom engine for most of its development. Then (due to publisher pressure supposedly) the game was switched to the Unreal 3 engine. Now it seems that they're switching back.