Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-Fix (#178): radar scan double-counted some units and missed others #178

Merged
merged 1 commit into from Jan 20, 2013

Conversation

wangds
Copy link
Contributor

@wangds wangds commented Jan 20, 2013

The radar scan unit count is often wrong in the heat of a battle. A recount is performed in the Unit_Sort function. A unit may be counted a second time at the expense of another if a swap occurred (e.g. unit swapped with a bullet). In addition, the final unit in the find array is not counted.

TrueBrain added a commit that referenced this pull request Jan 20, 2013
-Fix (#178): radar scan double-counted some units and missed others
@TrueBrain TrueBrain merged commit e68aa49 into OpenDUNE:master Jan 20, 2013
@TrueBrain
Copy link
Member

It btw still miscounts deviated units, but that might be intentionally.

@drnovice
Copy link
Contributor

drnovice commented May 3, 2013

Making hex editing on Dune 2 .EXE file I tried to remove all part regards array sorting and cycling on exactly g_unitFindCount instead of g_unitFindCount-1 it seems works for original game. Unfortunately I didn't find more room to add another cycle as showed here for opendune c++ code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants