Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.


Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Topic on User talk:BONKERS

I didn't take it as combative or in any negative way. Don't worry, I was just frustrated about important information being over generalized,removed or simplified when it didn't need to be.

I've been meaning to try and write more comprehensive stuff for AA with Nvidia cards here, but is just a lot of stuff to cover.

"I've been trying to get to full membership on NeoGAF for years, but my ISP keeps changing before the moderation queue comes around). "

I can understand the frustration, it took a long time to get on there too. At this point I can't remember if it was from waiting or from someone I knew. >_>


As far as the AA Fix is concerned. That is interesting, it probably does only apply to Fermi and greater, same as that SGSSAA only works on Fermi Cards and greater as far as I remember. Because I know the issues and fixes from the AA Fix DO persist to Kepler and Maxwell.


On the shadows, I forgot what 2x looks like, but 4x and beyond look leagues better, even if issues remaining are simply from how stuff works in the game engine. (Like they did in FFXIV 1.0), after checking Dragon Quest X since it also uses Crystal Tools the issues don't exist to lack of self shadowing and the stylized rendering approach.


"Ultimately I want to be able to perhaps heavily summarize that post here, or rather what to avoid, since this is about fixes and such (while still linking to it of course, I did a somewhat similar thing with the GPU-going-to-sleep explanation (even if it a bit long, and hopefully it's technically correct)). Or would that not be a good idea? "

I think adding things like the fact that it's Fermi and forward specific are ok. Simplifying something like this too greatly isn't a great idea I think. My link post has an in depth step by step process to get Nvidia Inspector set up to the point to fix it. Simplifying it to "Follow the guide in the reference" like I have it set up I think is the bare minimum it can get to.


"I'm probably rambling, so thank you for humoring me! FFXIII is just the kind of weird port that I'd expect from a JP company that isn't Falcom. Especially its official "XInput controller" recommendation (it doesn't support XInput at all or use XInput drivers of the controller, it just uses DirectInput and assumes the internal layout is the same as the XBox controller spec). Thanks again for the explanations! "


It is a weird port! I mean.. it's like they didn't quite think it through. I was so excited but skeptical when it was announced and I was right to be I guess. I mean, they can't be that out of touch. They are on the ball when it comes to Final Fantasy XIV ARR on PC. (Except for when it comes to AA and UI scale. Which hampers downsampling)

The controller nonsense makes literally no sense! I mean, if this is based off the Xbox 360 jp code branch, it'd HAVE to be Xinput. Being direct input would mean using BetterDS3 to map the PS3 controller to direct input would get it to work just fine. Same with the PS4 controller ,because isn't it just DirectInput??

Why change to DirectInput?

>_>