M1Combat

LOL

I'll bet it's not too much longer...

What about if you enable att before trim... I assume it works then? Also... what if you get to hover, trim, enable attm then trim again? All good there too?

I read in the thread a while back that there was some interest in locking the frame output of the GPU to 45 directly because it was even better than being framerate > refreshrate. Is that true and if so what is the best way to lock the GPU to 30/45/60 depending on hardware capability? Honestly I'm pretty sure I've NEVER experienced VR with absolutely no ghosting. In any title. Same with pancake displays... I've never used a pancake that was >60hz refresh though and I've only ever seen 90hz VR while looking at the sky so that doesn't count either LOL...

What's the best way to lock framerate with an nvidia GPU?? Does RTSS work? Nvidia inspector?? Anything better?

Do you have your stick type setup correct in the DCS options? Also... you're saying you get to a hover, trim (by tapping the FTR button I assume) and it's all good to there... but then when you enable attitude hold it starts to go places?

Thank you Raptor

If you don't retrim every time you stop moving the stick (especially if it's outside the SCAS boundary) then you're fighting the system. It's designed to be trimmed. In sim and IRL.

This is the way for air combat. I've downed many a Huey and Hind with the gun using this technique. Maintain FORWARD movement. Don't let them drag you into a slow strafing/turning fight. Boom and Zoom ;). I haven't tried on Apaches yet as I'm still flying the Apache for now :). BTW Volk... That's a GREAT vid

Pay attention to the blade pitch angle, that's all you need to do. It's above and left of your left knee. Start your dive. When you get to about 250 turn blade pitch down to ~3 degrees. Pay no attention to the flashing red lights. When you're getting to the bottom of your dive pull out of it and gradually increase blade pitch. Stay below about 5 degrees or so until you're back below "safe" speeds. The closer back towards ~275 you get you can turn the blade pitch back up... but be careful. You don't need to corkscrew unless you have a spot at the bottom of the decent that you don't want to overshoot. The control inputs that cause blade collision are roll right, rudder right and collective (AKA blade pitch). Also... Turn off the Alt hold AP channel. It will try to kill you. You're welcome.

"I use dampers to act like a pseudo force trim system." I think I understand the point you're making here but you have to understand that from the perspective of the aircraft... What your stick does when you let go of it has ZERO to do with trimming. It's just where the stick is. "Trimming" the aircraft is simply telling it to center the current SCAS parameters around where the stick is currently sitting and depending on mode try to hold this or that flight parameter. The fact that your stick doesn't re-center by itself does not replace the trim system. You still have to trim just like everyone else does except that you don't need to re-center the controls after releasing trim.

I don't think it's programming limitations. The SCAS will need to know what you're asking the controls "center" to be each time you move that center. That's done by releasing the trim button. Press the button, move the stick to where you want it, release the trim button. Just like IRL. With sticks that re-center you'll then also have to release the stick to let it center but assuming you have the correct options checked in the config of DCS you won't need to do that of course. To note... It seems that tap-trimming works better in the Apache than the Shark. I won't go into the details of why you "never" want to tap-trim the shark but suffice to say... In the Apache it seems to mostly work fine and doesn't cause the same problems it does with the Shark.

I think you can run Liberation on a dedicated server on another core if you have the mem for it.

DDC posted another work around up there... Look as far as you can left, reset your view, then look as far right. This will add the degrees you looked left to the degrees you can look right. Then when you're done look ahead and reset again. Not for the squeamish :).

Well... OK. I'll grant you that it's likely that not too many of us are still running 1080p. At least not the ones with top shelf CPU/GPU combos... As far as the fact that there are places where it helps considerably and places where it doesn't... that's pretty much just always true all the time really. You graphic specifically shows a case where the system was ALREADY GPU limited... and it that case it gained 7%. That's phenomenal. Of course the difference compared to a non 3d chip that's faster than whatever it was compared to here would show smaller gains. Again... that's kinda just how things work... But... Smaller gains than what? That smallest 13% gain you see here? Or smaller than the 46% gain? I don't care. Say we get 1/2 of the smallest gain there... so about 7%. That's worth it sir. That's 3FPS at 45FPS. That's nothing to sneeze at in the VR world. I get that in the GPU world gains of 30-40% per generation are normal... It don't work that way in the single thread CPU world friend. 7% gains (please keep in mind I've gone through great lengths here to be ULTRA conservative with the estimation) is... HUGE.

It appears to my eye that the graphic you provided shows a few things... If you have enough CPU ALREADY and are ALREADY GPU bound... you can maybe gain 7% by upgrading your CPU to the 5800x3D. If you are already CPU bound and your GPU is the one waiting... You can gain a lot more. How much depends what GPU you have of course.

Your graphic... assuming I'm understanding it correctly... clearly shows the opposite of what you say it does yes? In all the cases where the CPU was the 3900X the limitation is the main thread (CPU) aside from the bottom one and in all cases where the CPU is the 5800x3D the limitation is the GPU... Also in all cases there the gains were 7% in the case of the one that was ALREADY GPU BOUND... and the rest are from 13% to 46%... So... looks like a huge win for the 5800x3D yeah???

Yeah I suppose if you drop XMP memory in like a Dell workstation that's meant for business with one of those 140W PSUs I suppose that could be a problem :). The difference in V between regular DDR4 and what mine likes at it's XMP settings is 1.2 to 1.35V... So... Not gunna fry anything I don't think :). I don't have any crit errors to check at all. System hasn't crashed even once since I built it. Sorry about your sound stuff... Glad you got it resolved...

Most of the memory sticks any of us will be running have what's called an XMP profile. It's kinda like plug and play for memory timing for lack of a better way of explaining. BUT... If you make changes to your BIOS that aren't bootable most modern motherboards will load a set of safe defaults after a few failed attempts. The safe defaults set memory timings to low speed "safe" settings. You generally then need to go back into your BIOS and tell it to load the XMP profile timings. It's 100% a noob mistake. I'm not a noob. But I've made this mistake and I've been running in DDR4-2400 mem timings for quite some time. Running the basic 3600 timings from my XMP profiles now... Ugh. There's some more performance to be had if you want to tweak beyond XMP profile timings... but at LEAST make sure you've loaded those timings if you can :). Check your XMP's folks :).

They both have huds??? Calm down...

Well... I am familiar :). I'm just saying that there are significantly superior options out there in DCS... You just need to be willing to restart the mission intead of re-spawn. Or you can respawn too if you want it just takes a couple clicks. Esc/back to spectator/choose role/fly for re-spawn (there may be a hotkey too I'm not sure) and then if you want a mission restart just esc/Ctrl-R or maybe Ctrl+Shf+R? That will restart the mission. I just don't understand the strict locked requirement that it be "exactly the same thing" without any diversion what so ever. There's just no point as far as I can tell. Id bet if you go to the thread of the person who made the mission above I'd bet he can figure out a "respawn" command too... DCS is infinitely moddable and the ME is infinitely configurable with things like Moose... soo... ZERO need for the devs to provide you with exactly what you want when they've already spent YEARS providing a platform that will do what you want if you ask it to... Go ask it to :).

I can definitely see the benefit to the furball/dogfight mission... I just think there's something out there already. How about YOU go look :)... you're the one that knows what you're looking FOR.

I've played it... How do you know the mission I posted up there doesn't work that way? OR... that there isn't already another that does? Come on folks... Like I said I'm all for something like this but if you are NOT willing to go check out a mission that may do exactly what you want and all you ARE willing to do is ask for a tailored feature to be dropped behind a single click or maybe two that somehow devines "exactly" what "you" want then I'm actually against it. I think the dev time of ED is MUCH better spent adding features to the ME or fixing bugs or something. The COMMUNITY is more suited to using the provided tools to give you exactly what you want... Which has "almost certainly" been done already and you're just not actually interested enough in your feature to either go take a look and/or make it yourself and in so doing help yourself AND the community. That mission above was literally the first result in a very simple search. I'd bet that what you're trying to get done could be made in a basic form with the mission editor and a little research in a VERY short amount of time. Please shift your paradigm.

"Spawn four F-14 at 50 miles, angels 30"- 4x F-14 will spawn on your 12'o clock at 50 miles, at 30,000 feet "Spawn four F-14 at 50 miles, angels 30"- 4x F-14 will spawn on your 12'o clock at 50 miles, at 30,000 feet "Spawn four F-14 at 50 miles, angels 30"- 4x F-14 will spawn on your 12'o clock at 50 miles, at 30,000 feet

I mean who needs them to be at some exact distance anyway? Measure 10NM or 20 or whatever you want and then set them about where you want... No big deal... Don't get me wrong... the feature would be cool for sure... Uspecially if they made it reset the planes after each kill and all that and maybe so you could use the comms menu to spawn another fighter of your choosing... But wait... They would just use the ME to do that and I'm 99.9% sure SOMEONE has already created that mission :). Just go find it folks :)... Oh dang... Example: "Spawn two Mig 29 at 5 miles" - 2x Mig29 will spawn on your 12'o clock at 5 miles, equal altitude to your aircraft "Spawn four F-14 at 50 miles, angels 30"- 4x F-14 will spawn on your 12'o clock at 50 miles, at 30,000 feet "Spawn two Su-27 on my six" - 2x Su-27 will spawn on your 6'o clock at 1 mile, equal altitude to your aircraft https://www.digitalcombatsimulator.com/en/files/3321361/ You're welcome