Rip and tear!

Amazing! How did you get this done before release?

4 minutes ago, Fortress said:

Amazing! How did you get this done before release?

VPN to New Zealand with the Bethesda Launcher activated the game 5 hours ago

Does not work with the Steam version I think.

Quote

Sensitivity set in the console will not be saved, so it must be set every time you launch the game.

Oof that's annoying. Hopefully this will be patched soon. In the meantime, looks like I will be binding a key to the "m_sensitivity" command.

13 minutes ago, octiceps said:

Oof that's annoying. Hopefully this will be patched soon. In the meantime, looks like I will be binding a key to the "m_sensitivity" command.

I just found a workaround, you can set the m_sensitivity as a launch option

Thanks!

Thank you very much for all of this

Does the FOV also reset when using console if re-launching ? i.e is it required to set that as a launch parameter too?

Just now, TheNoobPolice said:

Does the FOV also reset when using console if re-launching ? i.e is it required to set that as a launch parameter too?

The console FOV does not register decimals, so you might as well set it in the menus.

Launch option doesn't work for setting sensitivity in the Steam version.

For Steam

You can hit ~ to bring up the console in-game and use m_sensitivity 2.026499 to set it precisely for now. Obviously use your value instead of mine.

edit: I don't know why I wasn't working before, but adding "+m_sensitivity 2.026499" with the quotes to the Steam launch options seems to work for me now.

Edited March 20, 20206 yr by Smash-Crunch

12 hours ago, Smash-Crunch said:

For Steam

You can hit ~ to bring up the console in-game and use m_sensitivity 2.026499 to set it precisely for now. Obviously use your value instead of mine.

edit: I don't know why I wasn't working before, but adding "+m_sensitivity 2.026499" with the quotes to the Steam launch options seems to work for me now.

Thanks, I figured out the issue. It wasn't working because I had entered another launch parameter as well. Seems the game will only apply one at a time.

Is it possible to test the weapon mod FOV and sens scaling for the heavy cannon precision bolt mod?

it seems like its approx 100% mdh to me, but in any case it’s too fast and I’ll need to use my dpi trick to bring it down.

19 minutes ago, TheNoobPolice said:

Is it possible to test the weapon mod FOV and sens scaling for the heavy cannon precision bolt mod?

it seems like its approx 100% mdh to me, but in any case it’s too fast and I’ll need to use my dpi trick to bring it down.

You are spot on  Added it now!

Worked great. Missed the m_sensitivity multiplier and thought it wasn't working (going off the 40) but a closer look revealed I'm an idiot.

 

Thanks boss!

After a ~250MB patch on Steam today, setting the sensitivity using the console command now saves, so no more need for the launch option.

Updated with vertical sensitivity calculation as it is not 1:1 with the same values.

5 hours ago, DPI Wizard said:

Updated with vertical sensitivity calculation as it is not 1:1 with the same values.

Good to know, thanks. So pitch is slower than yaw by default?

1 hour ago, octiceps said:

Good to know, thanks. So pitch is slower than yaw by default?

Yes, 50% of yaw. It's easy in the console as you can just double the yaw value for the pitch, but in-game it needs to be calculated as the values are completely different.

21 minutes ago, DPI Wizard said:

Yes, 50% of yaw. It's easy in the console as you can just double the yaw value for the pitch, but in-game it needs to be calculated as the values are completely different.

Hmmm are you sure about this? Setting  m_pitch to double the value of m_yaw makes vertical sensitivity feel way too fast.

1 hour ago, octiceps said:

Hmmm are you sure about this? Setting  m_pitch to double the value of m_yaw makes vertical sensitivity feel way too fast.

You're setting it to 0.044? If you've played a bit with the default you might just be used to the vertical speed being slow.

1 hour ago, octiceps said:

Hmmm are you sure about this? Setting  m_pitch to double the value of m_yaw makes vertical sensitivity feel way too fast.

Actually forget everything I said, it is 1:1 with the same values. I was playing around with different aspect ratios and didn't account for it!

So everything was correct before

I think I probably know the answer to this but will ask anyway...

Is there no way that manipulating the Horizontal and vertical sensitivities combined with lower or higher sens multiplier would result in different monitor distances for the precision bolt?

I can't use a dpi script because the command is used for so many other things where you wouldn't want it, unless I start writing multiple return functions for the different weapons, and it only enable the script when I select the heavy cannon.

I struggle to see the point of the base sens values being in the menu when the multiplier has so much granularity already.

Also, just in case anyone is interested the intro skip launch option still works from Doom 2016, i.e 

+com_skipIntroVideo 1

On 3/29/2020 at 1:37 PM, TheNoobPolice said:

I think I probably know the answer to this but will ask anyway...

Is there no way that manipulating the Horizontal and vertical sensitivities combined with lower or higher sens multiplier would result in different monitor distances for the precision bolt?

I can't use a dpi script because the command is used for so many other things where you wouldn't want it, unless I start writing multiple return functions for the different weapons, and it only enable the script when I select the heavy cannon.

I struggle to see the point of the base sens values being in the menu when the multiplier has so much granularity already.

Not possible, the sensitivity is a product of both values with no separation for ADS.

The only solution I can think of is to have a dedicated key/macro for selecting the heavy cannon, which also activates the DPI switch when zooming.