Versions 32.0+ give install error. Highest i can install is 31.0

[Guest websterr33]

Hello. I finnally decided to try Baldur's Gate and honestly, im in awe of the level of polish the community and Beamdog
have given to this game. 

About SCS, i tried 32.0, 32.7 and 32.8 - couldnt get them to start. 32.7 and 32.8 install some components but give error in:
"Improved NPC customisation and management"
"Allow player to choose NPC proficiencies and skills"
"Initialise AI components" 

My game version is 2.5.17.0 Siege of Dragonspear from GoG. I tried SCS with other mods installed, tried without any mods, tried even clean BGEE without any expansions and mods - those 3 components giving the same error everytime. This is the debug file https://uploadfiles.io/kq7kwswj of 32.7 with all mods and SoD,

 

 

 

 

 

 

[Guest websterr33]

Figured it out! Turns out my windows is 32bit and i needed to install Strawberry Perl for versions 32.0+ . Works like a charm now, cheers for the great mod.

[Jarno Mikkola]

Or you could just, you know, update your Windows.

[subtledoctor]

You might just want to use v31.  It lacks a few fancy bells and whistles but it was still pretty damn great. 

I recommend the 9/26/18 commit for having some bugfixes and faster install times than the official v31 releases.  I played a game of BG1EE with it, it was fine.  (on the right side, click the green "clone or download" button and download the .ZIP archive.

[Jarno Mikkola]

My bet is that it's an appeal for not needing to use tricks to update ones machine and just use the v31 instead, as it works "best" depending on use case. As the change is horrendous to someone like std.

[subtledoctor]

19 hours ago, Arthas said:

Hey, Is this suggestion merely for the 32 bit question, or do you actually recommend v31 over v32?

I highly recommend using the latest and greatest version available.

If, for whatever reason, someone cannot use v32 and must choose from among the earlier versions, that particular build of v31 is the best that I had used.

When I posted that, I hadn't see the poster mention that they had solved the problem by updating Perl.  If updating one's machine to work with the new versions is relatively easy and painless, then that is certainly the better course of action.