The issue NickSP44 is talking about is real, it's just not limited to Final Fantasy X. If you pause basically any Square Enix game (and maybe others), you will notice that the game becomes super pixelated, almost like the downsampling filter was turned off and you're running a really shitty-looking version of native resolution. Karasuhebi (talk) 22:29, 21 August 2016 (BST)
Here's some screenshots:
Pause screen on 6x native: http://i.imgur.com/Z33fEnZ.png
Pause screen on native: http://i.imgur.com/kRduELb.png
6x native: http://i.imgur.com/RvYPIWh.png
pause 6x: http://i.imgur.com/dj82V9J.png
6x native: http://i.imgur.com/TutogIE.png
pause 6x: http://i.imgur.com/yIL57PV.png
NickSP44 mentioned visual garbage on the pause screen, which definintely isn't there. What actually happens isn't a real issue or bug, the game just takes a snapshot of the current (3D) scene and displays that on the pause screen. Now obviously this snapshot is taken at the original PS2 resolution, as it was never meant to be upscaled to HD. And as PS2 level texture filtering "Bilinear (PS2)" doesn't filter it, it looks more pixelated than normal on higher than native resolutions. Enabling "Bilinear (Forced)" improves it. - FlatOut
- Interesting. I wonder why that happens. Bilinear (PS2) seems to be filtering the pause screen when you're playing at native resolution so I wonder why it doesn't do it when you're downsampling from higher resolutions. Karasuhebi (talk) 03:58, 22 August 2016 (BST)
Hello, i have a bad english so thanks for the change of my issues. The textureless levels and invisble platform are the same bug. I have write the two issue but in the past(when i have write "invisible" issue) only the first level of chibi was suffer for this(i admit i don't have explain the fully issue in the past because textureless was only chocking for me when i have see the platform invisible). Now(whit the pcsx2 1.5.0-1520 download this morning and older 1.5.0) all level ootdoors can suffer for this issue.
For the "armory gantz", i don't complain about the remove of this issue bad writed by me, but i thinks this is really a issue since i can play in native or x2 and the FPS are the same when i have this menu of "gantz".
Monster Trux Extreme: Offroad Edition
Oh, hi! The wrong publisher is GameFAQs' fault (they have very sketchy info on the regions other than US or JP), I could probably update all publishers/developers from IGN but it's not high on my list. What I wanted to address though is that SLES-53006 is already present on the wiki (for Hamster Heroes). If you own physical discs for the game I'll check Hamster Heroes then but that'd be a wonder for a budget title to be issued on two discs. --Ngng (talk) 14:57, 5 November 2016 (UTC)
Thankfully, I own neither game. But I checked the sides of the box and it looks like it says SLES-53006 on both. I couldn't find a print of the MTE:OE cover elsewhere with this code though. http://img.gamefaqs.net/box/4/7/0/75470_side.jpg http://img.gamefaqs.net/box/1/5/0/77150_side.jpg --FlatOut (talk) 15:47, 5 November 2016 (UTC)
- It's probably a photoshoped cover then. I've seen many photoshoped covers, -- it's easier to create a cover from the images available on the internet (in this case from the text fragments) than to find the physical copy and feed it to a scanner. --Ngng (talk) 16:02, 5 November 2016 (UTC)
Hey FlatOut, maybe you can help me. I'm trying to edit the page for NCAA Football 2002 and 2003, but when I try to publish my edits I get a message about a CAPTCHA that I'm supposed to do. I tried refreshing the page and the CAPTCHA still doesn't show up. After about a dozen tries I finally got my edit to stick on the NCAA Football 2002 page. Am I doing something wrong? Gamemassa (talk) 9:48, 13 November 2016 (BST)
I believe there are some internet browsers that can have issues with the CAPTCHA, possibly depending on the browser settings. But your user rights have been updated, so you wont get bothered by the CAPTCHA again. ;)--FlatOut (talk) 14:51, 13 November 2016 (UTC)
- Uh, hello again!
- "I prefer the correct titles, regardless of what other websites say.". It's not a matter of principle for me but I still want to avoid undesirable arguments in future. I believe there is no such thing as a correct title. The closest you can get is the most widely used one. You can also assert that the title is defined by the publisher (Amazon, Sony (the game can no longer be found on EA sites, what a surprise)) or by the boxart title (which may not always correspond with the SKU shipping name and may be changed on reissues). But if you still believe it should be a boxart you mustn't deny that the boxart for this game also has "LEGO" on it. As I said before, in no way it is a matter of principle for me I just like to reduce the risk of idle arguments (in case you'd be determined to rename everything and anything, I hope not).
- On the side note, I'll be away for two days, so start renaming as fast as you can in a few hours (an attempt at humor). --Ngng (talk) 21:31, 29 November 2016 (UTC)
- What the boxart says won't make me change a title, boxart titles are often up to interpretation(though LEGO is only a small logo on the bottom left, exactly how and where (co-)publishers usually print their logo). I started looking into it because the title on the side of the box (where the full title is usually written) and the information on the back cover/disc do not mention LEGO as part of the title either. I then found that both the developer and LEGO itself also mention the game without LEGO in the title(unlike some other games), which prompted me to change it.
- On the side note, thanks for alerting the spammers ;).--FlatOut (talk) 23:00, 29 November 2016 (UTC)
- The only title(s) that should matter is the one that shows up in the game itself. Everything else is irrelevant bullshit. The only title(s) I can guarantee you the developers wrote themselves (and therefore is what the developers intended and not some mistake from a retarded part-timer at the publisher) is the title on the main screen of the game. For example, some people think Kingdom Hearts II Final Mix is called Kingdom Hearts II Final Mix+ because that's the name on the box art, but that's incorrect. Kingdom Hearts II Final Mix+ is not the name of any game, it's the name of a product, that product being a 2-for-1 package of Kingdom Hearts II Final Mix and Kingdom Hearts Re:Chain of Memories.
- As far as Soccer Mania is concerned, LEGO is definitely not part of the game's title. That's a logo in the box art. Here's actual in-game footage of the intro of the game, where you can clearly see the word LEGO and the words "Football Mania" as far away as humanly possible from each other: https://www.youtube.com/watch?v=5CJumdKhVNw
- "I believe there is no such thing as a correct title. The closest you can get is the most widely used one" There is such a thing as a correct title, and it's not necessarily the one that's most widely used. In the case of the official title, it's not about what you believe, it's about what is. Karasuhebi (talk) 16:20, 3 December 2016 (UTC)
- I fancy myself a tolerant and a calm person (probably self-deceivingly) but you are trying really hard to wear my nerves thin. In what way this discussion was addressed to you? Could you please refrain from answering to my messages in the future and troll on the forums instead, I'd like some peace... --Ngng (talk) 17:03, 3 December 2016 (UTC)
I'm not saying the issue is invalid, I'm saying the solution to it is generic enough that it doesn't need to be on a specific game's page. If not we'd have the same exact issue and solution for all games with upscaling issues. See what I'm getting at? -Karasuhebi (talk) 15:32, 19 September 2016 (BST)
The issue is just not as generic as you think and neither are the solutions. You have to look for the solution for each individual game and can't just apply the same generic solution to all games with upscaling issues(otherwise that fix would likely be on by default anyway). This also means that the affected games do need to have the issue reported on the wiki page, so everyone can easily resolve the issue for the game they're playing. - FlatOut
Thanks for making worthwhile edits to the wiki, that info about the issues and their workarounds is definitely useful. This wiki needs more people like you to add in actually PCSX2-related things to the wiki. Keep it up! Karasuhebi (talk) 15:54, 3 December 2016 (UTC)
I wonder, are they really necessary? I mean it's sorta obvious from the cover itself whether it's PAL/NTSC if anyone checks out the full version image. It would probably look cleaner if we just leave the caption part empty maybe. Unless it's absolutely a must-have in there :P -- Ryudo (talk) 22:37, 12 December 2016 (UTC)
- They're not necessary as far as I'm concerned. I usually do keep 'em if there's a distinct difference between the covers of different regions. But instead of leaving the caption part empty, I'd personally rather see the captions removed from below the covers, and added as tooltips. - FlatOut
- True. Something like this you mean? (Don't mind the sizes)
- (Hover mouse over cover for tooltip)
- Or visible by default;
Core2 vs Core 2
It's definitely Core 2, not Core2. I assume it's because of the 'TM' thing maybe that some sites list it as Core2 while the majority lists it as Core 2 again, not sure. In the end it really doesn't matter I guess.
- Some sites, like perhaps Intel.com?
- I don't understand you guys. Why is of any importance how you prefer writing things? GSDX or GSdx, Core 2 or Core2, Lilypad or LilyPad, 2.9 GHz or 2.90 GHz (oh, my!). This is not even a grammar to be a grammar nazi. This is insane! --Ngng (talk) 21:24, 14 December 2016 (UTC)
About Nano Breaker
- Thanks for the video. It seems there's a difference between versions. The Software glitches seem slightly different too. - FlatOut
Renderer vs Mode
Hey so Ref told me he talked you about this and explained that they're renderers, not modes. Why are you reverting my edit? :( I understand it says mode in certain places, but in certain other places it says renderer, and to add to that we know they're supposed to be called renderers. So why not just call them what they are and worry about having them change the wording in PCSX2 as well so it's correct instead of worrying about having the wiki match the incorrect terminology in PCSX2? :) -Karasuhebi (talk) 19:49, 30 January 2017 (UTC)
- I know what they are and as I told him and you at the time that is not how it works in PCSX2. The user interface when changing or modifying the renderer options uses Hardware and Software mode. Renderer in that capacity is only used in passing references outside of the GSdx GUI. You can change it here once it has been fixed in a current stable release.
Blood Will Tell
- I merely cleared up and fixed the issues, to make sure all users can recognise and find the solutions they need without having to look up what it means or search for the location of the option they need to change.--FlatOut (talk) 18:51, 31 January 2017 (UTC)
- I don't know how that fixed minor issue got set to serious. If it is fixed though (without needing to change to Software Mode or modify another setting from the default setting), you should add that it has been fixed in the latest stable v1.4.0 or if it was fixed more recently in recent v1.5.0 builds. The issue I removed was not a game specific issue. All games suffer from pixelation when upscaling to some degree, Bilinear (Forced) is not really a solution. Some people prefer the pixelation, other people like the slightly blurred look of the Forced option. It's something that can be added as a preferred setting to a test report, not an issue.
- See the difference for yourself. This seemed game specific enough to me as I never encountered something like it in another game. Also I marked it as a note instead of a an issue for exactly that reason.
- That does look like a more specific issue. It doesn't look like it's just a texture filtering issue. Can you share multiframe GS dump of the issue(hold CTRL + SHIFT + F8 for 1-3 seconds when the issue is visible)?
- Thanks for the dumps. It's as I suspected based on the screenshots, the upscaling doesn't have an affect for (most of) the game. I've added a new issue for the game with your suggested workaround.