to all you arm chair PC experts out there
Actually, I'm not an armchair PC expert. I am a legitimate professional in this field, having run an IT consulting business of my own for 16 years now and before that I spend 10+ years working at Microsoft, where I supported games when I first started before moving to different positions in the company, eventually ending up as an Alliance Support Group Engineer responsible for being support of last resort for Fortune 100 companies, half a dozen of whom had my pager number. I had the authority to wake developers up in the middle of the night and task then with a 4 hour patch, if the situation warranted it. I was extremely well trained in all aspects of Microsoft products, from servers thorough DirectX and hardware because several of my assigned client corporations happened to be in the industry. The literal exact same things you're saying now were so common in cases vback then it's a little silly. "But this is the only game where it happens", for example. SO what? Maybe the other games you play don't use a single API call that this game happens to. That doesn't mean a darned thing about whether the game is optimized. Oh, sure, it
might but if that were the case then the issue would be universal, as I stated earlier. Since it isn't, it's a bug somewhere in the game's interaction with drivers, or it could even be a single DirectX API call unique to your use case in Elite but that other games you play don't happen to use. Or, just as likely if not moreso, it could be a cluster of API calls that Elite uses which happens to be unique to Elite among your personal choices in games.
Frankly, when I worked supporting games, if we saw a case where someone claimed their system was flawless and only this one game caused the issue, we knew that there was a greater than 90% likelihood that we'd see it resolved it with new drivers. In very rare cases an updated BIOS or changed BIOS settings might resolve it, after manually tinkering with hardware resources to avoid conflicts with the NIC in use. The BIOS bits are less common these days, as modern systems do a better job of sharing resources and avoiding conflicts, but
these things still happen. In a fair number of such cases, the problem ended up being caused by one wrong-headed "optimization" or another that the end user had applied. Often enough these were on the advice of random folks on message boards, and quite often they not only would only help in at most a tiny subset of situations, but quite often actively prevented the OS from managing resources as designed and thereby
causing the very issue complained of.
Sheesh! You can cut the cluelessness with a knife in this thread.
Indeed. A fair amount of it is your own, too. I say this in all sincerity as constructive criticism. For example:
FYI: MS still updates previous versions of Win10 with the same Cumulative Updates.
I don't use 1703 because there are too many issues for gaming still unresolved. So... I am running the latest version of 1511 which I believe was last updated two-three weeks ago.
1511 is the most stable version of 10 for gaming currently available.
This is some of the most ridiculous words I have recently read. By virtually every single account, the newer build's "gaming mode" is actually quite good at making things work
better for most folks. The build is in no way "unstable for gaming". It might be unstable with certain driver versions required by some games, but that's a game developer issue, not a Microsoft one.
Just admit the game has a serious flaw in these areas regarding the game engine and needs to be better optimized.
Why? The game works flawlessly on several systems I have, all of which are "inferior" in one manner or another to yours, mostly in GPU terms. Despite that, my performance is consistent at all quality settings including Ultra with SUperSampling. I don't generally play at those settings since it's excessive for me personally, but when I do my GTX 960 handles it at a consistent FPS rate in all conditions.
Apologists... WHY? What is the point in denying something so blatantly obvious?
Nice try to discredit those who disagree with you, but frankly you're the one spewing negativity and ridiculous accusations here. Several others offered what are reasonable possibilities, regardless of whether they specifically applied to you or not. Many of us have patiently tried to explain why we're disputing your assertion, since on our end the game runs perfectly well.
If were a network issue, the numbers would not be the same every time. They would vary, and there would be times when it was worse or didn't happen at all. I am not seeing that at all here.
This is pure fantasy. That simply isn't how it works. The fact that the FPS is identical each time indicates a static issue, sure, but it in no way rules out you7r NIC, your ISP, your router, or any of a dozen other factors in networking. Your GPU (or some other critical bottleneck-ish component in the system) very well may be sharing hardware resources with the NCI causing exactly the behavior you're describing.
So, yeah, there are excellent reasons why people are disputing your assertion. Not the least of which is while you claim to have some level of expertise, you make truly wrong statements as I've pointed out above. At the very least, you are misled in your thinking on this by your limited experience. And that's fair. But to ignore the experiences of others who are explaining that things work fine
for them and others they know, therefore demonstrating it is at least more complex than simply a a "poorly optimized engine" is simply silly. That, frankly, is what's whack-o here.
Edited to add: You may want to look up the definition of an apologist. You make i9t sounds as though it's somehow a bad thing when all it is is someone defending a thing. And, in fact, we're not really so much making apologies for Elite or FDev as we are pointing out that you're simply incorrect, sincere as you may be in your belief.