|
Your continuous donations keep RPGWatch running!
RPGWatch Forums » Comments » News Comments » NWN2: Mask of the Betrayer - Installation Tips & Hotfix

Default NWN2: Mask of the Betrayer - Installation Tips & Hotfix

October 1st, 2007, 15:28
We mentioned the Mask of the Betrayer hotfix in passing in the nearby newsbit about NWN2 but Sei Daneic wrote in to point out this thread on the official forums and it's probably worth highlighting:
When installing MoTB, please use the following instructions:

1. Install NWN2
2. Patch NWN2 to the latest version (1.10 as of Sept. 29, 2007)
3. Install Mask of The Betrayer
4. Download and apply the hot fix for your language, listed below.

Italian: Click Here
French: Click Here
German: Click Here
English: Click Here
Spanish: Click Here

If you do not apply the hot fixes, when you attempt to play the game you will see sections of missing text and the Campaign name will say it is undefined.
More information.
Dhruin is offline

Dhruin

Dhruin's Avatar
Watcher
Super Moderator
RPGWatch Team

#1

Join Date: Aug 2006
Location: Sydney, Australia
Posts: 11,964

Default 

October 1st, 2007, 15:28
Gonna add my 2 cent here:

Actually, instead of patching to 1.10, patch to the 1.06 and then proceed to install MoTB is the best way to go. No need for the hot fix either.

It worked for me and looks like it worked for people at QT3 too.

So far the game is running great, the stories and dialogs so far are great. Visually MoTB looked better than the OC to me for some reason, and performance is definitely better than the OC. I think my only disappointment right now is that gensai have rather crappy stats for a wis or cha based class And the camera control takes a little bit getting used too.

For those struggling with the camera, I found that in the Character mode, max out the camera rotation delay when you turn, and use the "hold LMB and drag" to turn the character and the camera worked best.
leth is offline

leth

leth's Avatar
Watchdog

#2

Join Date: Oct 2006
Posts: 205

Default 

October 1st, 2007, 16:27
I don't have MotB yet but the new patch certainly makes the game run a lot smoother.
woges is offline

woges

woges's Avatar
SasqWatch
RPGWatch Team

#3

Join Date: Oct 2006
Location: UK
Posts: 2,110

Default 

October 1st, 2007, 19:34
That's odd, all I have read so far says this is wrong.
Patching to 1.10 before installing MotB is what is giving everyone the error ("CAMPAIGN NAME NOT SET"), even reported in Watch forums, iirc.

Trust me, most of the names I have been called you can't translate in any language…they're not even real words as much as a succession of violent images.
Acleacius is offline

Acleacius

SasqWatch

#4

Join Date: Oct 2006
Posts: 2,491

Default 

October 1st, 2007, 19:36
I dunno … I just installed with whatever patch I had on the game, which I had last touched in ~June. Everything seems to work fine.

— Mike
txa1265 is offline

txa1265

txa1265's Avatar
SasqWatch

#5

Join Date: Oct 2006
Location: Corning, NY USA
Posts: 11,326

Default 

October 1st, 2007, 22:22
To get the strategy mode camera working like in vanilla NWN2, just set it to always center on active character. It'll rotate normally.
Prime Junta is offline

Prime Junta

RPGCodex' Little BRO

#6

Join Date: Oct 2006
Posts: 8,540

Default 

October 1st, 2007, 23:35
My understanding was that MotB has all the patch content up to and including 1.10 and should install straight over a vanilla NWN2 installation. Still, I guess they stickied this for a reason. *shrug*

-= RPGWatch =-
Dhruin is offline

Dhruin

Dhruin's Avatar
Watcher
Super Moderator
RPGWatch Team

#7

Join Date: Aug 2006
Location: Sydney, Australia
Posts: 11,964

Default 

October 1st, 2007, 23:39
That's odd, all I have read so far says this is wrong.
Patching to 1.10 before installing MotB is what is giving everyone the error ("CAMPAIGN NAME NOT SET"), even reported in Watch forums
As I understand it Patching to 1.10 before installing MoTB gets you all the fixes to the original campaign, but mucks up MoTB. Whilst not patching leaves you with a potentially borked original campaign — triggers not firing when you get the first shard and things — but a working MoTB, as least in the 'didn't patch at all' case.

I think the worry on Obsidians part if you have patched to somewhere before 1.10, installed MoTB and seem to have a working game, is that the version number has now become the expansion version number, but you won't *necessarily* have the version of all the files that they'll expect for that version number when you apply future patches going forward. Therefore they'd would prefer everybody to have everything that MotB didn't change at 1.10.

I believe the way they screwed up the 1.10 patch was by not backdating at least one of the essential files to before the datestamp on the expansion version, so the MoTB installer looks at that file , says 'oh, that's newer than the one I'm trying to replace it with, I don't need to bother' because 1.10 datestamp is after the expansion went gold, even tho' actually it really does.

The Hotfix sorts out those specific files. That's guesswork on my part tho'.

Making the whole patching system for NWN2 that they inherited from NWN1 work seems to have generally been giving Obsidian fits.

NOTE TO DEVS WRITING GAME AUTO-PATCHING SYSTEMS: I suggest a system where patch diffs are always taken from the original release game rather than incrementally, and are retained after patching on the users machine. When a new patch is received, the autopatcher first reverts the users installation to the original by reversing out the changes using these retained diffs before appling the new patch. It would then delete the old patch diffs, and retain the new patch diffs ready for the next patch.
SKapusniak is offline

SKapusniak

SKapusniak's Avatar
Traveler

#8

Join Date: Jun 2007
Location: Edinburgh
Posts: 18

Default 

October 2nd, 2007, 01:26
Originally Posted by SKapusniak View Post

NOTE TO DEVS WRITING GAME AUTO-PATCHING SYSTEMS: I suggest a system where patch diffs are always taken from the original release game rather than incrementally, and are retained after patching on the users machine. When a new patch is received, the autopatcher first reverts the users installation to the original by reversing out the changes using these retained diffs before appling the new patch. It would then delete the old patch diffs, and retain the new patch diffs ready for the next patch.
I can understand the sentiment SKap but the problem with constantly reverting is that the patches end up being huge.

In NWN1 Bioware always posted a Critical Rebuild type of patch which essentially did this and they are quite large now. This isn't always practical on the Auto-Updater system.

Developer of The Wizard's Grave Android game. Discussion Thread:
http://www.rpgwatch.com/forums/showthread.php?t=22520
Lucky Day is offline

Lucky Day

Lucky Day's Avatar
Daywatch

#9

Join Date: Oct 2006
Location: The Uncanny Valley
Posts: 3,173

Default 

October 2nd, 2007, 11:11
I simply installed MotB over NWN2 1.06, worked like a charm.
Maylander is offline

Maylander

SasqWatch

#10

Join Date: Oct 2006
Location: Bergen
Posts: 5,289
Send a message via MSN to Maylander
RPGWatch Forums » Comments » News Comments » NWN2: Mask of the Betrayer - Installation Tips & Hotfix
Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT +2. The time now is 03:54.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
Copyright by RPGWatch