prccowboy

you just need to set your Axis tune for the throttle to 'user curve' and adjust in-game for your specific throttle detents. I custom made my detents as a push through and hit afterburner somewhere around 20 on the scale

since we are talking about skin bugs, here is a very minor one: the HB_F14_EXT_01 - VF-103 Hi Viz Livery - PUSH stencil is backwards (not mirrored), see attached picture (from paint kit file) All other lettering is reversed (correct) but the PUSH lettering is normal (incorrect)

I have my monitor and windows calibrated to BT.2020 so typically try to keep DCS set to a gamma of 2.2-2.4; however, with lighting changes this doesn't always seem to be optimal. It would be nice if we had an in-game gamma calibration pattern so regardless of what calibrations (or lack thereof) that a user has they can adjust the gamma slider to match their individual setup to whatever baseline DCS is using. This may help with wide ranging user complaints from either too dark, too light, etc.

Created out of respect to a fellow DCS pilot who served with NATO AWACS, I have uploaded a skin of the 50th Anniversary NATO E-3A AWACS - Tail #442 I tried to keep it as historically accurate as possible, using photos of the actual aircraft. However, some minor creative license was taken given my artistic and skinning abilities and the confines of the E-3 model in DCS (notably location of tail number, etc.) v2.0 (2020-12-20) Updated to higher definition textures with more detail Files are here: https://www.digitalcombatsimulator.com/en/files/3309324/

BoneDust, did you ever get this figured out or fixed? I have same problem.

I'm having a similar problem with most F14 missions since the 2.5.6 update, including Create Fast Mission - the sim will start in map screen as if the player aircraft never spawned. Interestingly, in the HB Kish Kat Attack mission, it starts in map screen; However, after the 2 AI F14's launch from the carrier, the player F14 will spawn and you can start playing.

OK, quick update (I haven't had time for much testing) I can confirm SLI *IS working* on my rig running 2.5.4.25729. I had both GPU's running at around 90% utilization and framerates were about 75% higher than single card on that particular benchmark test. Note: I run single monitor and cannot comment on whether SLI works on multi-monitor or VR/WMR (I gave up on multi-monitor with SLI years ago)

SLI is working great for me on v2.5.3.22176. I am in process of updating to 2.5.4 and will provide feedback on latest build later

I had to go to 4.5GHz (didn't really want to push my CPU any hotter) to get min fps that I was happy with. As for background processes did you also monitor to see if any other programs are hitting the HDD's or network during your "hitches" ?

I usually have around 97% utilization on both GPU's, BUT I run single monitor currently. I'm starting to think that the multi-monitor setup with SLI is causing some folks performance drops, but since I don't run multi-monitor anymore I can't experiment to find a solution (and update my SLI guide)

He should be ok with a Rampage V Extreme and 5960x (40 lane PCI). That motherboard will run 4 x PCIe 3.0/2.0 x16 (x16, x16/x16, x16/x8/x8 or x16/x8/x8/x8 mode with 40-LANE CPU. However, I would suggest Nightstorm tries to modify his nvidia profile to allow SLI to work properly (probably won't fix the "hitches" but will allow the use of both gpu's)

check the autoupdate_log files in the DCS World folder. It should show what build you started with before the update/repair/etc.

I just updated to 2.5.3.22176. SLI is still scaling great for me and with no cloud flicker in this build. I think your issues are not DCS build related. As I mentioned before, post your NVI profiles and maybe we can figure out if there is something wrong in your config.

I've always had the same SLI scaling performance from 2.5.0 thru 2.5.3.21235 (I will try the latest build as soon as I can - but it is a pain from my current location to update with a capped bandwidth), but my point being that I still get a very good performance boost in SLI so I don't *think* the builds after 2.5.1 impacted SLI scaling (but you have very different hardware and drivers) yes, SLI is possible with your 16 pci lanes, but my point is that you are running x8/x8 not x16/x16 (I have seen benchmarks that show this will make a difference at higher resolutions and load) post your NVI settings, maybe we can find the issue there.

Hmm, I wonder if your PCI lanes are getting saturated with that 7700k and SLI with DCS. Do you have anything else using PCI-e? I've read conflicting opinions whether the limited PCI-lanes on the 7700 will impact performance in SLI edit: I noticed that both you (Drag80) and Snowblind are running cpu's with 16 PCI lanes - again not sure it there is a bottleneck there or not - just thought I would raise the possibility. FYI: I'm running an old i7-3930k@4.5 (with 40 pci lanes)

Not sure what to say. It is still scaling for me with NO cloud flicker in build 2.5.3.21235 Example Benchmark: With SLI: 88 fps No SLI: 52 fps I may try to update my build next week to see if there is something in the newer builds that killed SLI, but I'm happy with SLI performance and quality in 2.5.3.21235

I run both Stable and Open Beta versions

I am still getting great scaling using the settings I posted before, HERE However, I am still using the 385.69 drivers... GSync settings are available in either Nvidia Control Panel or Nvidia Profile Inspector.

if a single core on your cpu is already maxed then additional gpu power isn't going to get you better framerates (and you will see your gpu utilization drop). That said, what are your NVI profiles? what SLI compatibility bits? Finally, and I'm just spitballing here, have you tried disabling Gsync? Although I don't use GSync myself, I have read about problems with SLI and Gsync in other gaming forums.

I'm not sure what you mean between wing vapor and Lex vapor, but I still see wingtip vapor trails in 2.5.3.21235 with SLI enabled (at least in F-15 and A-10C, the 2 modules I tested). Are you referring to something else? edit: Never mind, I saw the new over-wing vapor effects in the Hornet discussions... (don't have that module)

I still get the same performance delta with the latest builds. In fact, I was forced back to a single card for a few days recently when one of my cards died. I repaired the bad card (reflow soldering) and I'm back to the same performance gains as shown in those older posts (but that's another story). Nevertheless, the experience again proved the difference in single and dual gpu SLI performance for me Anyway, I would be willing to help you troubleshoot if you want to PM me with details of your pc build and what you have done to enable SLI (and benchmark it)

Obviously. You can read the entire thread, or look HERE and HERE for examples of SLI performance gains

Fixed in 2.5.3.21235. No more flicker, good SLI performance These are the settings I use for SLI => https://forums.eagle.ru/showpost.php?p=3410823&postcount=65

To quote a little known movie, "I'll take it wherever I can get it" glad my suggestion fixed the problem for y'all - I've received a lot of help from others on this forum too

Yes! It seems that the cloud flickering with SLI is fixed in 2.5.3.21235 Thanks ED