![]() |
#1551
|
|||
|
|||
![]() Quote:
__________________
“Violent, irrational, intolerant, allied to racism and tribalism and bigotry, invested in ignorance and hostile to free inquiry, contemptuous of women and coercive toward children: organized religion ought to have a great deal on its conscience.” ― Christopher Hitchens |
#1552
|
|||
|
|||
![]() Quote:
I was on the other night with a pal and we decided we were going to try and crew a 110 together. My friend was unable to get into my 110 as it was showing the 'WPF Unavailable' message. Do all players who want to fly in the same aircraft have to first spawn at the same airfield? |
#1553
|
|||
|
|||
![]() Quote:
__________________
“Violent, irrational, intolerant, allied to racism and tribalism and bigotry, invested in ignorance and hostile to free inquiry, contemptuous of women and coercive toward children: organized religion ought to have a great deal on its conscience.” ― Christopher Hitchens |
#1554
|
||||
|
||||
![]() Quote:
That should do it.
__________________
Pilot #1 (9:40 hours flying time, 3/0/1 Fighters, 7/2/0 Bombers). RIP No.401 Squadron Forum ![]() ![]() ![]() Using ReconNZ's Pilot Log Book |
#1555
|
||||
|
||||
![]()
There is a procedure but it's not realistic. Best see youtube to instruction, that's the easiest way.
|
#1556
|
|||
|
|||
![]()
Fantastic, many thanks!
|
#1557
|
|||
|
|||
![]()
For those on teamspeak (and you all should be!) who want to see who is talking and on channel in-game you can use either TSNotifier or the TS3 native Overlay plugin. TSNotifier seems to cause problems when running Fraps so here are the steps to get the Overlay plugin working in the current version of TS3:
1. Install TS3 v3.0.5 client. 2. Proceeded through the setup wizard and ticked Enable Overlay, agreed to the warning about anti-cheat. 3. Close TS3 and open the config_user.ini in %appdata%\ts3overlay. Add the following: [LAUNCHER.EXE] dll.force_loading=true 4. Start TS3, log onto 216.52.148.29:9987 and start CoD. The C:\Users\Upstairs\AppData\Roaming\ts3overlay\confi g_user.ini entry looks like this after a successful test: [LAUNCHER.EXE] dll.force_loading=true statistics.tried_in_version=3.3.5 statistics.doesnt_crash_in_version=3.3.5 Also discussed on the ATAG forum here. |
#1558
|
||||
|
||||
![]()
Hmmm is that an older version of TS? I have the latest version.
|
#1559
|
|||
|
|||
![]()
3.0.5 is current.
|
#1560
|
|||
|
|||
![]()
Hi all,
yesterday night (GMT +1) after weeks of inactivity I got two hours to dedicate to CloD. I connected to ATAG server as red player, as usual at take off you spawn in the middle of mess with 35 player fighting around, so I cautiously headed nortbound to gain altitude, then I turned eastbound trough the channel. At 8000ft I was almost feet dry over France heading towards 5-6 wellingtons on their bombrun mission. Closing in their 7oclock I spotted a lone 109 climbing in their direction, I decided to go after him but when I gained his six oclock an heavy stutter almost freezed the pc. CTD was avoided but the contacts (109 and wellis) appeared frozen at midair, 20 seconds later connection with server was lost. At the following connection the players were only 5 and the mission started by night. It was a simply mission reloading or what? Does the mission voluntarly was launched by night or was it a server time mis-synchronization. THX |
![]() |
|
|