Dominic_Shade
Member
Guess it's time for me to pick up the HD Collection then, haha. Good to hear about the patch. Thanks for posting this, TC.
I just bought it too. Usually I try to get physical copies but $16 is just too cheap to pass up.
So...which is better, ZoE2 HD or ZoE2 emulated on PC? Oddly enough, I still have my retail PS2 disc...
Definitely HD version. No comparison.So...which is better, ZoE2 HD or ZoE2 emulated on PC? Oddly enough, I still have my retail PS2 disc...
I see. So to clarify and I apologize for asking:
ZoE 1 ps3 = ZoE 1 360 = ZoE ps2 on terms of performance?
When I said both consoles I was talking PS3 and 360.
All you need to know is that the PS3 version is the one to get and that both games are perfectly playable now. ZoE1 isn't quite as smooth as on PS2 but it runs well so it's not surprising that they didn't patch it though of course it would've been nice.
When I said both consoles I was talking PS3 and 360.
All you need to know is that the PS3 version is the one to get and that both games are perfectly playable now. ZoE1 isn't quite as smooth as on PS2 but it runs well so it's not surprising that they didn't patch it though of course it would've been nice.
The dips occur whenever your character is in close proximity to any and all alpha effects (such as explosions). The dips feel like small skips and stutters to the framerate and do impact fluidity. Technically speaking, it runs smoother than something like, say, Call of Duty but it still doesn't feel as smooth as it should.How frequent are the dips? Is it all the time?
It really wasn't. Not that it was unplayable, but the game would have frequent FPS hits. It was especially jarring when you'd get the camera just right in a 1v1 situation and the game would clearly run perfectly smooth (which never happens otherwise)--60 FPS or close to it. And it really stood out.I thought the performance of ZoE1 HD was very close to perfect as is tbh, but I don't really enjoy the game so I didn't play it all that much,
Didn't ZoE1 on the PS2 chug every time the environment was destroyed?The dips occur whenever your character is in close proximity to any and all alpha effects (such as explosions). The dips feel like small skips and stutters to the framerate and do impact fluidity. Technically speaking, it runs smoother than something like, say, Call of Duty but it still doesn't feel as smooth as it should.
The game originally operated at 60 fps without slowdown on PS2. It really was virtually flawless in that regard.
On PS3 it is more than playable but it isn't as polished an experience as one would hope.
Didn't ZoE1 on the PS2 chug every time the environment was destroyed?
I'll have to load it up again to be sure, but I feel that was intentional.Didn't ZoE1 on the PS2 chug every time the environment was destroyed?
Maybe I'm mistaken then. I just remember during the rescue mission in the town with the huge valley in the center, Id get a one on one fight against a cyclops or something, and the game would clearly run better than any other time.I'll have to load it up again to be sure, but I feel that was intentional.
I only say that because ZOE1 used field rendering (unlike the rest of KCEJ's output on PS2). You gain speed at the expense of image quality but you have to maintain 60 fps else you start losing half of the image data and the game will run in slow motion. So, if ZOE1 were to chug, the entire screen would become a pixelated mess (half resolution) during those moments. I don't seem to recall the game running into that issue, however.
Hexadrive and they fixed the game? very good news.
now maybe Hexadrive is the studio that is porting MGR seeing how Konami hired them for this? (since we don't have any info on that at all and PG look like busy making games)
They're ex-Capcom guys, apparently.Hexadrive also did the Okami HD port, and that was a good one apparently. They seem like a competent studio. Wouldn't mind to see their potential PC output.
I'm slightly pissed here, I bought the 360 version right off the bat because of the better framerate in ZoE2. I'm going to double dip now (probably on ebay) and grab the ps3 version.
I'll have to load it up again to be sure, but I feel that was intentional.
I only say that because ZOE1 used field rendering (unlike the rest of KCEJ's output on PS2). You gain speed at the expense of image quality but you have to maintain 60 fps else you start losing half of the image data and the game will run in slow motion. So, if ZOE1 were to chug, the entire screen would become a pixelated mess (half resolution) during those moments. I don't seem to recall the game running into that issue, however.
Exactly this, haha.I can finally unbox my copy lol.
Ok just bought this. Never played either. Should I bother playing 1? I don't get much time to play games these days...
I would start with 1, because ZoE2 is so much better that its hard to go back to ZoE1 once you've started ZoE2.
The games are not that big, I think you can beat ZoE 1 within 6 hours or so.
Not that I had asked the question, but I am now patching and I was going to ask same question. Thanks.
It's an alternate method for drawing an image which was used in many (usually early) PS2 titles. It's designed for interlaced displays. Essentially, you'd be rendering out to a 640x224 buffer (though the 640 could vary) and nudging each field by half a line every 1/60th of a second. It basically alternates rapidly between odd and even lines and gives the impression of a full 640x448 image. The benefits of this are simply that you can achieve an image that looks roughly equivlanet to 640x448 at 60 frames per second with less of a demand placed on the hardware.Sorry, can I get some clarification on what you mean by "field rendering"? I don't think I understand it.
Is that somehow different than plain old interlaced rendering that you see with any 480i console game? Does it refer to the difference between a game that renders internally at 480p with 480i output (not field rendering, I'd assume most/all Dreamcast and Xbox games) and a game that renders in 480i internally in the first place (field rendering, PS1, N64, Saturn "high resolution" games)?
I also don't understand how it could be directly related to the game entering slow motion instead of dropping frames when it can't maintain speed, since any game can be written to be framerate independent.
It's an alternate method for drawing an image which was used in many (usually early) PS2 titles. It's designed for interlaced displays. Essentially, you'd be rendering out to a 640x224 buffer (though the 640 could vary) and nudging each field by half a line every 1/60th of a second. It basically alternates rapidly between odd and even lines and gives the impression of a full 640x448 image. The benefits of this are simply that you can achieve an image that looks roughly equivlanet to 640x448 at 60 frames per second with less of a demand placed on the hardware.
Field rendering is perhaps the mode which specifically resulted in people calling out "the jaggies" as high motion scenes produced more artifacts than what you'd get while using a full frame buffer. I think it was worth it, however, as it allowed for a more larger selection of games operating at a higher apparent framerate.
I imagine GT3 shut people up in the end. I couldn't get into it, but I can't deny that is the most impressed I've ever been with a racing game's visuals, and I'm not sure I CAN be as impressed again: GT5 and Forza Horizon look pretty nice and I'm sure leagues ahead of GT3, but relative to when I first played them GT3 was just on another level altogether.Yeah, Ridge Racer V was the major offender back then due to the high speed of the game producing a lot of jaggies every time you drifted around a corner. This thing, at Ps2 launch, even contributed for some time to the idea that "Dreamcast is more powerful than Ps2!!!".
Did I miss something? Please elaborate.
It says a lot about ZoE1 vs ZoE2 when I recalled ZoE2 being double the length of ZoE1, but nope, it's either the same or shorter. It's just that ZoE2's THAT much more dense.
I need to check my time for ZoE2 again but it was around 4 hours, though admittedly I was playing on Easy as Normal pounded the crap out of me. I think what I said is still true though, ZoE2's a denser experience, whereas ZoE1 was kind of jut fetch quests until you beat the game.That's not true, 1 took me around 4 hours and 2 over 7 hours.
I need to check my time for ZoE2 again but it was around 4 hours, though admittedly I was playing on Easy as Normal pounded the crap out of me. I think what I said is still true though, ZoE2's a denser experience, whereas ZoE1 was kind of jut fetch quests until you beat the game.
Not even a day before I get avatar quoted. And ZoE2 even had some designs by Kazuma Kaneko!