22 réponses à ce sujet

[Arkalezth]

I'm copying a post from Axe_Edge on the BGR thread. I though it should have its own thread for reference:
 

Axe_Edge wrote...

"-home" added to a copy of your NWN2 shortcut is the answer.

The new shortcut tells the game to create, and to use, a separate and CLEAN NWN2 directory within "Documents" or "My Documents".  This new NWN2 directory can be named what ever you want.  Each directory created this
way (using different shortcuts) is its own entity.  No need to worry about overrides conflicting between modules/PWs.  It is crazy simple and fast.


1)  Make a copy of your NWN2 shortcut

2) In the properties of the new shortcut, change the shortcut's "Target" to whereever you want, including different drives.  My BGR install is:

"E:\GAMES\Neverwinter Nights 2\NWLauncher.exe" -home "F:\NWN2Mods\NWN2BGR"

- My game is installed within my E drive, this first part will not be changed (before -home).  I want the game to use the directory "NWN2BGR" within my F drive for haks, modules, overrides, saves, etc.. when I use this new shortcut (this is the part you add, starting with -home)

- What is NWLauncher.exe?  I use Skywing's Client Extension, as you should

- Quotation marks are correct

- There is a space before and after -home

3)  I like to rename the shortcut as it appears on my desktop.  The new shortcut is called "BGR"

4) Start NWN2 using the new shortcut.  The game will create the new directory and will put all the default folders/files it needs within, including the setting files with default settings.  The size of this clean directory is only about 5 mb.

5)  Shutdown NWN2.

6)  Install the Baldur's Gate Remake files into the new folder.

7) If you don't want to reset all of your favorite settings manually, copy/paste "nwn2.ini" and "nwn2player.ini" from your favorite install and into the new directory


Now, start NWN2 with the new shortcut "BGR" and it will use the new directory "NWN2BGR" for play.  The original install is not touched.  If you want to play the original game from the original NWN2 shortcut, go ahead, the game will not access the new directory.
 
I do this for every different mod and PW I have.  I have about 20 different NWN2 shortcuts.  Each mod/PW has its own shortcut/directory.  Keeps things very clean and without conflicts.

A note about PWs.  This works for them as well.  Just create the new directory using the new shortcut, start the game with the new shortcut, log on the PW, and the ADL will download to the new directory.

Using Kaldor Silverwand's  "NWN2 OC Makeover SoZ Edition" requires a little extra care.  This excellent mod make a change in the Program files\NWN2\CAMPAIGN folder, which is at a higher level than Documents\Neverwinter Nights 2

Pain has a better explanation, but I can't find it readily, at this moment.


Another example is a shortcut I used for a MOTB runthrough where I used Kaedrin's PRC , I used the following shortcut target:

"E:\Games\Neverwinter Nights 2\nwn2main.exe" -home "F:\NWN2Mods\MOTBKaedrin"

Modifié par Arkalezth, 22 décembre 2015 - 12:26 .

[Arkalezth]

I've been trying this method and it works like a charm. My only gripe is that you can't share certain folders (override, portraits...), which are sometimes big, between all the modules. If there is any way to have, for instance, a "centralized" portraits folder, I'd like to know about it. I tried using shortcuts, but unsurprisingly, that didn't work.

BTW, if anyone can think of a better title than "Installing modules separately", I'm open to suggestions.

Modifié par Arkalezth, 19 juin 2013 - 01:58 .

[painofdungeoneternal]

If instructions say program files\\....\\nwn2\\whatever, then you can change them to my documents\\nwn2\\whatever for just about every case. ( basically based on what i was told by Grinning Fool during the 1.23 beta, this applies globally regardless of authors instructions and only has a few exceptions (ie the fonts xml file for one ) and this is something i've done a lot of research/testing regarding )

If you do the campaign folder the only bug is there is two campaign folders visible, by adjusting scripts and other files in it to see which was running, I was able to determine that regardless of which is used it uses the files in the player folder. I could not find any issues beyond that.

Of course do this at your own risk - the author of OC Makeover does not support this, and if you want his changes globally applied then you'd want to put it in program files. If there is an issue which there could be, you should move that campaign folder to program files and retest the issue before reporting it ( because you are not following the authors instructions ).

But that being said, the fact you have never touched your original files and all changes are in a new folder means that any issues are isolated to that given folder, thus meaning no author can wreck your install or affect another authors work.

( for centralized, put the folder in program files OR adjust nwn2.ini for the folder location, and put in an absolute path, might also be able to use a symlink/shortcut type of thing )

Modifié par painofdungeoneternal, 19 juin 2013 - 06:49 .

[Arkalezth]

Thanks, I'll try that later.

(To be clear, I've no plans to use the Makeover personally. Just using this method for other community modules.)

[Tchos]

The pasted instructions seem to have lost the backslashes (\) in the file paths in the examples of what the shortcuts should look like. If anyone tries copying them from that example, they wouldn't work. Also, the later bit referring to the Makeover incorrectly uses forward slashes (/) in the file paths (forward slashes are used in web addresses, backslashes are used in Windows file paths). As an instructional reference post, those should be corrected.

[Kaldor Silverwand]

Arkalezth, you wound me

So, I have nothing against this method and would probably use it myself except that I always play using the Makeover because I don't enjoy NWN2 without it. And because the Makeover is installed where it is it is highly compatible with other mods for the OC and MotB without interfering with independent campaigns or modules the way that mods installed in the override folder do.

I do think that expecting typical users to use this method though is unrealistic. It isn't user friendly enough.

Regards

[painofdungeoneternal]

Tchos wrote...

The pasted instructions seem to have lost the backslashes () in the file paths in the examples of what the shortcuts should look like. If anyone tries copying them from that example, they wouldn't work. Also, the later bit referring to the Makeover incorrectly uses forward slashes (/) in the file paths (forward slashes are used in web addresses, backslashes are used in Windows file paths). As an instructional reference post, those should be corrected.

It's actually platform specific, so if you are on mac it's one way, windows the other. I adjusted my post regardless. ( most mac folks i imagine are using wine in some fashion or bootcamp anyway )

Modifié par painofdungeoneternal, 19 juin 2013 - 06:51 .

[Tchos]

Thanks for that info, Pain. I'm not familiar with Mac pathing convention.

I also see that since the backslash also disappeared from the line you quoted, but not in my original post, that it has something to do with the quoting. That means that to fix it in Ark's original post, the instructions may have to be taken out of the quote block unless there's some special formatting that can get around the stripping. Maybe enclosing the path lines with the [ code ] tags.

[painofdungeoneternal]

Slashes usually are "/" forward slash, generally the web, unix, everywhere except DOS it's the standard.

The backslash "\\" is used for escaping things in programming -- ie slash-n is a new line.

testing -- \

going into bbcode, entering & # 9 2 ; ( no spaces )
problem is that if you edit it again, it goes away

Modifié par painofdungeoneternal, 19 juin 2013 - 08:34 .

[Arkalezth]

Kaldor Silverwand wrote...

Arkalezth, you wound me

Heh, I have nothing against the Makeovers, but I doubt I'll be playing the official campaigns again.

I hadn't noticed the lack of slashes; I'll fix that. I also had to fix the format... Crappy forums.

Edit: I think it's all fine now.

Modifié par Arkalezth, 19 juin 2013 - 09:04 .

[Tchos]

Ark: Yep, all's fine now.

Pain: Yes, of course I don't dispute what are standards in any other system. I only wanted to make sure it shows a correct Windows path.

[Axe_Edge]

Arkalezth wrote...

If there is any way to have, for instance, a "centralized" portraits folder, I'd like to know about it. I tried using shortcuts, but unsurprisingly, that didn't work.

(horns deploy)

Hey Ark, if you feel like getting crazy wicked,  you can place a "symbolic link" (essentially, a fancy shortcut) within a new override folder that references a folder with all of your stuff in it.  A copy of this "symbolic link" can be put into other override folders.  A program doesn't realize the Sym Link is a shortcut.

I've used it with Windows XP and 7 (and still do).  Needs to be NTFS.  I use the command prompt to create the "symbolic link", with the junction (/J) parameter, but directory (/D) may be used.  Try not to put Sym Links within Sym Links.  The command line structure is:

MKLINK [[/D] | [/H] | [/J]] Link Target

Relatively easy/quick to make, just takes a bit of study.  As you know, plenty of great folks here.

Good luck 

(Contemplates closing the can of worms, but they look too tasty)


An example of the rabbit hole:

mklink /j "C:\\Users\\Games\\Desktop\\Dropbox\\NWN2\\ExampleWorking\\override" F:\\GAMESF\\NWN2Mods\\NWN2Example\\override

Any change I make within the override on the F: drive will be reflected in the override on the C: drive. This is how I get changes backed up to dropbox automatically (the dropbox folder is on my desktop).  Technically, quoates only needed when there are spaces within the path.

Modifié par Axe_Edge, 26 juin 2013 - 12:46 .

[Arkalezth]

I just ended up moving my "shared stuff" (mainly the portraits, as the override sometimes changes depending on the module) to the Program Files folder. I usually try to stay away from that folder, but I don't think a few portraits are going to mess anything up.

Thanks for the info anyway. It looks a bit more complicated than the solution I used, but it's good to have it for reference.

[painofdungeoneternal]

( note that Never Launcher supports -home folders, and even the creation of shortcuts via windows script host, which I am not sure is on every system, still not totally where this makes sense to me usability wise, but it does have support for people doing this. )

[Arkalezth]

I have installed several modules this way, but I'm experiencing some strange stuff lately: Sometimes, if I create a folder for a module which name has more than one word (i.e. "Subtlety of Thay"), somehow the game creates an alternative one with just one word ("Subtlety").

When this happens, I need to move all the files to this new folder in order to play - I can't start any non-official campaigns or modules otherwise - or get any override/UI mod to work.

I didn't have this problem with the first few modules I installed with this method, but now it seems to happen all the time. It's just a minor annoyance, but does anyone know why this is happening, or how to solve it?

[painofdungeoneternal]

You have to quote a path with a space in it, not quote a path without a space.

[Arkalezth]

I'm not sure of what you mean. The path's structure is the same as in other modules.

For example, the path "C:\\Games\\NWN2Mods\\Pool of Radiance Remastered" works, but "C:\\Games\\NWN2Mods\\Baltrons Beacon", or "C:\\Games\\NWN2Mods\\Subtlety of Thay" don't. They all have the same structure and spaces.

[kevL]

i wonder if there's an underscore or some sort of 'non printing' character in those paths

In the shortcut, you could try typing them out by hand, or copying them in straight from the windows Explorer address bar

[painofdungeoneternal]

In never launcher, if there is a space when making the command line, i have to add in spaces. If there is no spaces i do not quote. That seems to work, not doing so either does not work, or has unexpected results. ( i am pointing this out since my program to a degree assembles the path so it can launch the given module )

( note the following is from memory based on the command you provided )
E:\\GAMES\\Neverwinter Nights 2\\NWLauncher.exe -home C:\\Games\\NWN2Mods\\NWN2BGR

E:\\GAMES\\Neverwinter Nights 2\\NWLauncher.exe -home "C:\\Games\\NWN2Mods\\Subtlety of Thay"

To make this simpler you can remove the spaces from the path, or use underscores. You also should not use any wonky characters, but nothing here looks wonky.

You can also use my program ( never launcher ), check the debugging checkbox, browse to the given folder where it says player folder, and then hit play. A text file will open in my app holding the path used to start NWN2. This should be properly escaped so it will just work. ( note that i use the "start" command as well since that seems to allow more control, but the part after -home should be usable in a short cut )

If you have windows script host installed ( most do from what i understand ), you can hit save shortcut as well and it will make a short cut for you on your desktop, which should setup the quoting correctly. Of course if you don't that windows script host, it won't do anything. ( which is why my app is still a beta until i figure out other means to create shortcuts without a dependency like that )

Modifié par painofdungeoneternal, 08 juillet 2013 - 05:42 .

[Axe_Edge]

Hey, Ark.

In short, although spaces are ok when using quotes, it may be best to avoid spaces.  I don't use spaces when I create directories.  I do capitalize each word for readability. The names of the shortcuts, themselves, have spaces.


1)
I tested this and it worked great:

"E:\\GAMES\\Neverwinter Nights 2\\NWLauncher.exe" -home "E:\\GAMES\\NWN2Mods\\Test Space Module"


2)
I tested this separate shortcut, which did not work (of course):

"E:\\GAMES\\Neverwinter Nights 2\\NWLauncher.exe" -home E:\\GAMES\\NWN2Mods\\"Test Space Module two"


3)
I changed the target of the same shortcut back to the correct format, and it didn't work. The game kept starting, then, would become stuck. I noticed on the taskbar NWN2 was listed as running from a directory on my F: drive (coincidentally, the first directory in alphabetical order in my NWN2Mods directory, on the F:). The target of the shortcut pointed to the E: drive.  I used this target:

"E:\\GAMES\\Neverwinter Nights 2\\NWLauncher.exe" -home "E:\\GAMES\\NWN2Mods\\Test Space Two"


4)
I tried this format, which I figured wouldn't work:

"E:\\GAMES\\Neverwinter Nights 2\\NWLauncher.exe" -home "E:\\GAMES\\NWN2Mods\\"Test Space Module Three"


5)
I changed the target of this same shortcut to this, with the correct format, and it still didn't work:

"E:\\GAMES\\Neverwinter Nights 2\\NWLauncher.exe" -home "E:\\GAMES\\NWN2Mods\\Test Space Module Three"


6)
I created a brand new shortcut and changed the target. The game started and created the folders and files in the new directory.  I was unable to start a new campaign, due to none being listed. I looked into the nwn2.ini files in the new directory. Behold, the nwn2.ini was not completed. the nwn2.ini file only had the sound options within:

"E:\\GAMES\\Neverwinter Nights 2\\NWLauncher.exe" -home "E:\\GAMES\\NWN2Mods\\Test Space Module Four"

Seems like something keeps tabs on the shortcuts and/or directory names (possibly in RAM) and confused the game with like named directories. When I started NWN2 with other shortcuts, the game started correctly.  I use the CE and maybe it keeps track.  If the CE does, by no means is it a bug.

I generally do not use spaces within file and directory names, out of habit caused by programming with the old UNIX, Banyan, Novell, COBOL etc... standards decades ago. (whew, has it been decades, already?) 

Modifié par Axe_Edge, 08 juillet 2013 - 07:21 .

[Arkalezth]

Well, thank you all. I might experiment a bit with it tomorrow, but I guess I'll have to stay away from spaces from now on, just to be safe.

[Tchos]

For anyone reading this now, the forum has overcorrected on the display of backslashes, and is now showing double-backslashes where there should only be single ones.

[Arkalezth]

For anyone reading this now, the forum has overcorrected on the display of backslashes, and is now showing double-backslashes where there should only be single ones.

Ugh. Fixed the issue in the original post; thanks for the heads up.