blkspade

Well it wasn't an explicit statement of either, but it implies that there should be above average safety in buying the same kit at 2 different times. That said GSkill is a brand I prefer, for RAM.

In my experience it seems GSkill would sooner discontinue a series/sku, as opposed to randomly switching ICs down the line on a given sku.

It's actually unlikely that AMD is going to increase the core count on next GEN mainstream. The density increase of 7nm+ still doesn't allot the room needed on the AM4 package, unless they can shrink the IO die. They've already stated that there isn't going to be a change in core counts on the server package (which is the same silicon), so the CCD core density is likely remaining at 8. Physical changes more likely to happen are more cache and/or APUs with higher cores than previous gen. More cores is an eventuality though as ~5Ghz is the clock wall (before the power/thermal curve get out of hand) and IPC will eventually top out when they can no longer shrink features anymore. At some point more performance will only come from taking advantage of the increased density, for as long we're still on silicon anyway.

As there have been people on here with the highest possible hardware available running VR and reporting performance, its become quite apparent that there is no hardware that'll run DCS on MAX settings in VR without a reduced frame rate. The software just doesn't allow for it, and any money thrown at it would likely be a waste (if looking for immediate results) before we know how Vulkan will help performance.

So an apparent primary flaw with the F-16 was that it wasn't giving mid-course corrections to the AIM-120, yet was patched today. Now a common occurrence for DCS air to air missiles has always been that any 2 that incidentally come close enough together will detonate. You could do this to your own missile if you fired 2 too closely together at the same target while accelerating. The only missiles that seem to have any sort of radar signature in DCS are A-G and some SAMs. The only willful targeting of AA missiles I've seen before this has been with IR ones tracking the rocket motor.

Yeah they stagnated the industry for a really long time by continuing to reserve high core count CPUs for HEDT, and other shenanigans. While it probably won't mean much for our particular sim, AMD is basically sneaking in through the back door for getting multi-core gaming optimizations on consoles. Even though I'm not into civilian flight sims, I'm interested in how that next big one will run.

The F-14 can see missiles on datalink. Sent from my Pixel using Tapatalk

The missile can be launched in Situational Awareness Mode, and similarly so can the F-18 in LTWS, in DCS. There is however a high probability for the missile to miss if the target maneuvers a lot prior to the missile reaching active range. Neither can multi target from their respective modes.

This may be useful for 3900X owners. https://www.techpowerup.com/review/1usmus-custom-power-plan-for-ryzen-3000-zen-2-processors/2.html

I believe the point of that video is more about how to best allocate your money with a limited budget. Intel has been reluctant to reasonably reduce prices on older CPUs (4790K still sells for over $300 in some places). While every previous Ryzen gen drops by a lot. Tie that with fact that Intel's platform is basically dead, where as AM4 is going to have a final series of chips next year, should you want/need more CPU performance.

That's kind of the point I made in my first post, basically all the drives are rebrands besides Intel and Samsung, but the product being rebranded is from a company as reputable as the others. You bought an Asus 1080ti as opposed to a founder's edition straight from Nvidia. It's literally the same thing. I work in computer repair and have seen various early model SSD's and Optane (not technically nand) that had failed. The best thing you can do for ssd longevity is keep the temps (applies for HDDs too) in check and fill it once. If you can fill and wipe it without any issue, it's probably not going to experience a premature failure. Still have an OCZ Vertex from 2012 that's been in 3 different builds, going strong. I haven't had a drive failure of any sort since Maxtor and Quantum were still a thing.

At the same time firmware updates are to fix discovered problems or deficiencies. Samsung isn't putting out anymore updates for my EVO 850/860 drives. Sometimes there just isn't an actual reason to put out any more updates. That article mentions the firmware update to expand nand support for some future product that has nothing to do with the already purchased devices. They explicitly state that there wasn't really a quantifiable change between firmwares revisions. If it's doing what you expect it to out of the box (especially if you looked at reviews first) there not be a firmware update is kind of a non-issue.

I picked up a 2TB Corsair MP510 because it was down to $253 and is rated for 3300TBW a few months back. The Samsung equivalent had like 1/3 the endurance being marginally faster for way more money. Didn't seem worth it to me.

Guys the engine is multi-threaded, its just not doing all the things we'd like to see it do. Some one started a thread showing some degree of performance scaling with various thread counts. The only way the extra threads are being leveraged atm is in IO it seems, but the engine is aware of them. DX/D3D11 doesn't easily thread well. The Vulkan implementation should then be able to work with that thread availability. We probably don't need a bunch of engine features to have there own thread, since the main issue now is the render operation must be last and tied to the main thread behind everything else. One of the areas of focus in Vulkan is in not having the GPU waiting, by various means.

Nand is Nand, the main difference is that Samsung makes the stuff they sell while nearly everyone else us is using Micron's. Most of Micron's stuff has a higher TBW rating than Samsung which I rate higher than warranty even though they're all 5yrs. A choice in flash storage probably shouldn't be about max sequential unless you're doing high throughput workloads regularly The random read speeds of small files like in video games rarely benefit from having anything faster than a SATA SSD. They all benefit from keeping the controller cool. I'm seeing a near equal amount of failed older laptop m.2 ssd's at work that are based on either intel, samsung, or micron. Although all the micron ones I've seen have been Transcend modules.

I'm generally used to seeing the 120 almost randomly choose when to loft from the F-15/F-18, but never like that.

Just look up facetracknoir. Sent from my Pixel using Tapatalk

An EA release amounts to "proof of life" as to display the project isn't vaporware. I'm personally completely against the whole pre-order culture in games lately. Pre-ordering software is stupid because its something you do with a physical item in danger of their being a shortage of (that you for reason must have day 1). I can give ED a soft pass in not being backed by a huge publisher, but I still want product in "hand" within a time frame close to relinquishing funds from said hand. I can appreciate the associated discount on buying early, but shooting up to the full asking price just by being able to touch it is a bit ridiculous when its no where near complete.

So its a VR problem, a little bit of a CPU problem, but really a DCS engine problem. When ever your CPU can't keep up with the VR headset native refresh, frames are locked for smoothing, which loads your GPU less. No CPU available will fix the problem, in DX 11 it seems. This is called ASW (Asynchronous Space Warp) in Rift headsets, and I am unsure of the equivalent name for others. The tomcat actually hammers the GPU (1080ti) in VR, so I'm locked at lower frames with the GPU at 90%+. The CPU problem is something Vulkan should correct for.

It's not really about the real life counter parts being similar, its about how you would represent them in a sim/game. The framework that makes it possible is the same, and then the visual representation is altered on top of that for each platform.

That's actually becoming less of an issue with Microsoft increasingly supporting Linux development.

Just because Microsoft plans to end support, doesn't mean people are going to immediately stop using it.

Basically if you notice points of low performance where the GPU is being under utilized, that's from the CPU not keeping the GPU fed. Most of the performance improvement should be in higher lows, unless you're entirely GPU limited. Its certainly a more prominent issue in VR.

The lights do that as soon as you're cleared contact. Well at least for vertical and forward position.

Yeah, but the fact the AI will CFIT from time to time under stress kind of make up for that.