allmhuran

The connection is fine: - ping time in other online games is fine. - ping time to the DCS server in command shell shows 20-30 ms. - ping time in DCS server browser is 350 ms. - ping time on joining DCS game is 15000+ ms. It's only DCS multiplayer that shows this behaviour. Dropping from LAN to ADSL 1024 does not change the symptoms. It's definitley something in the DCS software regarding the communication between client and server. Edit: BTW I am with the same ISP, and on the same port, as I was 6 weeks ago. 6 weeks ago my ping times to the AEF server were reported at ~50ms in game. Two things have changed in that time 1) New version (or versions?) of DCS 2) I have a new computer with the e2200 ethernet controller. The super high ping right at the start is, intuitively, a result of the very long "pause" screen while trying to join the server, as if the ping is requested at the start of the pause, and the game finally responds once the pause screen goes away. Pause screen looks like this:

Was flying with a couple of guys a short while ago and I did see them skipping around in the air a lot, so this does seem to have some impact on gameplay despite the quick radio calls etc. Makes mid air refueling impossible. Just to reiterate, my client version is the same as the server version.

For my situation, here's what info I can give: DCS network connection type is set to LAN. DCS repair does not change the symptoms. Switching to a different ADSL modem/router does not change the symptoms. This is the modem/router I used to use (about six weeks ago) without any issues. If, before I launch DCS, I first start a ping -t to the DCS server I play on, it consistently reports a 25-30ms ping all through DCS startup, multiplayer startup, mission load and gameplay. Confirmed that my client version is the same as other players on the server. I don't see these symptoms in any other online game. Game response seems fine. A radio call requesting startup is responded to immediately (even when the game is reporting my ping at 15 or more seconds). Definitely a DCS software problem. I've been out of the game for a few weeks, but I did not see it on whatever version DCS was up to ~6 weeks ago. Hardware: I7 4770 20 gig ram GTX 670 MSI Z87 with Killer e2200 ethernet controller. << seems common with the OP Internet is ADSL 2+ @ ~10 meg. Edit: Changed killer ethernet config to TCP no delay - no change to symptoms.

Perhaps related... If I ping my regular server's IP in command shell I get a 20-30ms response. In the server browser in DCS, it says ~350ms. After joining the server, the game UI lists my ping at anywhere between 600 and 1000ms. If I alt tab out to command shell I still see my ping at 20-30ms I just checked and on first joining the server the game sits in a "paused" state with a slightly mis-rendered splash screen displayed for quite a long time. When I did get in I quickly checked my ping in the score screen and it was at 13000 and falling. I have the latest version of DCS installed

Necro in case the mission has been updated... I just got it a couple of days ago after playing through the Jackal campaign (really good!). The first mission seems impossible. Killing the ground targets is ridiculously easy... they don't even fight back. But then a flight of fighters comes in from the north and just tears everything up. There's no way to fly against these in A10s. In 6 attempts the most I've gotten is one kill, and my whole flight goes down in seconds every time. even when I'm trying to play hide and seek at 200 feet in the hills. I flew below 2000 feet the whole mission just in case... the briefing says 5000. Meanwhile, two flights of F15s just sit around scratching themselves off the coast. They never come in and provide top cover.

Yep, that's exactly why I was wondering if the laser could be used for markpoints, (ie not just for the TGP point designation or GBU delivery) FreFall: Yep, I'm past all of the basics of SPI, how to set it, unset it, use it, etc. This is, I suppose, a situation one level up in complexity: what that (very good) post does not describe is how the SPI is not "set and forget", it tracks with the sensor that set it, and therefore you can inadvertantly lose your SPI, either by slewing or boresighting the sensor that set the SPI, or, in the case of the TGP, by going beyond its gimbal limits such that it can no longer track the point originally set. This is where the markpoints become useful: they won't move, no matter what, and you can always get back to them easily by resetting your SPI to waypoint track. This allows you to set a target (with markpoint), then slew the TGP around the target looking for anything else in the area before you commit, at which time the markpoint lets you get back to your original target. What I was wondering is if there were any other methods to accomplish the same thing.

I have not been playing long and, as a forum search indicated, I was in the same boat as several other players in thinking that once I set a SPI it was a static point that my sensors would try to track. I now understand that the SPI is "constantly" being set. That is to say, if I set a SPI with the TGP, and then slew the TGP around, the SPI is slaved to the moving TGP and follows it from the initial position. This essentially solved my problem of wondering why my "SPI'd" targets kept on disappearing when I china-hat-forward-long to get back to it. Particularly a problem when performing an orbit offset from the target (to avoid air defenses) and getting obstructed by the aircraft, or the dreaded "gimbal roll" message, at which point I knew I'd lost my target for good. OK, so I read a bit, watched some videos, and decided that the mark-point technique seemed pretty good. Forget the SPI until you're actually in hot... just find a target and set a mark point, then come back, set markpoint as SPI, and you're ready to fire. But this then raised a second question... can you use the laser designator to make your mark point more accurate? I wasn't able to find any information about this. And it left me wondering what "most" people do to counter this? Do you use markpoints, or is there some other, better method? Or are you just so fast at finding targets that look exactly like surrounding terrain at >15 nm that you simply fly towards the target area, lock em up, fire, and bank away before getting in range of air defenses? (I don't believe you :) )

I've just gone through and set up customized snap views for internal cockpit panel views. I would like to have them in "toggle" mode so I am free to use controls with the mouse without holding down a key. I am also using a joystick POV hat to slew the pilot view around in general. My plan is/was to use the POV hat to look around outside, and use snap views to quickly see panel controls. When I use the hold-mode snap views, everything seems fine. That is to say, while the key is held the view goes to my saved snapview location. However, when I press the key for toggle mode strange things happen. First of all, my view immediately changes to one that is looking a little further down. Secondly, the toggle keys don't actually toggle. It's like they're in hold mode... a press and release of a snapview key will flick to the snapview but then return to the slight-eyes-down view. I noticed that if I turned on toggled mode, using my joystick hat was now jumping (and holding position) at some of the snap views. So it seems that my POV hat being in the centre position is overriding my numpad snap view keys when in toggle mode, drawing the view back to centre. I have checked my controls and the POV hat is only bound to view left/right/up/down slow under the view menu. It is not bound to anything under "view cockpit". Halp?

Thanks, I'll check out that config

Beginner tutorials FTW. If you do anymore, could you try to keep the camera more stable? When you're the one in control of where you're looking it's not as noticeable, but to a passive viewer the shaky camera is maddening (and gives me a headache!)

After watching many hours of DCS A10 videos on youtube I decided I'd better try out this DCS World thingy :D I'm an old hand in terms of flight sims... in that I used to play them almost exclusively, but that was many years ago. From F/A-18 Interceptor on the Amiga, through to the longbow series, Jane's F15 and Falcon 4.0. In other words, I have some familiarity with the basics. Soo anyhoo, after figuring out how to map all of the important functions for the SU25T to my cheap HOTAS (thrustmaster T-flight) with just a few additional keys, I went in for my first mission. I have since died many times without even seeing an enemy via the targeting camera.... but that's another story. What I did notice was that after being shot down the camera jumped to another unit. I was able to rotate the camera with the mouse, but the axes were backwards. Right was left, up was down, and so on. I soon discovered the same was true for the F2 camera. I don't see a way to change the external cam in options without changing the internal cam as well (ie, under axes commands there is just camera horizontal/vertical/zoom, no separation between internal and external). Obviously I don't want to fix the external camera just to have the internal camera be wrong. Is there a way to fix this? Secondly, would people recommend using the little minimouse controls (eg on the TM warthog or higher end saitek products) to control the in-game cursor, or do people generally just take a hand off the stick when they need to flick a cockpit switch in a module with an active cockpit (eg a-10)?