HLP Network

News:

HLP Donations Page has been reworked for supporting the site.
Please note that the previous "Tiers" are currently not operational (but will be worked on).
You can still cancel any previous re-occurring donations to make new ones which will go to the new Treasurer Admin (Zacam).

 
« Previous Thread Next Thread »
Print
Pages: [1]   Go Down

Author Topic: No Help/Play button in wxLauncher  (Read 1732 times)

0 Members and 1 Guest are viewing this topic.

Offline malakas13

  • 21
No Help/Play button in wxLauncher
on: August 23, 2016, 10:38:40 am
So installed everything manually (FS2 GOG, FS2 open 3.7.4, wxLauncher), configured everything in the launcher and everything went smooth.

Next day boot up pc, start launcher but no play button appears: http://i.imgur.com/Df51fTL.jpg

I reinstalled the launcher and play button pops up again. But then same thing today, play button is gone again.

Any suggestions? Thanks.
 

Offline urielsd

  • 23
    • Minecraft
    • Skype
    • Steam
Re: No Help/Play button in wxLauncher
Reply #1 on: August 23, 2016, 11:41:34 am
Is your DPI set to 100% in Windows? If not, try this reboot pc and verify if the Play button appears once again.
 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: No Help/Play button in wxLauncher
Reply #2 on: August 23, 2016, 01:52:12 pm
What resolution is your desktop?
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 malakas13

  • 21
Re: No Help/Play button in wxLauncher
Reply #3 on: August 23, 2016, 02:31:07 pm
Quote from: urielsd on August 23, 2016, 11:41:34 am
Is your DPI set to 100% in Windows? If not, try this reboot pc and verify if the Play button appears once again.

Apparently that did the trick, thanks!


Although the dpi were already set at 100% (smaller) I had to set 125% and then back to 100%.

 

Offline urielsd

  • 23
    • Minecraft
    • Skype
    • Steam
Re: No Help/Play button in wxLauncher
Reply #4 on: August 24, 2016, 03:46:49 pm
Glad I could be of help.  :yes:
It would be nice if the launcher handled different DPIs correctly, though  :rolleyes:
 

Offline Iss Mneur

  • 210
  • TODO:
Re: No Help/Play button in wxLauncher
Reply #5 on: August 24, 2016, 06:59:29 pm
Quote from: urielsd on August 24, 2016, 03:46:49 pm
It would be nice if the launcher handled different DPIs correctly, though
Yep :)
"I love deadlines. I like the whooshing sound they make as they fly by." -Douglas Adams
wxLauncher 0.9.4 public beta (now with no config file editing for FRED) | wxLauncher 2.0 Request for Comments
 

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: No Help/Play button in wxLauncher
Reply #6 on: August 25, 2016, 07:06:02 am
Writing DPI-Aware Desktop and Win32 Applications (MSDN)

From my skimming of the article, it seems it is possible to set the application as non-DPI aware, and let Windows automagically handle everything (wouldn't work on XP though)?
  

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: No Help/Play button in wxLauncher
Reply #7 on: August 26, 2016, 12:46:11 am
Quote from: jr2 on August 25, 2016, 07:06:02 am
From my skimming of the article, it seems it is possible to set the application as non-DPI aware, and let Windows automagically handle everything (wouldn't work on XP though)?
The application should already be set as non-DPI-aware.
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.
Print
Pages: [1]   Go Up
« Previous Thread Next Thread »