EGG

I have the below specs: i7-930 (2.8Ghz), 24Gb RAM, GTX 980Ti, SSD Yep this is a first gen i7 and I do need to upgrade at some point, but I'm trying to hold out until the spectre/meltdown fallout has settled a bit more and CPU's which negate most of these issues come out. Which might be without hyperthreading.. who knows. Anyway, I presently get 40 FPS on the ground in single player and about 80+ in the air. On MP maps this drops to 20 FPS on the ground and maybe 20-30 FPS in the air. I'm not certain MP was always this bad, but DCS is an evolving beast. Graphics settings are primarily medium at the moment. Are there any particular settings around view-distance which can affect MP FPS? I've tried playing with a few, but without much difference.

So it seems it is (for me at least, and some other players on the internet) linked to trying to join servers which are on a different version to the client, e.g. Open Beta vs Release. I've patched to Open Beta and can now join the server I was crashing from. From looking in my previous days crash logs, they had a number of complaints about Ticonderoga's, Kilo subs and a few other ship assets, so it's possible it's only the Open Beta servers which have deployed naval objects which will trigger the crash. The server listing page gives a listing of what server is running what version. https://www.digitalcombatsimulator.com/gameapi/serverlist.php?login=yes&by=PLAYERS&order=desc 2.5.3.22652 appears to be OB and 2.5.3.22176 appears to be release.

I'm on windows 7 actually.

I have the same visual c++ crash in MP. SP works fine, as do some MP servers, but others I will crash everytime at plane selection. I've tried updating the 2017 visual c++ libraries, that didn't help.

Antivirus is AVG, no software firewall. Today is different to yesterday. The following servers appeared: TTI - US Cold War Korea And for the below: Dynamic DCS seemed to have it's IP changed to 45.27.58.61 Two packets sent (one at the very beginning of the list, one in the middle) one received, but not in MP list 104th Packet sent out and received, but not in the server list. TTI - Aus Packet sent, none received Blue Flag Cauc Packet sent, none received 162 servers were polled, 91 responded and 69 were displayed. I'm not sure what the criteria is for not displaying a server that responds, it seems up to 600 ping is ok, so it doesn't appear to be that.

So because I was bored, I had a look at what packets are being sent out to the various servers when you attempt to refresh the multiplayer list. This is using Microsoft Message Analyzer because Wireshark doesn't list PID's. The request to the ED server is via SSL, so you can't see the contents of the master server list that comes back. But the DCS process will then attempt to poll ~180 servers for their status. So as a single example, I loaded the MP screen, which gave me among 111 servers: Blue Flag Caucasus (first time I've ever seen it) Cold War Korea! Servers I didn't see, but then had a look for their IP in the network logs: Dynamic DCS (47.27.58.61 ?) Nothing sent or received 104th Packet sent out, nothing received, but I had seen it earlier in the night. TTI - US Packet sent out, nothing received, but I had seen it earlier in the night. TTI - AUS Two broken packets received and then an ICMP timeout. It had been displaying correctly for me earlier. I'll have another look tomorrow, see if anything changes. It seems it's a per-server issue, apart from Dynamic DCS, which may not be coming back in the master listing.

My server listing has been flakey for a long while, there are servers that are out there, that I know exist, and yet often they won't appear in the server listing until either I refresh a dozen times, or they just never appear. My location is Aus. Almost always appear Aerobatics online some chinese server Sometimes appear Through-the-Inferno US Through-the-Inferno AUS 104th Hoggit Blue Flag PG Never appear Blue Flag Caucasus DDCS I think there's still a Cold War MiG vs F5 server? Seaquark's Korea server Below is an example screenshot of the listing I get. And if I refresh, I get something else. It's found another 14 servers. Is it like this for everyone? Can I store a local server listing for DCS to poll or something? It's annoying when I know there are populated, low-ping servers in my own country (TTI-Aus) and I cannot get them to show up in the listing.

I'll give that a go then, thanks for the replies.

That's a shame, I knew it was more of an interdictor, but I was hoping it would be something a little closer to F-111 Pave Tack or thereabouts. There isn't a lot of call for bridge removal in multiplayer servers. I'm wondering if that U22/A ECM pod might help a bit. Apparently in DCS mechanics it can lessen the lockon ability of SAM's if you punch Mode A. Does this actually work much? I guess I can find a SAM site and give it a go. Will it frazzle nearby team-mates radars?

Hi So I've been using Mavs on the Viggen for a while, usually the RB-75B, but I'm still finding the EP-13 really difficult for both: a) Slewing the sight to the right segment of terrain b) Making out targets from the ground clutter The other day I managed to hit 3 targets with Mavs on a sortie, but really couldn't see any vehicles there for the life of me. There were some smudgey bits and I was firing near the smoke from other burning things, but it was largely guesswork. A lot of multiplayer maps have their CAS zones setup for A-10C's, so the SAM engagement ranges can be quite far. Sometimes you only have a short period to try to lock onto something before your RWR starts telling you to get out of there. Has anyone found a better way to make this work? It would be nice if you could zoom in/out a bit with it. Or if there was an indicator on the HUD for where the EP-13 was looking. But I get the impression a lot of people have moved onto using the BK90.

So the AHK script below basically gives me what I needed, however it breaks the ability to zoom in or out on the F10 map. What does everyone else have zoom bound to? SendMode Input #SingleInstance Ignore WheelUp:: SendEvent {NumpadMult down} Sleep, 800 SendEvent {NumpadMult up} return WheelDown:: SendEvent {NumpadDiv down} Sleep, 800 SendEvent {NumpadDiv up} return

So the way DCS works is that you have a mouse mode for clicking and a mouse mode for panning/zooming, changing between the two using either LAlt-C or double-middle-click. I have a TrackIR, and had wanted to use the mouse to both click and zoom. At the same time. Yep. There's no problem regarding using the mouse wheel for spinning dials, as clicking and dragging them does just as well. So for a long while I would edit the clickable_common.lua file, and set: use_click_and_pan_mode = true This works perfectly in singleplayer, I can look around the cockpit, zoom on areas and click on switches. Unfortunately in multiplayer, editing this file fails the integrity check on some servers. So it's back to square one. I have some POV Hat axis bound on my Joystick to zoom, but would like it on the mouse also. So far I've tried: - a vast amount of googling - trying to assign the mouse Z axis to anything (seemingly can't be done) - looked at creating a per-aircraft input LUA mod, but decided this would probably fail the integrity check also Lastly I'm trying to create an AHK script to push in zoom commands via the mousewheel. This works in notepad, but DCS doesn't seem to care. I've tried both Send and SendInput below. Does anyone know why the below might not work? Failing that, what exactly does everyone else use to zoom in-cockpit? Do HOTAS users just look at exactly the button they want to press? (seems like a nightmare for MiG-21 startup...) SendMode Input #SingleInstance Ignore WheelDown:: ;SendInput {NumpadMult} Send, {NumpadMult} Sleep, 100 return WheelUp:: ;SendInput {NumpadDiv} Send, {NumpadDiv} Sleep, 100 return

If 4th gen jets run into legality issues, I'd still like (prefer really, to tell the truth) a number of the 3rd gen jets; Su-15TM, MiG-23BN, MiG-23MLD, Su-17, MiG-19. Or certainly MiG-25 if it was considered early enough. Heck, I'd love a Tu-128.

Yeah I thought this had been patched by now and tried to take off the other night. Gave it lots of throttle realized it wasn't getting to A/B, tried to take off and bang; tailstrike. Oh well, guess I'll wait for the patch. The throttle on my joystick is kind of wonky and doesn't want to play ball.