http://bugs.winehq.org/show_bug.cgi?id=24124
Summary: Warcraft 3: window resolution cannot go more than 1370x751 in window mode Product: Wine Version: 1.3.1 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl AssignedTo: wine-bugs@winehq.org ReportedBy: gufide_g@yahoo.ca
Created an attachment (id=30364) --> (http://bugs.winehq.org/attachment.cgi?id=30364) This is my terminal output
Just in the title, if I go more than that, it just don't fill farther.
My configuration is: 1.9 Ghz 1366x768 screen nvidia 8200mg
I used -opengl and -window in my launcher
http://bugs.winehq.org/show_bug.cgi?id=24124
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|opengl |-unknown Summary|Warcraft 3: window |Warcraft 3: window size |resolution cannot go more |cannot go more than |than 1370x751 in window |1370x751 in window mode |mode | Severity|normal |minor
http://bugs.winehq.org/show_bug.cgi?id=24124
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #1 from Wylda wylda@volny.cz 2010-08-27 09:20:39 ---
Can't confirm. I have native res & windowed res set to 1900x1200 and warcraft 3 offers me resolutions up to 1600x1200x32 and 1600x1200x16. I also try to lower my KDE resolutions, but always behaved correctly. Isn't there a typo in your resolution (1366 vs 1360)?
Works OK in all the following versions: * 1.3.0, 1.3.1, 1.3.1-221-gf6bcd27
nVidia GT240, v195.36.31 Debian Squezee 32bit
http://bugs.winehq.org/show_bug.cgi?id=24124
--- Comment #2 from Guillaume gufide_g@yahoo.ca 2010-09-01 16:35:08 CDT --- but did you try it in windowed mode? It happen only on it. I try on another screen (1440x900) and again, I have around to 35 empty pixel, only on window mode. I set warcraft 3 to my native resolution.
http://bugs.winehq.org/show_bug.cgi?id=24124
--- Comment #3 from Wylda wylda@volny.cz 2010-09-01 16:45:49 CDT ---
Yes, i tried that in windowed mode and then also in full screen mode.
http://bugs.winehq.org/show_bug.cgi?id=24124
--- Comment #4 from Guillaume gufide_g@yahoo.ca 2010-11-02 19:47:34 CDT --- (In reply to comment #3)
Yes, i tried that in windowed mode and then also in full screen mode.
But do you put warcraft 3 in window mode opengl with the force fullscreen of compiz? This is not a true fullscreen: warcraft 3 run in windowed mode, but you compiz force the window to be stretched and take your screen entirely. This was a little bit different, because that not happen in the true warcraft fullscreen, with opengl or directx. What I said is to get a window (not in fullsceen) at the size of the screen. I try this also on 1440x900. That happen again, about to 10 of non-existing pixel... I made a screenshot that describe the bug: http://img6.glowfoto.com/images/2010/11/02-1742114410L.png
http://bugs.winehq.org/show_bug.cgi?id=24124
--- Comment #5 from Guillaume gufide_g@yahoo.ca 2010-11-02 19:49:37 CDT --- oups! image here: http://www.glowfoto.com/viewimage.php?img=02-174211L&rand=4410&t=png... reply to comment #4)
(In reply to comment #3)
Yes, i tried that in windowed mode and then also in full screen mode.
But do you put warcraft 3 in window mode opengl with the force fullscreen of compiz? This is not a true fullscreen: warcraft 3 run in windowed mode, but you compiz force the window to be stretched and take your screen entirely. This was a little bit different, because that not happen in the true warcraft fullscreen, with opengl or directx. What I said is to get a window (not in fullsceen) at the size of the screen. I try this also on 1440x900. That happen again, about to 10 of non-existing pixel... I made a screenshot that describe the bug: http://img6.glowfoto.com/images/2010/11/02-1742114410L.png
oups! image here: http://www.glowfoto.com/viewimage.php?img=02-174211L&rand=4410&t=png...
http://bugs.winehq.org/show_bug.cgi?id=24124
Lance lancerdot@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lancerdot@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=24124
--- Comment #6 from Lance lancerdot@gmail.com 2011-02-01 21:50:16 CST --- I had a very similar problem in 25651 and posted a fix there. :)
http://bugs.winehq.org/show_bug.cgi?id=24124
--- Comment #7 from Guillaume gufide_g@yahoo.ca 2011-02-02 07:18:55 CST --- Created an attachment (id=33102) --> (http://bugs.winehq.org/attachment.cgi?id=33102) here's my screenshot
http://bugs.winehq.org/show_bug.cgi?id=24124
Guillaume gufide_g@yahoo.ca changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #33102|here's my screenshot |screenshot of the bug description| |
http://bugs.winehq.org/show_bug.cgi?id=24124
--- Comment #8 from butraxz@gmail.com 2013-08-05 12:32:40 CDT --- This ticket has not been updated for over 900 days. Development recommends to check the status on your bug every release or two and let to be known if the bug is still present. If not, mark it fixed.
Is this still an issue with 1.7.0 or higher ?
http://bugs.winehq.org/show_bug.cgi?id=24124
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #9 from Ken Sharp imwellcushtymelike@gmail.com --- Three years, no reply.
https://bugs.winehq.org/show_bug.cgi?id=24124
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Austin English austinenglish@gmail.com --- Closing.