Author Topic: Help Please?  (Read 4087 times)

0 Members and 1 Guest are viewing this topic.

So I downloaded the game, having never played it, and it...doesn't really work.
I load in, and the screen si shifted incredibly far to the right! The start menu words are at the very right side of the screen, slightly clipped.
I can make it into settings, and the resolution seems to be set to a 5;4 ratio on start up, for some ungodly reason, though my default screen resolution is 1920/1080.
I can change the screen resolution in the settings...but the screen is shifted too far for me to click "accept" or whatever is over there (I've never seen over there, so I'm not exactly sure what it says). I can tell it to default, which turns the resolution to a mildly more respectable ratio, but, again, I cannot actually accept changes.

 
This is a known issue. When you have desktop magnification active in Windows, FSO will be scaled up; You will need to right-click on the fs2_open executable, go to properties, open the Compatibility tab, and check the "Disable display scaling on high DPI settings" checkbox.

If it doesn't help:
Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

 

Offline niffiwan

  • 211
  • Eluder Class
I think JickOShadows is talking about MCO, not FSO :)
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...

 
Yes, I was referring to MCO. I apologize for not specifying.

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Yes, I was referring to MCO. I apologize for not specifying.
Posting in the MCO forum was specification enough; you didn't do anything wrong.

Some people just look at "all unread topics" and don't notice where the thread was posted; it was an honest mistake.

That being said, you could try disabling DPI scaling and see if it works for MCO, too.
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.

 
Ok, I will try that. Thanks guys.

  
Sweet! That DID work!
Thanks a lot guys!
Sorry I asked a question that was already answered. I had looked before posting, but hadn't seen that fix.

 
Hehe, I shouldn't write when I am tired. :p