Screen at incorrect resolution?

[mrbicrevise]

When opening a screen like this (or 1024x768):

Code: Select all

OpenScreen(1440, 900, 32, "Screen")

I noticed that rendered objects weren't showing up properly, so I used this to find out what was going on:

Code: Select all

a = MouseX()
b = MouseY()
StartDrawing(ScreenOutput())
DrawText(0, 0, "X = "+Str(a))
DrawText(80, 80, "Y = "+Str(b))
StopDrawing()

and found that the screen is only displaying something like 960 pixels in width; the rest is all off the right side of the screen. The same is true of hight. Is this likely simply to be a quirk of my monitor, or is there some way of correcting the x and y in OpenScreen() to get the full 1440x900 actually displayed on the screen?

[Demivec]

When opening a screen like this (or 1024x768):

Code: Select all

OpenScreen(1440, 900, 32, "Screen")

I noticed that rendered objects weren't showing up properly, so I used this to find out what was going on:

Code: Select all

a = MouseX()
b = MouseY()
StartDrawing(ScreenOutput())
DrawText(0, 0, "X = "+Str(a))
DrawText(80, 80, "Y = "+Str(b))
StopDrawing()

and found that the screen is only displaying something like 960 pixels in width; the rest is all off the right side of the screen. The same is true of hight. Is this likely simply to be a quirk of my monitor, or is there some way of correcting the x and y in OpenScreen() to get the full 1440x900 actually displayed on the screen?

It's a limitation of your video card. It seems that OpenScreen() is choosing the next best size to match what you requested.

Here's a quote from the manual under OpenScreen():

Width and Height should be standard combinations: 640*480, 800*600, 1024*768...

To find out what your card supports use ExamineScreenModes(), you can read in the manual to get some examples.

You can also Use OpenWindow() then OpenWindowedScreen to setup up a screen that is non-standard but is not full-screen.

[Rook Zimbabwe]

Have you tried this (from the CHM!)

Code: Select all

;
; ------------------------------------------------------------
;
;   PureBasic - Desktop example file
;
;    (c) 2004 - Fantaisie Software
;
; ------------------------------------------------------------
;

NbDesktops = ExamineDesktops()

MessageRequester("Information", "You have "+Str(NbDesktops)+" desktop(s)")

; Let's enumerate all the desktops found
;
For k=0 To NbDesktops-1
  
  Text$ = "Desktop n°"+Str(k+1)+#LF$+#LF$
  Text$ + "Size: "+Str(DesktopWidth(k))+"*"+Str(DesktopHeight(k))+#LF$
  Text$ + "Color depth: "+Str(DesktopDepth(k))+#LF$
  
  If DesktopFrequency(k) = 0
    Text$ + "Frequency: Default"+#LF$+#LF$
  Else
    Text$ + "Frequency: "+Str(DesktopFrequency(k))+" Hz"+#LF$+#LF$
  EndIf
  
  Text$ + "Name: "+DesktopName(k)
  
  MessageRequester("Information", Text$)
  
Next

To show what you have...

If you have nVidia be aware that though many modes are shown... there is "cheating" on nVidias part... sometimes... Stick to the more sane screen resolutions and you should have no real trouble.

[mrbicrevise]

Thanks guys - I used ExamineScreenModes() as you suggested, and got a list of all the supported resolutions, which includes my desktop resolution of 1440x900x32 @ 60Hz. However, this problem is happening on 1440x900, 800x600, 1024x768 and even that most lowly of resolutions, 640x400. Is there any way outside of using a windowed screen for me to get resolutions displaying properly?

(Ill-informed P.S.: could this problem be an issue with the software not compensating for my monitor’s wide aspect ratio? Or would that not make any difference?)

[Rook Zimbabwe]

OK silly question... what Monitor are you using? Have you checked your focus?

And yes... wide aspect is going to be a bigger and bigger issue in the future!

[mrbicrevise]

It's the 17" Wide XGA integrated into my laptop. And I'm afraid you've lost me with focus - thereafter my knowledge withers.

[mrbicrevise]

Although according to wikipedia:

"1440×900 resolution displays have also been found labeled as WXGA; however, the correct label is actually WSXGA or WXGA+."

...

[Rook Zimbabwe]

focus: to widen or narrow the screen to insure that ALL the image fits...

on a monitor it is those little widen and squeeze buttons that make sure you see ALL the window...

But widescreen is going to force some DX issues as well as game issues...

Are you using VISTA?

Have you tried to run my H3x game (Announcements Section) and if so... what do you see?

[mrbicrevise]

I'm running XP home. I've just tried your game, which is working fine, nothing's running off the side of the screen. Whatever you did there works for me, apparently!

[Demivec]

focus: to widen or narrow the screen to insure that ALL the image fits...

on a monitor it is those little widen and squeeze buttons that make sure you see ALL the window...

But widescreen is going to force some DX issues as well as game issues...

Are you using VISTA?

Have you tried to run my H3x game (Announcements Section) and if so... what do you see?

Focus wouldn't affect a laptop display. It would only affect a CRT.

[mrbicrevise]

Btw, could I see the OpenScreen() part of your H3x source? I can't figure out why that screen opens fine and mine won't.

[Demivec]

Btw, could I see the OpenScreen() part of your H3x source? I can't figure out why that screen opens fine and mine won't.

Perhaps you are experiencing a problem with the bit depth.

[mrbicrevise]

Nope, same thing happens for 32 and 16 bit depth.

[Demivec]

Nope, same thing happens for 32 and 16 bit depth.

You mentioned in your first post that you could read Mouse positions that were higher than the dimensions visible on the screen...is that correct? That would imply it the difficulty was related to your screen itself. The mouse coordinates would only show what was in the dimension of the screen that was opened.

If on the other hand, the mouse cordinates shown were smaller than the sizes in the OpenScreen() that would imply a software problem because your hardware is already displaying that size of screen for your desktop. Perhaps Fred can answer this question for you if that is the case and you could make a bug report.

To confirm your suspicions find others with screens that are similar to yours, in the forum, and have them test your code. You can also modify your code to draw a border around your screen (with lines) then run your code and do a screen capture by pressing "Prt Scr", exiting your program and pasting the image into your drawing program. You can then check the dimensions of the image to the one you saw displayed. If the image in the drawing program is the size you requested then the problem I suspect is outside of PureBasic and probably in the hardware or OS (especially if you're using Vista).

[mrbicrevise]

Thanks for the advice. I've been playing around with it, and it seems that while the images are displaying at the correct resolution, the mouse pointer isn't representing it. My guess would be that the image has been squashed to fit the wide aspect, but this has thrown off the mouse pointer somehow, if that sounds in any way plausible? In any case, I've clipped the mouse to the screen edges now, and hopefully it won't cause any major problems*.

* - Famous last words...