Menu ▾ ▴

#960 Fullscreen is not working properly

v3.1
closed-out-of-date
nobody
fullscreen (3)
Windows
User Interface
2018-05-19
2017-11-18
eddybbr
No

Fullscreen is broken on my system (AMD A8-7600, win10-x64) no matter even I disable or not the dx9 on the video options menu. thx in advance.

1 Attachments
2017-11-18.png

Related

Bugs: #960

Discussion

  • Jon Wegard Eriksen

    Jon Wegard Eriksen - 2017-11-20

    This got broken for me as well on both my laptop and htpc after the Windows 10 Fall Creators Update.

     

  • Adriaan Erasmus

    Adriaan Erasmus - 2017-11-25

    I have a similar problem.

    1. I installed WinVICE-3.1-x86-r34156 dated 2017-11-25 (today).
    2. I run Windows 10 64bit Professional with the creator's update on a DELL Latitude E6540. It has both the Intel HD Graphics 4600 as well as the AMD Radeon HD 8790M video cards.
    3. When I press [ALT]+D to go fullscreen I get the attached screenshot.
    4. I expected the fullscreen to work as it is supposed to.

    I tried to compile the source on Windows with MinGW32 but I can't get the configure script to complete. It fails with: configure: error: X11/Xaw/Tip.h is missing.

    SDL2VICE-3.1 also has a problem with fullscreen mode. Selecting fullscreen from the menu only shows a black screen but [ALT-TAB] back to Desktop and then back to SDL2VICE-3.1 reveals that it complains about the resolution not being optimal for the screen. Changing it to the optimal resolution has no effect.

     

    Last edit: Adriaan Erasmus 2017-11-25
    Thumbnail
    SDL2VICE-3.1.png
    Thumbnail
    WinVICE-fullscreen-issue.png

  • David Dekany

    David Dekany - 2017-11-26

    Same here. There's a workaround though. Right click your x64.exe then click on properties, select the compatibility tab then check the Disable fullscreen optimisations option, then hit apply and you're good to go.

     

    Last edit: David Dekany 2017-11-26

  • eddybbr

    eddybbr - 2017-11-26

    nice find mate, looks like typical fuck up from the M$ motherfuckers,

     

  • Querino

    Querino - 2017-11-27

    fuckup?? common, they call it "fullscreen optimisations".

     

  • compyx

    compyx - 2017-11-29
    • status: open --> closed-wont-fix
     

  • compyx

    compyx - 2017-11-29

    So can we close this as an upstream bug? It's not like we have any Windows devs to fix this stuff.

     

    • Anonymous

      Anonymous - 2017-11-30

      unless you will find a way to disable the win10 fullscreen optimizations (like the gamebar)

       

  • compyx

    compyx - 2017-12-01
    • status: closed-wont-fix --> open-need-info
     

  • compyx

    compyx - 2017-12-01

    Reopening this one, since although the current Win32 port is dead, we might run into the same problem with the new Gtk3 port.

    If someone can explain what the Win10 'Fall Creators Update' changed which broke our Win32 port, that would be much appriciated for our Gtk3 efforts, if that one also borks on the update, which remains to be seen.

     

  • WinstonSmith6079

    WinstonSmith6079 - 2017-12-28

    PROBLEM FIXED

    R-click on any and all VICE .EXEs that you use in fullscreen > Properties > Compatability tab > under Settings, tick the checkbox check ON for Disable fullscreen optimizations > OK, then close your VICE, reopen it again and go to fullscreen, no problem no more hehehehehe

    All thanks for this fix go to compyx @ #vice-dev @ Freenode on IRC! That guy rules, ya know! hehehehehehe

     

  • gpz

    gpz - 2018-05-18
    • Category: x64 --> User Interface
     

  • Michael Martin

    Michael Martin - 2018-05-19

    I've tested the four builds that run under Windows on my PC-gaming system (Win10, GTX 750Ti).

    • Native Win32 port has the problem and solution as described in this thread.
    • GTK3 works fine with no extra massaging.
    • SDL2 works fine with no extra massaging.
    • SDL1 works, sort of, but there's a noticable delay during the transition to and from fullscreen and I strongly suspect that the nVidia driver is doing some extra work behind the scenes to keep aspect correction and the like correct.

    I suspect that there's something Unusually Old-School about how we're going fullscreen in the old WinVICE code. Modern practice says to never actually change the desktop resolution at all, and just fill the screen at its current res with the graphics scaled to fit in that space (which GTK3 VICE does explicitly and SDL2 does under the hood for us).

     

  • Michael Martin

    Michael Martin - 2018-05-19
    • status: open-need-info --> closed-out-of-date
     

Log in to post a comment.

MongoDB Logo MongoDB