Chaos_Out

The lazy way to create a DCS server with the same build is to simply create a new DCS shortcut (or copy paste a new one) -->right click on shortcut --> properties -->shortcut tab --> put "--server --norender -w DCS.server1" at the end of the "Target:" box, so it would look like this: "E:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --server --norender -w DCS.server1 This creates a new folder in the windows saved games folder called DCS.server1. To open the server GUI, browse to E:\Program Files\Eagle Dynamics\DCS World OpenBeta\WebGUI and open the index.html file. Making a shortcut for the index.html GUI file makes it simpler to access, or use something like a Stream Deck like what I use. You can get fancy and change the shortcut icon to distinguish it from the regular DCS build too. I think the first time you try to run it, it might say can't run the same build or something, but once it creates that folder it should work the second time.

In the 20+ years of computer gaming, I've never heard of anyone using L3 cache as a serious metric for whether it will do well or game well. From what little research I've done, it doesn't appear to be that big of a deal on newer games, maybe it is for cpu rendering (referring to VFX movie stuff) where that extra memory could be useful, but I honestly don't know. Where DCS fits in that new vs old with all of the updates done + upcoming major ones (multi-core + vulcan), I'll let you decide. From what little research I've done on the 5800x3d, I personally would not want it at all. It's been "down clocked" to 4.5ghz and new reports are suggesting it can't be overclocked. There is also still the possible temperature issue and if they fixed that as well. Look at any benchmark testing done and you'll see almost always the biggest metrics for performance are speed and temps, in this case core speed. It's why Intel was the gaming champ for so long, since they had cpus that could hit 5ghz+ while AMD was sitting mid to low 4ghz AND games couldn't take advantage of multiple cores. Down clocked and LOCKED at 4.5ghz is a major downgrade from getting an unlocked cpu and getting it to 5ghz ballpark. Make no mistake, 4.5ghz to 5.0ghz, even the stock 4.8ghz (5900x), is huge, nothing slight about it. I got my 5900x to boost to around 5-5.1ghz without having to do anything crazy, and coming from my 2700x, which could only really do low 4s overclocked, it was a huge performance difference. DCS VR needs every little bit of performance possible, as only a couple of frames could be the difference between smooth clear gameplay and stuttery blurry gameplay. Bigger memory is only better if it's either faster or was even a bottleneck to begin with. For example, what good is a 3090 with 24GB of VRAM if you only 2D game and max out at 8-12GB (FYI DCS VR does in fact use up all 24GB). My 5900x and 3090 offer good clear performance, but it took a ton of trial and error tweaking to get there, and I have to lock it at 45 fps, and even then it's not always perfect and has moments of stutters when a lot of stuff is loaded (mainly at airports). I personally refuse to sacrifice clarity though, so I accept those small moments of performance hits. This also brings up another point, we don't know what OP has for a GPU. It could be that their money could be better spent trying to upgrade that instead of getting something that will offer either breakeven or marginal gains. Just my 2 cents. EDIT: And until the 5800x3d is released and benched, everything is just speculation.

I skimmed through some of this so sorry if already asked, but when the crash occurs, does DCS create a crash report or is it a Steam only crash? If DCS also creates a report you could look through that and see what might be triggering it. Also, I'll second the suggestion that a bad overclock could be the culprit. It could run fine 99.99999% of the time, but the slightest little thing could cause it to crash. I've had plenty of experience with this! Bad overclock runs fine on everything I throw at it except one specific program or game. I don't fully recall the specs of a G1, but my guess is it's lower than a G2, so your PC is pushing harder to power the resolution and etc., which makes a bad overclock stick out more. Also, does the Windows Event viewer generate any logs? If it's a bad gpu overclock (and it's nvidia) you'll usually see like a nvkd.dll error or something like that. It's been a while since I've seen that (when testing an overclock) so I can't remember exactly what it shows. A bad cpu overclock will mostly crash the entire system and event viewer will give you something like WHEA error APIC0, which is specifying that a specific core crashed the system (most likely under powered for what it was trying to achieve).

I don't know why anyone else hasn't chimed in about this as well, but until DCS gets the multi-core implementation, individual core speed is crucial for performance. I'd look at that more than anything else if you must buy right now. Can you overclock and get what a 5800x could get or close to it? Might save you some money. Also, I've read multiple people say how incredibly hot the 5800x gets, and is mainly why I chose to get a 5900x instead, which runs much cooler and also means you have more headroom to push the performance.

Second that it's probably your shader mod. Had this happen with a new shader mod and joining a MP server.

I had this same issue not too long ago. I would boot up, get in a flight and the fps would be really low and stuttering like crazy. At first I thought it was a shader issue since I was switching between 2d and VR, so I would close the game, delete the shader files (fxo and metashaders) and restart the game. It would then work correctly. After a while I think I noticed I just simply needed to restart the game for everything to work fine. What fixed it? I have no idea. Either an OB update, a Windows update, an updated shaders mod, dumb luck, or a mix of all of them, but I no longer have the issue.

Since the viper doesn't really need vertical trim, I have the traditional up and down trim hat bound to the OSBs that controls the HSD range.

I use Voice Attack to act as a macro to speed things up a bit or to keep my hands on my hotas, but having to keyboard bind every single thing gets cumbersome after a while (when factoring in other aircraft). I say the command and then it executes all of the keyboard bindings in the order I set it to .i.e. "setup radar" turns on my rwr, sets my countermeasure profile to semi, and then added it to turn on my hmcs; or "wing tanks" flips my fuel monitor switch to the wing tanks so I can see when to dump them after they're empty, and "normal" flips it back. My favorite is "dump wing tanks" or "dump center tank" when in a pinch since fumbling through the s-j menu can take a bit if in a hurry. It will automatically select the s-j page, select the tanks, dump them, then return back to the hsd. Just little QoL stuff I enjoy since I don't fly too often these days. I should also add I almost exclusively fly VR now so using a keyboard is out, and has never been something I've wanted to use while flying tbh. I would love to create a one button macro like the in-game startup function to free up some keys, but the macro pdf linked is giving me a headache while trying to wrap my head around it. So basically I'll likely end up binding the ECM 1-6 buttons (or 5? don't recall) and the xmit switch to the position I want, setup a voice command "setup ECM" or something, and then add those keyboard bindings to the voice command.

I pointed this out in another thread too, but if you want to re-arm mavs, as long as you don't jettison the racks, you won't have to boresight again.

Hey @speed-of-heat, I saw in the comments of the shader mod you linked that he isn't maintaining the mod anymore either. I haven't tried his, and your "legacy" 2.7 still works, or at least I don't get any error messages, but will things get updated by you once an update breaks the shaders? Just need to know if I should start looking for another source once everything breaks. DCS Performance Shaders - SIMPLEX 2.7.0.4625 Luke Marqs 12/19/2021 19:02:15 The mod still works, but performance being utterly terrible with 2.7x (even more with the last two updates), gains are now so small that it might not make any real difference anymore. TBH, I had enough of this BS with 2.7x. Right now, you either have a unicorn RTX3080 (or equivalent) or you're into stutter fest land. So, this is it, not going to update this mod any longer. Got sick of it and went back to version 2.5.6 (much better, also check my other files), and even thinking about going back to 2.5.5, to get best performance.

Just adding that I too couldn't get it to cycle targets with tms right (both short and long). I came here specifically wondering if it was bugged or something. Will try to test left first to see if it will then cycle. I have 3 sa-8 close together on a custom mission and using the HAD will sometimes re-select one I already fired at so the cycle is a must in my specific scenerio if I'm to use it.

Also, as long as you don't Jettison the rack, you can rearm mavs and shouldn't need to align again.

Use both. Reshade adds good color adjustments (vibrance/saturation, contrast) and sharpness, but at a slight performance cost. I've seem some complaints about shimmering or whatnot, I can't remember if it was about fsr or reshade, but I keep both on default and have Negative LOD bias set to "Clamp" in the nvidia control panel and personally don't have any visible issues. The sharpness alone is worth it to me. I flip it on and off to check the difference every now and then and wouldn't want to fly without it since I prioritize clarity when in VR.

I don't know if you got your solution yet, but couldn't you just use OBS to capture your gameplay? You can select just the center monitor for it to capture. Most streamers and youtubers use this software to capture gameplay footage.

Nice mission. Really helped fine tune my TWS and cranking/notching type stuff. My only gripe is that sometimes bandits spawned so far out, and flying almost a full 90 degrees away from me, that they must never pick me up and never turn in and just completely disappear from my radar and AWACS. I had to modify the mission so that I could see myself and them on the f10 map (which IMO should be default on in a trainer mission, but easy fix on my end) so that I could chase them down and get close enough for them to finally turn in. Without getting rid of the fog of war I was constantly spawning in bandits who would just aimlessly fly away and disappear.