BIT.TRIP CORE
Shoot Delay?
I noticed that when you attempt to shoot (via pressing the space key) there is a slight delay, so that by the time it's actually shot, the space key has already been released. In the Wii version, the instant the 2 button was pressed, it shot. I'm certain this isn't simple lag, as aiming does not have this delay, or anything else for that matter. Anyone else have this?
Dernière modification de Qyriad; 22 déc. 2012 à 13h44
< >
Affichage des commentaires 1 à 15 sur 16
Try adjusting your Vsync settings in your GPU's control panel.
Qyriad 28 déc. 2012 à 14h36 
My GPU doesn't have a control panel...it's too un-advanced.
Dernière modification de Qyriad; 28 déc. 2012 à 14h36
I have the same problem. I'm Hitting the key as the thing is on the line then it fires after it has passed. It makes the game un playable.
Sounds like a problem with either your GPU or your monitor. If you have an old monitor it could be input lag. A weak GPU can cause the same problem.
MattyD242 a écrit :
Sounds like a problem with either your GPU or your monitor. If you have an old monitor it could be input lag. A weak GPU can cause the same problem.

Im hooked up to a 60hz refresh 44inch tv via HDMI cable with a Radeon HD 6700 that works perfectly well with other games.
Check your HDTV's settings. Make sure it is on Game Mode to turn off all the post-processing, since this can introduce picture lag. It's only a few milliseconds per frame which is probably why you don't notice it in most games. The precision timing in this and other music games will mean any delay throws you off.
Qyriad 5 févr. 2013 à 12h09 
First of all, it's not an HDTV, it's just a plain old monitor. Second of all, I'm almost certain it's not simple display lag, because it's the game reacts slowly, not the monitor.
MattyD242 a écrit :
Check your HDTV's settings. Make sure it is on Game Mode to turn off all the post-processing, since this can introduce picture lag. It's only a few milliseconds per frame which is probably why you don't notice it in most games. The precision timing in this and other music games will mean any delay throws you off.

The game seems to have vsync enabled by default without anyway to turn it off through the game or a config file. So unless your GPU has a control panel, there is no way to turn it off.

@MicroGodrad

Out of curiosity, what GPU do have?
Qyriad 15 févr. 2013 à 11h49 
I just got a new computer, so NOW it's a AMD Radeon HD 7570. But I still have this issue. Even if I turn off V-Sync. It's also worth noting that the delay only happens when preforming a shot. Not when doing anything else.
I had this problem. It mysteriously goes away when you run the game in windowed mode.

This game is kind of a bad port, unfortunately. It has various issues that don't look like they've been noticed by the developers. Thankfully if you get rid of the lag problem, you can play it just fine.
Mika 25 janv. 2014 à 15h24 
Hi, I also have this problem, the shot goes a little late sometimes but I found the problem and how to fix it, just have to switch to a more powerful PC. In my case the problem gives me a computer with a dual core 2.3GHz processor with 3GB of RAM and 512MB of graphic class 4. However on my other computer which has a Quad Core 3.8GHz with 8GB of RAM and a 2GB GDDR5 Graphic Class 1 is perfect without any problem. Try and you will see. The V-sync has nothing to do (in my case still active and still not equal)
RED 23 févr. 2014 à 16h26 
op is talking about an input issue not a visual glitch, maybe the people who ported the game made a mistake
Qyriad 23 févr. 2014 à 17h06 
wiregrind a écrit :
op is talking about an input issue not a visual glitch, maybe the people who ported the game made a mistake
That's kind of what I was thinking was likely, but I was hoping it was either not that, or it was easily fixable.
It's unfortunately not easily fixable across all potential PC hardware configs. I'm the main guy that ported CORE/VOID/FATE/FLUX, but there was another guy whose sole bug-fixing was for these weird music/control sync issues. He basically got it working for whatever machines we were testing with but of course could not necessarily guarantee fixes across all hardware configurations. On the original Wii version, since the Wii is a fixed hardware platform, it only needed to be tweaked and would "just work" across all Wiis world-wide. This isn't an excuse as much as an explanation as to why it worked so well there and not for some people posting here on Steam. The original developers of these games might be watching these forums, so I'll let them more specifically vet this bug since I haven't worked on CORE in quite some time myself (just now wrapping up FLUX).
By the way, I just saw this old thread: http://steamcommunity.com/app/205060/discussions/0/882966057108000391/

Not sure if it may or may not be relevant for people in this thread having problems.
< >
Affichage des commentaires 1 à 15 sur 16
Par page : 1530 50