2.05 lockup issue

[pzgndr]

ORIGINAL: pzgndr
2.05 seems fine so far, but I've had it lock up on me twice now during orders after setting a waypoint, then couldn't do anything else except Ctrl-Alt-Del to end task. This is in Time to Dance scenario. Maybe there's something odd on my end running Win7 or something, but if others report a similar problem then there may an issue with the new build?

ORIGINAL: Capn Darwin
pzgndr, can you open a thread for this in tech support so we can track it? Just a simple cut and paste would be good enough. I'm a 64bit win 7 myself. Any more details about say about the lockup would be great too. Unit types, multi units, 1, 2, or 3 waypoints, etc. Every little bit helps.

Done. First time happened early in the game moving one of the scouts. Second time happened later in the game, also moving one of the scouts. So maybe the Humvees need to be checked out? Hope this helps.

[CapnDarwin]

Have you had any recent updates (windows or otherwise)?

[pzgndr]

No nothing I recall.  I will reboot and try some more.

[bosbes]

Also had a lock up; see inclosed file but in version 2.04. Where is patch 2.05?

[CapnDarwin]

Hoe ist, was that standalone or a PBEM game that locked up? What were you doing when it happened? Does it repeat if you replay? The more details we get from you guys with the problem, that better our chances of tracking it down. Even a screen shot of the locked up game may help us out. Also tell us you OS and country setting too.

As for 2.05 patch, the Matrix installer version should drop this week. We have a zip file fix on our website, but you would need to be comfortable with unzipping files to the correct folders.

Thanks for the report.

[IronMikeGolf]

I just had one. No game save, as it was during initial orders. Standalone user scenario, head to head. I had played that scenario before, many turns, no lockup. Game locked while second player was giving orders.

[CapnDarwin]

Jeff, thanks for the report and sorry for the bug. This is now a priority bug for us and we will be looking for the cause. This appears to be an odd item that came into being with 2.04 and maybe aggravated by 2.05. It does appear to be centered on giving orders.

We could use more info on the type of order it was and number of waypoints issued. Did you drag or adjust waypoints? The better we narrow down to a common cause the better the chance of a quicker fix.

[cbelva]

To add to what Capn Darwin said, which unit were you giving orders to? At what point in the orders setting did the lockup occur (i.e. selecting the unit, setting a waypoint, if so which waypoint, in confirming the order, how did you confirm the order (i.e. clicked on the unit icon, clicked on the UDP, or pressed "enter")? Thanks for all the info.
 
I am trying to trigger this error. So far I have been unsuccessful.

[IronMikeGolf]

I have not seen it again and it is a common order. STR:
1. Right click Soviet MRC
2. Select Assault
3. Select 3 waypoints
4. Right click the MRC
5. Select Hold from the popup dialogue

At that point, the game locked. Movement path was NOT displayed. It was the third such order done in the same fashion on the same type of unit in the phase. In this scenario, I was only giving orders to the three MRCs.

[cbelva]

Question for you Jeff, When it locks up are the waypoints still showing on the map? Early in development we had a problem with units occasionally not accepting the movement orders. People (including myself thought it was locking up). Rob eventually fixed it, but a short work around was to hit the esc key and reissue the orders. Just thinking out loud.
 
I am trying to trigger the lockup myself, but so far have been unsuccessful.

[pzgndr]

ORIGINAL: cbelva
a short work around was to hit the esc key and reissue the orders.

I had another lockup last night after setting a third waypoint. The waypoints still show up on the map fine. The issue for me is trying to click back onto the unit to issue final posture orders and not being able to do anything, including a save so we could send you something. I have not tried the Esc key work around. Maybe that will help and one of us can confirm that if/when this happens again.

ORIGINAL: Capn Darwin
This appears to be an odd item that came into being with 2.04 and maybe aggravated by 2.05. It does appear to be centered on giving orders.

I can't say I saw this in 2.04 because I barely played it before 2.05 came out, but maybe so. Wish I could provide more info.

[CapnDarwin]

Pzgndr, you guys are giving us great information. We just need to drill down to a common denominator to help us debug this. Try the Escape key if it happens again and let us know if it unsticks the game.

As a side question, are you plotting over a river/stream for the move? Or a minefield or obstacle?

Thanks.

[pzgndr]

ORIGINAL: Capn Darwin
As a side question, are you plotting over a river/stream for the move? Or a minefield or obstacle?

No nothing complicated like that. Other than it seems that multiple waypoints were involved in all of my lockups. Not sure if it was always 3 or sometimes 2; yesterday it was 3 waypoints and a lockup. But I will add for me that most or all of those lockups involved maneuvering around a terrain feature, so perhaps the changes of direction had something to do with the pathfinding algorithm? Again, the maneuvers weren't too complicated but maybe something in the code might have thought otherwise. Maybe this helps?

[IronMikeGolf]

Yes, the waypoints were displaying. I am unsure whether the posture dialog displayed. I may be assuming it did.

[pzgndr]

Here's an example of what happened yesterday. But not on setup, several turns into the game (Time to Dance scenario again) I tried moving the R/2nd unit basically as shown, using a hasty move. And again, I think most of my lockups involved hasty moves so maybe that's another hint.

[cbelva]

Another question for you guys. Did the lockup occur before or after you set the final waypoint stance (i.e. hold, screen, etc)? Thanks
 

[CapnDarwin]

Okay another set of questions.
Are you using a custom map? Does it have a matching FP9 file in the custom folder?
Are your lockups always 3 waypoints?
Are your lockups always a hasty move?
Do you see the calculated path?
Does the lockup happen when you click back on the counter?
Does it lockup after showing the End State dialog? Can you set the dialog or is it frozen?

Sorry if these are redundant, but I want to get Rob a clear picture of where the game goes off the rails.

Thanks for your help!

[IronMikeGolf]

On my lockup:

1. Using a set of william's custom maps. These were my Maps folder since 2.03. They use stock .FP9 files.
2. Yes, though it's only happened to me once.
3. It was an Assault move order
4. No
5 & 6. Unsure if it happened before or after the End State dialog. It was not visible.

[bosbes]

I can only agree with what has been said in this forum; lock up occurred during a standalone scenario (see picture in my earlier post) while giving orders.

[bosbes]

Lock up happened again, for the fourth time (!), in this scenario; see inclosed file.
By the way, it remains a great game!