Ram69

Howdy. My friend and I are trying to join up together where I'm hosting a simple server with the AH-64D. He is getting a "bad callsign. The callsign is already taken" error when trying to join me. Also, stupid question, but I've not done a multicrew aircraft in DCS before. Do I need to do anything special other than placing the aircraft and selecting it as client? In the player screen for the multiplayer mission, it only seems to allow the pilot seat to be chosen. Thanks.

I just went from 150KB/s up to 44MB/s. Getting back up there

Depends on what other modules and terrains you might have. I think Syria has had a big update as well. My download is around 82GB, so probably larger than that installed. But, again, depends on what you have for modules. Someone else mentioned theirs is only 7GB and they don't have Syria.

Was getting 65MB/s, now getting 0.7 130KB/s .... patience patience....

Early access went from officially stated as planned/hoped for in December, to by end of Q1. End of Q1 is end of March. February has been mentioned, but as a hopeful within the Q1 time frame, but there hasnt been an additional delay yet beyond the push from Dec to by end of Q1. It could be a lot worse. Another certain game has been *in* early access for 10 years now. Missing the first public guess to make it to *early access* release by a few months is a pretty dang successful caveated guesstimate in the dev world (imo). If we're still waiting for it to come to early access in December, then I might start to be a bit impatient While I can appreciate the perspective, I'm not sussed over a few month delay before I can start playing -- what will still be -- an unfinished and in-development product when it hits EA.

Dear, @Wags. Long time listener, first time caller. I saw that you happen to use the exact same stick (Constellation) and Throttle (CM3) as I do and will be using initially for the AH-64D. Any chance you might be willing to share your key bindings/config for the AH-64D at some point when it's closer to time for early access release? Thanks, so much.

Wow. I might still actually have one of those in a drawer somewhere. Had it with our Commodore 64 as a kid.

You also earn "miles" on purchases through the ED store, which you can use toward future purchases for an additional discount. Miles can't be earned if you buy through Steam. For every $10 spent, you get $1 worth of miles.

Thanks for the update. We had COVID hit our household last week, so I can definitely appreciate how disruptive that can be to an already incredibly difficult thing to predict, such as release dates in the development world Been wanting something like this from DCS since way back when I got the disc version of the KA-50. Can wait a little longer to stare blankly at the cockpit wondering wtf to do

How's that going for you, @Lucky? If it's a custom's delay, you may want to reach out to the shipping company directly to ask them about it. They may require some additional information from you, or -- if you're one of the "lucky" ones (bad pun) require import fees before scheduling out a delivery date. Mine sat in Chicago for just a day or two before being released and then getting an expected delivery date (which held). Mine was shipped via FedEx to the Eastern half of the U.S.

Not sure if it means we'll get "working wipers", but it's the 3rd bullet point in Wags' recent update:

Howdy. What are you folks liking who use the 200mm extension with the cm2 base as far as springs and cams go? I just swapped the pre-installed cams for the cosmo no center ones. Left the default springs, since they didn't come out with the screws and I just wanted to see the diff. I immediately didn't like those cams with the pre-installed springs as it feels quite inconsistent. Didn't even fire up dcs. The range feels more consistent with the pre-installed, but was maybe hoping for a centerless cam to get rid of the bump. Anyone have any preferences? I'll still fly the a-10c ii and be learning the f-18, so a decent balance with an emphasis toward helis would be preferred. Any suggestions on what config to try next? Thanks. more specifically, I'm finding the transition with default springs and cosmo no center cams while rolling the stick around from x to y axis, for example, to be quite harsh. like it wants to skip past the diagonals and move straight to an x or y.

Got mine today, as scheduled. Now in the "fun" of mapping sh*t

If it's helpful, in an email they told me that it'll ship 1-2 weeks after they charge and invoice your payment info. I was charged on the 30th and mine shipped on the 6th. So, you might still be a bit sooner. As of a few minutes to midnight last night, my tracking now has a status of "International shipment release - import" with a scheduled delivery date of tomorrow the 13th (it didn't have a delivery date, previously). I ordered in the first hour or two of the Black Friday sale on the 26th of November, was billed on the 30th, shipped on the 6th of December. If my delivery date holds, then it'll be about 2.5 weeks from order to delivery, which is quicker than I was anticipating I think I lucked out on backorder time, which (I'd guess) is probably a bit longer right now, but the rest of the timeline seems relatively predictable from there (customs/shipping issues notwithstanding).

I ordered on the 26th of November during their Black Friday sale. MongoosT-50cm2 base, alpha-r grip, t50cm3 throttle, desk mount, extension. Shipped on the 6th of December. Has made it to the U.S. as of today. At that time they had a banner that said average processing time was 1-2 weeks. That's no longer on their site, so not sure the impact of the Black Friday sale on processing times. You might find this thread useful on their forums where folks are posting their timeline on their orders: https://forum.virpil.com/index.php?/topic/1946-new-ordering-process-live-community-discussion/page/49/ The most recently shipped ones of folks that have volunteered in that thread are from the 26th of November.

Trackir doesn't appear to be the cause of stuttering either (for me). It just exacerbates it. But something to do w dcs does, when fps is off of pure 60, either above or below that magical number. If it's 50, or 100, it is more like a slow motion, choppy mess. Something that I'm not experiencing in other games currently or historically. Doesn't seem too likely to me at this point that there is an end-user cause or fix, since DCS is the only remaining variable from where I'm sitting. Trying to do anything and everything to maintain a perfect 60 (never above or below) is a workaround, imo, not a "fix". Going off of 60 is not the cause either (at least not outside of DCS).

Just fired up Star Citizen for the first time in a decent while. A game guaranteed to give you a sub-60 fps test bed Even at 26-35fps it was a considerably smoother experience with or without trackir. It was night and day different compared to even 50 in DCS. That's saying something when I can call Star Citizen smooth in comparison So, DCS seems almost definitely to be part of the equation for this issue (whatever this issue is). Of course, Start citizen is using about half of my GPU memory and utilization, where DCS pretty much always likes to gobble all 10GB of my video memory. Star Citizen performs relative to its framerate, be it 30, 45, 70 or whatever, with Vsync on or off. DCS World, for some reason does not. It's seemingly the only variable here when I get the "lettuce chopping" off of a pure and steady 60 and/or with vsync off. I have no idea why, but it's a shame when 55 or 75 is pretty unplayable (on DCS) for me

I've spent far too much time digging into this. I'm less convinced it's actually a trackir-specific thing. As someone else mentioned, I'm more thinking now that it's just exacerbated by Trackir. What I think is more likely going on is something to do with vsync being off and/or slipping from a perfect 60fps. I managed to create a situation a few times through jacking settings higher and an actual mission with AI where my fps got locked down to 30 a few times. Interestingly, 30 was actually a smoother experience than 50. 50 (and pretty much anything under or over 60) feels more like about 15. 30 feels like 30, but only sometimes. Locking my fps to 30 and/or going with half-refresh vsync doesn't consistently make it behave like 30. Even if it did, that's a pretty bad compromise. I don't know what's causing it. Tried many, many things, and read too many good and bad suggestions around the interwebz about it or that seemed adjacent to it. But, off of 60 (except sometimes with a perfect 30) or vsync off just behaves like 15fps or so. I happily played many games in the mid 40s in years past, so it's not just a situation of me being picky. Things just don't behave properly off of a perfect 60, for the most part. I do get higher frametime and more spikes when I'm off of that perfect 60. I'm sure it's related somehow. It's just not my historical experience at all that playing games off of 60 (with vsync on and a 60hz monitor) behaves so poorly where basically any other frame rate is essentially akin to playing at 15fps. Perhaps I'm just running into a situation where I'm a bit CPU bottlenecked once I add AI into the mix, due to the engine limitations of DCS on the multithreading front. Consequently, perhaps I'd experience this less with better per-thread performance. I don't think that fully explains why anything off of 60 is so poor in terms of "smoothness", however, as it's not at all representative of what 50 actually plays like, for example. But, I suppose my GPU waiting around for instructions from the CPU could cause the frametime degradation, and consequently the lettuce chopping experience. That still wouldn't explain why such a poor experience when playing at 70 or 100, however; only when falling below 60 in this case. I'm not planning on a new CPU just yet. Waiting to see what 2022 brings on that front before considering an upgrade, and that would be an overkill of a "workaround" -- at best -- for this particular situation. 50 is just a lot more likely once you throw ai and an actual mission into the mix. If it was 5% of the time, I wouldn't really care. But, it's more like 50% of the time when you're trying to do anything other than fly around, which is making it a bit untenable for me. Anyhoo, long post to basically say Don't know why things behave so poorly off of a pure and steady 60, and the lettuce chopping is not representative of my historical experience of playing at 50, or 70, or 40 for that matter. Don't know why it's an issue now, when not in the past. The two variables between then and now would be playing DCS again for first time in about 5 or so years, and a 3080 bought about a year ago.

Atomic bomb. Coming April 1.

Unfortunately, I've already tried both of those with no change regarding this issue. My trackir is responsive and fine, except in the above context. I mean, outside of this issue, Vsync on and at 60fps, it's great. Everything is glassy and so is my Trackir movement. I'm pretty over the moon w/ my performance (vs. 5 or 6 years ago when I was playing last ) outside of this little niggle of the trackir chopping up outside of anything other than vSync on, constant 60. I can just tell already that the more I get back into more involved stuff, that it's likely it'll only be an issue at all of the important times, and then will be frustrating. @BagpipeAs I mentioned, unfortunately for me, Vsync off causes trackir to start chopping lettuce, no matter the framerate.

@Bossco82Thanks for your reply. I'm running an RTX 3080 w/ this monitor: LG 34WN80C-B Granted, it's been a good 5 years since I've played DCS much at all (and on lesser hardware at that time), but I don't remember trackir inducing such stutter anywhere that isn't "on the nose, 60" (and vsync on. capped at 60 w vsync off is still bad). To answer your other questions, I'm running the "High performance" profile. I've just had a look and selective suspend is enabled. I can try turning that off to test. No hub. Trackir is direclty into the mobo. My trackir is set to smooth 50. I've also tried a range between 30 and 50. For those FPS, mostly what I'm jumping in to to test settings changes is low level over the city you start over in an A-10C II on the free flight instant action. 50 to a few hundred feet over the city there. I opted for FXAA today as a test, rather than in-game MSAA of 4x, just to give myself some extra headroom for missions and such. The difference was pretty significant (going from 80-100 to 100-125) and the visual loss was small enough that I was happy with the tradeoff. @will-I think you' might be right. As mentioned, it's been a while for me, but I just don't remember trackir behaving as such in DCS, in Arma, or other games. My experience has typically been that it behaves about as well as the frame rate That doesn't seem to be the case since coming back into DCS. Thankfully, it's a smaller occurrence as I get good performance for the most part (at least in more basic stuff as I'm re-learning it all over again at the moment). It's just a bit annoying, the prospect of having to have to dumb things down more and more in the future (as I get more into larger missions and such) just to keep a magic number so trackir doesn't crap the bed. The weak spot in my system is my CPU, an i7 6700k at 4.2GHz (I'm still not compelled to upgrade it yet). Otherwise, an m.2 NVMe 2TB Samsung 970 EVO Plus, 64GB DDR4 at 3200Mhz, c16. RTX 3080, @Bagpipe. Oh. And, it is Trackir 5, I've had since forever ago

That's interesting. Unfortunately, Fast didn't work well for me with regard to rrackir stutter Straight "on" at and 60fps does the trick (Adaptive is fine too, as long as it doesn't dip below 60, since that Vsync gets turned off and that induces trackir stutter for me. With fast, I'd get 100-125, but trackir behaved poorly as it seemingly does at any fps that isn't 60 and vsync on. with fast, even with 100+ fps, trackir view was more like 30fps (while numapd view, or centered straight ahead is fine in any of these scenarios that I've observed so far).

From all of the threads I've read on trackir-induced stuttering in DCS, it seems that there are only guesses. I've tried many settings. The end-result seems to be just to do whatever is needed settings-wise to *always* stay at 60 fps w/Vsync on. Don't go over 60. Don't go below, or trackir views will stutter while the game is otherwise fine (e.g. numpad views). Here ya' go, though. I was running at 4x MSAA as it ran well there and looks great, but I've opted instead for NCP MFAA, which makes text a bit more jaggy but mostly does the trick for buildings and trees in low level flight. I've opted for this just to give myself more room to stay at the seemingly magic 60 number required for trackir look around to remain smooth *in DCS*. With these settings, I'm hanging mostly around 100-125 in free flight on the Syria map, so I've got plenty of room as I'm only interested in not dipping too far below 60, problem is, even 2 or 3fps below 60 brings on the trackir-stutter. It's not a humungous issue for me at the moment as I've plenty of room to work with, but as I start playing more and more involved missions as I'm re-learning things, the occasional dips below 60 are untenable b/c of the strobe of trackir view in those situations (otherwise, I'd be fine with those as well, as it's still a smooth enough experience for me, and a momentary one, were it not for whatever is going on w/ trackir). I'd rather not dumb my settings down too much just to prevent trackir views from stuttering, as I've a good amount of room to work with already with my current settings and performance is otherwise great (for me).

Thanks, but as mentioned, I don't have G sync. My monitor is 60hz. I get trackir-induced stuttering if one of the two is true: * Vsync is on and my frame rate is anything other than a Vsync-imposed 60. If my fps is higher (e.g. vsync fast), trackir stutters. If it's even a few fps lower, trackir stutters. * If Vsync is set to OFF. Trackir will always stutter at any frame rate, uncluding w/ an NCP imposed fps cap. Vsyc off = trackir stutter always. Vsync on = trackir stutter if fps is anthing other than 60. Numpad is fine, so seems specific to trackir views.