A Night in the Pub Feb. 27/02 - by epithumia
BR4ZIL on 11/6/2023 at 22:57
Found the problem, the DML Script from your post differs from the one in the DML fixpack.
I used the one from here (copy pasted the script into a txt in the FM folder) and thus came across the problem.
After i changed it to the one in the DML Fixpack, its now working!
baeuchlein on 11/6/2023 at 23:38
Looks like the real problem is not the DML, but loading
NVScript.osm.
As BR4ZIL correctly found out, there are two different DMLs available. The older one seems to have been published on April 24th, 2018, and is still found in the newest T2FMDML package that is shipped with the latest version of T2Fix, v1.27e. The newer one is the one posted here on October 7th, 2021.
Both DMLs address the problem with the hideout goal (it was reversible, so if one climbed up and down the ladder for all eternity, the objective would always turn off and then on again). The newer DML, however, does this in a different way than the old one; the newer one needs NVScript loaded to work. When I remove
nvscript.osm from the osm folder of my Thief 2 installation, and then use either the new DML alone, or both in combination, the "hideout goal" does not tick off when going to the bottom of the ladder into the hideout. If I only use the older DML in T2FMDML, and
nvscript.osm is still not present, the objective nevertheless ticks off when reaching the bottom of the ladder.
My
Thief2.log (in the game folder) says that a
nvscript.osm of version 1.2.8.0 from August 15th, 2021, is being loaded. We need to find out what happens with BR4ZIL's Thief 2 installation. I would suspect that either, no NVScript is loaded at all, or maybe an older one for some reason - I don't know what version is required for the newer DML to work. v1.2.8 most likely is the one shipped with T2Fix v1.27e, and as I said, that one does work for me.
BR4ZIL, please start the mission with the newer DML again, then check whether there is a file called
Thief2.log in your Thief 2 game folder after that. If so, open it with some reader or text editor, and search for the word "nvscript". Many readers/editors will allow you to input a search string so that the reader/editor does the searching. Lazy people like me prefer this approach to another approach where the user has to search for text with his/her own eyes.:p
If you find a line beginning with
Code:
: Loaded script module "nvscript.osm"
you should also see something mentioned like
which is the version number of NVScript.
If such a line is
not present at all, NVScript was not loaded. If the line is present, but the version is below 1.2.8.0 (=1.2.8), then most likely the version loaded is too old for the newer DML to work.
And if
Thief2.log is not present at all, then I hope someone knows why it's not there, for I wouldn't.:confused:
Let's see what we find out about NVScript in BR4ZIL's Thief 2 installation.
BR4ZIL on 12/6/2023 at 00:09
@baeuchlein
It seems i have no nvscript.osm at all, i got this on my Thief2.log:
Quote:
Failed to load script module "nvscript.osm" (error code 126)
I downloaded nvscript 1.3.0 and placed it on the FM's folder, the new DML posted here in the thread now works too!
I guess "nvscript.osm" should somehow be included in the DML pack? or maybe pointed it out here in the post.
baeuchlein on 12/6/2023 at 00:34
Well, NVScript.osm is included in T2Fix releases, but installation of it is optional, as far as I know. The option should be called "Common script modules", but it might be present only in the "T2Fix with mods" package.
In ancient times, when the world was still young, the "Thief" game just a new kid on the block, and dinosaurs still roamed the planet, new FMs needing NVScript, tnhscript, and other scripts, usually stated this in the FMInfo.txt file, but it was up to the user to make sure the scripts were present. Late on, it became somewhat standard to put the needed scripts into the FM's zip file, but when newer versions of the scripts came out, older versions in FM archives sometimes caused trouble. Currently, a shift towards including scripts with T2Fix and not with the FM zips any more is notable, but I'm not sure yet whether this will continue or change once again.
DML fixes usually did not use scripts until a few years ago, AFAIK, but it's a new trend that more and more new DMLs need the scripts, too. I think T2Fix should begin to mention this if someone selects to install the T2FMDML package, but not the package containing the scripts.
By the way, two other important script modules are tnhscript.osm and script.osm (also known als "public scripts", or pubscript.osm sometimes). Today, these are usually found in the osm folder inside the game's main folder. If you don't have them (or that osm folder is not searched for scripts because of some configuration setting of "Thief 2"), the next bit of trouble may already be waiting for you, since several missions also need those scripts today, but don't ship them inside their FM zip files anymore.
fortuni on 12/6/2023 at 02:47
Glypher has updated the dml
He confirmed the old dml was correct but the new the dml fixes more stuff.
For the new dml to work correctly, ND 1.27 are required and the presence of NVScript.osm, or installed T2Fix 1.27.
As for not having nvscript.osm in your Thief folder, please reinstall T2Fix_1.27e making sure you load the optional 'common script modules' as well as 'FMDML package', your Thief install should then have an OSM folder at the top of your Thief folder
BR4ZIL on 12/6/2023 at 04:43
Quote Posted by baeuchlein
Well,
NVScript.osm is included in T2Fix releases, but installation of it is optional, as far as I know. The option should be called "Common script modules", but it might be present only in the "T2Fix with mods" package.
In ancient times, when the world was still young, the "Thief" game just a new kid on the block, and dinosaurs still roamed the planet, new FMs needing NVScript, tnhscript, and other scripts, usually stated this in the
FMInfo.txt file, but it was up to the user to make sure the scripts were present. Late on, it became somewhat standard to put the needed scripts into the FM's zip file, but when newer versions of the scripts came out, older versions in FM archives sometimes caused trouble. Currently, a shift towards including scripts with T2Fix and not with the FM zips any more is notable, but I'm not sure yet whether this will continue or change once again.
DML fixes usually did not use scripts until a few years ago, AFAIK, but it's a new trend that more and more new DMLs need the scripts, too. I think T2Fix should begin to mention this if someone selects to install the T2FMDML package, but not the package containing the scripts.
By the way, two other important script modules are
tnhscript.osm and
script.osm (also known als "public scripts", or
pubscript.osm sometimes). Today, these are usually found in the
osm folder inside the game's main folder. If you don't have them (or that
osm folder is not searched for scripts because of some configuration setting of "Thief 2"), the next bit of trouble may already be waiting for you, since several missions also need those scripts today, but don't ship them inside their FM zip files anymore.
Thats weird, as i do have a OSM folder, with all the scripts mentioned here. Theres even a NVScript.osm there too.
I also have a T2FMDML package on my main thief folder as well, altho i do believe the scripts dont actually work from there (Angel Loader doesnt seem to detect them).
Is this a AngelLoader issue?
fortuni on 12/6/2023 at 06:08
Quote Posted by BR4ZIL
Thats weird, as i do have a OSM folder, with all the scripts mentioned here. Theres even a NVScript.osm there too.
I also have a T2FMDML package on my main thief folder as well, altho i do believe the scripts dont actually work from there (Angel Loader doesnt seem to detect them).
Is this a AngelLoader issue?
I doubt it but that would be a question for Fen.
baeuchlein on 12/6/2023 at 11:17
If the scripts are in the
osm folder, but still remain unused, then some configuration setting might be wrong. In my installation, the contents of
osm are used because there is a setting for the "uber_mod_path" in
cam_mod.ini, near the end. It looks like this:
I cannot completely rule out that it might be located in another file for other installations, but I think it makes a lot of sense in
cam_mod.ini, so BR4ZIL should look into that file and check whether the line above is there.
If the line is there, but there is another character at the beginning, like in
Code:
;uber_mod_path .\OSM
then the appropriate setting might be "commented out", meaning it is disabled/not used. That would also explain why
osm\NVScript.osm is not used.
P.S.: I just noticed that the path to the scripts is also configured in the
darkinst.cfg file:
Code:
script_module_path .\OSM+.\
Another thing to check.
baeuchlein on 12/6/2023 at 19:00
I now played through the mission on easiest difficulty level with the new DML; once with this new DML alone, and once with both this DML and the one from 2018 (in T2FMDML) being active. It works sufficiently in either case. The only difference that might occur when both DMLs are active is a somewhat different response of the people in the pub to suspicious things, e.g., some of them falling down after a strange -WHACK- sound. But I'm not sure, and the mission can be completed in both cases, so we can leave it as is, and make sure the new DML is included in the next T2Fix's T2FMDML package.
BR4ZIL on 12/6/2023 at 21:10
Thank you! that was it.
My cam_mod.ini was weird... it had missing and garbled text for some reason... i wonder if screwed itself up somehow in some sort of bad saved config.
I did lost power to my home some days ago while i was playing Thief, i wonder if that was the trigger for this problem.
Anyhow, the FM is also working as intended with the DML!
I am sorry i completely went off-topic with my trouble, but i wasnt aware it was a problem with myself! :D
