Beta Testing 2.08

[nbohr1more]

1 minute ago, HMart said:

Played one of the default missions with 2.08 and I most say I saw no glaring problems but I've yet to play more to have a better idea.

One thing I saw tho, with the ambient occlusion the game becomes way more dark, don't know if is caused by some bad gamma settings on my side or is normal, I also played with W10 "nocturn light" on to make it easy for me to sleep. The flashlight was now much more necessary. 

Don't take with this that I didn't liked AO, I did, the game became more dark to me but also more atmospheric, in the shade objects got more grounded and I really love how you cast a "shadow" on the ground when you crouch or when get next to objects and how the guards feet also do the same has they travel through the shade. 

What AO system have you guys implemented? SSAO?

"Scalable Ambient Obscurence"

Try lowering the r_ssao_base value to 0.3 or 0.4 (higher numbers are the cutoff to how dark it can be).

 

[HMart]

2 minutes ago, nbohr1more said:

"Scalable Ambient Obscurence"

Try lowering the r_ssao_base value to 0.3 or 0.4 (higher numbers are the cutoff to how dark it can be).

 

Hum for a Nvidia tech it does seems to run well on my AMD GPU.  

Ok will do that but thinking more about it, perhaps personally I will let it be that dark, I liked that it forced me to use the lantern more often and so be more alert to the guards. 

[nbohr1more]

Please experiment and compare to 2.07

You can also raise the r_ambientGamma to compensate for some of the darkening.

Find a sweet spot with

r_postprocess_brightness

r_postprocess_gamma

r_ambientGamma

r_postprocess_colorCurveBias

r_postprocess_desaturation

[lowenz]

Differences between SSAO levels? (1->2->3)

[nbohr1more]

The SSAO levels determine how far the effect spreads from the occlusion zones. They are presets that internally

affect the base levels of the cvars so your cvar adjustments are relative to them.

 

case 1:
uniforms->maxMipLevel.Set(0);
uniforms->numSpiralTurns.Set(5);
uniforms->numSamples.Set(7);
sampleRadius = 0.5f * r_ssao_radius.GetFloat();
break;
case 2:
uniforms->maxMipLevel.Set(MAX_DEPTH_MIPS);
uniforms->numSpiralTurns.Set(7);
uniforms->numSamples.Set(12);
sampleRadius = r_ssao_radius.GetFloat();
break;
case 3:
default:
uniforms->maxMipLevel.Set(MAX_DEPTH_MIPS);
uniforms->numSpiralTurns.Set(7);
uniforms->numSamples.Set(24);

sampleRadius = 2.0f * r_ssao_radius.GetFloat();

 

[cabalistic]

SSAO shouldn't noticeably darken the whole scene - are you sure it's not the new gamma/brightness system that makes TDM look darker than before? You can look at the actual SSAO output via "r_showFBO 4" - this should be a white image with the darkened AO shades. If that image is somehow gray, then the effect may be misbehaving on your GPU.

[cabalistic]

Just for reference, this is what SSAO should look like:

So yeah, it does darken the (impression of the) scene, but it should not make a drastic difference. If you see different behaviour between SSAO turned on and off, please let me know so that we can debug the issue

[lowenz]

Unrelated to SSAO, got this warning in A New Job:

Edited March 27, 2020 by lowenz

[Filizitas]

Is SSAO already a thing in 2.08?? Wow

[lowenz]

Yes and it's SO good (temporally totally stable)

You can see "Medium" level in my screenshot.

Edited March 27, 2020 by lowenz

[Filizitas]

Trying to update to 2.08 isnt working for me, i followed the steps for the updater but then it yells at me with VS.

Running the named exe returns this:

My VS setup uses all the latest libraries already. I use Visual studio 17 and 19 in full setup.
I dont want to change this setup at all

What can i do?

[cabalistic]

Strange that it errors out, but if you have VS 2017 installed, you shouldn't need to install the redistributables, anyway. Have you tried starting the game?

[Filizitas]

Yee, it still says 2.07 in console and menu.  Maybe it cant finish the install now.

[stgatilov]

54 minutes ago, Filizitas said:

Trying to update to 2.08 isnt working for me, i followed the steps for the updater but then it yells at me with VS.

What can i do?

TDM 2.08 uses statically linked CRT, just like 2.05 and before did. So new tdm_update does not even attempt to install VCRedist. You have old tdm_update, which for some reason does not update itself.

• Did you set checkbox "noselfupdate" ?  (hint: you should not)
• Did you set checkbox "keep-mirrors" ? (hint: you should)
• Did you download the tdm_mirrors.txt file by the link in the original post and put it near TDM executables? (hint: you should)

If you did all of this properly, then I'm afraid it might be some access issue again, like tdm_update cannot overwrite anything in its directory...

[Goldwell]

So I updated to the latest 2.08 beta and went through the assets again. Good news is that the werebeast is all there now.

 

But here's some assets that are showing up a lil funky for me:

 

1) atdm:ai_manbeast & atdm:ai_manbeast_spear_thrower

 

2) models/darkmod/junk/dirt_edge02_grass.lwo

 

3) models/darkmod/loot/jewellery/lionhead_amulet.lwo

 

4) models/darkmod/nature/boom_shroom_flider.ase (I think this is an old one but thought i'd add it in anyway)

 

5) models/darkmod/weapons/volta_spear.ASE

 

6) models/darkmod/weapons/volta_spear_broken_shaft.ASE

 

7) models/darkmod/weapons/volta_spear_broken_tip.ASE

 

8 ) models/darkmod/weapons/volta_spear_bundle.ASE

 

9) models/darkmod/wearables/headgear/broadbrim_hat.lwo

[Filizitas]

I reinstall TDM completly then

/shrug

[stgatilov]

11 minutes ago, Filizitas said:

I reinstall TDM completly then

Did you check that all values are set correctly?

[Filizitas]

I did it as you said.
It installed tdm without any start exe O.o

I reded the update and now everything is 2.08

Edited March 27, 2020 by Filizitas

[VanishedOne]

@Goldwell I think lionhead_amulet.lwo has always been like that; it is on my 2.07 installation. The broken material is called tdm_blackheart_amulet so I suspect it's a Blackheart Manor asset that was only halfway added to core.

You're right about the shroom flinder problem being an old one; does https://bugs.thedarkmod.com/view.php?id=2559#c9479 help?

[Goldwell]

49 minutes ago, VanishedOne said:

@Goldwell I think lionhead_amulet.lwo has always been like that; it is on my 2.07 installation. The broken material is called tdm_blackheart_amulet so I suspect it's a Blackheart Manor asset that was only halfway added to core.

You're right about the shroom flinder problem being an old one; does https://bugs.thedarkmod.com/view.php?id=2559#c9479 help?

Well I guess that answers those ones, thanks! Hopefully they get fixed in 2.09.

 

Also I noticed that when the werebeast was in game it keeps displaying this message in the console

 

[Springheel]

Quote

1) atdm:ai_manbeast & atdm:ai_manbeast_spear_thrower

I think just the editor image is missing.  Do you see any issues in game? 

Quote

models/darkmod/weapons/volta_spear.ASE
2) models/darkmod/junk/dirt_edge02_grass.lwo

These two should be fixed in revision 15885

 

The other ones are super old models, so either something has broken, or they were never finished and were uploaded by mistake.

[HMart]

18 hours ago, cabalistic said:

SSAO shouldn't noticeably darken the whole scene - are you sure it's not the new gamma/brightness system that makes TDM look darker than before? You can look at the actual SSAO output via "r_showFBO 4" - this should be a white image with the darkened AO shades. If that image is somehow gray, then the effect may be misbehaving on your GPU.

By using gama 1.3 and brightness 1, the scene still looks a tad dark but much brighter than before, so yes gamma/brightness was the culprit, turning off or on, AO made almost no difference to the darkness but made a huge difference to the depth of the scene, sorry for my hasted "complaint".  Love the AO very nice guys.

Btw I also forgot to mention that i'm playing this on a new freesync monitor and it's gama is totally different to my old one, IMO the old one looked better but was only a 60hz screen and after experiencing higher refresh rates I just can't go back!    

r_showFBO 4 shows like you said, a white texture with dark "shadows", btw some of the shadows (not that many) aren't smooth but noisy, like dither noise, is that normal?  

 

[Goldwell]

14 hours ago, Springheel said:

I think just the editor image is missing.  Do you see any issues in game? 

These two should be fixed in revision 15885

 

The other ones are super old models, so either something has broken, or they were never finished and were uploaded by mistake.

 

Ingame the apebeasts seem to be showing up without issue.

 

But now ingame the werebeast is MIA ingame.

 

 

He is meant to be in the middle.

 

To make sure none of my def files were messing with anything I made this testmap in the dark mod base directory and made sure no FMs were installed. But yeah, in the editor the werebeast looks right, it's just ingame he is broken.

[cabalistic]

8 hours ago, HMart said:

By using gama 1.3 and brightness 1, the scene still looks a tad dark but much brighter than before, so yes gamma/brightness was the culprit, turning off or on, AO made almost no difference to the darkness but made a huge difference to the depth of the scene, sorry for my hasted "complaint".  Love the AO very nice guys.

Btw I also forgot to mention that i'm playing this on a new freesync monitor and it's gama is totally different to my old one, IMO the old one looked better but was only a 60hz screen and after experiencing higher refresh rates I just can't go back!    

r_showFBO 4 shows like you said, a white texture with dark "shadows", btw some of the shadows (not that many) aren't smooth but noisy, like dither noise, is that normal?  

 

I'm actually using gamma 1.4 and brightness 1.2 right now. The default values might still need some adjustments Yeah, some noise in the AO is expected, particularly in the distance or where the depth buffer is already crowded. As long as it does not disturb the actual rendered scene...

[Filizitas]

I used the SSAO too and tested it.

I actually find that it is very absent.
But i probably expect contact shadows.
You can clearly see that it is just screenspace.
But its generally totally ok! I use it now fulltime!