search

AdrianG130 / glidehqplusglitch64

Automatically exported from code.google.com/p/glidehqplusglitch64
0 stars 0 forks source link

wrong screen position #310

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Play any game in fullscreen with aspect ratio 4:3

What is the expected output? What do you see instead?
The top of the screen is missing. There is a black bar at the bottom.
On screenshots the top is not displayed correct. (screenshot2)

What version of the product are you using?
Glide64WIP_r269 Project64 1.6
I am using a widescreen monitor

Please provide any additional information below.
This is a regression. It is correct with Napalm WX release 1 (screenshot1)
screenshot3 shows the game with Glide64WIP_r269

Original issue reported on code.google.com by rato...@gmail.com on 8 Dec 2011 at 11:33

Attachments:

GoogleCodeExporter commented 8 years ago 
Did it occur to you maybe this is your monitors fault?

Original comment by ExtremeD...@gmail.com on 8 Dec 2011 at 2:13

GoogleCodeExporter commented 8 years ago 
I have this issue only with glide64. Other plugins work correct (Napalm WX 
release 1 included ==> screenshot1). Maybe there are problems with support of 
widescreen monitors.

Original comment by rato...@gmail.com on 8 Dec 2011 at 5:40

GoogleCodeExporter commented 8 years ago 
When it works with the first release, I think not

Original comment by WC-Preda...@web.de on 8 Dec 2011 at 5:40

GoogleCodeExporter commented 8 years ago 
Please test it. Has somebody here got a widescreen monitor?

Original comment by rato...@gmail.com on 8 Dec 2011 at 5:51

GoogleCodeExporter commented 8 years ago 
Any specific game that has noticeable truncation at the top in fullscreen mode.
I don't have this issue.

What is the window and fullscreen resolution that you select and your desktop 
resolution?
Problem with 4:3 aspect ratio and no problem with  16:9?
What about stretch?

Original comment by pokefan0...@gmail.com on 8 Dec 2011 at 7:28

GoogleCodeExporter commented 8 years ago 
16:9 works correct because there are black bars at the top and at the bottom.
With stretch it is the same as 4:3.
window resolution: 800*600
fullscreen resolution: 1680*1050
desktop resolution: 1680*1050

Original comment by rato...@gmail.com on 8 Dec 2011 at 9:44

GoogleCodeExporter commented 8 years ago 
Whether there is black bar at the top or bottom is not the problem as it 
depends on the resolution you choose for windowed and fullscreen mode.
It will be an issue if certain portion of the display image get truncated.

To test your so called 4:3 issue, use 1024x768 for both windowed and fullscreen 
resolution in the Glide64 settings tab.  Attach screenshot of the same image in 
windowed and fullscreen mode and tell us the difference.

Original comment by pokefan0...@gmail.com on 9 Dec 2011 at 12:55

GoogleCodeExporter commented 8 years ago 
Read the FAQ question on "How to get rid of black side bars surrounding image 
display?"
https://sites.google.com/site/1964mod/home/faq

Original comment by pokefan0...@gmail.com on 9 Dec 2011 at 7:51

GoogleCodeExporter commented 8 years ago

Original comment by gon...@ngs.ru on 9 Dec 2011 at 10:36

GoogleCodeExporter commented 8 years ago 
I found out that this issue causes other issues if Hardware FBE is disabled
==>issue 244
I have attached images to prove this:
for some reason the animation is visible at the top. The damaged part is 
exactly the same as the damaged part inside the screen. I think this causes the 
issue with the damaged textures too. In Zelda OOT the top of the menu and 
Link's portrait are damaged too.
Just to satisfy pokefan, I add the images in 1024x768.

Original comment by rato...@gmail.com on 9 Dec 2011 at 2:21

Attachments:

GoogleCodeExporter commented 8 years ago 
I don't see any black bars in your latest screenshot.
I can't see any truncation that you mention earlier about windowed and 
fullscreen mode or 4:3 aspect.
All your screenshot are different scene - which is windowed or fullscreen?

Since Gonetz has accepted this issue, I am sure he will fix your issue.

Original comment by pokefan0...@gmail.com on 9 Dec 2011 at 5:00

GoogleCodeExporter commented 8 years ago 
The 4th one is windowed
The last one is fullscreen - look at the top

Original comment by rato...@gmail.com on 9 Dec 2011 at 6:53

GoogleCodeExporter commented 8 years ago 
The best way to compare is to take a windowed and fullscreen screenshot at the 
exact same spot.  Looking at 2 different spot, I do not see any truncation at 
the top.  Also, there is no black bars as you have said with 4:3 aspect ratio.

Original comment by pokefan0...@gmail.com on 9 Dec 2011 at 11:27

GoogleCodeExporter commented 8 years ago 
as already mentioned the truncation is not visible on screenshots but the top 
of the screen is damaged

Original comment by rato...@gmail.com on 10 Dec 2011 at 9:21

Attachments:

GoogleCodeExporter commented 8 years ago 
Let me show you how to do proper screenshot - use window screen print of the 
entire emu window and copy to paint.  If there is corruption, it will be 
captured - see my screenshot.

Obviously, I don't have problem with DKR in windowed or fullscreen.
Also, if you have read the FAQ that I point you to read, you will probably 
understand how to get rid of black side bars if you choose the correct 
resolution that matches your aspect ratio or use stretch - obviously some black 
side bars will still be there as explained in the FAQ.

Original comment by pokefan0...@gmail.com on 10 Dec 2011 at 10:58

Attachments:

GoogleCodeExporter commented 8 years ago 
Please stop that discussion. I accepted the issue. It was introduced with r224. 
You may use glide3x.dll from a release prior r224, e.g. this one 
http://code.google.com/p/glidehqplusglitch64/downloads/detail?name=Glide64_r214.
rar&can=2&q= , until I fix that issue.

Original comment by gon...@ngs.ru on 10 Dec 2011 at 11:02

GoogleCodeExporter commented 8 years ago 
Does anybody else has that problem? 
I can't reproduce it anymore, so I need a tester.

Original comment by gon...@ngs.ru on 13 Dec 2011 at 10:25

GoogleCodeExporter commented 8 years ago 
Fixed by r276.

Original comment by gon...@ngs.ru on 15 Dec 2011 at 9:54