![]() |
|
Real Warfare 2: Northern Crusades A new chapter in the Real Warfare realistic real-time strategy games series. |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
Goblin Wizard - thanks!
|
#2
|
|||
|
|||
![]()
Great!
But another patch/Hotfix comes out next week? I didn't see any fix for crashes on the siege that doesn't let me pass ![]() |
#3
|
|||
|
|||
![]() Quote:
Quote:
|
#4
|
|||
|
|||
![]()
I hope so. I am getting the same thing, a pointer error or address violation at some point in the Koch campaign. It seems to get more frequent the longer I have been playing the game or the more times I start it up after it crashes.
Is it possible there is a 'memory leak' issue? |
#5
|
|||
|
|||
![]()
It's possible but I'd say that it's an error that causes other errors and the whole thing works like an avalanche. If you know the exact moment when the first error happens you can run the game through the editor with debugger activated. The problem is you have to know a little about scripts and where to set break points for debugger.
|
#6
|
|||
|
|||
![]()
Storming means assaulting in this case.
|
#7
|
|||
|
|||
![]()
Hi, Sneaksie
![]() |
#8
|
|||
|
|||
![]()
Should have thought of that
![]() |
#9
|
|||
|
|||
![]()
I really hope so yes. I dont really understand if storming really means Storm as in bad weather in this case. The Kock siege doesnt include that, it's always sunny
![]() But lets hope it does. Really good support and work by the developers |
![]() |
Thread Tools | |
Display Modes | |
|
|