D4niel

NICE! Ty!

Cool. Because all I said is that even an old chip like Phenom II could run this game. That conversation began after I started doubting if a high end modern CPU is what this game requires. A better and faster chip is always better in any game :D About the Phenom and DDR... Yes, that is what I also remembered after posting. It in fact can barely handle 1600mhz. Or cant at all. 3x r9 390 is exactly because: 1. Electricity here is very cheap. 2. Its cold outside and fresh air means too cold inside. So here is never too much heating at winter time. 3x r9 = more fresh air. 3. My mobo can do 16-16 and 16-8-8. So I'll see what is best and what would be the needs at the time. Maybe only two way CF, as my 3rd r9 is a 290 with 4gb mem. 4. These cards are here 70-90€ each delivered, so that is another reason. And about the project itself: Its more about the chinese water cooling solution and Im confident to use old and cheap hardware with it. Plus the old hardware is not bottlenecking me at 1080p @ 75hz if I get the CF going. That said, I also would not recommend CF to anyone. Only worked with GTA 5 flawlessly for me. Years ago with HD 7870 CF.

Man, at first the good quality of your troll upset me as I knew you pushed me to waste my time once more replying to your... Input. And explaining myself because you made it look like I said or meant something I did not. But then I realized you gave me a great idea about the Phenom CPU and replying to you would be fair. As opposed to what I said that it has the same single core performance as FX-8350 (not as pumpkins, cucumbers or tomatoes!), you researched that its neglibly inferior instead: 1.2 to 1.5 ratio. If only I and nobody else would believe that the graph is not fake, nor its misleading or inaccurate and that the used cores are running at 80%, then the Phenom II 965 still would do its job even in DCS! This leads us to the point: Im currently preparing for a project some people might find interesting to follow and see the results. Will make a blog of progress on three forums, including DCS. Its about well performing in 2020, cheapest possible watercooling rig, featuring aluminum+plastic chinese loop (except the pump being standard) and 3x r9 390 GPUs. Not only it will be silent, but it will be inside a sleeper mATX case on ATX board and 4-6x radiators. It will have FX-8350 chip, but a perfect addition to the DCS forum would be to actually see how a Phenom II 965 works in DCS! There is also a good chance you would get the necessary validations then. Your bluff backfires, dude. If you knew why my Crossfire is not working and that it would not, then you would use the opportunity to be smart and educate me about it, instead teaching me about clock speeds not being important. Its one of the first things you learn when planning to build a first rig. Often happens when still a child. The fact that the clock speeds ARE NOT as important as some people think, in case you are not with me. Bit: True about the polling. Witnessed that before in a game Cities Skylines. However, DCS does not stutter, so I scratch that possibility of CPU spiking to 100%. And the CPU is cool. Sorry offtopic and Im out!

1. The picture is bad, because I uploaded it here, in forum gallery and so its resized from 1080p res. 2. No overheating and not throttling. Not even close. And not using any power saving modes. Not in windows and not in bios. 3. There is no overall percentage usage present in the picture. All 8 cores ar invidually recorder. 2nd-9th graph. 4. You are right about the core count not being useful. Its a fact in many games. Most optimal CPUs for gaming are the 4 core i7 I think. 5. DCS uses clearly two of my cores more than 50% each and another two around 20% each. Rest of the cores are allmost idling. Im not running anything other in the background except MSI afterburner itself. 6. Im not arguing. I explained facts, measured my claims in case I remembered something wrong and then presented the proof document. 7. I remember being quite surprized some time ago when I saw the low CPU usage. In fact, I could dig out my 10-11 year old Phenom II CPU and run the game just as well as with FX-8350. It has 4 cores, same per core performance and it clocks to 4.9ghz also. So it seems the answer is: A 10 year old mid-end CPU with 4 cores would run this game fine.

I had to verify Im not giving false info. This is a quick test. Start is game loading and then high intensity flying over Las Vegas. I guess I got my settings better set now, as its about 40-55fps actually, but the GPU vs CPU performance is well seen. I heard few times people say this game uses mostly one core... Not here. GPU usage on the top, FPS on the bottom and cores in the middle:

Im very surprised a veteran member with a high end system in sig would say this game requires more CPU than GPU. I have an FX-3850 4.9ghz CPU, its running 16gigs of 2050mhz ram and my severe bottleneck is a single r9 390, wich is a 512bit memory bus GPU with 8gb memory. 1080p I get around 30fps over Las Vegas (up to 80fps caucasus) and despite allmost max settings, Im bleeding for that extra and crucial +0.5x SSAA (2x SSAA). The max antialiasing vs. allmost max is a huge difference. SSAA or MSAA. So my CPU is chilling when I play DCS and Im currently waiting for another r9 390 to arrive. That said, Im having huge problems with crossfire not working with this game, except two times it did and now I hope I'll find out if its a hardware issue with the third r9 on the way. SO: Nvidia cards seems to be the better choise and most def the popular one. Ram you do need min 32gb for multiplayer. Im reaching the 16gigs on large operation missions in singleplayer. DCS has or had a memory leak that adds 200mb or so to your used ram each time you restart a mission (or maybe even just a new flight in the same mission). So my experience is that this game runs on surprisingly weak CPU, but to get what it shines with, you need a killer GPU to run 60fps+. And YOU WANT max settings! Also keep in mind that the type of GPU should be high bus width and 8gb or more memory, unlike close range FPS games that do not benefit of those parameters. -Slower CPU -Large GPU -32gb ram or first 16 and then another 16 later when you enter multiplayer scene. -No idea of HD, but SSD's are cheap and actually even getting old already :D. Pick second hand 120gb kingstons for 10€ each and put them in a raid 0

Looks like another point im missing is how to keep the fragile drunk Kamov not breaking apart. I cant imagine anything else, except a very delicate precision hard turning master skills and nothing like easy flying everybody is praising this chopper should be :D

Ok! Now the silent, un-clickable bastard is located and other useful things well understood. Thank you both! Also the trim-while rudder is comprehended and implemented succesfully. Now I guess its all about practicing stops, fast stabilization and landings. Not having huge problems to keep it going or following a road for example, but stops would be entertaining for someone to watch :D

Ok! It was about not trimming! Cant see the logic why trimming should be implemented when being still/hover and ruddering with heading AP on. Specially if rudder trimming is disabled by default in settings and as someone just mentioned here its not implemented in real Ka-50 choppers. So trimming does the job, but as its not a real thing in reality, it seems here is something else going on. Would still like to find the route mode switch and indicator anyway... Thank you!

Ok, week two now I guess. Thank you all for helping. I did read the manual, but could not find the mystical route mode switch. Found it in settings and that its binded to R button, but I cant feel it, see or hear. "Its on the collective". What is the collective? No kidding. Flight stick? where on it? A panel? Which one? Where is that switch or an indicator?

So just to clarify: After stabilizing the chopper and pretty much not moving in any direction, having all AP modes turned on and trying to rudder in any direction, it is normal for the heading AP to force me back to where I was pointing my nose at? As well it is normal for the chopper to slowly turn to a random direction if the heading AP is not enabled? Meaning this button has to to be also wanked depending on a situation? Is there a way to stop the chopper and quickly choose targets, shoot and then switch to a next target in the group from a distance without juggling and wanking buttons and the stick? Not to mention to keep the chopper from breaking apart. Im making progress, but this is ridiculous. Flying a flanker after this is like taking a bath.

Thanks for heads up. Will check the pages asap. So far trying to remember disable the autopilot input configurations before practicing that "lazy flying";)

First of all I must say I love this game and wish devs can fix as much as possible, as soon as possible. I have never before experienced as much voodoo with my computer or a game before. Actually zero voodoo before this game since windows 1995. Ironically zero is a number close to what I have since invested in games vs. XXX-XXXX€ in DCS World. Hardware + DCS module vice. So I also have this problem and I have this problem also. Here is the cause in my case, what happens and how to fix it: Cause: Deleting Metashaders2 and fxo folder in /user/DCS Result: GPU powers down and sound starts clipping (system crash). Manual system restart required. This is a random time bomb type of anticipated event. What is going on in game has no effect. It would happen in main menu if I would idle there, usually happens when loading to cockpit and if not there, then very soon in game. Fix: Bang your head to that wall and it will go away! Yes! My procedure is to load each map once succesfully and then the crashing stops entirely. GPU overclock might crash faster or not, but after the problem is stabilized, I can set up a 10% overclock on my GPU and no problems. There is nothing special in the log file. No errors and the last line is something like "passed control to player" or whatever related to all being completed succesfully. Why do I delete these folders? I read somewhere that It might be a performance "boost" (reset to normal) if system changes had been made. My sad case is that I cant get crossfire to function and so I have been doing changes quite a lot during these couple of months. That is another story and I got high hopes its a hardware related issue, which will be fixed after I get a third GPU to cross-test the other two. SOMEONE POSTED ABOUT PSU!!! Dont waste your money! Not related to DCS (I hope so), my PSU began severely undervolting 3.3v and caused computer to crash. Similar like this, but it crashed, did not tilt with only GPU powered off. So now I got a new Seagate Prime Platinum 1300W PSU, wich is performing as it should and DCS is not. GPU: r9 390 OC (x1, as CF is BS atm) FX-8350 @ 4.9Ghz 16gp 2050mhz ram 2x SSD RAID 0 Sabertooth 990fx Mobo (1300w PSU for future plans) And my OC'd system is stable and its all components run cooler than they would at stock settings.

Hey! Wow! Thanks! I went to the ka-50 special settings for the first time and the rudder trim was unchecked (already). So I checked it and now its all good! No wonder trimming didnt stop the spin :D. And Yes, Im using at least the two autopilots all the time and yaw when I wanted to stop the spin. Im yet to figure out how to use yaw full time without it interfering my heading to wherever it thinks its locked to :) Thank you!

Thank you!