Kaiza

Nice, thanks c0ff, always appreciate your proactive work!

I am not sure if you are aware, but if you use normal comms you dont need that button. You just need to push mic switch forward/back/down to talk on comms. You only need the / key if you have easy comms set.

Wont update for this Kiwi either...

Hi, server specs are: i7 2600K@3.4GHz, 8gig RAM Windows server 2008 64 bit

MP crash from tonight. All players crashed and server restarted: Client: # -------------- 20121111-093330 -------------- Èß) # C0000005 ACCESS_VIOLATION at 3F5EC95E 00:00000000 00000000 00000000 0000:00000000 3F5EC95E 0029F0E8 0000:00000000 47AE147B 0029F0F0 0000:00000000 00000000 0029F0F8 0000:00000000 00000000 0029F100 0000:00000000 00000000 0029F108 0000:00000000 00000000 0029F110 0000:00000000 00000000 0029F118 0000:00000000 3F872410 0029F120 0000:00000000 Ordinal2()+532410 3F583CA4 0029F190 0000:00000000 Ordinal2()+243CA4 3F58238E 0029F2F0 0000:00000000 Ordinal2()+24238E 3F578DFE 0029F320 0000:00000000 Ordinal2()+238DFE F8708721 0029F3B0 0000:00000000 Ordinal99()+8721 F8708BEA 0029F400 0000:00000000 Ordinal99()+8BEA 3F65F029 0029F490 0000:00000000 Ordinal2()+31F029 3F66193D 0029F4F0 0000:00000000 Ordinal2()+32193D 3F679684 0029F520 0000:00000000 Ordinal2()+339684 3F679579 0029F580 0000:00000000 Ordinal2()+339579 3F700498 0029F5F0 0000:00000000 Ordinal2()+3C0498 3F7018D8 0029FAE0 0000:00000000 Ordinal2()+3C18D8 3F7042CF 0029FB90 0000:00000000 Ordinal2()+3C42CF 7691B22D 0029FBC0 0001:0001A22D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 76E86861 0029FC10 0001:00025861 C:\Windows\system32\ntdll.dll RtlUserThreadStart()+21 Server: # -------------- 20121111-093325 -------------- # C0000005 ACCESS_VIOLATION at 3F33C95E 00:00000000 00000000 00000000 0000:00000000 3F33C95E 0018F3C0 0000:00000000 3F2D3CA4 0018F430 0000:00000000 3F2D238E 0018F590 0000:00000000 3F2C8DFE 0018F5C0 0000:00000000 FB5F8721 0018F650 0000:00000000 FB5F8BEA 0018F6A0 0000:00000000 3F3AF029 0018F730 0000:00000000 3F3B193D 0018F790 0000:00000000 3F3C9684 0018F7C0 0000:00000000 3F3C9579 0018F820 0000:00000000 3F450498 0018F890 0000:00000000 3F4518D8 0018FD80 0000:00000000 3F4542CF 0018FE30 0000:00000000 7680652D 0018FE60 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 76EFC521 0018FEB0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

Thanks c0ff. Was there any other changes to the multiplayer side with 1.2.2?

This wiki article on ITAR may give you a little insight http://en.wikipedia.org/wiki/ITAR

I am not familiar with the HSI that you have attached however: NDB approaches are different to VOR in that you will not get a course bar/CDI bar. All you get is a needle that points to the station. You will only get a course bar on a VOR, TACAN, ILS or GNSS approach. What was you course bar dialed up to? I suspect it may have been a VOR, in which case the deviations that were displayed were not reference the NDB, they were reference a VOR that was elsewhere. To fly a NDB approach you need to dial up the course, but only for reference for your inbound track. Use the needle to track inbound rather than the course bar. Remember "push the head, pull the tail" so if your ADF needle is right of the inbound course (this means you are left of track) you need to "push the head" ie come further right to "push" the head back on track.

What ever missions you like. I reccomend joining one with 3-10 players. Yep, if the server is open people come and go during missions No, most people fly on their own Only if people are running TARS, but on open servers people dont tend to run TARS very often, it is normally used on closed servers.

Page 88 of the manual: 1. Master Mode Control Button (MMCB) Duration Long = Air-to-Air Mode.

In air to air mode: Alternatively on the UFC:

Its the sad reality of multiplayer at the moment unfortunately. The only types of missions that seem to work OK, are simple missions with less than 10 players (that all join at seperate times), and no CBUs. There doesn't seem to be as much complaining around here as their used to be, I think that is because a lot of people are starting to give up. I am just living in hope that a dedicated server program is just around the corner that will solve everyone's problems, and those 32+ player games with all aircraft types that people have been dreaming of can become a reality. Stable dedicated server + TARS with CA functionality = the dream that keeps me playing this.

Thanks Paganus. Do you have mix of aircraft types or just A-10s?

Thanks for all the input guys. I should have added that flights normally consist of a KA50/A-10 mix. Additionally we had none of these issues prior to the arrival of DCS World. Yep latest version, yep all missions were modded in 1.2.1 prior to use. The mission we played last night was doooms "Longstraw". I haven't played it before, but doesn't seem like there is a particularly large number of units on start. We have tried on 4 different missions of various complexities with same results. Have not tried that one but will give it a go. It is not my server, but this is what I could dig up: i7 2600K@3.4GHz, 8gig RAM Windows server 2008 64 bit Both interesting points. I have no idea ENO. The server only has A-10C installed as far as I am aware.... I am going to try and get "Megagoths" .lua mod here:http://forums.eagle.ru/showpost.php?p=1594373&postcount=1 a go. I am crossing my fingers this may help! Thanks again for all the input.

Looks really positive. If this works, you, my friend, could be the savior of MP. Will try immediately. Nice one.

I have just come out of 2.5 hours of trying to start another MP mission that has been a complete mess. We have tried this multiple times on multiple servers with the same result every time. Are we the only Squad that launch flights after a brief where everyone joins together? We have tried: -Keeping the server paused until all clients in pit -Keeping the server paused until all clients are spectators -Joining one at a time -Joining together normally What we get: -Most commonly: as soon as the game is unpaused or the client is in the pit, massive warping to the point where aircraft crash into each other and the tarmac becomes a mess of burning A-10s. People rejoin the slot and warping continues. We try to ride it out to let the server calm down but the piles of wrecked A-10s gets so big no one can join any slots. It is impossible to play. But also: -People cant join the server -People get connection interupted when trying to join -People get server ping timeout error -People can get in to the server but can't join any slots -Server ping spikes from 1000ms back down to normal The server is 70meg up and similar down. It is set to "LAN". Tonight we restricted players to 6 to try and help the stability, but no change. What I would like to know is two things: 1- Do any other squads/groups run missions where clients join the server together at a similar time, and if so do you see these problems? 2- Is this a logged issue that is currently being worked on at ED? Many thanks for any help in advance. I am pretty much at my wits end, so any help is very much appreciated.

Yep it is quite normal at the moment unfortunately, hopefully we will see some improved stability in future patches. For us it seems to be tied to the number of players (any more than 6-8 and all of a sudden it goes from smooth to players crashing) and when the a-10 guys drop CBUs it also seems to cause problems. I hadn't really picked this up, but now that ENO says it, it does seem to affect the rotor heads more these days. It's just a matter of waiting for patches to address the problems.

^^^^^^^^^^^^^^^^^ This

Hey man, just checked out your track. Your problem is that you are trying to lock up a building. The mavericks you are using are AGM 65D which are IR guided. They require an target that exhibits an infra red signature to lock. To destroy buildings like that you are best to use force correlate mode on a TV guided Maverick, but that is something you can learn later. Everything else looks good though, so try again with a target such as a tank and you will be good to go. Cheers

Are you pressing TMS up to lock the target? You have to keep trying until you can get a lock. Have you warmed up and selected maverick in the DSMS?

Here is the location:

Interestingly, since the last update, the radio speaker feature has been working for me...

Negative, those radio freqs down the bottom are not functioning at the moment and not required. Did you guys uninstall the old TARS before you reinstalled? Not doing this caused problems for us.

Check out page 646 of the manual. It decodes the 9 line for you. In short a "9 line" is a standard operating procedure for passing a target for close air support from a ground or air unit to a supporting aircraft. 4 is the altitude and 6 is the position of the target. You can enter those coordinates into the CDU and create a waypoint on your target. When the JTAC says 1,2,3 N/A, it means that they are not applicable as a "Type 3" attack is being used. You can find more out about type 1, 2 and 3 in the manual and also here: http://forums.eagle.ru/showthread.php?t=72701&highlight=close+air+support+%289-line%29 If a JTAC is SADL equipped he will send the data via datalink. This will appear as a red triangle. You can hook this position in your TAD and attack it rather than entering the position manually. Check out this guide for additional reading: http://www.google.co.nz/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CB4QFjAA&url=http%3A%2F%2Fforums.eagle.ru%2Fattachment.php%3Fattachmentid%3D43043%26d%3D1286623016&ei=TMOMUPn5E82iige26oHgAQ&usg=AFQjCNFKTHTxnKke7VZ4G9wcf0gXLHB7aw

Could not get the Su-25 working either. Su driver listed as "spectator" in TS3 panel.