|
|
|
|
|
|
|
|
Re: JA2 Night Ops Bug Reports[message #226949] |
Mon, 13 July 2009 01:16   | |
profound
|
 |
Messages:65
Registered:October 2004 Location: Lithuania |
|
|
Well, I also experience long stopwatches time after time. Generally, NightOps in this respect feels very 'vanilish', compared to quite speedy v.1.13.
Some bugs and mismatches(v.1.02):
1. Firstly, very annoying - time does not flow in turn based mode. I had a 30 minutes(real time) battle Mercs&Militia vs Army which was played in full TB mode and in game time took one minute :dontknow2: Disappointing and frustrating - so valuable mercenary reinforcement from nearby city sector, which I had ordered, came only after the battle.
2. Collimator scope(on P90) seems flawed - second aim-click adds negative bonus to accuracy.
3. Vanilla left-over - grenades which explode on the roof, injure people inside the building. Annoyances with civilians!
4. Heavier and lighter grenades have the same throwing range.
5. Strangely enough, additional night illumination control (ALT -/+) does not work. I remember it working on older .exe versions, though.
|
|
|
|
|
|
Re: JA2 Night Ops Bug Reports[message #232122] |
Sun, 30 August 2009 13:53   | |
Burzmali
|
  |
Messages:242
Registered:March 2007 Location: Estonia |
|
|
happnened about 3-4 times in the whole campaign, that means in over hundred battles. the moment when game goes from turn-based into real-time, but the battle is not finished, somebody says: its not over yet or something like that. i think its usually random who says it. so sometimes i got "Barry says..." and the problem is - i had not Barry in sector or even on my team at all. so it seems in some situations some random variable that should go over mercs in sector (or, really, over their numbers in table of mercs to find corresponding replica from their speech table) gets compromised. equal to zero, obviously, as Barry is the first one (or #0) in table. its kinda nuisance, as the portrait frame does not disappear from the screen for some time. still, if a variable gets illogical value, there is usually some error elsewhere: some other function writes its result into wrong place or something like that.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|