View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0024357 | AI War 2 | Bug - Gameplay | Jan 24, 2021 5:30 am | Jan 25, 2021 11:50 am | |
| Reporter | Chthonic One | Assigned To | Chris_McElligottPark | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | Beta 2.721 Histiocytes And Circles | ||||
| Fixed in Version | Beta 2.722 AI Wave Balance | ||||
| Summary | 0024357: Selection issue with galaxy map and planets | ||||
| Description | Every now and again, there is an issue with selecting certain planets on the galaxy map. Mousing over them will cause the planet name to appear, but the tooltip for the planet will not appear. Neither will the tooltip for the first row of icons appear unless you mouse over almost the very bottom of the icons for the row. Instead you get the tooltip for the warp lanes to the left or right of the planet. Saving and reloading will correct the issue, as well as waiting up to 5 minutes. Zooming in and out will not correct the issue. Swapping planets will not correct the issue. Pausing will not correct the issue. Only Saving and reloading, or just sitting and waiting while paused for the game to let you select the planet instead of the warp lane. This makes it very aggravating to give any commands to move to a planet, or to even view a planet. Nor can I give you a save with it happening as upon loading it will not be happening. It happens at random even without anything going on, so it's not a matter of heavy CPU load. I don't know why it is happening. I don't know how to reproduce this. However it happens to me all the time. | ||||
| Tags | No tags attached. | ||||
|
|
When this is happening, is it also showing the name of an adjacent planet? It sounds like this is hovering over a planet link instead of a planet. I can't think of any circumstance where the name of the planet would show up from your mouse cursor (aka knowing that you're hovering over it) other than that. I haven't been able to recreate this problem in any way, and I've never been able to observe it first-hand. I have fixed a lot of the cases that caused it to more commonly happen, but yours is now the second report I have since my most recent fix. Any added details you can give about what else is happening on the screen would be useful. If there is a tooltip for the link with another planet, if there's a wave coming in to this planet, if any other planets have their name pop up beyond just the one you're hovering, etc. I worry that maybe this is related to incoming waves, potentially ones that you don't see the notification for yet, but it's hard to be sure. |
|
|
No, it is showing the name of the planet I'm hovering over, but highlighting the warplane to one side or the other. |
|
|
I was thinking, do you think it is because for some reason the warp lanes are being treated as higher priority, or in front of the planet for some reason, albeit briefly. |
|
|
Also, no incoming waves. I was trying to send my Spire fleet home to defend against a coming exogalactic force. |
|
|
Though this was before I destroyed that warp gate, so maybe it was before the notification hit for the wave warning. |
|
|
The fact is though, it went back to normal though while the game was paused and I sat there patiently. I didn't have to run the game until the wave was passed. Just eventually it let me select the planet. |
|
|
Also, apologies for the multipost. I just woke up and am currently scatterbrained and trying to remember the events of last night. Did not sleep very well due to a barking dog that got trapped in a room while I was the only person in the house. |
|
|
No worries on the multipost! This is very odd indeed, and I'm not sure why it is happening. I think that I may just need to bite the bullet and switch to using more raycast layers and doing a pair of raycast calls. One to hit planets or icons, and another to hit the lines between them ONLY if no other lines are hit. Or it may be possible for me to do a raycast that intersects multiple colliders even in the same layer, and just return the list. I can't recall on that for sure. If that works, then I can just look at the results and give priority first to planets and then to icons and then to the wormhole lanes. Or icons, then planets, then wormhole lanes, either way. It's been a while since I looked at that type of code. In the past, most of my work on trying to fix this bug has been to get the colliders to not intersect or block one another, but I think that the time for messing around with that is past. |
|
|
Thanks! * Re-coded how the raycasts to hit planets and icons on the galaxy map works. It now does a non-allocating "hit all" raycast, rather than only hitting the first item. ** In this new code path, it first tries to find a ship icon that is enabled and linked to an actual ship. If it does, then it hovers over that. *** Our suspicion is that in the past, it was hitting some of these, but they were actually disabled or not linked to a ship for some reason, and so you'd get just blankness. This should no longer be possible. ** If if doesn't find any ship icon that is valid where your cursor is, then it looks for planets. Assuming that your cursor is over a planet at all, then even if there's a partially-enabled icon, that won't matter. *** Additionally, if there's a collider somehow in the way for the link between two planets, it doesn't matter since it isn't even checking for that yet, and won't do so unless it finds you are not over a planet itself. That was something that was getting in our way in the past, and while we thought we fixed all those cases, hopefully none of them will be possible as a problem now (even in edge cases). ** If we still have found nothing (we're not over an icon or a planet), then it looks for the link between planets to see if you are hovering over them. *** Knock on wood, this should solve all the strange edge cases of planets not being clickable but still showing the planet name when you hover over them, etc. Those cases were increasingly rare in general, but hopefully this gets the last of them. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Jan 24, 2021 5:30 am | Chthonic One | New Issue | |
| Jan 24, 2021 12:06 pm | Chris_McElligottPark | Note Added: 0060384 | |
| Jan 24, 2021 12:06 pm | Chris_McElligottPark | Note Edited: 0060384 | |
| Jan 24, 2021 6:20 pm | Chthonic One | Note Added: 0060386 | |
| Jan 24, 2021 6:21 pm | Chthonic One | Note Added: 0060387 | |
| Jan 24, 2021 6:22 pm | Chthonic One | Note Added: 0060388 | |
| Jan 24, 2021 6:23 pm | Chthonic One | Note Added: 0060389 | |
| Jan 24, 2021 6:24 pm | Chthonic One | Note Added: 0060390 | |
| Jan 24, 2021 6:26 pm | Chthonic One | Note Added: 0060391 | |
| Jan 24, 2021 8:04 pm | Chris_McElligottPark | Note Added: 0060392 | |
| Jan 25, 2021 11:50 am | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Jan 25, 2021 11:50 am | Chris_McElligottPark | Status | new => resolved |
| Jan 25, 2021 11:50 am | Chris_McElligottPark | Resolution | open => fixed |
| Jan 25, 2021 11:50 am | Chris_McElligottPark | Fixed in Version | => Beta 2.722 AI Wave Balance |
| Jan 25, 2021 11:50 am | Chris_McElligottPark | Note Added: 0060393 |
