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

its safe to say where not getting an updated version #15

Open
AsheX1 opened this issue Feb 15, 2024 · 4 comments
Open

its safe to say where not getting an updated version #15

AsheX1 opened this issue Feb 15, 2024 · 4 comments

Comments

@AsheX1
Copy link

AsheX1 commented Feb 15, 2024

title

@LifeWulf
Copy link

Sadly I'd have to agree.

@Klemci
Copy link

Klemci commented Apr 12, 2024

24 February 2024
https://www.nexusmods.com/talesofarise/mods/5

Q@:
There are at some side quests in the DLC story where you would need to talk to someone. Once the conversation ends, it goes into an infinite loading screen. It seems they all happen in Viscint, weirdly enough.

@A:
Any chance you could test this INI with it and see if it lets them work ?:
https://pastebin.com/zTQ6FwTy

Q@A:
I was able to complete the quests that go into an infinite loading screen with your test INI file on v30.

@Klemci
Copy link

Klemci commented Jul 12, 2024

Someone found about value to set recently (Nexus last answwer of the INI topic):

Specifically, the issue is with the MinimumNPCDistance setting, that's what causes the issue. All of the others work fine. The maximum value I was able to set for MinimumNPCDistance while making sure that it would never cause the infinite loading screen was 6153 - it was different for each quest but talking to Lagill on the streets of Viscint during the quest Relaxing Residence while being stood as close to the city gates as possible is what required the lowest value. It doesn't seem to be linked to any specific NPC, at least not one that's visible or interactable in normal play. Values of 6153 and 6154 had the same NPCs loaded in, but 6154 would cause an infinite loading screen while 6153 would not. The only thing that seems to be in roughly the right location to be at the threshold of that distance was actually the fast travel point - maybe that has something to do with it?

In any case, it might be worthwhile setting the default value to 6153, or even round down to something like 6000 to make it cleaner and be 100% safe, just so that people don't experience any gamebreaking bugs. Then add a note to the .ini stating that a value that low is only necessary for some side quests in the DLC.

@Klemci
Copy link

Klemci commented Jul 17, 2024

DLC done, no crash, with 6150 set (tho).

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

No branches or pull requests

3 participants