Ram69

Finally got around to trying this after getting updated and all from a few months off. Didn't notice any difference vs not having the mt.lua file added, but -- on the brighter side -- my experience has returned back to a much smoother one as of today (so far) with far less frame time spikes and resulting stutter. Back to a much more buttery experience again Was still having massively bad performance from the new rotor dust effects in the apache while hovering low over grass. Interestingly, enabling DLSS (quality) cleared that right up. DCS still does seem to prefer my e-cores, however, and regularly parks and unparks some of my p cores (represented by the big peaks and valleys in the graphs). Not seeing one p-core and thread remaining pegged at 100% anymore (with or without the mt.lua), so that's a positive at least, and perhaps helpful with the frametime spikes I was seeing a few months back:

Don't want to derail this, but fwiw, I did a completely fresh install of win 11 (was previously on win 10) on a brand new 4tb m.2 and the whole stutter issue got worse for me in Win 11, than it was on win 10. I tried unparking cores on win 11 (and 10, previously), along with the usual suggestions and it didn't make any difference for me. Went from still being able to have enjoyable play sessions on win 10, to putting dcs aside for now, unfortunately. I say this only to let you know that moving to win11 isn't a holy grail here (at least not in my experience). In my case, it actually made things worse. YMMV, but set expectations accordingly.

Ended up doing a move from win 10 to win 11 last weekend via a completely fresh install onto a new 4TB 990 pro m.2. Frame time spiking is unfortunately way worse in win 11 now. Causing unplayable stutter on instant action runway start in the apache on Marianas. Disabling core parking made zero difference. I'll be back next patch I guess. Tired of messing with it.

Wow. Not really an aircraft for me, but may pick it up just based on the video alone. Really some amazing work showcased in there. That interactive manual is such a great feature. Would that all DCS aircraft had something like that. Just wanted to say great job and best of luck to you on this one.

Mixed bag for me. I ran both of these, but it was the 2nd one that actually let power settings (or QuickCPU app for that matter) properly unpark the cores (Win 10): My performance issues are intermittent. Some launches, DCS favors my e-cores and tends to load them up more, bringing frame time spikes and stutter along with it. Other launches it doesn't do that so much and the game runs better. In any case, the first launch of DCS after properly unparking all cores, it just loaded up my e cores and didn't really produce a positive result. So, it seems the general issue I have with e cores sometimes being preferred over p cores, which also causes my performance issues when they happen, still persists after unparking cores. A different game I've been messing about with again lately loads up all of my cores without needing to disable core parking, but said game isn't exactly a benchmark for performance I did find the core usage to be surprisingly good in said other game, though, without any manual intervention necessary. ymmv.

I believe dlss only uses TAA, hence why AA is greyed out when DLSS is enabled, as it's forced to taa in that case

It isn't possible to select an AA option with DLSS turned on. They mentioned having DLSS *or* DLAA turned on, rather than both

The day of the patch was... interesting for me. Was experiencing a lot more frametime spikes and stutter and such, but interestingly things smoothed out the following day (yesterday) and my frametime graph is nice and smooth. Performance is mostly good so far (predominantly empty maps), save some framerate dumping in certain parts of Sinai I've never noticed previously, but 2.9 sure does seem to have a preference for my e-cores. Is this representative of what others have been seeing in terms of usage? I'll get two cores/threads typically pegged at 100% and the majority of the rest of the usage seems to be on my e cores. Removing affinity from affected cores doesn't do anything as that load is simply transferred to two others. Cores/threads 8 thru 11 are the ones that are chosen to get pegged out. Maxed out cores happens even on the main menu. As with the previous patch or two, I'm still having issues with MT dcs exe failing to launch properly about half the time. I just relaunch until it gets a proper load. Never could find any cause. Little disappointed it's persisted with this patch, but it's little more than an annoyance given the easy solution. I do wonder if there's some relation between pegging 2 cores and preferring e cores, though. Performance wise, it feels like I'm riding a handicapped line that's easily crossed with any increase in demand above a baseline empty map, while quite a bit is getting left on the table (anecdotal, as that may be). EDIT: Oh, and one other thing I've noticed is that the entire "hue" of the screen sometimes changes from normal looking to a less dynamic, washed out, blue'ish tint for a few seconds before flickering back to normal. This has happened on Sinai, I've not done enough of other maps yet to see if it's happening elsewhere. This also comes with occasional black screen flicker. The only new settings I'm using are SSS on and DLAA (instead of previous 2x MSAA). Will continue to tinker with different AA settings and maps to see if this happens more broadly or not.

I have this strange feeling that the download speed for this patch is going to be on the slower side

If you wanted to accidentally on purpose post the full 2.9 changelog a bit early, that would be cool

I use Authy from Twilio myself as my 2FA app of choice. It also has a handy multi-device support feature, which is great if you don't wnat to have to dig out your phone every time when you're using a personal and trusted devices, and also great if you ever lose or break your phone. You still have another way at getting at your codes and not having to reset 2FA for every app (which would be dozens and dozens for me) or rely solely on back up codes in a situation like that: https://authy.com/blog/multi-device/ I have it on my phone, personal laptop, and desktop, for example. When I built a new computer over the holidays, it made adding the new computer into my existing 2FA app a breeze. Easy to remove an old phone and add a new one into the "chain" of linked devices as a result. (not sponsored, not affiliated in any way Just the one I use for my personal accounts and work ones).

Looks like it's back up at least for now (for me, anyway). Thanks.

Wondering if you might be having an issue with the cdn you use to deliver game files right now. A friend in an other state was downloading the open beta and got toward the end and got a 577 error. As a test, I hit trial on a module to prompt a fresh download and I also got the error from a different ISP and in a different state. These pages are also both throwing 577 errors for me at present. "Origin not resolvable": http://cdn.digitalcombatsimulator.com/ http://updates.digitalcombatsimulator.com/ "00000.000 === Log opened UTC 2023-09-13 19:46:55 00000.010 INFO : DCS_Updater/2.16.3.18 (Windows NT 10.0.19045; Win64; en-US) 00000.010 INFO : src-id: xxx 00000.010 INFO : cmdline: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\dcs_updater.exe" apply xxx 00000.032 STATUS: Initializing... 00000.050 INFO : basedir: C:\Program Files\Eagle Dynamics\DCS World OpenBeta 00000.050 INFO : variant: openbeta 00000.051 INFO : Command: install RAZBAM_AV8BNA 00000.051 INFO : DCS/2.8.8.43704 (x86_64; EN; WORLD,AH-64D,UH-1H,KA-50,F15C-REDFLAG_campaign,A-10C,A-10C_2,FA-18C,HEATBLUR_F-14,F-15C,SU-33,PERSIANGULF_terrain,SYRIA_terrain,MARIANAISLANDS_terrain,THECHANNEL_terrain,NEVADA_terrain,SUPERCARRIER,WWII-ARMOUR,KA-50_3,P47D30,SPITFIRE-MKIX,CAUCASUS_terrain,NORMANDY_terrain,SINAIMAP_terrain,CA,F-16C,MI-24P) 00000.051 INFO : branch: openbeta 00000.052 STATUS: Downloading version info... 00000.329 STATUS: Servers are unable to complete your request. Please, try again later. 00001.847 === Log closed.

And high over Caucasus before: After:

I've always stayed away from texture mods and haven't used a mod manager for DCS until today. Was reading about this last night so decided to give it a go today. Watching back a track on Marianas map with settings that max my 3080's 10GB of dedicated VRM, here's how it looks with these optimized textures disabled: And, here's how things look with them enabled: I'm still maxing out my dedicated vram with those particular settings and that map, but the savings are clear. Thanks for your work on this @Taz1004

Same issues when it doesnt crash outright for me. around 50/50 whether mt launches successfully or not for me. It's

Thanks for that. I'm playing on a flat screen, however, and not using vr at all.

Nothing ticked there.

Unfortunately, it still happens

Thanks for the reply @Flappie. I actually tried a full repair yesterday prior to generating that log. The cleanup was new to me, so I just did that and then ran another full repair with " Check all files (slow)" and "Search for extra files after repair". It loaded to black screen and crashed on first launch after that. I deleted "fxo" and "metashaders2" (again) and I've had 3 successful launches, so we'll see, though I think that's likely a red herring as I deleted those folders around half a dozen times yesterday and failure to launch has happened immediately after doing so in the past as well. If that changes this time around after the cleanup, I'll update

Weird how someone sharing their work devolves into protesting that they gave too much credit to the medium they used (dcs) and nitpicking side topics and the choice of words from a non native english speaker that arent really that relevant anyway Great work on you short. Saw some nice things I havent really seen in other dcs vids. In spite of the upbeat tempo of the music, I think there is still more opportunity to let some of those beautiful shots you mentioned have some more breathing space, and break up the progressively rapid fire cadence, by letting them have their moment. You did some of that earlier and the pace changes were great earlier on when i had more of a chance to enjoy the shot before it sped away Great work. Thanks for sharing your pointers on how you used some of the tools available to you in dcs and made the most of them.

Howdy. I'm attaching a the log after using the mt.lua file as requested by @BIGNEWY in one of the pinned threads. It's been about 4 months since I played until today, but I'm now experiencing (at least half the time) crashes on launch of the mt-bin exe. It's not something I had an issue with in March/April'ish. Typically, the game loads to the main menu in about 5 seconds or so, and that is still the case with the single-threaded exe. Now, the mt-bin exe will either black screen and/or hang my system for tens of seconds, or just outright fail to launch before it stops responding and crashes. I've attached the most recent of those incidents (black screen on launch and eventual "not responding" crash). On rarer occasions, it will load into the main menu (though, not in the expected way with the loading bar, etc) but still be non-responsive with mouse and keyboard inputs (including ctrl+alt+esc) being extremely laggy/non-responsive. The other 40-50% of the time, the mt-bin exe will load as normal to the main menu in about 5 seconds. Additionally, I'm noticing massive stutter/hitch inducing frame time spikes on the mt-bin exe that aren't present in the single-threaded exe and weren't so persistently occurring previously (around 4 months ago when I last played). Not sure if related or what's changed in recent patches since April'ish, but it's pretty persistent and fun-killing. Frame time in general is much flatter in the mt bin exe, but the spikes are far more frequent and large when compared to the single-threaded exe frame times, which have more variance, but lack the spikes and the persistent hitching/freezing that happens in mt. Can pretty much see specs in the log file, but 13700k, 64GB DDR5, RTX 3080, 3x 2TB Samsung Evo 970 plus M.2 drives, 3440x1440 (frame time spikes and crash on load happening at 2560x1080 as well) native, trackir, etc, etc. Thanks. dcs.log

Hey, @McGraw If it's helpful to you at all, I've created a small little mission file you can use that has 48 unarmed somethings to shoot at. You'll start hot and ready for lift off from parking with 50% fuel and a heavy full load of Hellfire missiles. There are 8 columns of 4 unarmed vehicles each, sitting in a farm field about 7km south of the airfield you'll start at. Just a basic set of waypoints to include takeoff from parking hot, turning point over the targets, and a refuel and rearm waypoint back at the airfield. You can add this to your DCS folder in "Saved Games" (at least on Win 10) Then, in DCS, just head to "Missions" on the right menu, choose "My missions", and then this "shootStuff" mission. You can then hit the "Launch multiplayer server" button at the bottom right: nullName your server and give it a password. Maybe make it a public one so he can just search for the name in the server browser to easily find it and he can add it as a favorite, which will hopefully persist: You'll, of course, want to make sure you've opened up the port that you see when you're creating the server so that your dad will be able to see and join it. If you need help with that, reply back with the brand of your wifi router and we can try to find a link online that steps you through it. If it's something you've never done, you'll just type an ip address into your web browser's address bar and load it, then enter the user and password info that's likely listed on the back or underside of your router. That will load the interface to interact with your router's setting where you can enable port forwarding if needed. It'll effectively be a peer to peer connection between him and you, with you acting as the host: Hope that might help a bit, at least. I'm no mission editor pro, but it's just a basic kind of target practice for you to teach your dad with. Some of the vehicles will start moving once you start shooting at them, so you'll have that as well. If your rotor isn't spinning and you can't click anything when loading in, it's because the "server" is likely paused, if you will, with a default setting of "Resume manual". You can change that in the "Advanced" menu (see previous screenshot) to "Resume on load" or "Resume with clients" so you don't have to worry about it moving forward. Or, you can just hit the "Pause" key on your keyboard after your loaded into the mission to resume when ready. shootStuff.miz

I think maybe the su-33 that came randomly included in something I bought last year (Supercarrier, maybe?). Along with that, I purchased the F14 and 18. Those two have seen little more than a precursory fly around, and an attempted aerial refuel in the f 18, which ended in fratricide . I bought that stuff a year ago or so and it's sat in the hangar along with everything as I've not played since shortly after the apache came out until recently again. I've probably learned (and forgotten and re-learned again) the a10c the most, followed maybe by the blackshark. I'm on my way (for the 2nd time) with the apache, which is my precious. Getting hooked on it now. Other stuff I own has had at least a small handful of hours flying around and such, like the huey. I did recently pick up the channel map, which I haven't even flown on yet. Was thinking of getting a ww2 bird for some janes ww2 fighters nostalgia. It'll probably mostly sit in my hangar though.

You can also experiment with your pitch and roll axis curves to land on something that works well for you and for your stick. And your curves might change over time as you get more adept at controlling it. Higher curves in the beginning will make hovering easier, but can also make things feel a lot less responsive. As you get better you might land on a lower curve where your stick is more responsive, but where you're not bobbing and weaving everywhere trying to hover. Your mileage may vary with your stick vs. mine, as I have the long curved extension from virpil with a virpil base, so I have a good long throw on my stick. I started with a high curve (like 25 or 35, even) at first to practice and get more proficient at hovering. I've worked my way down to a much smaller curve as I've gotten better at controlling it in general, as it's a lot more responsive. Hovering needs real fine adjustment, which is tough at first. It gets easier. Practice is a real thing for the Apache vs. some of the other dcs helos, imo. I use a twist stick for rudder. I have pedals, but I also have a bad back and pedals aren't friendly to it, so I get along fine with a twist rudder, even still. Again, the 2 cents of a very non pro DCS'er.