[DX11] Help regarding Nvidia Profile Inspector (NPI)
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
@JHTrucker I'm playing at native resolution of 2k - 2560x1440 so setting a DSR is pointless (I tried it already). Except of massive fps drops, I don't get any quality upgrade, quite the opposite (because of DSR smoothing).
This was taken at 4x MS + 4x SGS with LOD at -1.000, but I played also at 8x MS + 8x SGS with LOD at -1.500 with same results. These bad textures are result of this particular bit 0x80000A7F. I tried other ones, some fixes these issues on signs, but cause even bigger issues elsewhere. So, this one, in particular, was a compromise, since the game looks great with it except for these small signs.
Let's hope SCS will eventually do something about AA so we could stop using NPI workarounds.
This was taken at 4x MS + 4x SGS with LOD at -1.000, but I played also at 8x MS + 8x SGS with LOD at -1.500 with same results. These bad textures are result of this particular bit 0x80000A7F. I tried other ones, some fixes these issues on signs, but cause even bigger issues elsewhere. So, this one, in particular, was a compromise, since the game looks great with it except for these small signs.
Let's hope SCS will eventually do something about AA so we could stop using NPI workarounds.
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
Thanks again, i would rather have smooth gameplay than max fps, i will try all the settings you suggest and see what works best, also i hear quite a bit about uset t_averaging_window_length, is there a certain number i should set this to ?JHTrucker wrote: ↑December 1st, 2021, 7:01 pm@robswfc - You can decide at what fps you are happy to constantly run at or have high fps that constantly drop.
Most people want max fps whilst I want smooth constant fps and that's why I run at 30fps 2xMSAA 3840x1024 with my old hardware.
NOTE 3A/3B is what I suggested you look at, but here is what i'd try.
I assume your NPI vsync settings are 'app control' and that you haven't forced any settings there.
Your 144Hz monitor - config.cfg:
uset r_mode_refresh "144"
uset r_vsync "3"
That will give a constant 48fps if it can.
uset r_mode_refresh "144"
uset r_vsync "4"
That will give a constant 36fps if it can.
uset r_mode_refresh "120" - if your monitor can run at 120Hz
uset r_vsync "3"
That will give a constant 40fps if it can.
As an example, BenganJ had a gtx1660ti and set all his extreme settings from his first post and 4xMSAA and locked at 30fps because his gpu on his 60Hz monitor couldn't keep 60fps.
uset r_mode_refresh "60"
uset r_vsync "2"
That will give a constant 30fps if it can.
An another option would be to use 'tear control' to turn off vsync when the fps drop below it. This way it'll only drop the fps it needs to rather than drop to the next vsync level... but you will see screen tearing when vsync is off.
Using one of the above config settings and then do these:
In NPI set Vertical Sync to 'app control'.
In NPI set Vertical Sync Tear Control to 'Adaptive'.
Or, if your monitor is gsync/freesync then look here: viewtopic.php?p=46155#p46155
EDIT: Just in case you don't know why you have fps drops.
Your cpu generates each frame.
Your gpu renders each frame.
If your fps drop and gpu usage is 100% then your gfx settings are too high bottlenecking your gpu.
If your fps drop and gpu usage also drops then your cpu is too busy running the game etc or current frames are more detailed which takes your cpu longer to generate, your cpu is the bottleneck as it can't meet the demand which is why your gpu usage drops.
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
Set averaging_window_length to double your in game refresh rate, make sure V Sync is on. I use G Sync so not sure what that would be.
PC: 5600X/16GB Crucial Ballistix 3600Mhz/Gigabyte RTX 3080
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
averaging_window_length:
I would set it to double your vsync fps rather than double your Hz.
Original info here: viewtopic.php?p=25158#p25158
But that was back in 1.37 and as you all know SCS has made a lot of 'heavy' changes since then.
Importantly, this doesn't fix frame drops, it helps with rubber banding where the fps are constant but the forward motion speeds up and down.
Example why vsync fps and not Hz:
uset r_mode_refresh "144"
uset r_vsync "4"
Is vsync 36fps and so set averaging_window_length 72 (2 seconds or 8 seconds using Hz).
uset r_mode_refresh "60"
uset r_vsync "1"
Is vsync 60fps and so set averaging_window_length 120 (2 seconds).
uset r_mode_refresh "120"
uset r_vsync "2"
Is vsync 60fps and so set averaging_window_length 120 (2 seconds or 4 seconds using Hz).
I just think 2 seconds is enough as i'm sure there's a point where too many past frames calculated may lead to other problems?
I would set it to double your vsync fps rather than double your Hz.
Original info here: viewtopic.php?p=25158#p25158
But that was back in 1.37 and as you all know SCS has made a lot of 'heavy' changes since then.
Importantly, this doesn't fix frame drops, it helps with rubber banding where the fps are constant but the forward motion speeds up and down.
Example why vsync fps and not Hz:
uset r_mode_refresh "144"
uset r_vsync "4"
Is vsync 36fps and so set averaging_window_length 72 (2 seconds or 8 seconds using Hz).
uset r_mode_refresh "60"
uset r_vsync "1"
Is vsync 60fps and so set averaging_window_length 120 (2 seconds).
uset r_mode_refresh "120"
uset r_vsync "2"
Is vsync 60fps and so set averaging_window_length 120 (2 seconds or 4 seconds using Hz).
I just think 2 seconds is enough as i'm sure there's a point where too many past frames calculated may lead to other problems?
multimon_config.sii files: viewtopic.php?p=17658#p17658
controls.sii edits: viewtopic.php?p=24744#p24744
TrackIR Driving Enhancements: viewtopic.php?p=46613#p46613
Extra Cameras: viewtopic.php?p=46034#p46034
controls.sii edits: viewtopic.php?p=24744#p24744
TrackIR Driving Enhancements: viewtopic.php?p=46613#p46613
Extra Cameras: viewtopic.php?p=46034#p46034
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
ok i see (i think) thanks for the explanation and your help the game is playing better than it was, still get the odd drop but not as constant.JHTrucker wrote: ↑December 2nd, 2021, 2:28 pmaveraging_window_length:
I would set it to double your vsync fps rather than double your Hz.
Original info here: viewtopic.php?p=25158#p25158
But that was back in 1.37 and as you all know SCS has made a lot of 'heavy' changes since then.
Importantly, this doesn't fix frame drops, it helps with rubber banding where the fps are constant but the forward motion speeds up and down.
Example why vsync fps and not Hz:
uset r_mode_refresh "144"
uset r_vsync "4"
Is vsync 36fps and so set averaging_window_length 72 (2 seconds or 8 seconds using Hz).
uset r_mode_refresh "60"
uset r_vsync "1"
Is vsync 60fps and so set averaging_window_length 120 (2 seconds).
uset r_mode_refresh "120"
uset r_vsync "2"
Is vsync 60fps and so set averaging_window_length 120 (2 seconds or 4 seconds using Hz).
I just think 2 seconds is enough as i'm sure there's a point where too many past frames calculated may lead to other problems?
Thank you
- AustinN360
- PPM
- Posts: 10
- Joined: March 9th, 2021, 9:11 am
- Location: Telford UK
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
The problem has seemed to have disappeared in the latest Beta Update.AustinN360 wrote: ↑November 25th, 2021, 6:10 pmHere is a video showing the issues I am having.
My NPI Settings:
And my current Congfig.cfg File:Code: Select all
<?xml version="1.0" encoding="utf-16"?> <ArrayOfProfile> <Profile> <ProfileName>Euro Truck Simulator 2</ProfileName> <Executeables> <string>eurotrucks2.exe</string> </Executeables> <Settings> <ProfileSetting> <SettingNameInfo /> <SettingID>2916165</SettingID> <SettingValue>917504</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Texture filtering - Driver Controlled LOD Bias</SettingNameInfo> <SettingID>6524559</SettingID> <SettingValue>0</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Ambient Occlusion</SettingNameInfo> <SettingID>6714153</SettingID> <SettingValue>3</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Texture filtering - LOD Bias</SettingNameInfo> <SettingID>7573135</SettingID> <SettingValue>4294967284</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Maximum pre-rendered frames</SettingNameInfo> <SettingID>8102046</SettingID> <SettingValue>3</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Texture filtering - Quality</SettingNameInfo> <SettingID>13510289</SettingID> <SettingValue>4294967286</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo /> <SettingID>14888842</SettingID> <SettingValue>2147486335</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Anisotropic filtering setting</SettingNameInfo> <SettingID>270426537</SettingID> <SettingValue>16</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Power management mode</SettingNameInfo> <SettingID>274197361</SettingID> <SettingValue>1</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Antialiasing - Mode</SettingNameInfo> <SettingID>276757595</SettingID> <SettingValue>1</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Toggle the VRR global feature</SettingNameInfo> <SettingID>278196567</SettingID> <SettingValue>0</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>VRR requested state</SettingNameInfo> <SettingID>278196727</SettingID> <SettingValue>0</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>G-SYNC</SettingNameInfo> <SettingID>279476652</SettingID> <SettingValue>1</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>G-SYNC</SettingNameInfo> <SettingID>279476687</SettingID> <SettingValue>1</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Anisotropic filtering mode</SettingNameInfo> <SettingID>282245910</SettingID> <SettingValue>1</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Antialiasing - Transparency Supersampling</SettingNameInfo> <SettingID>282364549</SettingID> <SettingValue>56</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Antialiasing - Setting</SettingNameInfo> <SettingID>282555346</SettingID> <SettingValue>37</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Memory Allocation Policy</SettingNameInfo> <SettingID>286335539</SettingID> <SettingValue>2</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Enable G-SYNC globally</SettingNameInfo> <SettingID>294973784</SettingID> <SettingValue>0</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Antialiasing - Line gamma</SettingNameInfo> <SettingID>545898348</SettingID> <SettingValue>35</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Threaded optimization</SettingNameInfo> <SettingID>549528094</SettingID> <SettingValue>1</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> <ProfileSetting> <SettingNameInfo>Triple buffering</SettingNameInfo> <SettingID>553505273</SettingID> <SettingValue>1</SettingValue> <ValueType>Dword</ValueType> </ProfileSetting> </Settings> </Profile> </ArrayOfProfile>
Any ideas what could the the issue?Code: Select all
# prism3d variable config data uset s_init_intro_music_mute "0" uset s_init_intro_music_volume "1" uset s_init_ui_music_mute "1" uset s_init_ui_music_volume "0.5" uset s_init_master_mute "0" uset s_init_master_volume "1" uset s_output_driver "{28ee00ea-4086-4649-a182-d2ec7dc5403a}|0|VoiceMeeter Input (VB-Audio VoiceMeeter VAIO) (48000 Hz)" uset s_live_update "0" uset s_suspend_sound "1" uset s_sound_debug "0" uset r_show_sun_cascades "1" uset r_tonemap_debug "0" uset r_drr_strength "8.0" uset r_hide_helpers "0" uset r_full_resolution_corrections "0" uset g_mm_help_shown "1" uset g_frame_image_fmt "jpg" uset g_frames_path "" uset g_editor_zoom_speed "1.0" uset g_map_note_user_id "0" uset g_color_feedback "1" uset g_disable_hud_activation "0" uset r_wireframe "0" uset g_interior_camera_zero_pitch "0" uset r_multimon_exterior_in_aux "0" uset r_multimon_interior_in_main "1" uset r_multimon_rotation_aux "0" uset r_multimon_rotation_right "0" uset r_multimon_rotation_left "0" uset r_multimon_rotation_center "0" uset r_multimon_vert_offset_right "0" uset r_multimon_vert_offset_left "0" uset r_multimon_border_fov_right "0" uset r_multimon_border_fov_left "0" uset r_multimon_fov_vertical "0" uset r_multimon_fov_horizontal "50" uset r_multimon_mode "4" uset r_use_depth_bounds "1" uset r_buffer_page_size "30" uset r_deferred_debug "0" uset r_mirror_scale_y "1" uset r_mirror_scale_x "1" uset r_scale_y "1" uset r_scale_x "1" uset r_normal_maps "1" uset r_sunshafts "1" uset r_color_saturation "1.0" uset r_color_yellow_blue "0.0" uset r_color_magenta_green "0.0" uset r_color_cyan_red "0.0" uset r_color_correction "1" uset r_light_flares "1" uset r_cloud_shadows "1" uset r_dof_filter_size "0.5" uset r_dof_transition "400.0" uset r_dof_start "200.0" uset r_dof "1" uset r_ssao "0" uset r_smaa "0" uset r_fake_shadows "2" uset r_sun_shadow_texture_size "4000" uset r_sun_shadow_quality "4" uset r_mirror_group "3" uset r_mirror_view_distance "700" uset r_deferred_mirrors "2" uset r_nowmi "0" uset r_startup_progress "0" uset r_setup_done "1" uset r_gamma "1" uset r_manual_stereo_buffer_scale "1.0" uset r_manual_stereo_ui_fov_game "100" uset r_manual_stereo_ui_fov "80" uset r_manual_stereo_ui_dist_game "0.5" uset r_manual_stereo_ui_dist "0.8" uset r_manual_stereo_in_menu "1" uset r_minimal_unfinished_frames "0" uset r_no_frame_tracking "0" uset r_fullscreen "0" uset r_mode_refresh "60" uset r_mode_height "1080" uset r_mode_width "1920" uset r_path "" uset r_device "dx11" uset i_virtual_cursor_speed "500.0" uset g_stream_exts ".ogg;.mp3" uset g_thrustmaster "1" uset g_tobii "1" uset g_trackir "1" uset g_lod_factor_pedestrian "15" uset g_pedestrian "1" uset g_light_span_factor "1" uset g_light_distance_factor "1" uset g_vehicle_flare_lights "1" uset g_auto_traffic_headlights "1" uset g_lod_factor_parked "15" uset g_lod_factor_traffic "15" uset g_traffic "1.0" uset g_kdop_preview "0" uset g_screenshot_on_bug_quality "100" uset g_screenshot_on_bug "0" uset g_shoulder_block_coloring "0" uset g_debug_map_limits "0" uset g_city_name_move "0" uset g_developer "1" uset g_semantical_pause_inactivity "120" uset g_pause_on_disconnect "1" uset g_semantical_ff_inactivity "300" uset g_steam_rich_presence "1" uset g_steam_browser "1" uset g_steam_screenshots "2" uset g_artist_id "0" uset g_save_format "2" uset g_trailer_cables_mode "2" uset g_spec_trans_refill_tank "1" uset g_flyspeed "32.768" uset g_online_loading_screens "1" uset g_news "1" uset g_colbox "0" uset g_radio_mode "1" uset g_ignore_low_fps "0" uset g_truck_light_specular "1" uset g_gfx_all_scales "0" uset g_gfx_advanced "1" uset g_gfx_quality "-1" uset g_hq_3d_scale "0.0" uset g_hq_3d_screenshot "0" uset g_menu_aa_limit "0" uset g_additional_water_fov "20.0f" uset g_water_reflect_actor "0" uset g_rain_reflect_hookups "1" uset g_rain_reflect_actor "1" uset g_rain_reflect_traffic "1" uset g_rain_reflect_cache "1" uset g_rain_reflection "3" uset g_reflection_scale "0" uset g_reflection "3" uset g_grass_density "2" uset g_veg_detail "2" uset g_save_indicator "1" uset g_game_version "1.43.0.40" uset g_force_online_lscrs "0" uset g_hw_info "1" uset g_sns "" uset g_glass_debugging_level "0" uset g_line_sort "0" uset g_cargo_sort "0" uset g_bloom_standard_deviation "0.5" uset g_bloom_override "0" uset g_bloom "1.0" uset g_global_force_load_selector "0" uset g_desktop_fadeout "60" uset g_minicon "0" uset g_console_state "0" uset g_console "1" uset g_texture_usage_stats "0" uset g_fps "0" uset ui_tooltip_delay "0.4" uset r_imgui_scale "1.0" uset r_output "-1" uset r_adapter "-1" uset r_vsync "2" uset r_color_mode "0" uset r_anisotropy_factor "1" uset r_texture_detail "1" uset cf_asus_aura "1" uset cf_razer_chroma "1" uset v_bug_break "0" uset t_locked_fps "0" uset t_averaging_window_length "60"
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
Good to know.AustinN360 wrote: ↑December 4th, 2021, 1:46 am
The problem has seemed to have disappeared in the latest Beta Update. :party: :party: :party: :party: :party: :party: :party: :party:
My first reply to you on November 24th included this:
"As a test, assuming you're using this NPI AA, set scaling to 125% to disable it."
I think you'd have seen the same issue without AA based on the fact you say the beta update has now fixed it.
SCS must still be messing with gfx changes but not talking about them.
multimon_config.sii files: viewtopic.php?p=17658#p17658
controls.sii edits: viewtopic.php?p=24744#p24744
TrackIR Driving Enhancements: viewtopic.php?p=46613#p46613
Extra Cameras: viewtopic.php?p=46034#p46034
controls.sii edits: viewtopic.php?p=24744#p24744
TrackIR Driving Enhancements: viewtopic.php?p=46613#p46613
Extra Cameras: viewtopic.php?p=46034#p46034
Re: [DX11] Help regarding Nvidia Profile Inspector (NPI)
Hi….I am using ATS 1.43 and the scheme is working excellent for the AA. I am finding the road signs and building signs hard to read at a far away distance. As you approach the signs they become clear. Not sure if this is related to SCS doing their improvements in this area. I tried increasing the -1.5 to a higher number but things remain the same (I’m using 8x for both as I find it relieves pressure off the system from the 4x but still experimenting with this, I do know the 8x only gives you 4x but I think there is less pressure on the system for some reason). The 4x is also blurry at far distances. So not sure if anyone else is having this problem. I am using the latest nvidia drivers and there seems to be no sharpening filter like we had before where we could set the sharpening value to 60 and .17 but there is some kind of a scaling factor option and if you open it up you can set a sharpening value for the 60 if even this is the same thing as before. I haven’t tried this yet but tomorrow I’ll give it a go. If I do set this value then the options for setting full screen and aspect and perform scaling by gpu on monitor are all greyed out which might be ok. I might have to set a sharpening value in the GeForce experience overlay to see if it helps but it might make things worse as things up close are already sharp and looking ok. If you have any ideas that would be excellent, cheers
Edit: I set this value to 60 and it definitely helped with the sharpening, obviously not perfect but much better as I think ATS has a low lod radius circle. I might try a lower value like 50 to see the effect because if set too high then I tend to notice more shimmering of textures like road lines for example.
Edit 2: I like the 60 better.
In regards to the shimmering textures, I found out that in the NPI I had the 16x but in the NCP it was set to application controlled, so I set it to 16x in NCP and the shimmering is reduced and back to a normal state. In the NCP, a bunch of other settings were messed up as well and not sure why these changes happened but I re-checked everything and the game looks awesome again.
Edit: I set this value to 60 and it definitely helped with the sharpening, obviously not perfect but much better as I think ATS has a low lod radius circle. I might try a lower value like 50 to see the effect because if set too high then I tend to notice more shimmering of textures like road lines for example.
Edit 2: I like the 60 better.
In regards to the shimmering textures, I found out that in the NPI I had the 16x but in the NCP it was set to application controlled, so I set it to 16x in NCP and the shimmering is reduced and back to a normal state. In the NCP, a bunch of other settings were messed up as well and not sure why these changes happened but I re-checked everything and the game looks awesome again.
Last edited by VSigda on December 15th, 2021, 2:47 pm, edited 2 times in total.
- AustinN360
- PPM
- Posts: 10
- Joined: March 9th, 2021, 9:11 am
- Location: Telford UK