Launcher reverts to 4.0 as Default Engine

Development Getting Started & Setup
, , , ,
1

Everytime I try to launch the engine with the launcher, it always selects 4.0.2. I want to use 4.2.x and when 4.3 comes out, I’ll want to use that. Is there a way to set the default engine so that it doesn’t keep resetting to the wrong one? Its very irritating.

2

Hi awilliams1702,

Hmm, sorry about that. It should remember the last engine you have launched and select that by default each time you run the Launcher.

Are you using the drop-down selection on the left side bar, and then hitting the launch button for it? Or are you following a different flow?

Thanks,
Leigh

3

Its the drop down. It resets back to 4.0.2 every single time I launch the launcher. I haven’t touched 4.0.2 since 4.1 came out and likewise I haven’t touched 4.1 since 4.2 came out.

4

Ok, that definitely sounds like a problem then :). I’ll investigate this, could you provide some files for me if that’s ok?

Logs; Please zip up the full Logs folder and attach:
C:\Users\USERNAME\AppData\Local\UnrealEngineLauncher\Saved\Logs

Saved Config; Please attach Game.ini
C:\Users\USERNAME\AppData\Local\UnrealEngineLauncher\Saved\Config\Windows\Game.ini

After doing this, you could try a couple workarounds if you like which may work:-

  1. Uninstall other engines that you do not use, if possible.
    or
  2. Manually edit the above Game.ini file to set your Active app:
    [UnrealEngineLauncher]
    ActiveAppName=UE_4.2

Thanks,
Leigh

5

Update: this is still an issue even with 4.3. It still defaults to 4.0.x.

I can’t do the whole logs folder as its too big for the maximum upload, but here is the game.ini file (I added an extra .txt because .ini was rejected)
link text

6

You know its strange. I was just looking at my game.ini file and it shows
ActiveAppName=UE_4.3
which is correct yet is still goes to 4.0.x However I also see this and wonder if this is the issue:
LastUsedAppName=UE_4.0: Production-Windows

7

I manually changed everything to 4.3 that was 4.0. It made no difference.

8

Hello,

I apologize that this did not receive a full answer before. Is this still occurring for you? If so, I will reopen the investigation and assign a new technician to look into the cause. For now, I am marking it as answered, but if you respond we can reopen the investigation.

Cheers!