4 replies to this topic

[MegaBopper]

Greetings,

My son asked me to set him up to run Mechwarrior online on our family computer after he saw me running it. He is a different user than me and wants to set up his own account so hopefully this is allowed. Our family computer runs Windows 7 Home Premium. Mechwarrior online runs just fine from my administrator ID that I installed it on. I have made sure that all of the necessary file permissions are in place so that it should run from any administrator level ID. All of the patches that have shown up to date have been successfully applied as far as I know.

Knowing that the client has to work in administrator mode I tried running the client from his Win 7 userid in administrator mode. It seems to hang in some kind of loop after we try to run the front end launcher and will not even proceed to the front end GUI to play the game.

After that failed I tried setting up a separate clean new administrator level userid to see if there was just something wrong in my son's account that caused the problem. The same failure occurred.

I am new to the game myself and do not have sufficient technical expertise in Windows 7 to be able to do more than simple administration and fixing.

Sorry if this is the wrong place to post this but I did not find a general problem support forum so please be kind?

Is anyone able to please help?

(Title edited by author on 11-24-2015 to reflect that a workaround has been found.)

Edited by MegaBopper, 24 November 2015 - 01:29 PM.

[Tarl Cabot]

The issue is likely the default install directory which installs the game under your windows user name. The game needs to be installed into a general location, eg c:\games\MWO

I would also suggest in the future installing games in a similar location to prevent issues.

Edit, the default location which can cause issues

C:\Program Files (x86)\Piranha Games or C:\Program Files\Piranha Games

But ever since Vista OS, any game installed by default into said location, which are then copied over and all future updates patched relocated to a virtual location for windows security purposes, something like c:\users\windows acct name\appdata\etc...

For regular programs that is okay but for games, especially online games that are always being updated/patched can cause all sort of issues. This was a major issue for SOE games and they took them almost a year, trying different locations until they settled on a default location and it was no longer Program Files folder.

Edit
An example
old C:\Program Files(x86)\Daybreak Game Company\Installed Games\EverQuest II

New C:\Users\Public\Daybreak Game Company\Installed Games\EverQuest II


I do hope that PGI review their default installation location, as it will save lots of headaches down the road.

Edited by Tarl Cabot, 20 November 2015 - 07:26 PM.

[MegaBopper]

Thank you for the reply.

I originally installed the game at "F:\Games\Piranha Games\Mechwarrior Online". The permissions are set for the entire directory tree so everyone has full access. Is there anything else that could cause this?

Best Regards

[Ironwithin]

MegaBopper, on 20 November 2015 - 09:43 PM, said:

Thank you for the reply.

I originally installed the game at "F:\Games\Piranha Games\Mechwarrior Online". The permissions are set for the entire directory tree so everyone has full access. Is there anything else that could cause this?

Best Regards

You should try your luck with the actual support staff. Just hit them up with an e-mail roughly outlining the problem and pointing to this thread.

[MegaBopper]

A workaround has been found for this issue:

After reading the post @ http://mwomercs.com/forums/topic/196531-launcher-fails-to-launch/page__view__findpost__p__4400626, we found a "Piranha Games" key tree under "HKCU/Software" in the registry using my ID but missing from my son's ID. We exported this group and reimported it into the "HKCU/Software" group under my son's Windows 7 ID. The problem with the front end launcher failing to run appears to have been resolved. We are still testing but so far have not found any issues that appear to have been caused by making this change.

Apparently when the game is installed this key group is only generated on the installing user's ID and even though users must run in administrative mode and all of the necessary permission keys are in place for both the files and the registry this key group is not generated when other users attempt to run the game on their own user ID's. I don't know if this is by design or represents a bug but this workaround appears to be working O.K. for us so far.

If we find anything further that is relevant to this issue we will further update this thread.

Best Regards

(Edited by author to add link to source of information used to do this workaround)

Edited by MegaBopper, 24 November 2015 - 01:45 PM.