8000 Can't find v58, only v56 · Issue #131 · Norbyte/ositools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Can't find v58, only v56 #131

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 “Si 8000 gn 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

Open
jwes11 opened this issue Jul 18, 2023 · 10 comments
Open

Can't find v58, only v56 #131

jwes11 opened this issue Jul 18, 2023 · 10 comments
Labels
bug Something isn't working

Comments

@jwes11
Copy link
jwes11 commented Jul 18, 2023

Operating System

Windows

Extender Version

v56

Game Version

v3.6.117.3735

Bug Summary

Very new to github and modding in general, I cannot find v58 for the script extender, and it is required for a lot of the divinity 2 mods I have downloaded, please help. I download the latest version and it says I am on v56

Links

No response

@jwes11 jwes11 added the bug Something isn't working label Jul 18, 2023
@Norbyte
Copy link
Owner
Norbyte commented Jul 18, 2023

Hi,

The extender auto-updates when you launch the game so it should be on v59 after you start the game once.

@jwes11
Copy link
Author
jwes11 commented Jul 18, 2023

I have launched the game with the script extender twice now?

@jwes11
Copy link
Author
jwes11 commented Jul 18, 2023

It was not installed and launched fine, then with it on it wouldn't load a game and it gave me an error saying 56 is on and I need 58 and it wouldn't launch

@MatejB-N
Copy link

I can also confirm, it doesn't auto-update and stays at version v56. Weirdly enough, if you download an even earlier version of the script extender, it just updates up to v56.

@FACENC
Copy link
FACENC commented Jul 21, 2023

I'm seeing the exact same behavior. Game launches and shows v56 as the version running. No combination of enabling mods, loading game, launching seems to make a difference. I manually downloaded the v59 .package file from as listed in https://dbn4nit5dt5fw.cloudfront.net/Channels/Release/Manifest2.json, but I'm assuming I can't just drop it into the directory to trigger the update. Should I enable some logging in the console or something?

I can confirm I see EoCApp.exe communicating with a cloudfront server when I launch the game and monitor it in Resource Monitor, but I'm never receiving any update.

image

@faketaxibdo1983
Copy link
faketaxibdo1983 commented Aug 13, 2023

Такая же проблеиа

@Yuhiora
Copy link
Yuhiora commented Aug 21, 2023

I'm seeing the exact same behavior. Game launches and shows v56 as the version running. No combination of enabling mods, loading game, launching seems to make a difference. I manually downloaded the v59 .package file from as listed in https://dbn4nit5dt5fw.cloudfront.net/Channels/Release/Manifest2.json, but I'm assuming I can't just drop it into the directory to trigger the update. Should I enable some logging in the console or something?

I can confirm I see EoCApp.exe communicating with a cloudfront server when I launch the game and monitor it in Resource Monitor, but I'm never receiving any update.

image

Hi!
Don't u fix that?

@Norbyte
Copy link
Owner
Norbyte commented Aug 21, 2023

Hi,

What game version are you running?
v58 is only available for game version v3.6.117 above, i.e. non-torrented builds.

@TaynotKelly
Copy link

I've having this issue as well it would seem.
I'm also not able to connect to this extension while loading the game? (Another commenter has also made this claim, and I'm getting the same error message)
Just wondering what I may have done wrong, I'm using the MManager which I thought would make things easier.

@Norbyte

@aelfwyne
Copy link

Similar. Need v60 for PIP, stuck on v59. Have the JSON file in the bin directory that's supposed to tell it to download v60 but it does not update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants
0