LDG-Gaming

Tried reducing some display settings, although reduced the blood settings (was everything on by default)...game looked a bit worse, but - TDM ok, one freon round ok, second round - crashed again.(
Any other suggestion before reinstalling whole game? There must be some solution, I hope...
Can I find out the reason from the UTlog file?

Take a picture of the crash you're getting or post the crashlog

Might help give a more accurate fix than just suggesting 'change settings'

what's your graphic card? Have you tried to install the latest available drivers?

Cant take a picture of it - the game simply quits without any report or message.( Than Im able to start it immediately and join again. I can see quite a lot warnings in the loq but dont have a shine about them:D

DAMN guys! Im the right dumbass I think:D - first line - "Command-Q hit"
I have set special wep function on command, so every time I throw a knife and then push Q (binding to assault rifle) I give a game order to quit.)
Thanks for your attention, appreciate that!

"Log: Command-Q hit...quitting game!
Log: appRequestExit(0)
Exit: Preparing to exit.
Log: Purging garbage
Exit: Game engine shut down
Exit: SDL client shut down
Log: Waiting for file streaming thread to finish...
Exit: OpenAL Audio subsystem shut down.
NetComeGo: Close TcpipConnection 37.59.16.144:8040 Fri Jul 5 16:00:39 2013
Exit: Socket shut down
Log: d
Log: (Karma): Level Karma Terminated.
Log: Garbage: objects: 92321->0; refs: 1543179
Exit: Object subsystem successfully closed.
Exit: Exiting.
Log: FileManager: Reading 0 GByte 440 MByte 333 KByte 772 Bytes from HD took 67.846466 seconds (67.846466 reading, 0.000000 seeking).
Log: FileManager: 0.000000 seconds spent with misc. duties
Uninitialized: Name subsystem shut down
Uninitialized: Allocation checking disabled
Uninitialized: Log file closed, Fri Jul 5 16:00:40 2013"

You are pressing CMD-Q accidentally?



Hope it's fixed now

pupimassa wrote: "Log: Command-Q hit...quitting game!
L

Equivalent to ALT+F4 that gives special powers in BW server

Im not sure if changing controls will eliminate the problem completely, but hopefully it will reduce it - the truth is it hapenned even when I wasnt using knife throwing, but not so often. Ill see.)

So it happens again, Im afraid it isnt so simple - here's what .log says about the last crash:

first "Warning: HMCAttachment DM-AkBal2k4.HMCAttachment (Function BWBPRecolors4MainPro.HMCAttachment.PostNetBeginPlay:00A3) Accessed None 'Weapon'"

than: "Warning: AntiTCCSecurity DM-AkBal2k4.AntiTCCSecurity (Function AntiTCC2009r6.AntiTCCSecurity.O30970O:008B) Accessed None 'O86270O'"
- this message is 20x the same

and at last: "Log: Unreal Call Stack: USkeletalMeshInstance::Render <- FDynamicActor::Render <- FDynamicActor::Render <- RenderLevel <- FLevelSceneNode::Render <- FPlayerSceneNode::Render <- UGameEngine::Draw <- USDLViewport::Repaint <- USDLClient::Tick <- ClientTick <- UGameEngine::Tick <- UpdateWorld <- MainLoop
Exit: Exiting.
Log: FileManager: Reading 0 GByte 353 MByte 43 KByte 948 Bytes from HD took 3.623369 seconds (3.623369 reading, 0.000000 seeking).
Log: FileManager: 0.000000 seconds spent with misc. duties
Uninitialized: Name subsystem shut down
Uninitialized: Allocation checking disabled
Uninitialized: Leak detected using FMemStack [Size: 65524]
Uninitialized: Log file closed, Fri Jul 5 23:26:50 2013"

cant this be a problem with HMC canon?

The HMC part is irrelevant, that's caused by some HMC's 3rd person model for someone else trying to access the 1st person weapon, which only exists on the server and for its owning client.