Beta Testing 2.09

[stgatilov]

1 hour ago, PranQster said:

So, the installer did not automatically update it's .ini file, so I didn't see the newer updates as available.

Sounds like something which should be fixed, no?

Do you see anything suspicious in the log file when it cannot update? Is your user allowed to overwrite the ini file?

[PranQster]

The only information in the log file is from after I succeeded in updating the .ini file after manual edit. There is nothing in the log from previous to that. I might have deleted the old log file in  my attempts to fix the installer earlier today.

As far as user permissions goes... I did check that and had write permissions for both user and group on the .ini. I also set write permissions for 'Others' as well, but that didn't help.

Edited February 9, 2021 by PranQster

[PranQster]

When I download the installer manually, there is no .ini file packed with it. If the .ini file is not already present in the darkmod folder, the installer complains that there is not .ini file and does not work. So:

a. The installer was not downloading a new .ini file during the self update before presenting the TDM updates?

b. It was downloading a new .ini, but not updating the current one, despite having permissions to do so?

Also, what happens when someone downloads the installer for the first time and has no 'tdm_installer.ini' packed with it and gets the error of a missing .ini file when trying to get the updates listed?

[stgatilov]

On 2/9/2021 at 1:23 PM, PranQster said:

When I download the installer manually, there is no .ini file packed with it. If the .ini file is not already present in the darkmod folder, the installer complains that there is not .ini file and does not work.

The installer always downloads the tdm_installer.ini when you leave the first page, unless you check "Skip config file download" (which is necessary mainly for debugging). This might sound inefficient, but config file is a small chunk of text, so it's not a big problem downloading it again and again.

The root of error is clear: installer does not download config file. Maybe it also cannot download itself (i.e. cannot self-update). Maybe it also cannot update your TDM installation, and you are still on old version (although I'm pretty sure it would throw some error if that happened).

I have no idea why download fails. Perhaps if you share log file immediately after the run when config download failed, it would show something.

[grayman]

I might have a lighting issue.

Here's a link to a test map.

When you start, walk to the edge and look down. You have 2 lights beneath the water, rather dim.

Jump into the water and submerge. Note the light brightness has changed.

When you come back up and climb out, look again at the 2 lights. Now they're both very bright.

Any idea what's going on? If you never submerge, the lights will stay dim forever.

Here's my cfg file.

 

[madtaffer]

Should water dim the light automatically?

[Sneaker]

On 12/29/2020 at 11:43 AM, cabalistic said:

@Araneidae You could try to change the color precision to 32 bits (either in the menu or by setting `r_fboColorBits 32` via the console or in your darkmod.cfg. Perhaps we don't have proper detection for 64 bit color buffer support right now, and that messes things up if your card doesn't actually support is, as lowenz's post suggests?

Although I wouldn't really understand how disabling tonemapping could influence this, but who knows...

I just updated to the latest beta and I also ran into this bug. When I set 'r_fboColorBits 32' that did fix the screen jello corruption.  Just wanted to let you know... not knowing whether that's expected or not in the beta.  thanks.

[stgatilov]

On 2/13/2021 at 9:17 AM, Sneaker said:

I just updated to the latest beta and I also ran into this bug. When I set 'r_fboColorBits 32' that did fix the screen jello corruption.  Just wanted to let you know... not knowing whether that's expected or not in the beta.  thanks.

I wonder if you have the exact same GPU model as @Araneidae?
Do you happen to use the same driver?  (I.e. same OS, and same type of driver in case you are using Linux)

[stgatilov]

The announcement about 2.09 release will come soon.

I'd like to thank everyone who took part in this beta phase!
With so many people taking part in the beta phase, we can make official releases more stable, and ready to be run on diverse machines that players have! Not to mention: with the diverse set of FMs we have

 

In order to switch from beta build to the official 2.09 release, just run tdm_installer with default settings and allow it do what it wants.
You can restore config file at the end of update: it is perfectly safe this time.

Please check that tdm_installer displays version 1.02 after self-update (in window title). I have tested and verified it myself, but better check it to be safe.

Actually, beta209-06 and release209 are exactly the same versions, so this update will be purely cosmetic: no new data will be downloaded, no savegames will be broken between these two versions.

[Sneaker]

7 hours ago, stgatilov said:

I wonder if you have the exact same GPU model as @Araneidae?
Do you happen to use the same driver?  (I.e. same OS, and same type of driver in case you are using Linux)

Yes, I think so... I'm on fedora 32 also using a really old Radeon card.

[Araneidae]

11 hours ago, Sneaker said:

Yes, I think so... I'm on fedora 32 also using a really old Radeon card.

Just for definiteness, can you tell us what running

lspci |grep VGA

reports?  I get

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950]

Alas, I don't know how to interrogate my driver version, but I know it's stock install.  Thank goodness that AMD finally works properly out of the box, but guess I need to think about upgrading ... once the graphics card market has stopped being insane!

Edited February 15, 2021 by Araneidae
Fix highlighting

[Sneaker]

8 hours ago, Araneidae said:

Just for definiteness, can you tell us what running

lspci |grep VGA

reports?  I get

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950]

Alas, I don't know how to interrogate my driver version, but I know it's stock install.  Thank goodness that AMD finally works properly out of the box, but guess I need to think about upgrading ... once the graphics card market has stopped being insane!

Sure:

01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS780 [Radeon HD 3200]
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770]

the first is the onboard gpu, the 6770 would be the card I use.  my setup has been good enough for me, but recently it's been really showing it's age. 

Edited February 15, 2021 by Sneaker

[lowenz]

Pre-GCN Radeon, as exptected.

[DeTeEff]

Don't know if this is the right place, but I have some problems with both updaters...

[DeTeEff]

Now it suddenly works...I guess the mirror site was a bit cranky and wanted some alone time... Looking forward to see the fruits of your hard work guys!

[Jedi_Wannabe]

3 hours ago, lowenz said:

Pre-GCN Radeon, as exptected.

So Radeon HD 6700 is out, what about a 6950 card? That's what I'm running and I can't run 2.09, just goes to black screen after launch.

[nbohr1more]

8 minutes ago, Jedi_Wannabe said:

So Radeon HD 6700 is out, what about a 6950 card? That's what I'm running and I can't run 2.09, just goes to black screen after launch.

Did you try "r_useNewBackend" "0", "r_useBindlessTextures" "0" and "r_fboColorBits" "32" in darkmod.cfg ?

[Jedi_Wannabe]

Just tried those. Still black screen at launch.

[nbohr1more]

Hmm...

r_useMultiDrawIndirect 0

image_useNormalmapCompression 0

r_tonemap 0

I presume that you tried deleting your darkmod.cfg as well?

[Jedi_Wannabe]

4 minutes ago, nbohr1more said:

Hmm...

r_useMultiDrawIndirect 0

image_useNormalmapCompression 0

r_tonemap 0

I presume that you tried deleting your darkmod.cfg as well?

Deleting config was my initial step, yes. Tried those 3 and still no difference. I can however hear menu music and when my cursor moves over a menu item.

And super big thanks for the quick responses, by the way!

Edited February 15, 2021 by Jedi_Wannabe

[nbohr1more]

No problem.

Please attach your darkmod.cfg.

In addition, please launch TDM and attempt to open your console ( CTRL + ALT + ~ ) the invoke "condump blackgfx.txt" and post the resultant file to the thread.

Also, try locating and deleting your shader cache. I believe it should be under C:\Users\You\AppData\Local\AMD

[Jedi_Wannabe]

19 minutes ago, nbohr1more said:

No problem.

Please attach your darkmod.cfg.

In addition, please launch TDM and attempt to open your console ( CTRL + ALT + ~ ) the invoke "condump blackgfx.txt" and post the resultant file to the thread.

Also, try locating and deleting your shader cache. I believe it should be under C:\Users\You\AppData\Local\AMD

Thanks so much I’ll try those and report back tonight after dinner if I have more time.

[wesp5]

I just checked out 2.09 final and noticed that my additional info text about the locked desktop resolutions has not be added. May I ask why? And will this be added to 2.1 at least to avoid confusion if it's not planned to add full screen resolution changing back itself?

Edited February 15, 2021 by wesp5

[Dragofer]

@wesp5   Usually the last beta build (release candidate) becomes the release build unless something major has broken. I think this is mostly a tradition from the tdm_update.exe days, since packaging new builds and sending them to tdm_update was a ton of work. I think this has become easier now with the new update method, but I don't know how much work it still is.

[Tarhiel]

Wow, guys, optimization in 2.09 is above and beyond awesome - Painter's Wife, where I had before in the worst parts around 45 FPS, at best 75-85, now thanks to Image Sharpening I can now have 95 where before I had 45 and 120+ where I before had 75-85.

And without noticeable drop in image quality.

This is unbelievably awesome!

Edited February 15, 2021 by Tarhiel