AAO25.com
America's Army => General Chat => Topic started by: bvsnipes on Sunday, August 18, 2013, 07:31:11 AM
-
:mad: im getting soo sick of all these bs errors and sooo many people are complaining do something about it or kill the game cuz that is what it is coming down to!! :censored:
-
try to disable SAI on your server, also on client side and check it out again.
maybe it helps. if not, post it in here please.
thank you
-
:mad: im getting soo sick of all these bs errors and sooo many people are complaining do something about it or kill the game cuz that is what it is coming down to!! :censored:
Hello,
welcome on the forums. Instead of come here to complain about things everybody is aware of since a week, maybe you could try to help by posting your criticals ... You don't think they try to fix it? Maybe you can stop playing for a while if it's so horrible ...
-
Build AmericasArmy_Build_[2004-06-01_02.01.01]
OS: Windows NT 6.1 (Build: 7601)
CPU: GenuineIntel PentiumPro-class processor @ 2195 MHz with 4095MB RAM
Video: NVIDIA GeForce GT 555M (1422)
General protection fault!
History: UObject::ProcessEvent <- (InteractionMaster Package.InteractionMaster, Function Engine.InteractionMaster.Process_PostRender) <- UInteractionMaster::MasterProcessPostRender <- FPlayerSceneNode::Render <- UGameEngine::Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- Level SF Hospital <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 706D7564 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free
----------------------------------
However, like spanky said before play the game in windowed mode and no problem whatsoever!
-
Build AmericasArmy_Build_[2004-06-01_02.01.01]
OS: Windows NT 6.1 (Build: 7600)
CPU: GenuineIntel PentiumPro-class processor @ 1498 MHz with 1023MB RAM
Video: Intel(R) HD Graphics (2932)
General protection fault!
History: UObject::ProcessEvent <- (InteractionMaster Package.InteractionMaster, Function Engine.InteractionMaster.Process_Tick) <- UInteractionMaster::MasterProcessTick <- TickLevel <- UGameEngine::Tick <- Level SF Hospital <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 706D7564 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free
-
Hmmm weird....I am getting these errors now in window mode :shock:
It still worked yesterday evening but now after the update is seems to be worse
-
Yes, after last update I got CE's too... Hope U guys fix it soon...
-
yeah snipes, thats exactly what we Need, 1000 different "critical error" threads, that will be the solution to all of our Problems lol :D
-
yeah snipes, thats exactly what we Need, 1000 different "critical error" threads, that will be the solution to all of our Problems lol :D
noone told you to comment? i was just telling them....
-
but he is very right!
-
noone told you to comment? i was just telling them....
If you just tell em mate, why dont you use the existing thread for that? :)
Multible threads for the same problem doesnt help em und does not help you :)