ViewtifulJC
Banned
Cave fucking up their first Steam release smh
So depressed about this release. One of my most anticipated releases of the year.
What, over 3 FPS? The porting studio has been very vocal and we're dealing with the ridiculously-easy-to-patch Steam/PC platform. Give it a few days.
It's likely that this issue didn't show up on their test systems.
Are you serious right now? Playing a shooter with a constant 3 frame drops ever second is like playing a fighting game with the same issue for me.
Yes, I realize that 3 FPS is a big deal when it comes to scoring in a shooter.
Personally, there's no way I'm going to notice a 3 FPS difference on a G-Sync monitor unless I'm ridiculously familiar with the game's speed.
I'm thinking this is running at 56 FPS for everyone. People who just aren't sensitive to it or not running a counter just don't see the difference.
Crimzon Clover was also patched multiple times in its first few weeks after release. I've pretty much resigned not to take scoring too seriously in the first few weeks of a PC shmup release. And Degica has earned a pretty good track record here so I will give them the benefit of the doubt. Plenty to do with survival runs, and patches almost never completely invalidate practice.
Cave fucking up their first Steam release smh
Honestly, this might not be something to patch. It could be a situation like Cave's first arcade hardware, where the games run at some odd refresh rate (57.something), and given that the games are framerate-dependent you'd be altering the game speed by something like 4% when nudging them up to 60hz. So there's an internal framerate lock and then they throw vsync on top of that?
I don't know. I'd LOVE to know how the 360 version handled it, if so.
I turned off gsync and see the judder. I'll try forcing vsync off and leaving gsync off. I'm guessing I'll get screen tearing and a 56fps game.
they don't. SH3 games all run at 60Hz exact (somewhat atypical in itself, since most "60Hz" arcade games aren't 60Hz but 59.9whatever or something)Honestly, this might not be something to patch. It could be a situation like Cave's first arcade hardware, where the games run at some odd refresh rate (57.something), and given that the games are framerate-dependent you'd be altering the game speed by something like 4% when nudging them up to 60hz. So there's an internal framerate lock and then they throw vsync on top of that?
I don't know. I'd LOVE to know how the 360 version handled it, if so.
I turned off gsync and see the judder. I'll try forcing vsync off and leaving gsync off. I'm guessing I'll get screen tearing and a 56fps game.
I honestly think the FPS issue is being way overblown. I didn't notice any glaring issues during gameplay, even though I'm getting the 55-57 FPS reading as well. Honestly, who is to say this wasn't intended behavior?
Risette said:they don't. SH3 games all run at 60Hz exact (somewhat atypical in itself, since most "60Hz" arcade games aren't 60Hz but 59.9whatever or something)
Yup, forcing off vsync and I get the same 56fps. Only a wobbly image instead of a juddery one, lol.
Someone phone Cave and/or MAMEDev and ask if the arcade hardware actually ran at 60hz, cuz I'm betting it didn't. And if it didn't, someone phone M2 ask what they did to adapt it to the 360's output resolutions.
I wonder if M2 just said fuck it and pushed the game up to 60hz on 360, but since there's a far wider range of refresh rates on PC, they decided to lock it internally to the original arcade hardware's rate.
edit:
Out of curiosity, did you get the 60hz figure from MAME? I think that MAMEDev uses 60hz as a placeholder sometimes, but I'm not sure.
they don't. SH3 games all run at 60Hz exact (somewhat atypical in itself, since most "60Hz" arcade games aren't 60Hz but 59.9whatever or something)
You can continue as much as you want.It doesnt have infinite continues right?
I'm still not even sold on the idea that the FPS counter isn't being thrown off by something the game does and you're already calling scores from the game void? Can we not jump to ridiculous conclusions before all the research is even complete?Because it isn't from what I'm reading. And scoring is pretty damn important on a STG. Like I said, you're score is null and void with framerates like that.
It doesnt have infinite continues right?
I feel like this 3PS issue should only matter for the top 1% and is being blown out of proportion. Competing for a world-record? Ok then, I get it. The other 99% of people will probably not see a change in their scores going from 56FPS to 60.
I'm still not even sold on the idea that the FPS counter isn't being thrown off by something the game does and you're already calling scores from the game void? Can we not jump to ridiculous conclusions before all the research is even complete
But... that's how it works man. It's not a ridiculous conclusion. You're score just doesn't count. The game isn't running at 60fps. I noticed this. I turned the counter on and my eyes were not deceiving me. The SH3 1000B and 1000D boards ran its games at 60hz. Why are you trying to come down on me for point out that the score you get on this game is invalid because of it.
Nevermind that even if it -is- running at the incorrect speed, it's nothing new for Cave ports. Ketsui 360/PS3 actually runs too fast compared to the arcade hardware and this is widely known, but no one considers it a bad port because there's nothing that could have been done to fix it; modern consoles and displays just can't do the weird framerates these games want sometimes.
Your score was never going to count against someone playing on the arcade hardware because it's a port. No one compares arcade and port scores; they've always been different and separate. Your score does, however, count against everyone else playing the exact same PC port, which seems to be behaving pretty consistently across many peoples' PCs.
But... that's how it works man. It's not a ridiculous conclusion. You're score just doesn't count. The game isn't running at 60fps. I noticed this. I turned the counter on and my eyes were not deceiving me. The SH3 1000B and 1000D boards ran its games at 60hz. Why are you trying to come down on me for point out that the score you get on this game is invalid because of it.
I see the game is jittery as well. Why am I getting shit on because of this. IF this were a AAA title that had this same issue there would be a shit storm. I'm not even saying anything bad about this game. I'm only stating what is fact.
Again, I'm wondering where the 60hz figure came from. It could be totally valid, but it makes no sense for a deliberate cap to be in place if so.
Alright so I gave away a Mushihime-sama Matsuri pack.
First person that PMed me got it.
It's gone.
EDIT: For what it's worth, I haven't had any frame-rate issues in the 14 hours I've spent with the port. Even if I had played the 360 version, I probably still wouldn't be able to tell the difference.
Take it with a grain of salt.
THAT I see as a major problem for anyone who experiences it. I was only referring to 56fps vs 60.I see the game is jittery as well. Why am I getting shit on because of this. IF this were a AAA title that had this same issue there would be a shit storm. I'm not even saying anything bad about this game. I'm only stating what is fact.
By the way, nice spot on the original nice leaderboard.
Why are there caps of 55-56, 59, and 60? That's what people are reporting.
Same here. I actually find vertical shooters easier to play on smaller screens, only because I can see everything and plan my pathing easier.team anti-tate
CAVE is going to look into this and see if we can adjust it to 60 FPS, where the framerate will appear more even.
Aw, yeah! I scored higher than Tain and pepsiman! Still a bit behind Elixir.
Didn't Degica put out an APB for any experts at Mushihimesama 360 to assist in bug-testing?
Wouldn't they of all people notice something like this?
We did. The issues that cropped up are issues that we *all* missed. PC development is hard, yo.
In any case, we're following the feedback from launch closely. Crashing errors, 56-59 FPS cap, and V1.5 sound errors are high priority fixes right now.
Aw, yeah! I scored higher than Tain and pepsiman! Still a bit behind Elixir.
Having a lot of fun with the game so far, glad a decided to grab it cause I haven't played a shmup in a long time. But ya'll are trippin way too hard over 3ish fps.
We did. The issues that cropped up are issues that we *all* missed. PC development is hard, yo.
In any case, we're following the feedback from launch closely. Crashing errors, 56-59 FPS cap, and V1.5 sound errors are high priority fixes right now.
Oh goodie.
Though I'm unsure if I really want this.
I mean, I was getting pretty comfortable with 56-57 fps.
Hmm...hold up a minute, something isn't quite adding up.
Didn't Degica put out an APB for any experts at Mushihimesama 360 to assist in bug-testing?
Wouldn't they of all people notice something like this?