Issues in 2.08 final

[Darkness_Falls]

Thanks Kingsal! Actually, it turns out I'm kinda dumb. Your screenshot example being really dark on my end helped me realize the issue. I had Brightness down really far on my monitor and that was helping to make my water super black. In my defense, though, I always drop the Brightness way down and Contrast way up when playing Thief I and 2. I do it for T1/2 because it really makes the colors vibrant and rich (but not over-saturated), with rich/deep blacks, too. It's a trick I use on my LCD display to replicate the look of Thief that I had on my old CRT monitor back in the day. It's really effective for me. Without it, the nature of the LCD monitor tech causes brightened, luminous greys instead of deep blacks. I thought, and have always assumed, I'd want/need to do that for TDM Maybe that's why I've always had gamma woes with TDM

I'll have to do some TDM testing at some point now, as maybe TDM just isn't as compatible with that approach as T1/T2 is for me. In looking at your map (and my screenshots above) with Brightness up a bit, I think I'll be okay. The coloring for the missions, in general, won't have as much pop as I like, but at least I can see everything now

I can delete my above posts if mods want me to; or they can if they wish; since it takes up so much room on the page. But it might help future people see if they encounter the same issue, I suppose(?)

 

 

Edited August 17, 2020 by Darkness_Falls

[wesp5]

17 hours ago, kingsal said:

As noted in that thread, the console command to turn off the boop is "s_playDefaultSound"  "0". I thought it was off by default but I guess not.

If it is not set to 0 by default it should be, because it sounds very much out of place most of the time! Or choose a more subtle sound than a beep.

Edited August 17, 2020 by wesp5

[kingsal]

2 hours ago, wesp5 said:

If it is not set to 0 by default it should be, because it sounds very much out of place most of the time! Or choose a more subtle sound than a beep.

Well its meant to sound out of place so developers hear it and fix the sound, but yeah it shouldnt be on in the release build.

[wesp5]

34 minutes ago, kingsal said:

Well its meant to sound out of place so developers hear it and fix the sound, but yeah it shouldnt be on in the release build.

So this is kind of a "the sound is missing" sound. Nice idea! With Bloodlines you always need to check the console for that ;).

[wesp5]

Okay, so I found another issue which may be connected to 2.08 or some specific missions: Sometimes for notes a font is used that is very pixelated and barely readable. See this example from Shadows of Northdale Act II:

[lowenz]

FPS increase after the menu loading

 

Why???? GeForce 1050 Ti, lastest drivers
 

Edited August 20, 2020 by lowenz

[duzenko]

4 minutes ago, lowenz said:

FPS increase after the menu loading

 

 

 

Why???? GeForce 1050 Ti, lastest drivers
 

VSync + fps cap?

[lowenz]

No VSync (I'm using an adaptive sync monitor) an 80 FPS Cap.....

Adaptive sync perfectly working in the declared range (48-75, so smooth!)

39 FPS after loading the savegame -> Esc->Menu->Esc -> 54 FPS......

Edited August 20, 2020 by lowenz

[duzenko]

18 minutes ago, lowenz said:

No VSync (I'm using an adaptive sync monitor) an 80 FPS Cap.....

Adaptive sync perfectly working in the declared range (48-75, so smooth!)

39 FPS after loading the savegame -> Esc->Menu->Esc -> 54 FPS......

Sounds like a driver issue. 39 is half of 80

[lowenz]

Let me try with another cap

[lowenz]

39 with 60 FPS cap too....

WTF, in other missions too!

 

Edited August 20, 2020 by lowenz

[duzenko]

No idea then

[PranQster]

12 hours ago, lowenz said:

39 with 60 FPS cap too....

WTF, in other missions too!

 

Hmm... this looks a little familiar

Are you only getting the frame rate drop after having loaded a savegame? Or any time you access the menu, as though it toggles each time?

Edited August 21, 2020 by PranQster

[lowenz]

Only after the savegame loading+ESC, then the situation goes normal !

 

And yes, for who's asking "What map is that!?!?!?".....it's a nice surprise coming to you from our good PranQster (with some little support by me) 

Edited August 21, 2020 by lowenz

[PranQster]

55 minutes ago, lowenz said:

Only after the savegame loading+ESC, then the situation goes normal !

Next time I'm in the 'shop, I'll test that and see how my system behaves.

[stgatilov]

On 8/20/2020 at 4:23 AM, wesp5 said:

Okay, so I found another issue which may be connected to 2.08 or some specific missions: Sometimes for notes a font is used that is very pixelated and barely readable. See this example from Shadows of Northdale Act II:

I think it is fixed already, see here.
Should work properly on latest dev build.

[stgatilov]

On 8/21/2020 at 1:14 PM, lowenz said:

Only after the savegame loading+ESC, then the situation goes normal !

Does it work the same with Uncapped FPS and without, with VSync and without?

[wesp5]

8 hours ago, stgatilov said:

I think it is fixed already, see here.
Should work properly on latest dev build.

Ah, I must have overlooked that thread. Good to hear it is already fixed! Anything new about the failed lockpicking sound playing all the time?

[stgatilov]

14 minutes ago, wesp5 said:

Ah, I must have overlooked that thread. Good to hear it is already fixed! Anything new about the failed lockpicking sound playing all the time?

I think no.

I recall there is an issue about it somewhere.
I tried to listen more attentively to lockpicking sounds, but did not hear anything suspicious. I guess it causes to little harm to bother.

[wesp5]

31 minutes ago, stgatilov said:

I tried to listen more attentively to lockpicking sounds, but did not hear anything suspicious. I guess it causes to little harm to bother.

I find it very annoying! For each successfull attempt the failing sound is played. This wasn't the case in 2.07 and should thus be easy to fix.

[vozka]

Apart from the aliased text which has hopefully been fixed for next versions, and which I started seeing again i 2.08 after seeing it a couple times in 2.07 and then never again, I also encountered a couple black objects. 

Both screenshots are from Northdale part 2, first one is from the path to city watch station, second one is from inside the station. 

If I recall correctly, the round lamp was already fixed during the betatesting, but apparently only for the turned on state (or maybe it was a similar looking but different model). It looks fine when turned on and emitting light, but when you turn it off, it turns black. With the hanging lantern it's possible that nobody noticed, I only did after seeing it for about the third time. 

[wesp5]

I think it's time to take a closer look at the "Open Doors on Unlock" feature, as I got once again stuck because I had this set to off. Missions that are affected are the upcoming "Now and then", according to the forum search function also "The painter's wife", "The Alchemist" and "Hidden Hands: Initiation", and I remember another mission where it happened to me.

Can this somehow be circumvented by updated dev or script files or do the mission authors need to fix this on their side? If there is no common solution, shouldn't this option be removed? I don't know how many players there are who don't come looking here for help, but if they don't some of these missions are just completely not playable when this option is set to off.
 

[joebarnin]

3 hours ago, wesp5 said:

I think it's time to take a closer look at the "Open Doors on Unlock" feature, as I got once again stuck because I had this set to off. Missions that are affected are the upcoming "Now and then", according to the forum search function also "The painter's wife", "The Alchemist" and "Hidden Hands: Initiation", and I remember another mission where it happened to me.

Can this somehow be circumvented by updated dev or script files or do the mission authors need to fix this on their side? If there is no common solution, shouldn't this option be removed? I don't know how many players there are who don't come looking here for help, but if they don't some of these missions are just completely not playable when this option is set to off.
 

I can only speak for my mission (the soon-to-be-released "Now and Then"), but this issue can be resolved in the mission scripts. I fixed it yesterday so it'll be in the released FM. Here are the details.

In this mission I use the atdm:combination_lock_small. As is discussed in various threads, when using this asset you have to include the appropriate script file(s) in your <fm>\script folder. In this case, atdm:combination_lock_small has spawnarg "scriptobject" = "numberwheel_lock". At some point, when I was developing my first FM, I got a hold of numberwheel_lock.script (which was at the time included the TDM release. Subsequently it was removed, I think). I've put this in my \script folder for each FM I've built, and it works fine.

Except in the following case: the door is a secret door that isn't frobable, and it has open_on_unlock=1. The default code in numberwheel_lock.script makes the following call when the combo is correctly entered:

t.Unlock();

The variable 't' is the target of the combo lock (the door). This statement unlocks the secret door, which, because open_on_unlock=1, opens it. Except: if the user has "Open Doors on Unlock" = Off, that overrides open_on_unlock. So in that case the door isn't opened. And since the door isn't frobable, there is no way to open it even if it is unlocked.

The fix is to modify numberwheel_lock.script to call t.Open() as well t.Unlock(). This unlocks and then opens the door. Oh, and you have to remove the open_on_unlock=1 spawnarg from the door too.

These changes work fine, and are appropriate IMHO, since each FM 'owns' their copy of numberwheel_lock.script. It's a shame that each FM developer may need to make this adjustment, but I think that's an artifact of numberwheel's history.

[wesp5]

Couldn't this be fixed for all missions by readding numberwheel_lock.script with the changes you added?

Edited August 31, 2020 by wesp5

[joebarnin]

2 hours ago, wesp5 said:

Couldn't this be fixed for all missions by readding numberwheel_lock.script with the changes you added?

Possibly. But I think there were reasons for removing the script from the release. According to this post talks about it: 

  

On 1/10/2019 at 6:27 AM, nbohr1more said:

In 2.07 it was decided that the numberwheel script from "A New Job" was too specialized to that mission and

that it shouldn't be a mod asset because it was causing mission developers too much trouble when they tried to

use it. To my knowledge, we sent the word out that this change would be happening and any mission using the script

has been repacked to include it in the mission package rather than inheriting from the mod asset base.

Looks like I need to fix my "Mission of Mercy" FM. It is broken now - I guess I didn't see that notification.