Author Topic: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]  (Read 288067 times)

0 Members and 1 Guest are viewing this topic.

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
...does Windows allow direct access to this, or does it attempt to block direct modification of the compatibility reg path?  MS might block it to try to deter people from relying on legacy settings instead of updating their programs to use user profile specific (instead of machine-wide) reg paths.

 

Offline m!m

  • 211
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
It worked on my machine for quite a long time with both Windows 7 and Windows 10 but now it suddenly stopped. The problem isn't that reading the compatibility path fails but that reading the "old" path fails.

 
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
Ok, wxLauncher SERIOUSLY needs a way to distinguish between game controllers in Windows. Doesn't matter if it's a Logitech Wingman Extreme 3D Pro or a Madcatz Xbox 360 controller, all it says is Microsoft PC-joystick driver. ARGH! I should not have to switch out game controllers completely to avoid hassle with figuring out which one is the stick and which the gamepad.
There are only 10 kinds of people in the world;
those who understand binary and those who don't.

 

Offline m!m

  • 211
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
:nervous: Well, that problem has already been "fixed" for antipodes/SDL2 builds but the old builds require using the old API which is currently broken. Antipodes should be merged soonTM so then that issue will be fixed for most users...

 
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
Well that's good. I mean, I knew which one it had to be because of the order they had been plugged in, but if I leave them plugged in and I reboot, who knows which will initialize first? I look forward to the upcoming code merge and fixed behavior.
There are only 10 kinds of people in the world;
those who understand binary and those who don't.

 

Offline m!m

  • 211
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
In my experience the order stays the same even after a reboot but that may have changed in newer Windows versions.

  

Offline CT27

  • 210
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
Which is the better one to use:

.10.1 in this thread

or

0.11.0 in http://www.hard-light.net/forums/index.php?topic=89162.0

 

Offline m!m

  • 211
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
If you are using 3.7.4 final then 0.10.1 is sufficient. If you want to use a recent nightly then you should use 0.11.

 

Offline CT27

  • 210
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
Oops, then.

When I saw the newer number I installed 0.11  (and I'm using 3.7.4 final).

However, I haven't run into any problems yet.  Should I delete 0.11 and switch back to 0.10.1?

 

Offline m!m

  • 211
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
No, keep the newer version.
What I meant was that if you have 0.10.1 installed and if you are only using 3.7.4 then you don't need to change that. However, due to changes in how FSO interacts with the launcher the recent nightlies require 0.11 in order to work correctly.

 

Offline Trivial Psychic

  • 212
  • Snoop Junkie
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
I've been keeping up with updates to both FSO and the launcher, and I've noticed a few updates to the launcher today that seem somewhat significant.  May I suggest that a new build might be in order?
The Trivial Psychic Strikes Again!

 

Offline Mars

  • I have no originality
  • 211
  • Attempting unreasonable levels of reasonable
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
So this has started happening whenever I try to launch FSO via WXLauncher, and I can't figure out why.

[attachment deleted by admin]

 

Offline Iss Mneur

  • 210
  • TODO:
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
Please try it with the debug build posted in the OP and paste bin the log as described in the OP under troubleshooting.
"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 Mars

  • I have no originality
  • 211
  • Attempting unreasonable levels of reasonable
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]

 

Offline Iss Mneur

  • 210
  • TODO:
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
I don't see a failure in that log.  Did the assertion box come up on this run?
"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 Mars

  • I have no originality
  • 211
  • Attempting unreasonable levels of reasonable
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
Ultimately I got these dialog boxes and total crash on launch attempt

[attachment deleted by admin]

 

Offline Mars

  • I have no originality
  • 211
  • Attempting unreasonable levels of reasonable
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
<etc>

[attachment deleted by admin]

 

Offline Mars

  • I have no originality
  • 211
  • Attempting unreasonable levels of reasonable
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
I have also tried disabling Aviria Active protection, which I had assumed to be the cause.

 

Offline Iss Mneur

  • 210
  • TODO:
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
Please try this build.
"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 Mars

  • I have no originality
  • 211
  • Attempting unreasonable levels of reasonable
Re: RELEASE: wxLauncher 0.10.1 beta [Updated 2015/09/26]
!!! It works. Do you need anything from me to figure out why?