Bug report - losses incorrect

[Don Maddox]

There appears to be another bug with DA. In the current version the Victory Status report is showing 30-40% losses before the scenario even begins. Yet, there a 0 losses shown at the bottom where it breaks them down by type. From what I can tell so far, this doesn't effect most of the original DA scenarios, but all the ones that have been made with more recent versions are affected. I just checked the scenario that CPangracs released a few days ago and it has the same problem (Blue - 31% losses, Red - 36% losses on turn 0).

These losses seem to continue to mount throughtout the scenario, but what's even more confusing is that they don't appear to be adding up right. I created a shell scenario to test what's going on. I gave the Red player 3 objective markers worth 100VP each. I didn't give any to Blue. At the start of the scenario this should have been 0% losses for each side and 100VP for Red. Instead, both sides had 30-40% losses and when Blue captured the victory markers Red showed as having 500 points. :hmmm:

Something is wrong somewhere. Anyone heard from Col Lunsford lately? We need to find out what's happening and get it fixed or we may have to delay the tournament.

[Don Maddox]

I assume everyone else is seeing the same thing?

Not sure what's going on here. The more I mess with it the more confusing it seems. In the attached image you can clearly see the disparity of the losses.

[cbelva]

I am seeing it to different degrees. Another problem which I have observed while testing a scenario I was working on is with ownership of objectives. I have seen blue forces sitting on objectives previously owned by the red force still showing ownership by the reds. I have not seen it consistently so I cannot tell what is happening. I was not going to mention it until I was more sure of what I was seeing.

[Don Maddox]

Yes, I think that is part of the problem I am seeing. I am having difficulty consistently reproducing it. Sometimes it happens and sometimes it doesn't. There may be more than one bug at work here.

[Gary]

Don,

I'm seeing the same thing. I checked through some of the stock scenarios and the same thing seems to be happening there as well.

Gary

[Hub]

Checked as well- same thing, including some of the stock scenarios...Too bad, things looked good for awhile.

[Don Maddox]

Thanks for the feedback gentlemen. Let me know if anyone has any ideas what is causing this. I have been attempting to contact Col Lunsford without any success so far. The OPFOR tournament is slated to begin in just a few days. If we can't find a solution by then we may be forced to postpone it until Jim gets this fixed.

[cbelva]

I have found another interesting observation. If you open a scenario to play a game(vs computer or e-mail), it shows the incorrect losses at the beginning of the scenario. But if you open the same scenario in the editor first and then click on the button to "return to main menu" and then restart the game, the loss points are not there. It is showing the correct loss points as "0" for both sides. I have not gone any further such as play a scenario to tell if the loss points remain consistent. If you were then to use the pull down menu to open a new scenario and select the same same, the incorrect loss points are back. I have no explanation for what is going on. This may help someone else understand what the problem. We will more than likely have to wait on Col Lunsford to return.

[Don Maddox]

Don,

I've been out of the net since Monday. I will look at this ASAP today
and get back with you.

Jim


Hopefully, well get this resolved soon. I'll update everyone as soon as I hear anything.

[Jim Lunsford]

I've checked the code and cannot find any problems that would cause the issues some of you have reported: inaccurate loss reports and objective status. What is particularly interesting is that I have not altered this part of the program for some time. I did observe the inaccurate loss reporting after loading a recent CGSC scenario; so I can see first hand what the problem looks like, but I cannot replicate the problem when I try to build a new scenario from scratch. Could it be that the original file some of you are using is corrupted? I know that the CGSC file I have was so corrupted that TJ rebuilt it before the students used it.

To further help ID the origin of the problem, did anyone who experienced this problem build a scenario using a previously saved game or use the new Weapons Editor to import an existing OOB file?

The function that checks the ownership of objectives is very simple. At the end of every game turn it checks to see which Red and Blue forces have footprints that overlap with every objective. It then creates a tally of the total Red/Blue RCP for each objective and awards ownership to the force that has the most RCP.

I want to solve this problem before the end of the weekend. I will unfortunately have to travel most of next week and will not be able to work on the code or read email until I return on Friday. If anyone can tell me something more that would enable me to further pinpoint the problem, please reply ASAP. I appolgize for your inconvenience and will field a solution as soon as I can ID the source of the problem(s).

[Don Maddox]

Jim,

Thanks for the time and effort. I have created several scenarios from scratch and I'm getting the same problem in all of them. I have not used the weapons editor to import an existing OOB file either, although I did use it to add a few custom units. Having said that, I'm getting the problem even when I don't use any of those custom units in a scenario.

I have noticed this: when I'm in the scenario editor and actually building or editing a scenario, the losses show as 0% (which is correct as the scenario hasn't started yet). But when I open the very same scenario to actually play it, I then immediately see the losses jump to 30-40% on turn 0. Not sure if this info is helpful or not.

[Don Maddox]

Here is an update on the status of the OPFOR tournament. Col Lunsford is currently unavailable due to other issues. He will be back very soon. He is aware of the bug and has been working to nail it down. I will be out of town for 5 days starting Saturday morning. We will get this issue resolved and hopefully get the tournament running shortly after I return. For now, just be patient. Some of you may want to start a small DA PBEM just to get in the hang of it. Can't hurt.