Beta testing 2.10

[joebarnin]

5 minutes ago, AluminumHaste said:

Do you have a glprogs folder in your darkmod directory?

Yes I do. I just deleted it, and now it works fine. Thanks! My apologies, I should have thought of that.

[AluminumHaste]

Awesome, I had the same thing in mine and deleting that got it working.

[stgatilov]

5 hours ago, AluminumHaste said:

Just tried updating 2.09b install on my 2nd desktop to 2.10b5, and I get this error every time.

I wrote to the mirror owner.

Meanwhile, I think you can choose mirror manually (not Kowmad's) to avoid the issue.

[AluminumHaste]

I forced it to taaki east still got the message

[wesp5]

9 hours ago, AluminumHaste said:

r_froboutlinepreset 5

Thanks, so you pulled 5 and moved 6 into it's place? Makes sense as 5 looked like none at all anyway...

[lowenz]

12 hours ago, joebarnin said:

Yep, on the light I have:

volumetric_light=1

volumetric_dust=.002

volumetric_noshadows=-1

Worked fine in beta04, but not in beta05.

What are those line?

[lowenz]

Interesting behaviour with an Intel UHD 750:

*borderless fullscreen: 

*exclusive fullscreen: 

 

In ex-fullscreen mode the average framerate is course a little better (14 vs 12 @2560x1440) but the interesting thing is the nervous frame time behaviour due to how the driver manages the exclusive fullscreen mode. Is it fixable? (the same happens @1280x720, the "right" resolution @which you can play the game with the UHD 750)

Edited January 27, 2022 by lowenz

[lowenz]

the same happens @1280x720, the "right" resolution @which you can play the game with the UHD 750 - with integer upscaling to 2560x1440

->

Edited January 27, 2022 by lowenz

[AluminumHaste]

3 hours ago, wesp5 said:

Thanks, so you pulled 5 and moved 6 into it's place? Makes sense as 5 looked like none at all anyway...

 

Not sure what you mean sorry, nothing has changed with the presets since a few betas ago.

If you had custom settings for the froboutline, they may have been wiped out when you updated. Did you click the option to restore the old darkmod.cfg in the installer when updating to 2.10b5?

[wesp5]

1 hour ago, AluminumHaste said:

Not sure what you mean sorry, nothing has changed with the presets since a few betas ago.

I'm pretty sure the dark outline was 6 when I last used it, unless I mistook it when I wrote that:

https://forums.thedarkmod.com/index.php?/topic/21196-frob-outline-poll/page/3/#comments

 

[AluminumHaste]

5 and 6 are BOTH dark outlines, 5 is hard geometric dark outline, and 6 is soft shader dark outline.

Go in the game and open the console. Type in

r_frobOutlinePreset

and press Enter. You'll see the description of each preset.

[AluminumHaste]

Also, wtf is up with the grabber? Rotating items in the grabber is bonkers stupid now. If you start rotating too quickly, or give another input, even in the same direction as the original input, it will start rotating in the opposite direction.

 

in 2.09b it's easy for me to rotate this box back to flat.

But in 2.10, I can't make any sense of what it's doing.

Now, this is partly my fault, I've noticed this looooong before the beta release, but I usually don't have much reason to rotate items in the grabber, except maybe righting toppled candles, but I don't think it should be released in this state.

[stgatilov]

4 hours ago, lowenz said:

Interesting behaviour with an Intel UHD 750:

In ex-fullscreen mode the average framerate is course a little better (14 vs 12 @2560x1440) but the interesting thing is the nervous frame time behaviour due to how the driver manages the exclusive fullscreen mode. Is it fixable? (the same happens @1280x720, the "right" resolution @which you can play the game with the UHD 750)

I have no idea if this is fixable, since TDM does not make any difference between the two modes.
"Borderless" fullscreen only makes the TDM window 1 pixel wider in vertical direction, which supposedly forces most drivers to not do anything fancy but go through regular windows compositing.
Also the two modes differ in how they work if you set non-native resolution: proper fullscreen will ask your OS to change resolution globally, while borderless does not support this case at all (not sure what would happen).

You can try to play with "Uncap FPS" and "V-Sync", I'm sure some of these settings will remove FPS oscilations.

[datiswous]

41 minutes ago, AluminumHaste said:

Also, wtf is up with the grabber?

I think it has to do with the following:

You can try doing:

tdm_drag_new 0

And see if it behaves similar to 2.09 again.

 

I recently had some issue with positioning a chair, maybe this is the reason as well.

Edited January 27, 2022 by datiswous

[stgatilov]

1 hour ago, AluminumHaste said:

Also, wtf is up with the grabber? Rotating items in the grabber is bonkers stupid now. If you start rotating too quickly, or give another input, even in the same direction as the original input, it will start rotating in the opposite direction.

Do you have any problem with light/small objects?

I can see the problem with a box, although it happens on "tdm_drag_new 0" too.

[AluminumHaste]

33 minutes ago, stgatilov said:

Do you have any problem with light/small objects?

I can see the problem with a box, although it happens on "tdm_drag_new 0" too.

Rotating the candles seems fine.

[lowenz]

3 hours ago, stgatilov said:

I have no idea if this is fixable, since TDM does not make any difference between the two modes.
"Borderless" fullscreen only makes the TDM window 1 pixel wider in vertical direction, which supposedly forces most drivers to not do anything fancy but go through regular windows compositing.
Also the two modes differ in how they work if you set non-native resolution: proper fullscreen will ask your OS to change resolution globally, while borderless does not support this case at all (not sure what would happen).

You can try to play with "Uncap FPS" and "V-Sync", I'm sure some of these settings will remove FPS oscilations.

Of course in those tests the framerate is already uncapped and V-Sync is off

 

So it can be something strictly OS+driver related.....

Edited January 27, 2022 by lowenz

[wesp5]

4 hours ago, AluminumHaste said:

5 and 6 are BOTH dark outlines, 5 is hard geometric dark outline, and 6 is soft shader dark outline.

Go in the game and open the console. Type in

r_frobOutlinePreset

and press Enter. You'll see the description of each preset.

Yes, I can do that, but on my system only outline 1 works, all others look like outline off. And I didn't change anything manually about the outline in my cfg file and I didn't restore my old cfg either...

Edited January 27, 2022 by wesp5

[AluminumHaste]

r_newFrob 1

[wesp5]

Sorry, but it doesn't work with r_newFrob 1 either, also preset 1 worked fine before...

[AluminumHaste]

Do you have glprogs folder in your Darkmod directory?

[duzenko]

21 hours ago, lowenz said:

the same happens @1280x720, the "right" resolution @which you can play the game with the UHD 750 - with integer upscaling to 2560x1440

-> 

I wondered if Intel got their shit together with that new chip. Apparently not (as expected).

Their "market targeting" is utter nonsense. They put 96EU into 25W or even 15W chips and the 125+W chips only include 32/24/16 EUs.

[lowenz]

2 hours ago, duzenko said:

I wondered if Intel got their shit together with that new chip. Apparently not (as expected).

Their "market targeting" is utter nonsense. They put 96EU into 25W or even 15W chips and the 125+W chips only include 32/24/16 EUs.

That's my same&main concern.

IHMO it's an issue of the OpenGL driver with the desktop compositing (in some GPU-bound scenarios).

Edited January 28, 2022 by lowenz

[wesp5]

16 hours ago, AluminumHaste said:

Do you have glprogs folder in your Darkmod directory?

No, I do not. Do I need it for the latest 2.10 beta? I don't think I ever had one before...

[nbohr1more]

13 minutes ago, wesp5 said:

No, I do not. Do I need it for the latest 2.10 beta? I don't think I ever had one before...

Did you ever install the fresnel mod ( tdm_base01.pk4 has the glprogs folder in it )?