Portugeezer
Gold Member
Doesn't matter TBH, as they haven't even touched a 3DS.Burai said:It also has a ton more RAM than the rumoured 64MB in the 3DS. 256MB in the 3GS, touch and iPad, 512MB in the iPhone 4.
Doesn't matter TBH, as they haven't even touched a 3DS.Burai said:It also has a ton more RAM than the rumoured 64MB in the 3DS. 256MB in the 3GS, touch and iPad, 512MB in the iPhone 4.
DennisK4 said:And yet somehow Halo: Reach will sell millions and Castlevania will be a success even though they are sup-30 and 'Amir0x unplayable'....
EuropeOG said:I doubt they will, they don't even care about the Wii.
I sense the iRony as Nintendo are Japanese and seems they are being overlooked by Western developers.
Hmm...?
I've been told that developers coded stuff on a PC and that most some teams had a single 3DS to debug/run/test their games with. :lolcosmicblizzard said:Maybe they should get their hands on a 3DS. I have a hard time believing they couldn't get one if they asked.
well if a bad thing is successful than it must be good and not a problem to anyone everDennisK4 said:And yet somehow Halo: Reach will sell millions and Castlevania will be a success even though they are sup-30 and 'Amir0x unplayable'....
swing and a missEmCeeGramr said:well if a bad thing is successful than it must be good and not a problem to anyone ever
Jin34 said:Below spec but Capcom had MT Framework working in a way many people here thought was pre-rendered bullshots in a few months? :lol :lol :lol
Nah, a home run, but it seems that the other team took the ball and went home.DennisK4 said:swing and a miss
Instro said:Kind of a weird comment. "It wont work, but we dont actually know the specs and we havent actually been given a dev kit *hint hint*".
If there is enough interest, it will happen.
EmCeeGramr said:Nah, a home run.
Well, it would help if NoA was more than a mere marketing operation.brain_stew said:Well technically it is below spec. UE3 on mobiles has required a full ES 2.0 compliant device thus far which is one of the major reasons it doesn't work on the original iPhone. Of course, there's nothing in the Epic Citadel demo that couldn't be reproduced on the 3DS of course (outside of texture resolution) but it would require Epic to make use of fixed function units inplace of their proprietary shader code and I don't believe the last bastion of software rendering, Mark Rein, would jump at the chance to do that.
Personally, I feel this one is on Nintendo. Getting UE3 up and running on the 3DS (and yes, I believe it is possible it'd just require the swallowing of some pride, the CPU is probably the biggest bottleneck not the GPU) is one of the biggest "gifts" Nintendo could give to western third party developers. If they're at all serious about wooing third parties then collaborations with the likes of Epic are exactly the sort of things they should have been doing, no matter how incompatible the company culture is.
My guess it that Reggie doesn't have the power to do that kind of stuff.ksamedi said:Another one of Reggies incompetencies. I would have thought that Epic was the first company you go to if you want to broaden the handheld audience in the US. I guess Reggie thinks differently.
So it might work, as they have no idea what the specifications are. That last part confirms that they haven't gotten a good look at the hardware and might even be a bit miffed about it."No. It's below our [minimum specifications], from what we can tell. We don't have a 3DS, so there's no way for us to verify that, but everything we've been led to believe is that it's below our min-spec. You couldn't do a game that looks like [Epic Citadel] on it, for example. Like I said, we really don't know enough about it to make a formal comment, but I think if they considered that our engine would be good on it, they would have probably talked to us about it."
brain_stew said:If they're at all serious about wooing third parties then collaborations with the likes of Epic are exactly the sort of things they should have been doing, no matter how incompatible the company culture is.
Lonely1 said:Only up to 128 usable for single apps, though.
Teetris said:Heh, would be funny if they did it later on tho. What with recent developments and all
As far as I know, Carmack does care. They don't consider what they do marketable, but Carmack loves to tinker with all kinds of hardware, and he seems to get a kick out of very limited devices. Didn't he even code their DS game all by himself, just for the challenge? Bethesda might never release a 3DS game, and they don't seem to license their engines anymore, but I wouldn't be surprised if Carmack already had a 3DS devkit to play around with.EuropeOG said:I doubt they will, they don't even care about the Wii.
I sense the iRony as Nintendo are Japanese and seems they are being overlooked by Western developers.
Hmm...?
brain_stew said:Well technically it is below spec. UE3 on mobiles has required a full ES 2.0 compliant device thus far which is one of the major reasons it doesn't work on the original iPhone. Of course, there's nothing in the Epic Citadel demo that couldn't be reproduced on the 3DS of course (outside of texture resolution) but it would require Epic to make use of fixed function units inplace of their proprietary shader code and I don't believe the last bastion of software rendering, Mark Rein, would jump at the chance to do that.
Personally, I feel this one is on Nintendo. Getting UE3 up and running on the 3DS (and yes, I believe it is possible it'd just require the swallowing of some pride, the CPU is probably the biggest bottleneck not the GPU) is one of the biggest "gifts" Nintendo could give to western third party developers. If they're at all serious about wooing third parties then collaborations with the likes of Epic are exactly the sort of things they should have been doing, no matter how incompatible the company culture is.
Amir0x said:they do know the specs, that's where he is getting his general guess about whether UE3 will work on 3DS or not from
Jin34 said:I know about the 2.0 thing but we know that the 3DS can do all those things and rather easily, not some TEV crack your head to get shaders like the GC/Wii. It's a matter of semantics and very disappointing that something so minor is the excuse.
.
Instro said:Well I was just thinking that if he knew the exact specs there really wouldnt be any guessing involved. From the last sentence it seems like hes kind of annoyed that they dont have the hardware or exact specs on it.
"We don't have a 3DS [...] they would have probably talked to us about it." - No, I'm not making shit up. Epic could have asked for a devkit many, many months ago. As a middleware provider, they probably would have gotten one. They obviously didn't.2San said:Do you just make shit up, because you can?
I think it was more that he wouldn't of minded Nintendo coming to him and asking about the engine use.Hey, if the 3DS was able to use UR engine, that would expand the business of selling it more and would probably give the engine a longer shelf life.Amir0x said:from the last sentence it just seems like he feels if there was some information about the hardware he didn't know that would make UE3 work, Nintendo would probably be privy to those details. And since Nintendo hasn't shown any interest either, there probably isn't any secret core that will allow UE3 in its current form to run on the platform.
I really have no idea where people are coming up with these elaborate ideas about how butthurt Epic is
Epic is just ok, trust me, they're not worried if they get a 3DS dev kit :lol
Well stated. This is one of the main reason why I don't care for this style of gaming on the smartphone side of the spectrum. Then again, maybe I would care if something dropped that was a real experience that rivaled my ds or home console.viciouskillersquirrel said:I don't get what the big deal is. 3DS specs are designed with battery life for gaming use as a top priority, unlike (say) current smartphones, where anything approaching intensive use drains the battery in mere hours.
People are going on about the iDevices running UE3, which, while neat, doesn't take away from the fact that these devices just barely run it right now and even then, only for an hour or two before you have to recharge the battery. UE3 on mobile devices is currently just a proof-of-concept sort of thing. Actual commercial releases of titles using the engine are still a few more iDevice revisions away just yet. Smartphones have the power (just), but they lack the efficiency to run this engine in a truly mobile way.
I'm really not surprised that UE3 doesn't run on 3DS. You'd be hard-pressed to run it on anything less powerful than a laptop.
Lonely1 said:Only up to 128 usable for single apps, though.
[Nintex] said:I've been told that developers coded stuff on a PC and that most some teams had a single 3DS to debug/run/test their games with. :lol
Amir0x said:from the last sentence it just seems like he feels if there was some information about the hardware he didn't know that would make UE3 work, Nintendo would probably be privy to those details. And since Nintendo hasn't shown any interest either, there probably isn't any secret core that will allow UE3 in its current form to run on the platform.
I really have no idea where people are coming up with these elaborate ideas about how butthurt Epic is
Epic is just ok, trust me, they're not worried if they get a 3DS dev kit :lol
It may be, but:Zzoram said:You guys think *only* DOUBLE the available RAM of the 3DS isn't a big deal?
Source: http://www.gamasutra.com/view/news/..._Capps_On_Bringing_Hardcore_Flavor_To_iOS.phpGamasutra said:Have you gotten a lot of demand and stuff from people you've talked to? Some of the publishers that have worked with it?
Oh, really, really, absolutely, yeah. It kind of surprised us honestly, that we'd be talking to one of the big-tier publishers, I don't need to say who, and they're porting games and they're making tens of millions of dollars making fantastic games on iPhone. We had no idea that business was growing so fast, and they were so excited to be taking existing IPs built on our engine over to the mobile space, so we were like, "Gosh, we really need to get on this right away." That's really how we're looking at it.
viciouskillersquirrel said:People are going on about the iDevices running UE3, which, while neat, doesn't take away from the fact that these devices just barely run it right now and even then, only for an hour or two before you have to recharge the battery. UE3 on mobile devices is currently just a proof-of-concept sort of thing. Actual commercial releases of titles using the engine are still a few more iDevice revisions away just yet. Smartphones have the power (just), but they lack the efficiency to run this engine in a truly mobile way.
I'm really not surprised that UE3 doesn't run on 3DS. You'd be hard-pressed to run it on anything less powerful than a laptop.
yoopoo said:So iPhone has more bits than 3DS...how many more bits? 32..64 bit, 128!?
Vic said:Why Epic getting on-board with the 3DS is anyhow related to the west supporting the handheld?
Instro said:Because thats more fun, also because Mark Rein is a bit of a jerk.
Vic said:Why Epic getting on-board with the 3DS is anyhow related to the west supporting the handheld?
Mass storage, caching - that stuff. I've only seen slightly outdated datasheets, but assuming those are still relevant, at least as a comparison, Nintendo uses mass storage several times faster compared to what Apple uses. Even stuff like Plants vs. Zombies has noticeable load times on iPhone - far worse than any DS game, or 3DS demo I've seen. If you have really fast mass storage, you can get away with a lot less RAM.Zzoram said:You guys think *only* DOUBLE the available RAM of the 3DS isn't a big deal?
Vic said:Why Epic getting on-board with the 3DS is anyhow related to the west supporting the handheld?
Cataferal said:Fine by me. I've grown tired of the UE3 look that's become prevalent on the home console front.