Author Topic: Weird Screen Cutoff  (Read 1422 times)

0 Members and 1 Guest are viewing this topic.

Offline Frak_Tastic

  • 26
  • Giggity Giggity Fracker!
Hi Everyone - apologies if this issue isn't specific but my screen resolution seems to be wrong.  My desktop is maxed at 1920 x 1080 (ViewSonic VX 2770 series monitor) and the video card is updated (Radeon 6800 series).  The WX launcher matches these settings, but it's cutting off the bottom of the screen in the game.  I tried changing a few resolution settings in the launcher and the desktop but i can't seem to fix it.

Any ideas?

[attachment DELETED!! by Strong Bad]

 

Offline niffiwan

  • 211
  • Eluder Class
Try setting the resolution in wxLauncher manually.

i.e. add -res 1920x1080 to the Custom flags (advanced settings tab)
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
It might also be (some very slight) DPI scaling; try disabling that if niffiwan's suggestion has no effect.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline Frak_Tastic

  • 26
  • Giggity Giggity Fracker!
Re: Weird Screen Cutoff - Fixed!
The extra flag did the trick, thanks niffiwan!  WIH looks great on the new monitor.

Do either of you think I should make a bug report?

 

Offline niffiwan

  • 211
  • Eluder Class
There's a semi-known issue with Windows 10 & wxLauncher not setting the resolution properly. But there doesn't yet seem to be an official bug report for that on github so it's probably worth reporting it there.
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...