-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Text rendering broken in Tactics Ogre: Let Us Cling Together by default for all builds since v0.7.6-1383-g856fe3e (updated, a.k.a Games that may have issues with Mipmapping ON by default) #2286
Comments
http://report.ppsspp.org/temp/recent/game/ULUS10565_1.00 Other games potentially with this/similar issue: -[Unknown] |
That's a whole lot of games that could be broken in the list. I think I'll make a quick edit to reflect that. |
eaede89 still doesn't do the trick, unfortunately, for Tactics Ogre. |
@solarmystic actually, it does fix some textures, like the buttons during name selection. But it seems the actual letters, the value is 0x100001, which seems to mean fixed at 1.0. Darn. If I treat this the same as 0, it actually works, but per some posts on the forum it sounds like these mipmap levels are abused for font characters or something... -[Unknown] |
You're right, i didn't notice it before, and i check it again. Here's an observation. If you turn on Mipmapping prior to starting the game, select New Game, and head to the Name Entry screen after you won't see any letters and such but turning it off makes it reappear. That's the current behaviour. If you start the game without mipmpaaping however, and then head to the Name entry screen and then, turn ON mipmapping, the letters do NOT disappear. Even after you repeatedly turn it on and off. Wonder why. Behaviour exhibited in 1508. |
It's really weird. I reverted the "fix" for now until it can be investigated more as raven02 reported that it broke something. |
Well, I think that changing the setting doesn't clear the cache, but it does affect what mipmapping is used, so that's why it seems to partially apply during runtime. -[Unknown] |
Issue has been resolved with v0.8.1-648-g88685b0 88685b0 Closed. |
(UPDATE 1:- Potentially others too, see http://report.ppsspp.org/temp/recent/kind/99, thanks @unknownbrackets )
Issue is as stated above. Last build not to have this issue is v0.7.6-1381-gffb1d65 by default.
Tested using the 32bit Orphis build on Windows 7 64 bit, with the following specs:-
Intel Core 2 Duo t9550 @ 2.8 GHz
AMD/ATI Mobility Radeon 4670 1 GB
8 GB DDR3 RAM
Problem repro:-
Solution:-
v0.7.6-1383-g856fe3e and all builds since then have Mipmapping set to ON by default 856fe3e , which wasn't the case in previous builds which had it OFF by default. So the issue never manifested itself and remained undetected.
Disable Mipmapping and the issue will be fixed for now until the problem can be identified and rectified in code.
Mipmapping OFF in the same build:-
Logfile:-
http://pastebin.com/4m0e29VT
The text was updated successfully, but these errors were encountered: