Quote from kesvalk:
ok, have a nice trip and bring souvenirs...
i guess, in a way, that i'll actually be doing
It'd be more fun in hell with the cool people than heaven with all the stuck-up pricks.
Archived M2K2 Forum
Quote from arkarian:
nice ryu. ps3 ftw.
i'm a little pissed tbh. the damn thing only plays in 50hz on a ctr. what the hell? even all gamecube games played in 60hz! no to mention a lot of ps2 games did.
i'm lucky it's at least "fullscreen", though letterboxed because of forced widescreen - but that doesn't squish the grafics so it's fine by me.
Club 27 Goals
Quote from J_SNAKE:
I have never played Minecraft in my life, because there is nothing to play.
Oh, well okay. You're a confusing guy sometimes.
And yeah, the constant 30fps on the ps3 was pretty annoying. And that pretty much every game was 720p so it looked all blurry and shitty on a 1080p LCD. Wipeout HD looked and played fantastic though.
i have no idea what a game locked at 30hz even means. in europe it's just thatwe used to have PAL technology for crt tvs while in the us and japan it was NTSC. almost all pal games were butchered versions of their ntsc originals - most of them ran about 18% slower and had the image squished vertically.
in the ps2/gcn era pal games started to distinguish between 50hz and 60hz mode. 60hz mode just meant the game would play as a ntsc region game, and would require a tv capable of displaying at 60hz.
now sonic generations on my ps3 hooked onto a crt displays in 567(or whatever it exactly was)i, pal, instead of ntsc. because of that it runs 18% slower than it's supposed to run.
anyways, i don't think games play at 30hz. you must be mixing that up with 30fps. funny enough, even if you have a game that runs at 30 fps, with a shitty pal conversion you could end up with a game running at sloppy 20fps. i noticed this with skyward sword when i tested that in pal mode, and there was a very noticable drop in framerate.
in the ps2/gcn era pal games started to distinguish between 50hz and 60hz mode. 60hz mode just meant the game would play as a ntsc region game, and would require a tv capable of displaying at 60hz.
now sonic generations on my ps3 hooked onto a crt displays in 567(or whatever it exactly was)i, pal, instead of ntsc. because of that it runs 18% slower than it's supposed to run.
anyways, i don't think games play at 30hz. you must be mixing that up with 30fps. funny enough, even if you have a game that runs at 30 fps, with a shitty pal conversion you could end up with a game running at sloppy 20fps. i noticed this with skyward sword when i tested that in pal mode, and there was a very noticable drop in framerate.
Quote from ryu:
anyways, i don't think games play at 30hz. you must be mixing that up with 30fps. funny enough, even if you have a game that runs at 30 fps, with a shitty pal conversion you could end up with a game running at sloppy 20fps. i noticed this with skyward sword when i tested that in pal mode, and there was a very noticable drop in framerate.
As a gamedeveloper with highest technical-quality-demands I know exactly how all that stuff works. Gamers could benefit from that knowledge but I know they won't do so I won't explain you everything.
Let me say this though: The way game-loops are made now differs from how they were made in the past. If you sync the game-loop to the screen-refresh how it was done before than your game will update with that rate, resulting in slower and faster versions. Today a 30 hz-game won't run at 20 hz on no matter what screen you have. The reason why it looks choppy is because the screen is missing frames if its number doesn't match up well with 30fps. So not every game-frame is displayed, but the game is still running at 30fps.