Search the Community

Kanium Sunday 17th of Sep 1800 UTC "Operation Gauntlet" by Swordsmandk Where: Kanium TS : teamspeak3.i3d.net:10077 World Clock 1800 UTC Everybody is velcome , though we recommend that new players contact Major Duck, Swordsmandk to get an intro to our use of TS and get setup and get a small get familiar session sometime before the scen as it can be a very very steep learning curve to play multiplayer compared to single player. Its our experience that most new players hang around much longer with that approach and most learn something new that way. We have no requirement for participants to be a member of our VU(Virtual Unit) and you can be a member of other VU's and still play with us or to participate on any number of games etc..., we have a rule that says that your only velcome when you want to play and remember family is more important then the game. 1) SITUATION: a) Enemy: ENY attack in direction of the BERG RAILYARD has been slowed and ENY losses are high. We estimate ENY will attempt a flaking move south along R375 to turn our flank. An ENY mixed BTN of T80, BMP2, Hinds and possible older equipment has been sigthed heading along that road. ENY will be supported by heavy artillery and electronic warfare units with jamming equipment. b) Own: Most of our defence have been focused on holding Berg Railyard. To the south along R375 we have TNK COY (-) with mech support to delay ENY advance towards MORSHYTTAN and the ROAD JUNCTION just north of it. We have more reinforcements comming in from the south but they will have to pass through the junction and MORSHYTTAN to be able to support our defence in the area. We have been unable to reach higher command due to HEAVY radio jamming, so essentially it is up to you as COY CO to delay ENY advance on MORSHYTTAN for at least 1,5-2 hours. Delay ENY advance while keeping casulties low. c) Attachments and detachments: - 2 x TNK PLTS STRV 122 + 2x CO/XO TNK (Reserve PLT can be called in from MORSHYTTAN only if 50% tnk Casualties have occured) - 1 x MECH PLT CV9040B with NLAWs and GUSTAVS - 1x RECON PLT CV9040B with GUSTAVS - 1x CSS PLT - 2x OFF MAP BTY 155 - 1x UAV - Engineer assets for pre planned obstacles + 1 PLT ENG with M136 AT + 1 Biber 2) MISSION: 1) Delay ENY advance on MORSHYTTAN and ROAD JUNCTION for at least 1H30M - 2H 2) Minimize Casualties and conduct mobile warfare when possible 3) Protect UAV (Keep it at range from ENY since its the only one you have) ROE: 1) Only recon units is allowed to deploy north of 48 2) NO artillery strikes north of FLOT is allowed 3) Game will end if either CO or GM ends it due to losses or capture of objective 3) EXECUTION: [Finally: The player's mission] SIGNAL: COY: 26000 A1 PLT: 46000 A2 PLT: 31000 A3 PLT: 33500 Note: This will be a multi crewing scen so find a partner to dance with

Welcome to [Kanium] - 11th ACR: Delay at Bad Hersfeld - Sunday April 24th 1800 UTC http://www.timeanddate.com/worldclock/fixedtime.html?msg=Kanium+Sunday+game&iso=20160424T20&p1=4609&ah=2 Teamspeak: Server info: teamspeak3.i3d.net:10077 PASSWORD: NO PASSWORD REQUIRED

(EDIT - Read the first post incase you are experiencing a similar problem, and I have since posted the resolution directly below in #2). Hi guys, Very strange this, but when launching SB PRO PE (latest version 2.460) nothing happens for about 10 minutes then it springs to life and loads as normal... Up until yesterday it launched immediately, and has done since I received it. I've rebooted and its the same, each time it takes AGES to launch. Once I had a similar error that Vacquero received in his post (only once though): http://www.steelbeasts.com/sbforums/showthread.php?t=13103 However, I too have the latest DirectX, drivers etc. As I say, it was working perfectly well yesterday (doing the UAV testing), but today its not behaving. Very odd. Rebooting makes no difference, and there is nothing appearing in the event logs to point to a system problem. Any ideas? I'm running on a laptop, Windows XP Home, 4GB memory, 512MB graphics etc. The game runs very smoothly on this system and only really suffers FPS hits when there is a lot going on-screen, but other than that it holds 45-60 most of the time. I can't see it's hardware or driver related. Thanks, Quagmire