Launcher Not Loading with ESO64.EXE

Utildai · March 2016

When you click on the 64b client to load the game, it doesn't load the launcher... I am assuming this will cause issues with patching? Would we need to run the 32b client first, let the launcher patch, close it then load the 64b version?

UrQuan · March 2016

Any time you run the game directly from the exe it doesn't load the launcher. This is regardless of whether you open the eso.exe or the eso64.exe so you need to actually open the launcher in order to patch. You don't have to run the 32 bit client - just open the launcher.

Xendyn · March 2016

Just use the launcher for patching and .exe for playing.
I haven't used the launcher except patch day in over a year.

Utildai · March 2016

So, I would need to run the Bethesda.net_Launcher, let the game patch, close the launcher then start the 64b Client? I am reading you correctly?

UrQuan · March 2016

Utildai wrote: »

So, I would need to run the Bethesda.net_Launcher, let the game patch, close the launcher then start the 64b Client? I am reading you correctly?

Yup, you've got it.

Xendyn · March 2016

yep and once it's patched, you don't have to use it again until another incremental or hotfix comes in.
I just made a shortcut on desktop for the .exe

Utildai · March 2016

Thanks a lot guys... never really tried a game this way.

Nestor · March 2016

Utildai wrote: »

So, I would need to run the Bethesda.net_Launcher, let the game patch, close the launcher then start the 64b Client? I am reading you correctly?

Yep. You don't patch all that often. Also, on patch days, I pull the Launcher up, set my PC to not go to sleep. This way the game patches while I am at work and I can come home and start playing right away. Then I use a shortcut to the exe to launch the game.

It also stops me from watching the patcher which is right down on the list with watching paint dry as not fun to do. In fact, it also stops me from messing with the launcher while it is patching. Which like paint, is not something you want to mess with while it is doing it's thing.

Khaos_Bane · March 2016

Nestor wrote: »

Utildai wrote: »

So, I would need to run the Bethesda.net_Launcher, let the game patch, close the launcher then start the 64b Client? I am reading you correctly?

Yep. You don't patch all that often. Also, on patch days, I pull the Launcher up, set my PC to not go to sleep. This way the game patches while I am at work and I can come home and start playing right away. Then I use a shortcut to the exe to launch the game.

It also stops me from watching the patcher which is right down on the list with watching paint dry as not fun to do. In fact, it also stops me from messing with the launcher while it is patching. Which like paint, is not something you want to mess with while it is doing it's thing.

Having the launcher not launching the correct .exe or at least optionally on the screen is either intentional or complete laziness on the Dev's part.

I cannot see how this would be a design oversight, nobody could miss something so obvious.

UrQuan · March 2016

Nestor wrote: »

Utildai wrote: »

So, I would need to run the Bethesda.net_Launcher, let the game patch, close the launcher then start the 64b Client? I am reading you correctly?

Yep. You don't patch all that often. Also, on patch days, I pull the Launcher up, set my PC to not go to sleep. This way the game patches while I am at work and I can come home and start playing right away. Then I use a shortcut to the exe to launch the game.

It also stops me from watching the patcher which is right down on the list with watching paint dry as not fun to do. In fact, it also stops me from messing with the launcher while it is patching. Which like paint, is not something you want to mess with while it is doing it's thing.

Unless you're using two-brush wet blending techniques to get a smooth transition from a base shade to a highlight shade. Then you need to act fast and mess with it before it fully dries.

But, um, I guess I can't think of a way to apply that as an analogy to the launcher...

kraxammer · March 2016

Khaos_Bane wrote: »

Nestor wrote: »

Utildai wrote: »

So, I would need to run the Bethesda.net_Launcher, let the game patch, close the launcher then start the 64b Client? I am reading you correctly?

Yep. You don't patch all that often. Also, on patch days, I pull the Launcher up, set my PC to not go to sleep. This way the game patches while I am at work and I can come home and start playing right away. Then I use a shortcut to the exe to launch the game.

It also stops me from watching the patcher which is right down on the list with watching paint dry as not fun to do. In fact, it also stops me from messing with the launcher while it is patching. Which like paint, is not something you want to mess with while it is doing it's thing.

Having the launcher not launching the correct .exe or at least optionally on the screen is either intentional or complete laziness on the Dev's part.

I cannot see how this would be a design oversight, nobody could miss something so obvious.

This ^

I hope ZOS adds the option to open the 64 client on the regular launcher screen soon. That would be nice. For some reason the ESO64.exe shortcut I put on my desk top does not work . . .keep getting the ..."Granny" error. I have to keep going into the ESO program files to launch the 64 client. . . QoL pain in the arse.