Author Topic: Interface clipping  (Read 443 times)

0 Members and 1 Guest are viewing this topic.

Offline Mars

  • I have no originality
  • 211
  • Attempting unreasonable levels of reasonable
I have no doubt I'm doing something wrong. When I dusted off my Freespace 2 install, and ran the November 3rd nightly at 1080p on my Windows 10 AMD-FX CPUed, 7850 machine, the interface extends beyond the edges of the screen and buttons etc beyond the edge are out reach of the game cursor - which stops at the edge. Screenshots appear to be normal. This applies to all the other 16:9 resolutions and seems to be unrelated to monitor settings. What could I be doing wrong?

EDIT: For some reason it works in 720P,
« Last Edit: November 03, 2015, 09:24:58 pm by Mars »

 

Online AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Do you have DPI scaling enabled by chance?
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 Mars

  • I have no originality
  • 211
  • Attempting unreasonable levels of reasonable
Huh, yes I did and yes it does fix it. Why does it effect SCP and not most other games?

 

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
I think there's a way to have the program handle this correctly, or at least, to request the compatibility option to be flipped for itself, and FSO doesn't have that yet.  At least FSO can now request to use the more powerful graphics card in a multiple graphics card system (like one with an Intel HD and an AMD or nVidia card).