Sn8ke_iis

Hey Flanker, If you are in the States, you don't have to buy from Bestbuy to get those builds. You can buy direct from their websites and you will have more choices for components and most likely get a better price. https://www.ibuypower.com/ https://www.cyberpowerpc.com/ I concur with Bit, get the best CPU you can afford right now and 16 GB of RAM. Especially if you are running at 1080p resolution. That's the foundation. Upgrading your RAM and GPU later when you have more fun money and get a higher resolution monitor is easy. Not as easy to upgrade motherboard and CPU later without essentially rebuilding the system yourself. RAM and GPU are easy to sell online to recoup some of your investment. And once you get more comfortable swapping out components, building your own system from scratch in the future will be easy peasy.

Hey BlacleyCole, Sent you a PM, interested in some of your Saitek stuff. Thx.

The way he phrased it implied it was the entire area of the map. He should have said 388 mi of land area. Why would you only fly over land in a Pacific Island map? That doesn't make any sense. There is no carrier in the Russian Black Sea Fleet and US Supercarriers can't get to the Black Sea. I was referring to the PG and Normandy map. You can even attack the Hoover dam with a carrier battle group placed in Lake Meade if you really want to. What ever blows your skirt up. I like to play DCS, not complain about it online. This was the best newsletter I have ever read and very looking forward to GA's 2020 video. Happy flyin' guys.

I'm really good at OC and graphics tuning. Tuning for VR is a whole new rabbit hole. I'm still not done and I've had it since October. :smilewink: The new Nvidia drivers and the new SteamVR and WMR for Steam betas seem to be helping though. Enjoy, it's an awesome experience.

Of course it's mostly water. It's a Pacific Island map. I was correcting the 388 miles square figure. I have no idea where he got that number from. Most people don't have high end systems, this will be good for new players with mid range rigs. It also means you can populate the map with lots of AI objects/ships/carriers with less hit on performance. There isn't enough room on the current maps for large scale carrier to carrier engagements. Man some of you guys will complain about anything. It's a FREE map.

Best Newsletter Ever! Happy New Year everybody. And some of you guys need to check the newsletter and your math before complaining. 400 km x 400 km = 160,000 km squared 1 km = 0.62137119 248.54847689 x 248.54847689 = 61,776 square miles and some change. That's huge!

Best newsletter ever, I'm so excited!

That means you can turn up your draw distance, shadows, and other CPU bound settings accordingly. DCS's VR setting is actually quite conservative for high end rigs and is just a starting point. I started with my maxed out 2D settings from SLI. I had to turn off Global cockpit illumination and mirrors which is a bummer, and decrease draw distance, MSAA, and heat blur but it's worth it for VR. Rain drops and the dust/fog features available in the ME are also quite taxing. You'll also be able to run higher settings without fpsVR enabled due to the overhead. When up at high altitude and just dogfighting another couple fighters I can hit 90fps. I like to fly low in the cities and through the valleys with lots of trees.

There's a native tool that will monitor the reprojection and give you a little colored box in the upper left hand corner indicating whether or not you are CPU or GPU bound or hitting 90fps. It's free and has less overhead than FPSVR. In my experience I'm CPU bound when flying low over complex areas and with lots of trees. This is an intro to the settings but he hasn't updated with the latest Betas. https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/ This is the developer's Github . https://github.com/MicrosoftDocs/mixedreality-enthusiast-guide/blob/master/docs/before-you-buy-faqs.md To turn it on it's in this file: \Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\resources\settings // Automatic motion reprojection indicator to display the mode currently selected // green = off because application can render at full framerate // light blue = on because application is cpu bound // dark blue = on because application is gpu bound // red = off because application running at less than half framerate // “motionReprojectionIndicatorEnabled” : true,

Good question! As the software is constantly updated there really isn't adequate documentation for Afterburner and Riva Tuner unfortunately. There is this to get you started but it is out of date. https://www.yumpu.com/en/document/read/6756633/pdf-msi-afterburner-user-manual There are also the forums on 3Dguru.com about Afterburner and Riva Tuner. https://forums.guru3d.com/forums/msi-afterburner-overclock-application-discussion.55/ https://forums.guru3d.com/forums/rivatuner-statistics-server-rtss-forum.54/ The quick and dirty is you need to check the block for Show in On-screen Display under the monitoring tab in the properties GUI. To set the hotkey to turn it on and off while gaming you need to press an unused or redundant key like F1 in the Toggle On-Screen Display field. Then you won't change your view while pressing it as that is the standard cockpit view. You can still turn it off and on for other views you just have to press the toggle before. Make sure you press APPLY and OK or the changes won't save. And finally, go to the Riva Tuner icon in your system tray and make sure it is toggled on there as shown in the screen snip. To customize the font size and colors you kind of just need to play around in the GUI to get familiar with it. The colors are displayed in hexadecimal color codes but you can pull up a palette to choose.

Happy New Year's Mr. Biggs! As you scroll down under the monitor tab in the Afterburner GUI's properties you'll see two relevant stats. RAM usage is right under CPU power and is for your motherboard's or system RAM usage. As you scroll down past GPU temperature and GPU usage you'll see Memory usage.. This is tracking usage for your video card's RAM or VRAM. As the 2080 Ti has 11GB you are G2G. In the OSD in the screenshot I uploaded you can see GPU and MEM in green. In my OSD I have it set up to show MEM usage as well as the clock speed. On a related note, on the GPU line of the OSD I have temperature, utilization, frame buffer (FB), and then clock speed. As long as that is not maxed out, you should not be hitting any bottlenecks. Of course as always YMMV and it can depend greatly on variables like texture settings, resolution, and AA settings. I just sat down to run a few benchmarks I keep procrastinating and saw your question. MSI Afterburner is a great tool, especially the OSD when paired with a hot key toggle. If you haven't recently, make sure you delete the: C:\Users\user*\Saved Games\DCS.openbeta\fxo C:\Users\user*\Saved Games\DCS.openbeta\metashaders2 That should wipe the VRAM for a clean slate after updating, changing graphic settings, or switching maps and modules. Hope that helps.

What are heat skins? Do you mean thermal interface material (TIM)? What MB do you have? Most current ones should have a heat sink and TIM included. If not I would go with what norbot posted. I like to check temps with a cheap laser thermometer I got at Home Depot for $15 as well as readouts in AIDA 64 to get an idea of hotspots for liquid cooling. NVMe SSDs along with the Southbridge controller are consistently the hottest parts of my motherboard that aren't under waterblocks. They can easily exceed 70 degrees C during long gaming sessions.

AMD, Intel, and Nvidia all have some of the smartest people in the world working for them. Jim Keller left AMD to work for Tesla in 2016 and works at Intel as of 2018. All three of those companies have a foundation of decades of proprietary tech and engineering processes. Just their patent portfolios alone would make anybody's head hurt. Jenson Huang is the CEO of Nvidia and has been since it started. Lisa Su is CEO of AMD and has been with the company since 2012 and is an electical engineer. She has a resume that would make any EE or CTO drool. I admire Steve Jobs for his vision and he was obviously a genius. But he wouldn't have been able to start Apple without Steve Wozniack who was the technical guy and lead designer of early Apple computers. All teams need a good leader to be effective and have direction. They are still teams.

The Consumer Electronic Show (CES) is coming up in a couple weeks in Vegas. Should be some interesting rumors and "leaks" coming out, hehe. We got Z490, Ampere, and now this. Hopefully they are all out with good availability by next build season. Intel is still stuck on 14nm+ per the leaks on WCCFTech.com Good times ahead boys! My Reverb needs those frames!

Nobody is trolling you. You should not be taking this personally and my posts were not intended to upset you. You just need to utilize the search feature of the forum to research these issues before you give out wrong information. This is how we learn. There isn't enough time in the day to figure this all out yourself by trial and error, which is why we share this information on forums. It's important any erroneous information gets corrected so as not to confuse new players. A lot of new players and people new to benchmarking have made the same mistakes you did and would be oblivious if not for feedback on threads like these. Nobody here accused you of faking your graph. I'm not sure why somebody would do that unless they have too much time on their hands and a strange sense of humor. I suggested posting it as an attachment so we could get a better look at it to interpret if for you as it's very difficult to read even when zooming in. The fact remains that DCS uses only 2 cores and the developers and testers can confirm that. You should reread Bit's post again as he explained very well why the Afterburner's graphing does not accurately portray CPU usage or how many cores DCS uses. I was genuinely interested if you could get Crossfire to work in DCS which is why I mentioned it. I am able to get SLI to work but that is due to someone very painstakingly and tediously testing SLI compatibility bits in Nvidia Inspector. I was able to find that information by using the search feature. I would never have had the time or motivation to test all those different compatibility bits myself. I'm not aware of anyone getting Crossfire to work. https://forums.eagle.ru/showthread.php?t=201454&page=12 That's the thread for SLI. I don't know if AMD has an equivalent utility to test for Crossfire utilization. Good luck with your project.

I'm sorry but that is incorrect. I guess I wasn't clear. DCS only uses 2 cores. One for audio, and one for the rendering pipeline to send the draw calls to the GPU. Feel free to contact one of the Mods who does testing and they will confirm this. Showing usage in a graph doesn't change that as there is much more going on under the hood and there is no way to say that the 4 core utilization you are showing is from DCS as it is not showing application specific usage, only that it is being used. You should do a little more research on these forums before giving out incorrect technical advice as this has already been covered ad nauseam. As I said, you want the fastest single thread IPC performance CPU you can afford. Especially for draw distance, shadows, and AI objects. Even more so on MP servers. Settings like resolution and AA will be more GPU limited. You should read the readme.txt in the root folder of your install and it will cover some of these things. Appreciate you trying to help, though. https://www.cpubenchmark.net/singleThread.html Your FX-8350 has about half the single thread performance as the R5 3600 and the Phenom II even less. So that is a very poor recommendation for a new build. Moore's law is very real and for a simulation as demanding as DCS that unfortunately means upgrading every 2-4 years. Especially if you want to play at more than 1080p 30fps. CPU architecture and chipset bandwidth influence performance more than clockspeed. Clockspeed is just a metric of the clock cycle pulses going through the transistors of the processor and is not an accurate gauge of performance between CPUs. Have fun trying to get AMD Crossfire to work in DCS. Let us know how that goes for you. If you want to upload a graph that is legible you need to put it as an attachment or link to imgur or another file sharing service.

What Bit said is in fact the case. The current DCS engine is CPU limited for many graphics settings like draw distance, shadows, and AI objects. While resolution and AA settings use GPU mostly. The DCS engine is limited to 2 CPU cores and the rendering pipeline that sends draw calls to the GPU is limited to one core. If you play at 1080p and are trying to hit 120fps the CPU will most likely be your bottleneck as well as VR if you are trying to hit 90/45fps. For 1440p and 4K flatscreen the CPU will be less important as most of the current gen processors (9700K/R5 3600) can handle 60fps. Your picture is very difficult to see but Windows will by default jump rapidly from core to core to prevent overheating and throttling. For DCS you want to turn off all power saving features and let your BIOS and Windows choose the fastest core in your chip. A good quiet air cooler or AIO is highly recommended if liquid cooling is outside your budget. The overall percent usage of your CPU can be misleading as that is calculating from the whole chip being used as a given. You want your fastest core and GPU at close to 100% with good cooling to maximize performance and eye candy. You want the fastest single thread IPC performance you can afford. Multiple cores right now are only beneficial for background programs like TACVIEW, and streaming/recording processes. For the OP. PC Parts Picker has many suggested builds for around your budget. Paul's Hardware YT channel also has some great videos for budget builds. Gamer's Nexus YT does the best benchmarks these days when comparing CPU and GPUs. Just keep in mind the DCS graphic engine is unique so even other DX11 game benchmarks might not be a good indicator of performance.

Cheers! Merry Christmas! Hopefully we don't have any more friendly fire incidents this year when Santa is inbound from the North Pole. It was unfortunate what happened last year :D

TARGET does all that too. Maybe something is getting lost in translation here, I can barely code "Hello World" in C++. The GUI generates the code for you. There's no coding necessary. There's no way I would be able to do that without the GUI. The user interface makes it all point and click. Easy peasy. It even gives you a 3D model of the controller and you just click on the button you want to assign. Much better than the wall of text in the DCS speadsheet. If I can do it, anybody can do it. I'm into hardware and benchmarking, I'm not a coder by any stretch of the imagination. I can't even read the text scripts you guys keep posting. Looks like Ancient Greek to me. One thing I noticed when I was working through your F-16 script in Foxy is that you went through a lot of trouble to emulate key presses for a lot functions that were already in DCS as joystick buttons. I'm not sure about FOXY, but TARGET can emulate all 32 joystick buttons and the 8 way hat. The DCS developers did a fantastic job of mapping all the joystick functions already and you were kind of reinventing the wheel. I just emulated the joystick buttons as typical press and releases like the default and it worked great. I did steal your idea for mapping the landing gear lever as a layer under the speedbrake switch and it worked great. Just an FYI.

I got you Bit, when you run the script it will create a new device called Thrustmaster Combined and you will still need to assign stick and throttle axis in the DCS spreadsheet. The P-51 is one of the more basic layouts, the cockpit is very intuitive to use with a mouse for start up especially in VR. In the diagram attached the [D] represents the down layer for use in conjunction with the paddle switch as modifier. As you can see I have all the basic functions that are part of my standard template. Kneeboard, zoom, TIR center and reset, etc. I have all the function keys F1-F12 mapped to the hat switches for views and the comms menu as well. They follow a clockwise convention left to right for the 3 hats, with the trim hat switch moving your cockpit head position with the paddle pressed. Otherwise it's just a normal trim switch. It sounds like a lot but it's very intuitive with a little practice. I keep those consistent regardless of module. You can move your head around, change views, check kneeboard, reset TIR, all with HOTAS. Note: I changed the default TrackIR keys for recenter and pause IIRC. But that's easy to do, so if that doesn't work you'll need to adjust yours accordingly. Sometimes I have to add custom keyboard combos in the DCS spreadsheet to prevent conflicts but I don't think I had to do any for the P-51. The F-16, that was a struggle with the Cougar/TUSBA and the Warthog stick together. I actually tried to use Rudel's template for Foxy but couldn't get my Cougar throttle to be recognized without the TUSBA. You might get an error if you don't have the MFDs but you can adjust the profile to exclude those with a few mouse clicks. To use an imported script for the first time you have to press edit configuration in the TARGET GUI and then use the file explorer to pull it up. Then go through the pages and press save and finish then it should save to the default path on your machine. DCS P-51D.zip

That's one of my favorite features. I've lost count of how many hours of fun time I've lost in CLOD and DCS due to unplugging controllers, Windows device issues, or unknowingly deleting the .cfg file. I have a standard template that I use for all aircraft with consistent muscle memory for views, comms, zoom, TIR/VR recenter, etc. When I try out a new module, I can just hop in and fly without having to reassign in the DCS spreadsheet. You only have to learn one GUI and it works with all games and sims. The process of assigning a unique profile for a new module really aids the learning process. I retain it better than RTFM. Easy to back up and share as well. The only issue I've had with Target is having to make sure USB power saving features are turned off in BIOS and the registry. Otherwise the script can think the device is unplugged and kick back an error. The error codes usually show up in a search engine.

CPU wise you should be good but I wouldn't get your hopes up with the GPU unless you were to turn down eye candy settings quite a bit. I was able to hit 4K @ 60fps in single player with a liquid cooled and overclocked Titan Xp with FXAA forced in the Nvidia driver. But judging by this benchmark you might be able to push 4K at medium to high settings. IIRC I had to turn off global cockpit illumination and MSAA was definitely a no go. https://www.videocardbenchmark.net/high_end_gpus.html Keep in mind that is a synthetic benchmark. YMMV in DCS and performance can vary based on game and drivers.

LOL, I was just showing you the script for reference. The Graphic User Interface (GUI) does it all for you, no scripting necessary. The GUI is all just point and click with the normal pull down, drill down menu conventions. It's very intuitive. I assure you if you can script in Foxy you can use the GUI. But whichever works best for you. Good luck, I hope you get it figured out. :crash:

I have a Gsync gaming monitor and when I was playing with TIR with Gsync enabled I did not notice any screen tearing. What I did notice was stuttering and choppy animation at 87 and 94 fps. At 117+ it wasn't really noticeable. Unfortunately, Gsync and Freesync don't work with TIR as the middleman. The framerate of your monitor and GPU won't match precisely and will have frametime issues. You can see it on a graph in MSI Afterburner to make sure your eyes aren't playing tricks on you. If you pause TIR and pan your view with the mouse, Gsync works butter smooth. When I played on a 4K 60Hz TV with Vsync it was very obvious if I couldn't maintain 60 fps. 58 or 59 fps would look choppy. But still no tearing. When you are flying in single player at high altitude or over the ocean you can maintain 120fps with a decent rig, but that's hard to do when flying low over lots of trees or over cities with lots of objects and shadows to render without having to sacrifice eye candy. Now to make it even more confusing. My Samsung 4K could do a neat trick and interpolate frames to kick up 60 fps to 120 fps with the TV's on board ASIC GPU, which helped to smooth out TIR and animation in general. But at the time the HDMI 2.0b standard could only push 4K60 through the connector. I think this might have recently changed with a firmware upgrade but I have not tried yet. If you go with the TV make sure it has HDMI 2.1 if you want to be future proofed. Those cables and connectors can push 10K at 8 bit RGB 4:4:4 chroma color depth.

Have a look at the current version's GUI. I have the oil radiator function set on a 3 way toggle on the base of the Warthog without a layer so not exactly what you are trying to do but it works very well. I know a little C++ and R but that just helped me read the syntax. I always use the GUI. Easy peasy. I've only had to edit the script manually a few times. The first screen shot shows the oil cooler function on it's own 3 way switch. The 2nd is an example of a layer I have set for the hat switch to control trim and cockpit camera with the paddle switch acting as the modifier. The 3rd is the script.