You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
okay so basically its been a more common issue recently but some players have this folder structure: titanfall2/r2northstar/r2northstar
why this happens? no idea. possibly messed up manual install, but they all seem to be around version 1.6 (a couple hours after writing a version of this happening on 1.17 happened) so it could be related to that as well? dont have a clean version myself to look at
basically what happens is titanfall2 has a new, working northstarlauncher.exe and northstar.dll. titanfall2/r2northstar has everything thats new, and working fine, but also acts as the "root" folder for the nested install, meaning it has a old .exe and .dll.
because northstar now checks for .dll files inside of profiles, launching the new, 1.17 .exe from the titanfall2 folder that looks for profile r2northstar, which then finds the old .dll inside of there, and loads the old 1.6 mods from titanfall2/r2northstar/r2northstar/mods instead of the new, working 1.17 mods from titanfall2/r2northstar/mods
removing titanfall2/r2northstar/northstar.dll (the old version) and launching the same .exe as before, northstar launches 1.17 properly
if, instead, we just move new updated northstar.dll to profile directory (aka r2northstar here), this solves this from happening in the future (and could showcase the ability to interchange .dll files with profiles better)
i think the most this affects are the build instructions where the .dll would need to be placed in its own profile, but im more than happy updating build.md myself accordingly if this gets changed
Loading DLL from profile dir is not possible with R2Northstar/NorthstarLauncher#451
We should move DLL now already cause apparently some players have an old nested install which now causes the old version of Northstar to be loaded.
The text was updated successfully, but these errors were encountered: