SkateZilla

VRS doesnt Model HOL Blocks, Nor do they model every system in the Hornet, and half the systems modelled are "Baked" to look real without using any real world data. HOL has Zilch to do with the display colors, it's the Programming Language the aircraft uses.. Not going to happen, their 3D Model Assets are licensed and do not belong to them.

Which makes it hard to debate if it's overpowered or nerfed, There's Plently of Aero Data, and there's plenty of Western Systems Docs.. so it's a Hybrid, like the Jeff,. But if there was only ever 1, you cant say it was O.P or Nerfed..

The only time you'd ever see 85% utilization in DCS is if your in the sky with no terrain or objects nearby, in a cockpit with no MFDs or Mirrors to render multiple viewports. Once you populate the environment, the object counts and DX11 CPU Overhead bring GPU Utilization down, for EVERY GPU, on EVERY CPU Platform, for EVERY User. It's a DX11 Fact, Even More so in MP, and Even more so in VR or Multi-Screen systems. High DCS Object/Unit Counts = DX11 CPU Overhead and Thread bottlenecking.

Adding V-Cache Wont Fix the DX11 CPU Overhead and/or Threading bottlenecks you typically see in DCS. What it will do is give you quicker accessing of command functions in the cache vs calling the system memory or page file. it helps in Titles or DCS Scenarios that do not face any bottlenecks, but in MP Missions, the scripts and object counts alone will hit both the Threading Wall, and the DX11 Overhead Wall. The Best case Scenarios are +25%, on a game that has always run 200+ FPS already, at 720P, thus removing any CPU or GPU Bottleneck, but giving a boost in the sheer fact that the game's GFX Engine didnt have to poll the system memory for the directx commands, etc. The performance is there and I'd say it's the best AM4 CPU to have for gaming, but as results for DCS, you wont see any vast magical improvements.

Model#'s typically help, as Ram pricing varies more by latency and platform now than size.

As Stated previously above, You'd have to use a shortcut until the new version of the app is done. There's no way to add the new commands to the current version as it's legacy code and been archived.

it depends on rendering pipe lines, viewports and total resolution. ie a F-86F Cockpit's MSAA Footprint would be less than, a F-16 or F-18 with MFDs set to 1024x1024, as you'd have multiple rendering viewports using memory.

This is normal until you get MT and Vulkan, due to the bottlenecks present in the ST Core and DX11.

Your card was already Xrayed when: - it was loaded onto a container ship from nVidia, - again when it was unloaded from container ship at destination, - a few more times in general logistics of going to and from the warehouses, - a few more times in general logistics of going from warehouse to stores or customer directly.

Yup, Didnt realize the slide simply said "Cache" didnt specify L2 or L3, But 7950X35 is 16MB L2, 7900X3D is 12, and 7800X3D is 8

They Put CFTs on the F-15Cs that were flying out of iceland, outside of that, ANG started to adopt them.

Well the L3 Cache is Tricky, in the past it was per core, as all the cores were on the same die, and the L3 was adjoined to the Cores, so a laser cut core, would also cut the L3. With Zen, it's per CCX, as the Cache is centrally located on the CCX Between the cores, but any core on the CCX can access the L3 Pool. So if they Stack the Extra say 64MB on the VCache on one CCX, and there's 7950X is 16 Cores and 64MB of Cache / 2 CCXs = 32 MB L3 Per CCX. (64 MB Total). So: The 7950X3D is basically the Full 16 Cores x 2 CCX x 32 MB + the 64MB of VCACHE = 128MB L3 The 7900X3D is basically the cut 12 Cores x 2 CCX x 32 MB + the 64MB of VCACHE = 128MB L3 The 7800X3D is basically the 8 Cores x 1 CCX x 32 MB + the 64MB of VCACHE = 96MB L3 And you can look at any CCX's that fail 3 Cores can be cut to 4 as well, So you can have 2 SubRevisions of 7900X3D, Depending on Defects in the yields. One with 8 Full Cores on a CCX, and 4 on the other, the 32 MB of L3 Per CCX Remains accessible + the additional 64MB of L3 VCACHE. One with 6 Full Cores on a CCX, and 6 on the other, the 32 MB of L3 Per CCX Remains accessible + the additional 64MB of L3 VCACHE. The Performance would be limited to thermals on the CCX without the VCache Stacked on it. What confuses users now is AMD's Site lists 7950 and 7900X3D as 128MB L3., and the 7800X3D as 96. While the slide published shows, 104MB ,140MB , 144MB of L3 Cache, So where's the additional 8/12/16 MB of L3 Coming from...?

Verify you've set the saved games folder.

it really depends on how they want to breakdown the V-Cache.

Not all cores, but the CCX sans V-Cache is the CCX that will have the Cores permitted to go that high, the CCX w/ V-Cache will have a lower limit due to voltage and thermals.

$50 it was a split rail PSU and one of the rails went Poof.

There's a whole 5800X3D thread in the hardware section.

plus any strictly gamer that isnt doing anything else doesnt need 24 or 32 threads, lol Also the studio I was at last week uses the 5800X3D as the VCACHE speeds up the VFX Rendering. But they also said they would be considering upgrading to 7950X as the chip would give them the ability to assign 16 threads to render VFX and coordinate w/ GPU Rendering items with the VCACHE, and another 16 threads for Compressing using the CPU-Powered HVEC Codec at 5.7Ghz.

in Video Rendering they will sell, especially with 24 threads and 12 of them at 5.7 Ghz out of the box. As I can specify which cores I want my post effects rendered on, and which cores I want my final MKV Compressed with, As much as GPUs already handle, Exporting from the Editor, GPUs arent as fast as 12 cores. Using a GPU for compressing HVEC1 for Streaming is fine, but most studios use those CPU Cores for rendering scenes.

Yup, 7800X3D is one CCX w/ 3D VCACHE 7900X3D is two CCX w/ 3D VCACHE on the Full 8 Core, and then none on the 2nd CCX w/ 4 Cores Disabled. 7950X3D is two CCX w/ 3D VCACHE on the Primary CCX and none on the 2nd. But, The CCX's without 3DVCACHE are the ones that will be Allowed to Turbo to 5.6/5.7 GHz. on the 79xxX3D Chips. So one CCX is VCACHE Heavy, and the other Turbos higher on those 2 CPUs. I'm looking to get a 5800X3D 2nd hand, as that's the highest my Mainboard will Allow.

No All 3 of those are FPU/11 (480GAL) Tanks

AM5 is right behind DDR5.

Sounds more like a bad power sin wave / frequency problem. Bad fans wont kill a pc, there's too many failsafes on modern hardware, it wouldnt shutdown to save the hardware if temps were too high, Gotta ask yourself, what caused all these fans to go bad so quickly, then eventually either the Mainboard VRM, the processor or the PSU Rails.