| 1 |
The current single-unit selection technology is twofold:
|
1 |
The current single-unit selection technology is twofold:
|
| 2 |
* Every unit has a selection hitvolume that exists just to be hit by mouse raytraces.
|
2 |
* Every unit has a selection hitvolume that exists just to be hit by mouse raytraces.
|
| 3 |
* There is a widget that turns tiny selection boxes into mouse raytraces so that moving the mouse a little while selecting a unit still works.
|
3 |
* There is a widget that turns tiny selection boxes into mouse raytraces so that moving the mouse a little while selecting a unit still works.
|
| 4 |
\n
|
4 |
\n
|
| 5 |
I have set the selection hitvolumes to be larger than the normal hitvolumes to make individual units easier to select, as well as to make it easier to issue attack or set target commands. There is a toggle in unitdefs_posts that replaces normal hitvolumes with selection hitvolumes for the purposes of visualisation. Perhaps the large units don't need selection hitvolumes that are much larger than their normal hitvolumes. Anyone is free to do some notepad deving and mess around with the selection hitvolumes to configure them better.
|
5 |
I have set the selection hitvolumes to be larger than the normal hitvolumes to make individual units easier to select, as well as to make it easier to issue attack or set target commands. There is a toggle in unitdefs_posts that replaces normal hitvolumes with selection hitvolumes for the purposes of visualisation. Perhaps the large units don't need selection hitvolumes that are much larger than their normal hitvolumes. Anyone is free to do some notepad deving and mess around with the selection hitvolumes to configure them better.
|
| 6 |
\n
|
6 |
\n
|
| 7 |
https://zero-k.info/mediawiki/index.php?title=Zero-K:Developing#Getting_sources
|
7 |
https://zero-k.info/mediawiki/index.php?title=Zero-K:Developing#Getting_sources
|
| 8 |
\n
|
8 |
\n
|
| 9 |
The relevant files are gamedata/unitdefs_posts.lua (where some programmatic selection volume calculation is carried out) as well as individual overrides in units/<name>.lua.
|
9 |
The relevant files are gamedata/unitdefs_posts.lua (where some programmatic selection volume calculation is carried out) as well as individual overrides in units/<name>.lua.
|
|
|
10 |
\n
|
|
|
11 |
Changing how raytraces are done is an engine change or a complete reimplementation of selection. Making the icons highlight is either an engine change or a complete reimplementation of icon view.
|
Single unit selection is bad in Zero-K