Fastbreak

Hello wernst, I have come to a similar conclusion as you did. Matt Wagner in one of his interviews talked about ED's expectation mangement and their trying to adjust users' expectations to an appropriate level. I deemed it a quite reasonable step to avoid frustration or annoyance to both ED and users. Thus -with regard to the 2.7 update- I was hoping for the best, but took some errors into account. When I realised the immense performance loss (fps/frametimes) I had to remember the begining in 2008 ... unfortunatelly. I do not enumerate all items neither my error recovery, I'm simply tired of it. Conclusion plus: I never lost my interest in flying DCS, but with 2.7 update I did. Until further measurable results (not marketing statements), I have stopped flying (especially helicopters), because DCS momentarily is simply below the accepted quality for flying! For the time being I continue to not purchasing any module (first stop due to long-time missing KA-50 bug-fixing). Best Fastbreak

Today's update brings everything, but no fps / frametime improvement. You have set your piorities, haven't you? BTW "I appreciate those of you having performance issues, we know you are not making it up, PC's can be a mystery sometimes, I have said before I have seen the same machines perform differently for no apparent reason and it can be frustrating. We will continue to optimise and look at individual cases, try to help where we can." I don't feel amused by such a comment. That's a quite audacious way to shifts the existing performance loss to users' side. Different systems are daily business in software development. If ED is not able to manage the performance problems of their software in a reasonable time, they should at least direct their staff to not communicate such a statement that subtly implicits a properly working 2.7 DCS version. To remember: It is not by any means! And, it's not a great help to continue to optimise, either. It has simply to be ED's necessary fast step to a flawless DCS 2.7 version that makes ~15% (maybe more?) of the users also harness their product at all - and a premise to sustain their customer relationship. ... For everybody within the 15% mystery group, I recommend to regularly light votive candles ...

Dear chrisofsweden, "A properly modeled contrast locking system would be really cool, but I honestly think that is years and years away, simply because it probably would be very taxing performance wise. It's already a very fine balance between realism/eyecandy and FPS for the absolute majority of us. " Please do not reason your very personal opinion about a topic with a reference to the "absolute majority of us", no matter if intentional or unintentionally. You cannot know what the majority thinks about a certain technical implementation of a KA-50 feature as long as you have not carried out a survey/have the result. Have you? So your statement is -with friendly words- illogical (...)

Dear ED, Regardless of your minor shortcomings in your latest 2.7 update, such as ~ up to 38% FPS loss and considerably increasing frame times on my side, I am incredibly impressed of your tight endeavours to improve DCS ! Please be so kind as to asap disclose when you will have restored the (latest slide show) simulation to its former airworthiness! Thanks awfully.

"I really hope they don't can the BS3 update entirely. I was really looking forward to this when I heard about the Apache coming into the game. It would really help balance REDFOR and BLUFOR"

WISE WORDS - YOU ARE ABSOLUTELY RIGHT, FRI13 !!!

Hello folks! Dear Quadg, "I think we all expect too much from Automatic stuff from the 1980's I think we should be impressed it works at all." "where some see bugs, others see as actual limits of the old technology. we need an expert to say who is right." To specify, today's coding errors, related to 1980's technology simulation, are the problem. Systematically fly, test, read, and understand why KA-50's coding is still less sophisticated, it will become obvious. I explicitly exclude unthinking fanboy comments who are eager to jockey a jack of all trades device instead of looking deeply into a module with its pro and cons on technical or strategic side. Please, do not perceive my clear words as a a hidden (or open) affront to you. Dear 3WA, "I agree with holding back on buying any new aircraft from DCS until they fix the issues with their other aircraft, especially the oldest ones. I am seriously beginning to lose faith in them. " Thank you so much that you fully comprehend !!!

I do not contradict your thoughts, they add up. If ED were willing to look at Black Shark, they probably would issue a short statement to sort out misunderstandings - actually they did not. I have waited paitently until today, another one or two years (2.7 release) are in no way acceptable ! I appreciate DCS very much, but I forgo (further) knocked up modules or maps. If bug-fixing, product completion and communication even fails, every ED customer should think about the elementary rules of business and let his money talk until his KA-50 module is complete and fully fixed. I myself will do so for sure, notwithstanding the interestings rotor wings to be announced.

Why bother with a track. This is a WELL KNOWN issue, and has been complained about for YEARS. >> IGNORED OR CANCELED ? Come on, ED. Don't give us the "give us a track" BS anymore. You know EXACTLY what is wrong here. >> GREY MATTER RULES ? There is NO contrast lock. You're using simple code for time of day, and a few other factors. >> CUNNING RANDOM FUNCTION ? You guys need to fix this. We need REAL constrast lock for EO. You're developing all these new radar systems now. Please fix the problem with EO on your, what was it?, 2008 RELEASE DATE helicopter! >> HEAVY GOING ? ED'S RESPONSIVENESS TO KA-50 BUG-FIXING IS WOEFULLY INADEQUATE UNTIL THIS DAY ! DO THEY NEED KICKBACKS ?

Good evening 3WA, I agree with you 100%. I also understand that system extensions cannot be done due to governmental restrictions or that errors can come into being now and then. Nevertheless I just wait for the next stage in process, the module completion in function and graphics with a straightforward communication to customers by return. Communication is quite simple, it belongs to the fundamentals in this situation. Several friends are dedicated aviation hobbyist who have been long-time customers since ED's first product launch. They cast a very sceptical eye on ED, whereas it was me who have championed ED's endeavour all the time. The side note* in the first newsletter 2021, rather its style was unfortunatelly the last straw. No schedule, no reference to bug-fixing, either module completion (forum is full of details and a lot of them I can confirm), no reaction to comments in forum, no KA-50 content in newsletters, nothing meaty at all - DIE MANNSCHAFT send their regards, but maybe ED is more adaptive than DIE MANNSCHAFT ... So Say We All! * "Note: Due to new Russian Federation laws pertaining to the gathering of information of Russian military equipment, we have had to reconsider our plans to add new systems to the Ka-50. We continue to update the cockpit, as well as a highly detailed updated external model."

ED again did not report on the plans for the essential KA-50 bug-fixing / development in the lastest newsletter yesterday. ED takes their KA-50 customer as seriously as their Ka-50 product, don't they? ED is suggestive of the KA-50 not to be fully fixed and completed (related to existing KA-50 module), but in return ED boisterously dangles with new helicopter modules (EA) in front of their KA-50 customers. I am very curious how long customers (and fanboys) are willing to go along with this recurrent waiting game. As rotor wing enthusiast I do not abandon hope and keep my fingers crossed for ED to be able to introduce a professional quality management asap to achieve and maintain the desired level of quality in products and services within their company. As a customer who chews on apposite but missing information, I am obliged to abandon my every intention to buy other helicopter modules or the channel map - my buying would give consent to that veil of silence.

KISS - Keep It Stupid and Simple Make what we have work at 100% after more than 12 years - a new contrast lock system would be nice, indeed. Unfortunatelly ED wait out the problems without any information about KA-50's further development / bugfixing in their newsletters. Customer retention measures at their best! OMG

Well, it's phenomenal - the way ED ignores this error. So many dedicated descriptions and no feedback respectively bug fixing. Thank goodness, the new exterior view of the KA-50, that ED has announced, will valorise the high-end KA-50 simulation to a greater extent than any bugfixing.

If the Apache development time is similar to KA-50, well, the Apache could be a real threat for the KA-50 ... in about 10 years? And of course, to bridge the dire straits and to avoid a rebelion, ED will introduce a big shiny red all around extinction button for all fast and furious fan boys. Forgive me, please, I could not resist...

Hello SWEIynx, I hope you can find a solution very soon! From time to time my PC behaves odd. But it has never turned out a problem by hardware (updates), but it has always been linked to DCS updates or errors. It is essential you test with different games, test software etc. Fastbreak

Hallo SWEIynx, I have no solution to your problem, but just some additional info. Same Windows and OS here, too. Nearly fresh installations (15th Dec), too, and from the beginning of the installation I have also "minor" screen problems (black screens and switching back from three monitors to primary monitor) and one time a blue screen. Most times in MP. Different NVIDEA drivers (Aus GTX Strix 1080ti, clean with DDU before) did not help on my side, using two lanes of my power supply for graphics card, either. No mods, of course. No overclocking or VERY SLIGHTLY overclocking made no difference for me. Instability only with DCS OB (latest), windows desktop with two monitors no problems. My logs (have deleted them) showed a lot DX11 errors, one crash report was sent to ED. Just a short, imprecise description, I know... I have my windows cache manually set to 48 GB. Without doing it I had some months ago severe problems with the sim crashing every time.

Hello IIuricane, yes, I have understood your question, but, mea culpa, my answer was nubilous. Sorry. I did so, because I deem TeamSpeak , TeamViewer etc. more convenient than writing a (long) text. I would suggest to write a new monitor file with new center viewport. Adapt X,Y coordinates that fit to your second monitor. Copy it into the folder with the monitor profiles and select it ingame in OPTIONS menue. Best Fastbreak

Hallo IIuricane, this opportunity is already given, I myself use 3 monitors. Check your monitor / resolution setting at OPTIONS menue in DCS. Please do a search in the forum for further details. If you have problems, you can leave me a message in German. I can show you via live access (e.g. TeamViewer) what exactly to do. Best Fastbreak

Good evening Volk. I have expressed my displeasure and disappointment over missing bug-fixing confirmation and KA-50 disinformation. To not become a crosspatch, I decided to have done with this nuisance, but I have learned my lesson (...). I hope other KA-50 aficionados may give their own thoughts to ED's approach and may consistently react to it, too (...). Below the line ED has announced great highlights for 2021 - they're going to talk the talk, they've got to walk the walk! See u slightly below top tree level Fastbreak

From official news, 08 January 2021, not more than a passing mention related to KA-50. "Note: Due to new Russian Federation laws pertaining to the gathering of information of Russian military equipment, we have had to reconsider our plans to add new systems to the Ka-50. We continue to update the cockpit, as well as a highly detailed updated external model." Ignoring their statement of Russian Federation laws, I was I was totally taken aback by fact that they have not given any more information on KA-50 updates and accordingly bug-fixing either, especially after all the corresponding user contributions. In a nutshell, PATHETIC!

Hello FalcoGer, Ommmmh! Everything is going to be alright! But yes, I sense their engagement exactly the same every now and then.

Hello Sh4rk, I have experienced the same effects you describe and illustrate (with your also aesthetically pleasing art design ). Just like you, I also hope for a new contrast-based Shkval system. In all fairness, I have to admit that I expect them to get it started, because it would be the next logical step in Ka-50 evolution. According to the principle: There is no such thing as impossible. Bye for now Fastbreak

It is quite nice that you guys are all helping to describe the faulty KA-50 behaviour in detail. As a reaction to your descriptions and the time you have invested, I would have expected a short ED comment in advance explicitly confirming that they will offer solutions later on (regardless of the announced new features). Such statement would have been strategically fine, it would not have browbeaten them into appointing a time, either. On the other hand they told us to give due notice on news, what is less sophisticated, because ED leaves the impression, at least on my side, they will wait out the all-time problems. Another thought that has come to my mind is that ED might have realised that the KA-50 program code is unstructured to such an extent they will have to reprogram it in many areas and in a time-consuming way ... ? Nevertheless, neither I am entitled to speculate nor I am interested in, but I keep my fingers crossed for above-mentioned confirmation* * i.e. : We confirm project "See KA-50 and die !"

I would like to join Raisuli's greetings. Merry Christmas and a happy new year from Germany - may everybody of your team stay healthy in 2021. Best Fastbreak

I seriously hope that ED momentarily work on the KA-50 to finally bring KA-50 to 2021 level - in 2021, SOON! Beyond doubt, I swooned over a KA-50 at the ripe old age of 12 years, if ED would not only take the announced new features into consideration, but would finally fancy remedying ALL LISTED deficiencies, too. Needless to say either, that KA-50 will not be parked when other helicopter(s), that hopefully will raise the bar, appear on the scene. Roll up your sleeves and get to work