What kind of settings is he trying to run the game in?
Absolute lowest settings.
Silly question, but is it a laptop?
Nope. It's a desktop.
What kind of settings is he trying to run the game in?
Silly question, but is it a laptop?
Cross posting from Steam thread, figured this thread might have people who want to know about this as well.
Someone wrote a little injector that fixes the Xbone controller issues in Final Fantasy XIII-2 (and XIII according to readme), and it also has the framepacing removal in it. Both optional if you only want to use one or the other since the framepacer removal can cause some issues apparently.
http://steamcommunity.com/app/292140/discussions/0/487877107138721625/
Briefly tested the xboner fix and it worked great.
With the Xbox 360 controller LT and RT are mapped to a single parameter: DIJOYSTATE::lZ. However, with the Xbox One wireless controller the triggers are mapped separately to DIJOYSTATE::lZ and DIJOYSTATE::lRz. I wrote the fix as follows:
joystate->lZ = (BYTE)(128 + (joystate->lZ / 255.0)*127.0 - (joystate->lRz / 255.0)*128.0);
Unfortunately if the fix is not applied the default state would be for lZ to have the value 0. This would correspond to RT being pressed. This seems to lead to trouble.
Have the performance issues with this port been fixed?
It may work with even more games, from the Steam thread:
I knew that was coming. So predictable. You have nothing so you played the "she's not real" card. Hate is still hate whether the person in question is real or not.
Why does this game run so awfully? I've tried every 'fix' I could find on the internet but nothing works. It stutters a lot, it lags, it goes randomly blurry, it crashes if I try to play in fullscreen. The first game played perfectly fine for me from beginning to end.
Sweet, now it has also started randomly freezing with the music still playing. Even better.
Never heard of these types of troubles with this one.
Why does this game run so awfully? I've tried every 'fix' I could find on the internet but nothing works. It stutters a lot, it lags, it goes randomly blurry, it crashes if I try to play in fullscreen. The first game played perfectly fine for me from beginning to end.
Looks like its rendering some low resolution.
For some reason both FF13 and 13-2 don't work properly at 2560x1440.Game looks really bad at 1440p. The hell?
Looks like its rendering some low resolution.
Using dsr x2.25 to get 2160p is the only way to make it look decent.
Why does this game run so awfully? I've tried every 'fix' I could find on the internet but nothing works. It stutters a lot, it lags, it goes randomly blurry, it crashes if I try to play in fullscreen. The first game played perfectly fine for me from beginning to end.
Sweet, now it has also started randomly freezing with the music still playing. Even better.
I don't understand how I can get six hours in, finish an area, then wander around that same area the next day and suddenly get freezing.
Game looks really bad at 1440p. The hell?
Looks like its rendering some low resolution.
Using dsr x2.25 to get 2160p is the only way to make it look decent.
For some reason both FF13 and 13-2 don't work properly at 2560x1440.
From what I've seen in the steam community hub for both ff13 and 13-2, seems like people with overclocked intel CPUs (someone mentioned getting 55~60fps on 13-2 with a 4.4GHz i7 5820k for example) are getting little to no performance problems, seems like both games are very dependent on single core performance.Unfortunately, this is just how this port is. Tons of frame rate drops everywhere, no matter how strong your pc is.
For some reason both FF13 and 13-2 don't work properly at 2560x1440.
Yeah, anything that's an exact multiple of 720p will look bad if I remember right. Something like that. I think I ended up playing at 1620p.