Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move NorthstarDLL to profile dir #522

Open
GeckoEidechse opened this issue Jul 22, 2023 · 1 comment
Open

Move NorthstarDLL to profile dir #522

GeckoEidechse opened this issue Jul 22, 2023 · 1 comment

Comments

@GeckoEidechse
Copy link
Member

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.

@itscynxx
Copy link

itscynxx commented Jul 22, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants