[DX11] Help regarding Nvidia Profile Inspector (NPI)

[JHTrucker]

@BenganJ - I can't add anything "text" to that post... but the pic just needs to be there, at the bottom is more than good enough.
If it's a problem, just forget it. 11 people downloaded so far without seeing what it was!
I added the LHD/RHD zip yesterday without issue.

[BenganJ]

@JHTrucker

I'll fix it when I'm finished with dinner! :D

EDIT: DAMN, this was REALLY odd! I hade to change the word
'Move' almost at the bottom to 'Relocate'! DON'T ASK ME WHY! :roll: :shock: 8-)

[JHTrucker]

@BenganJ - Craziness! I guess i confused it with all my mad multimon ideas. Thanks.

[alonzam99]

so is there a solution to the "g_cam_window_block 1" for trackir users ? becuase now it works only when using mouse..

[BenganJ]

@alonzam99

Sadly it seems as if SCS themselves has to do that, as we don't know of
any parameters to correct. :( JHTrucker has shown HOW they could do
it, but it's up to them, I think!

[Ronin]

@olaf28 - Glad that you're happy with a "not ideal" solution.
What is your mirror distance set to? I use 100.
uset r_mirror_view_distance "100"
uset r_deferred_mirrors - perhaps set this to 0.

If you'd like to try another "smaller file" i've added "Smaller view 3, 4 & 5 (untested)".
Smaller view 1 - Has image 90% height and 80% width
Smaller view 2 - Has image 80% height and 80% width
Smaller view 3 - Has image full height and 70% width (black bar left and right)
Smaller view 4 - Has image full height and 65% width (black bar left and right)
Smaller view 5 - Has image full height and 60% width (black bar left and right)

Number of pixels per image (smaller = higher fps)
V0=2073600 <--1920x1080 full size image
V1=1492992
V2=1327104 <- works ok for you.
V3=1451520
V4=1347840 <- should run the same as V2
V5=1244160 <- better but less screen width

@JHTrucker

This week I tested a lot with versions 2, 3 and 4 of the small monitor setup.
The testing is quite intensive because you have to constantly start, shut down ETS2.

I have set = uset r_mirror_view_distance "100"

As mentioned earlier, version 2 works best for me. Version 3 and 4 works a little better, but;
- with version 3 the screen is small. You can fill this up by filling it up with, for example, mirrors.
- with version 4 the screen is even narrower. It seems like I now have an older 4: 3 TV screen. :D :D This doesn't really look nice anymore.

I also looked at the effect for the AA. This is still present but less clear.
As an example I added a zip file with 3 examples:
- Full screen with AA
- Full screen without AA
- Version 4 of the smaller screen with AA.

But to be tear free use:
uset r_vsync "2"
NPI frame limiter to 31 <-- if tear free that'll stop 45 fps and not conflict with vsync at 30.

I am now using uset r_vsync "2" with the NPI frame limiter set to 35. This works best for me.

[JHTrucker]

Yes i did show how SCS could/should do it but that would mean SCS having to read it here... i'm not member of SCS forum.

If anyone knows how to load cam files on the fly (or any mod file, without loading your profile again)... then we just need the original cam file that moves sideways and through the window and a modded one that just turns (no sideways movement) so head stays within cab at all times.
Now the button that opens the windows gets used for the cam file swap process as well... and that's a crude "potential" starting solution, but i'm only missing how to load on the fly. The modded cam files are easy.

The problem is VR Headsets... SCS rightly think having VR stop dead at a given place causes issues for VR users and so won't block it, ok.
However, trackir isn't a VR headset. I've used trackir for many years (trackir 3 bought new) and all racing sims stop your head from turning too far left/right to simulate restricted head movement when strapped into a racecar. There's never been an issue with this type of "block" for me.
SCS simply need to allow access to a config.cfg variable like that g_cam_block but for trackir users to decide for themselves to block or not.

[JHTrucker]

@olaf28 - I can give you a 100% width and 70% height? That'll be a ultra wide view instead of 4:3 or 16:9, black bar top and bottom.
Pixel count would be 1344000 compared to V3=1451520 & V4=1347840

[JHTrucker]

@BenganJ - Strange discovery.

Using the standard STEP 2 Single.AAv4 file, you get AA applied. Not strange.

Edit the file:
normalized_x: 0.000000
normalized_y: 0.000000
normalized_width: 0.900000 <--- change width.
normalized_height: 1.000000
This means screen image will be 90% width and 100% height.
Check game = no AA. Still not strange.

Edit the file again:
normalized_x: 0.000000
normalized_y: 0.000000
normalized_width: 1.000000 <--- change back to 1.0
normalized_height: 0.900000 <--- change height.
This means screen image will be 100% width and 90% height.
Check game = AA applied. This is the strange bit.

Conclusion, the image doesn't have to fully match the game resolution, just the width has to match (100%) for AA to get applied to the whole screen no matter how high that image is.

[alonzam99]

Yes i did show how SCS could/should do it but that would mean SCS having to read it here... i'm not member of SCS forum.

If anyone knows how to load cam files on the fly (or any mod file, without loading your profile again)... then we just need the original cam file that moves sideways and through the window and a modded one that just turns (no sideways movement) so head stays within cab at all times.
Now the button that opens the windows gets used for the cam file swap process as well... and that's a crude "potential" starting solution, but i'm only missing how to load on the fly. The modded cam files are easy.

The problem is VR Headsets... SCS rightly think having VR stop dead at a given place causes issues for VR users and so won't block it, ok.
However, trackir isn't a VR headset. I've used trackir for many years (trackir 3 bought new) and all racing sims stop your head from turning too far left/right to simulate restricted head movement when strapped into a racecar. There's never been an issue with this type of "block" for me.
SCS simply need to allow access to a config.cfg variable like that g_cam_block but for trackir users to decide for themselves to block or not.

I hope they will add it in the final version.