How could they lose something they never had in the first place?V8 Ninja said:I wouldn't necessarily say they've lost PC exclusivity (according to Wikipedia, they lost it in 1992), but this is a bit of a hit to PC gamers. Of course, I don't expect too much to happen, maybe an increase in console ports if anything.
That's probably not the best example to bring up - those games have terrible mouse+keyboard controls. They were designed with controllers in mind, even FFXIV (which, unlike 11, actually launched on the PC).Garak73 said:It could be adapted to controller. Final Fantasy MMO's are and I don't see that things are really so different.
I was under the impression that the work was largely being done by a third party (Nihilistic if memory serves) anyhow.Aeshi said:Does this mean they might start working on Starcraft:Ghost again?
Why are you so certain it's going to happen? The removal of LAN is stupid, yeah, but BNET 2.0 is fantastic piece of software, it works brilliantly. There's no evidence whatsoever that Blizzard will be gimping games for consoles, just that they'll be developing them.Garak73 said:Because it has happened to other companies and it will happen to Blizzard. BTW, Blizzard is no longer as respected as they used to be. The nonsense with SC2 not having LAN and forced BNET 2.0 has lowered alot of opinions.Rusty Bucket said:Why do you immediately assume that Blizzard would gimp the game for consoles? They're one of the most respected PC developer around, and it's painfully obvious that the PC is their primary platform for Diablo 3. How about we don't jump to conclusions? At least wait for some actual details.Garak73 said:WOW has pretty low specs, I don't see why the 360 couldn't run it.joebear15 said:how?????????????? I mean what one of the games they design would port well at all to the consoul. I mean I thought thats why they had not already done this is because all the games they design would be terrible ported..
I mean could you imagine a wow port and how gimped it would have to be ot be playable on the xbox.
I do think it's a mistake though for Blizzard to start making PC games for the console. Look what happened with Morrowind and then Oblivion. Morrowind was a PC game first that got ported to the XBOX. It was a bad port considering the load times alone but they apparently got more sales on the box than they did on PC and as a result Oblivion was built around a console and then ported to the PC with console menus.
Well, the Blizzard that made games with Spawn and LAN support is no more. Why not expect this?
The engine is almost 12 years old now. That's like saying "Oh well you know, the Painkiller engine looks better than the Build engine" It's a completely different platform, they're pushing the engines limits, which isn't necessarily poorly coded, they're forcing the engine to do things they didn't initially design it to do, coded as well as it possibly can be without a complete engine rewrite. It'll cause unexpected issues, slow downs, and almost obscene amounts of resources. Considering all that, they've done a damn fine job with it.Garak73 said:So the game runs inefficiently? Those graphics should run fine on a HD ready console like the 360. If those graphic make the 360 cry, then that's inefficient coding. We've seen games on the 360 that look alot better than WoW.oplinger said:FFXI was designed for the PS2, ported to PC, not the other way around.Garak73 said:It could be adapted to controller. Final Fantasy MMO's are and I don't see that things are really so different.Johnnyallstar said:Just because it has low specs doesn't mean much. There would have to be a special controller scheme designed for it... I.E. a mouse and keyboard, because the controller is very limited. After that, well, there is an issue with space on the older systems. The whole of the game is bigger than the space of the original 20gb hard drive.Garak73 said:WOW has pretty low specs, I don't see why the 360 couldn't run it.
But Diablo, I can imagine that working out quite well on console, though I think I'd still prefer it on PC. Point and click movement would suck on console. I hope it's changed to wasd.
As for space, well, a bigger HDD would be required for some people but now that the 250GB is standard and they are cheaper for the older models...it would be acceptable. Remember, the PS2 needed a HDD to play FF XI and alot of people were willing to do that.
Not that I think they should move WOW to the console, I am just saying they could.
Also WoW still uses the WC3 engine, which has been heavily modified to use higher resolution textures, dynamic shadows, and now many other visual effects. The engine uses a very harsh brute force method to render most of it, it would make a 360 cry. They'd have to turn off many of the advanced effects they added into the game just so the RAM on the 360 could be used. It's more than just a control scheme.
I ran WoW on it's highest settings about a month ago. When comparing WoW to Final Fantasy XIV, WoW looks horrible and Final Fantasy XIV looks no better than Final Fantasy XIII, which is on the 360.
Not that surprisingGalaxy613 said:Coming from Gamasutra:
http://www.gamasutra.com/view/news/31551/New_Blizzard_Ads_Seeking_Diablo_III_Console_Devs.php?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+GamasutraNews+%28Gamasutra+News%29The developer, also behind World of Warcraft and StarCraft, is hiring "lead designer, console," "lead programmer, console" and "senior producer, console." The newly-posted positions are under "Diablo III." Gamasutra has contacted Blizzard for comment on the new ads.
This is very surprising, but at the same time, not very considering the way Blizzard has been growing itself lately... I guess they are now looking to spread to consoles.
It very well could, but the resources the pushed engine uses are far beyond what a 360 can handle. they'd have to turn off many of the added on features. It's not the fact that the engine's old, or necessarily cludgy. It's just pushed beyond it's limits, and has no easy way to do things. Think of it like sewing by hand vs sewing with a machine. One's just stepping on a pedal to do -all- the hand motions. the WC3 engine does not own a sewing machine. So it has to make due with the processes it knows how to do, and the new tricks blizzard tries to teach it.Garak73 said:So why can't the 360 run a 12 year old engine?
Check this.Garak73 said:WOW has pretty low specs, I don't see why the 360 couldn't run it.joebear15 said:how?????????????? I mean what one of the games they design would port well at all to the consoul. I mean I thought thats why they had not already done this is because all the games they design would be terrible ported..
I mean could you imagine a wow port and how gimped it would have to be ot be playable on the xbox.
I do think it's a mistake though for Blizzard to start making PC games for the console. Look what happened with Morrowind and then Oblivion. Morrowind was a PC game first that got ported to the XBOX. It was a bad port considering the load times alone but they apparently got more sales on the box than they did on PC and as a result Oblivion was built around a console and then ported to the PC with console menus.
Well, the Blizzard that made games with Spawn and LAN support is no more. Why not expect this?