Page 1 of 1

Why do these lines show up at the bottom of the game?

Posted: Mon Aug 12, 2013 10:12 pm
by Taran
The game starts out fine then a few minutes into it this line will show up at the bottom of the game.
I am using the latest version of the Emulator.
Here are some screenshots of what happens.

Also...is this the best version of the emulator? I never had these issues in 1.52..so was wondering if maybe another version was still prefered over this one.
You have to open the image in a new tab btw to see the line im talking about.
Interesting thing also.
When this happens in a game it seems to copy the top of the screen and put part of it at the bottom in the form of the line right?
Well when i keep the emulator on and just go to file and start a different game completely that line stays..with the previous games image. So the line does not go away..or even copy the new game into the image..but actually keeps the old games image in the new game...if you see what i am talking about.

Re: Why do these lines show up at the bottom of the game?

Posted: Tue Aug 13, 2013 2:51 am
by DaveTheMan
Un-Check Maintan Aspect Ratio

Re: Why do these lines show up at the bottom of the game?

Posted: Wed Aug 14, 2013 4:14 am
by Taran
If i uncheck that the game stretches way to far and fills my whole screen...making the image blurry and and throwing the image way off. Playing with ratio on makes the game look way better. I think i found the issue. Its because Chrono Trigger has that black bar at the bottom of the screen in combat areas. Does not happen in the menu and world map. In games that do not have the black bar i have no issues.
The issue is fixed quickly by saving on a save state then loading. Takes about a second to do all that so its not a big deal.

Re: Why do these lines show up at the bottom of the game?

Posted: Thu Aug 15, 2013 1:20 am
by BearOso
That's leftover garbage on the texture brought into visibility through bilinear filtering. It's a pain, but it's certainly possible to get rid of it. It might be handled in the latest snapshot, but if not, OV2 should be able to fix it.