Chris Posted June 5, 2014 Share Posted June 5, 2014 So in V1.02 I turned off the feature that disabled move animations for units moving about in terrain outside the player's vision (we use it to speed up turns). A few hours ago I also updated the Stable branch with that specific change in a 10kb stealth update. This means that both branches of the game should have this feature disabled. Please can you let us know in this thread if you encounter the invulnerable / untargetable alien bug at any point from now onwards, on either branch? Quote Link to comment Share on other sites More sharing options...
dragoon Posted June 5, 2014 Share Posted June 5, 2014 I played about 12 hours ago; steam made me update before playing. I think I was running V1.01? Or maybe it was already 1.02 by that time? I encountered an untargetable alien in one of the first missions. He was hanging out inside the alien ship. Grenades didn't kill him, stun rod didn't kill him, etc. He kept shooting at me though. After he moved once or twice, while I was flinging the mouse around, I noticed the targeting reticule pop up when my mouse was 3 or 4 tiles away from him. I figured the game may simply be displaying his location incorrectly, hence why everything would 'miss.' I stood a shotgunner next to where I thought the alien really was, I manually aimed at the tile, fired, and killed it. So yeah, have fun debugging how the displayed position vs actual position can get out of sync Quote Link to comment Share on other sites More sharing options...
Chris Posted June 5, 2014 Author Share Posted June 5, 2014 I only did the patch to the Stable branch about 4 hours ago max, so thankfully your experiences don't discount us from having found the issue Quote Link to comment Share on other sites More sharing options...
Chris Posted June 5, 2014 Author Share Posted June 5, 2014 Also, bump. Quote Link to comment Share on other sites More sharing options...
legit1337 Posted June 6, 2014 Share Posted June 6, 2014 (edited) Playing tonight. Will post. EDIT: Nothing so far. Edited June 6, 2014 by legit1337 Quote Link to comment Share on other sites More sharing options...
Chris Posted June 6, 2014 Author Share Posted June 6, 2014 Good. I think we've found the culprit then, or at least I'll ask the coder to take a closer look at that part of the code. I note nobody new has posted the bug on the forums either whereas it was getting posted a lot a few days back. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.