Jump to content

Recommended Posts

Posted

Hey gang,

 

Most that are familiar with Nvidia Inspector are probably already aware, I was messing around with it this morning and gave this a try and it works quite well for me so thought I might share this as well.

 

Ok so if you use the Nvidia control panel to set certain things for DCS, you are probably aware that the DCS profile is hard coded into the control panel, ie it points to your stable release version of DCS ( 1.2) for the executable.

 

Now Nvidia still uses the old naming convention, Digital Combat Simulator:Black Shark for the DCS.exe executable. But this applies to all of DCS World, and will point to your DCS 1.2 install. Any settings you may have in there for DCS will only be effective with the 1.2 version.

 

DCS does such a good job with the graphics settings, about all I use the profile for are for things like setting AA and AS to application controlled, setting my graphics to single display performance mode, setting my monitor refresh to highest available as I have a 144 hz monitor, and setting power management to maximum performance so my graphics card does not down-clock whilst playing. I am sure others use it for many other settings as well.

 

So, how do I manage these same settings between my other two versions of DCS - 1.5 and 2.0?

I use Nvidia Inspector, which allows me to load up the profile for Digital Combat Series: Black Shark, from there I can remove the link to the DCS.exe executable( not delete the profile, simply remove the link). Then it will allow me to add the new link, by clicking the add link button, and browsing to the new executable - the DCS.exe executable in my DCS 2.0 Open Alpha directory. Click apply, and voila - when I fly DCS 2.0 Open Alpha my preferred settings for DCS are applied.

 

Should I elect to fly the 1.5 Open Beta, I just do the same - remove the link to the 2.0 Open Alpha, and add the link by browsing to the 1.5 Open Beta and choosing the DCS.exe executable from within that directory.

 

So my DCS profile I have set , remains the same and used throughout the different versions. And it really only takes a moment, to go into Nvidia Inspector and change the link out to the version you are flying.

 

Hope this may be of benefit to others, it certainly helped me as I was trying to figure out how to make my profile for DCS to work between the different versions I was flying.

  • Like 1

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted

Hi and thanks for this

 

Three questions, since the control panel vs inspector thing always had me confused:

 

1. Could you make separate profiles for the various DCS installs?

 

2. Nvidia Inspector just needs to be ran once, and the settings are stored/applied whenever you start the game. Or do you have to start Inspector/have it running whenever you start your PC and fire up the sim?

 

3.Inspector Settings override Nvidia Control Panel settings, correct?

Posted
Hi and thanks for this

 

Three questions, since the control panel vs inspector thing always had me confused:

 

1. Could you make separate profiles for the various DCS installs?

 

2. Nvidia Inspector just needs to be ran once, and the settings are stored/applied whenever you start the game. Or do you have to start Inspector/have it running whenever you start your PC and fire up the sim?

 

3.Inspector Settings override Nvidia Control Panel settings, correct?

 

 

1: Absolutely, just create each profile and link it to the appropriate dcs.exe. for that version you are creating it for.

 

2: Yes, once you apply settings from within Inspector, you can close it and they will always be applied for that profile.

 

3: Yes. No need to go back into control panel.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted (edited)

Actually correction no, can not create separate profiles for each version - when try applying the dcs.exe executable it will not allow as that name is already in use.

Even though it is in a separate directory, it still uses dcs.exe name and that causes the problem in trying to create multiple profiles.

 

Because it uses the same naming convention on the executable between versions that causes the problem.

That is why my way worked for me, because I remove the link to the executable and apply the appropriate one for the version I am flying. It really only takes a moment to do.

Edited by dburne

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted

I have separate profiles in inspector for beta/alpha and the current release. I just created a brand new profile with my own name for each version and pointed it at the relevant exe. I did have to delete the existing stock 'DCS: Black Shark' profile first though before I could add my additional ones. This might be what's preventing you from adding multiple DCS profiles. I'm guessing the next time we get a GEForce update that stock Black Shark profile will come back and muck things up though.

  • Like 1

i7-4790K@4.7GHz : EVGA 1070 SC : 16GB Corsair Vengence Pro : 2xEVO 840 SSD : EVGA 850W PSU : CORSAIR H100i Cooler : ASUS Z97-AR MB : CORSAIR OBSIDIAN 750D FULL TOWER

Posted

Yeah I expect your are correct, the problem lies in the default dcs.exe in Nvidia control panel, as long as it is there it will be a problem trying to use the same named exe for other directories.

 

That is why it works for me to just remove the link to the standard dcs.exe and link to the build I am currently flying.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted

Could you share your nvidia inspector settings please?

 

A screen capture could be great.

 

Thanks.

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted
Could you share your nvidia inspector settings please?

 

Here are mine.

Again mine is pretty simple and straightforward, as I set most my graphics preferences in the game GUI.

 

I use it mainly for making sure it runs at 144hz on my monitor's refresh rate, and maximum performance for power management.

 

I may end up going in and making some more adjustments and experimenting down the road as DCS 2.0 progresses.

 

DCS%20Inspector.jpg

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted

Thanks for sharing mate.

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted

Interesting dburne, that setting you have for the refresh rate !

 

Never used that ( wasn't even aware it could be used ) with any of my sims... Will give it a try, at 60, since that's the best my cheap ASUS LED monitor can give...

 

With this profile, do you use VSync ticked in the sim ?

Flight Simulation is the Virtual Materialization of a Dream...

Posted

I do not run VSync at all, but I have a 144Hz monitor ( which is why I set refresh to highest available).

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted (edited)

Thx dburne.

 

I just reecently started ticking the "VSync" option, but will probably revert to the older method with no VSync.

 

Both 1.5.2 and 2.0 give me excellemnt performance even with my hardware, the GPU certainly making the difference...

 

And just one more thing...

 

I believe Inspector is not sensitive to the actual path of the executable, but only to it's local name. When the executable starts being executed by the system, Inspector traps that and applies the profile. Otherwise it wouldn't prevent me to add the same name from both 1.5.2 and 2.0 bin folders, so...

 

I believe we do not really have to switch between folders, and simply leave "DCS.EXE" there. Provided DCS always starts from and exec with that name, the profile will be applied... ?

Edited by jcomm

Flight Simulation is the Virtual Materialization of a Dream...

Posted

I believe Inspector is not sensitive to the actual path of the executable, but only to it's local name. When the executable starts being executed by the system, Inspector traps that and applies the profile. Otherwise it wouldn't prevent me to add the same name from both 1.5.2 and 2.0 bin folders, so...

 

You may be right, I do tend to like to do things the long way around LOL.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...