@Black Pebble Auto-click seems to be back. GUI items are clicked or "activated" without a finger near those elements.
How do we screencap this as "proof"???
Where are you seeing this, and on what platforms?
@Black Pebble Locations as mentioned above for this release version (that are noticed). Platform is Android.
On previous build, I also saw dabo wheel activating without me entering dabo screen, and spins auto-starting. Oh, and yes, my screen is clean and wiped down.
Unfortunately, this is not an issue we've seen any reports of that I'm aware of. It's also not something we've been able to reproduce internally.
The best way to see if there is anything we can do to address is to submit a ticket (if you haven't done so) with as much detail as possible, and to also encourage others who are experiencing it to do the same.
I understand that's not the response you would like to see, but in order to diagnose the issue, we need to be able to reproduce the issue, and right now here doesn't seem to be enough to go on. Otherwise it's possible this is a circumstance that's specific to a set of circumstances unique to you.
As for your question on proof, if you are able to reproduce it, the best way to demonstrate it would be to record the video.
You giving me a reply and a "Nod" (pun intended ) on this issue is greatly appreciated, @Black Pebble ! As to you guys not seeing reports of this, I guess past CS members dismissed these tickets as "buyer's remorse" and either just reversed the charges or rejected these claims. I say this from personal experience, which you can cross reference from the tickets that I've submitted in the past.
These issues have happened to me, to other crew in my fleet, and to members of other fleets as well. They've also occurred on a range of devices that varies from Samsungs to Nexus phones and tablets. For me personally, they've happened on N5, N7-2013, and N6. I haven't seen it happen on my iOS devices yet but that's because I don't play on those devices as often as I can on my Androids. And if you remember, I still can't play on steam at all, even with the latest release.
Unless the loss is sizable, as in a loss involving hundreds of a farmable item or with dilithiums, most in my fleet don't bother with submitting a ticket anymore because we know CS staff are overloaded as it currently stands. We don't want to cause them unnecessary stress with mundane refarmable items, which lessens or eliminates any unintended stress or negative feelings emitted from either direction.
We're already starting to take screen caps every now and then, but honestly, the process of generating several dozen screenshots in a sitting really detracts from the gameplay experience. Especially with recent GUI changes that only show 2 rows in inventory and 3 (or was it 4?) for crew roster, well... You can guess how many screenshots that would take! The proverbial infinite number of monkeys on typewriters doth not create Shakespeare, but a frustrated, profanity-laden, Redshirt... (Oh gawd!!! Not more screenshots!!!)
As to video, well, let me dust off my GoPro and strap it on to my forehead first... I'll try that one out and let you know how it goes... <I'm joking!!!> But seriously, my devices don't have space left to vidcap gameplay because this game has already consumed +3Gb/device on them!!!
<*ahem*... sorry for the rant... I'm stepping away from the keyboard now...>
In the immortal words of Spock: "Live long and prosper"
you mean the automatic purchase of an item in faction store while clicking on another item? that was never fixed for me, I kept experiencing it even with previous version.
In this case, it was during the last event where items were clicked or "build" was activated. As well, sub-screens were entered and exited without clicking them.
Also, I'm trying to figure out how I lost 297 dilithiums. Exactly 297... this happened between a span of 3 hours with no notifications at all... and I'm afraid of talking to CS. They make me feel like we're all scammers.
297 dil should be the amount needed to instantly complete a 3hr shuttle.
Actually, it's 298. I just launched shuttles and that's what was displayed on the screen.
In the immortal words of Spock: "Live long and prosper"
I can say this is definitely happening all the time in faction store to me.
I don't know if it's PC thing or if it's just easier to notice with, well, mouse... half of the time game elements are half centimeter (well, on my monitor) lower than what is shown on screen. As in you press heart in the crew window and it don't light up then you move mouse down and it does.
You giving me a reply and a "Nod" (pun intended ) on this issue is greatly appreciated, @Black Pebble ! As to you guys not seeing reports of this, I guess past CS members dismissed these tickets as "buyer's remorse" and either just reversed the charges or rejected these claims. I say this from personal experience, which you can cross reference from the tickets that I've submitted in the past.
These issues have happened to me, to other crew in my fleet, and to members of other fleets as well. They've also occurred on a range of devices that varies from Samsungs to Nexus phones and tablets. For me personally, they've happened on N5, N7-2013, and N6. I haven't seen it happen on my iOS devices yet but that's because I don't play on those devices as often as I can on my Androids. And if you remember, I still can't play on steam at all, even with the latest release.
Unless the loss is sizable, as in a loss involving hundreds of a farmable item or with dilithiums, most in my fleet don't bother with submitting a ticket anymore because we know CS staff are overloaded as it currently stands. We don't want to cause them unnecessary stress with mundane refarmable items, which lessens or eliminates any unintended stress or negative feelings emitted from either direction.
<*ahem*... sorry for the rant... I'm stepping away from the keyboard now...>
The best way to ensure that appropriate attention is put on bugs is to submit detailed tickets. While the forums are an avenue for raising such issues, production tends to prioritize based on tickets, as well as the level of details in a ticket.
For example, sending tickets with a subject line of "The game is broken for me" without any platform information makes it difficult to properly triage and sort the ticket. Whereas including a succinct summary will make it easier for Player Support to appropriately escalate it to the right folks within the production team for investigation.
In a situation such as you're describing, where we're unable to reproduce it internally, we need both volume of tickets and clear information on the devices, OS and any reproduction steps. Particularly if you're on an Android device or a PC, as the possible configurations for those platforms can be complex. This will help the production team set their priorities accordingly, and more quickly resolve the bugs. And it'll help make the case that this is not an isolated situation unique to you.
Hosun Lee Civilian, Brand and Marketing Ex-Disruptor Beam
Just wish they wouldn t brake things that have not been broken before, OR do a proper testing!
But after 2 years of repeating promises to do better, i am just......
Regarding Steam: I couldn t agree more, this is a mobile game.
How many of the Timelines User play on steam regulary? My guess < 5% .
I pretty much only play on steam. The game works a lot better on steam, I don't get the ad offers, and it's just easier and faster to accomplish just about everything. The game also looks much better on a pc. I only play it on a phone if I am not around my computer and that is usually just a quick check in to deal with voyages and/or shuttles.
You giving me a reply and a "Nod" (pun intended ) on this issue is greatly appreciated, @Black Pebble ! As to you guys not seeing reports of this, I guess past CS members dismissed these tickets as "buyer's remorse" and either just reversed the charges or rejected these claims. I say this from personal experience, which you can cross reference from the tickets that I've submitted in the past.
These issues have happened to me, to other crew in my fleet, and to members of other fleets as well. They've also occurred on a range of devices that varies from Samsungs to Nexus phones and tablets. For me personally, they've happened on N5, N7-2013, and N6. I haven't seen it happen on my iOS devices yet but that's because I don't play on those devices as often as I can on my Androids. And if you remember, I still can't play on steam at all, even with the latest release.
Unless the loss is sizable, as in a loss involving hundreds of a farmable item or with dilithiums, most in my fleet don't bother with submitting a ticket anymore because we know CS staff are overloaded as it currently stands. We don't want to cause them unnecessary stress with mundane refarmable items, which lessens or eliminates any unintended stress or negative feelings emitted from either direction.
<*ahem*... sorry for the rant... I'm stepping away from the keyboard now...>
The best way to ensure that appropriate attention is put on bugs is to submit detailed tickets. While the forums are an avenue for raising such issues, production tends to prioritize based on tickets, as well as the level of details in a ticket.
For example, sending tickets with a subject line of "The game is broken for me" without any platform information makes it difficult to properly triage and sort the ticket. Whereas including a succinct summary will make it easier for Player Support to appropriately escalate it to the right folks within the production team for investigation.
In a situation such as you're describing, where we're unable to reproduce it internally, we need both volume of tickets and clear information on the devices, OS and any reproduction steps. Particularly if you're on an Android device or a PC, as the possible configurations for those platforms can be complex. This will help the production team set their priorities accordingly, and more quickly resolve the bugs. And it'll help make the case that this is not an isolated situation unique to you.
Does this mean if we encounter an issue and started a forum thread but don't hear or see anything about it we should submit a ticket as well? Is a ticket always the best way to bring attention to bugs we find?
Does this mean if we encounter an issue and started a forum thread but don't hear or see anything about it we should submit a ticket as well? Is a ticket always the best way to bring attention to bugs we find?
You should start a ticket as soon as you can, as we are unable to create a ticket on your behalf.
And yes, a ticket is the best way to bring attention to bugs. What happens when Community sees a thread about an issue is we will do our best to raise it to the production team, but they still need the additional information in a ticket in order to do any deep investigation. The number of tickets received on a bug are also a good way to gauge the severity of an issue, as it can be more difficult to do so by reviewing forum posts. A ticket also helps production track the issue from inception to resolution more effectively since it's in the system.
Hosun Lee Civilian, Brand and Marketing Ex-Disruptor Beam
@Black Pebble Auto-click seems to be back. GUI items are clicked or "activated" without a finger near those elements.
How do we screencap this as "proof"???
Where are you seeing this, and on what platforms?
@Black Pebble Locations as mentioned above for this release version (that are noticed). Platform is Android.
On previous build, I also saw dabo wheel activating without me entering dabo screen, and spins auto-starting. Oh, and yes, my screen is clean and wiped down.
Unfortunately, this is not an issue we've seen any reports of that I'm aware of. It's also not something we've been able to reproduce internally.
The best way to see if there is anything we can do to address is to submit a ticket (if you haven't done so) with as much detail as possible, and to also encourage others who are experiencing it to do the same.
I understand that's not the response you would like to see, but in order to diagnose the issue, we need to be able to reproduce the issue, and right now here doesn't seem to be enough to go on. Otherwise it's possible this is a circumstance that's specific to a set of circumstances unique to you.
As for your question on proof, if you are able to reproduce it, the best way to demonstrate it would be to record the video.
You giving me a reply and a "Nod" (pun intended ) on this issue is greatly appreciated, @Black Pebble ! As to you guys not seeing reports of this, I guess past CS members dismissed these tickets as "buyer's remorse" and either just reversed the charges or rejected these claims. I say this from personal experience, which you can cross reference from the tickets that I've submitted in the past.
These issues have happened to me, to other crew in my fleet, and to members of other fleets as well. They've also occurred on a range of devices that varies from Samsungs to Nexus phones and tablets. For me personally, they've happened on N5, N7-2013, and N6. I haven't seen it happen on my iOS devices yet but that's because I don't play on those devices as often as I can on my Androids. And if you remember, I still can't play on steam at all, even with the latest release.
Unless the loss is sizable, as in a loss involving hundreds of a farmable item or with dilithiums, most in my fleet don't bother with submitting a ticket anymore because we know CS staff are overloaded as it currently stands. We don't want to cause them unnecessary stress with mundane refarmable items, which lessens or eliminates any unintended stress or negative feelings emitted from either direction.
We're already starting to take screen caps every now and then, but honestly, the process of generating several dozen screenshots in a sitting really detracts from the gameplay experience. Especially with recent GUI changes that only show 2 rows in inventory and 3 (or was it 4?) for crew roster, well... You can guess how many screenshots that would take! The proverbial infinite number of monkeys on typewriters doth not create Shakespeare, but a frustrated, profanity-laden, Redshirt... (Oh gawd!!! Not more screenshots!!!)
As to video, well, let me dust off my GoPro and strap it on to my forehead first... I'll try that one out and let you know how it goes... <I'm joking!!!> But seriously, my devices don't have space left to vidcap gameplay because this game has already consumed +3Gb/device on them!!!
<*ahem*... sorry for the rant... I'm stepping away from the keyboard now...>
Not sure how to reconcile this with the advice cs is giving, anyway. First thing I'm instructed is have all other apps closed & double check none are running while playing timelines...
So even if you had the space on your device to vidcap gameplay, how will that happen with only timelines allowed to be running?
Having just had my last ticket resolved fairly, i am adding this comment that however necessary it was to send repeated clarification, cs did earn satisfied rating in the end.
I’ve run into this issue a couple of times on my iPhone X. The first time, I couldn’t close the window and accidentally bought the chronitons while trying to swipe up to close the app.
Luckily, Disruptor Beam’s support has been awesome and refunded me the dilithium, but I just encountered the issue again, so I wanted to post it here so that they have visual evidence of it.
Comments
You giving me a reply and a "Nod" (pun intended
These issues have happened to me, to other crew in my fleet, and to members of other fleets as well. They've also occurred on a range of devices that varies from Samsungs to Nexus phones and tablets. For me personally, they've happened on N5, N7-2013, and N6. I haven't seen it happen on my iOS devices yet but that's because I don't play on those devices as often as I can on my Androids. And if you remember, I still can't play on steam at all, even with the latest release.
Unless the loss is sizable, as in a loss involving hundreds of a farmable item or with dilithiums, most in my fleet don't bother with submitting a ticket anymore because we know CS staff are overloaded as it currently stands. We don't want to cause them unnecessary stress with mundane refarmable items, which lessens or eliminates any unintended stress or negative feelings emitted from either direction.
We're already starting to take screen caps every now and then, but honestly, the process of generating several dozen screenshots in a sitting really detracts from the gameplay experience. Especially with recent GUI changes that only show 2 rows in inventory and 3 (or was it 4?) for crew roster, well... You can guess how many screenshots that would take! The proverbial infinite number of monkeys on typewriters doth not create Shakespeare, but a frustrated, profanity-laden, Redshirt... (Oh gawd!!! Not more screenshots!!!)
As to video, well, let me dust off my GoPro and strap it on to my forehead first... I'll try that one out and let you know how it goes... <I'm joking!!!> But seriously, my devices don't have space left to vidcap gameplay because this game has already consumed +3Gb/device on them!!!
<*ahem*... sorry for the rant... I'm stepping away from the keyboard now...>
Actually, it's 298. I just launched shuttles and that's what was displayed on the screen.
If it's NOT PC-only thing, well...
The best way to ensure that appropriate attention is put on bugs is to submit detailed tickets. While the forums are an avenue for raising such issues, production tends to prioritize based on tickets, as well as the level of details in a ticket.
For example, sending tickets with a subject line of "The game is broken for me" without any platform information makes it difficult to properly triage and sort the ticket. Whereas including a succinct summary will make it easier for Player Support to appropriately escalate it to the right folks within the production team for investigation.
In a situation such as you're describing, where we're unable to reproduce it internally, we need both volume of tickets and clear information on the devices, OS and any reproduction steps. Particularly if you're on an Android device or a PC, as the possible configurations for those platforms can be complex. This will help the production team set their priorities accordingly, and more quickly resolve the bugs. And it'll help make the case that this is not an isolated situation unique to you.
Civilian, Brand and Marketing
Ex-Disruptor Beam
I pretty much only play on steam. The game works a lot better on steam, I don't get the ad offers, and it's just easier and faster to accomplish just about everything. The game also looks much better on a pc. I only play it on a phone if I am not around my computer and that is usually just a quick check in to deal with voyages and/or shuttles.
Does this mean if we encounter an issue and started a forum thread but don't hear or see anything about it we should submit a ticket as well? Is a ticket always the best way to bring attention to bugs we find?
You should start a ticket as soon as you can, as we are unable to create a ticket on your behalf.
And yes, a ticket is the best way to bring attention to bugs. What happens when Community sees a thread about an issue is we will do our best to raise it to the production team, but they still need the additional information in a ticket in order to do any deep investigation. The number of tickets received on a bug are also a good way to gauge the severity of an issue, as it can be more difficult to do so by reviewing forum posts. A ticket also helps production track the issue from inception to resolution more effectively since it's in the system.
Civilian, Brand and Marketing
Ex-Disruptor Beam
Not sure how to reconcile this with the advice cs is giving, anyway. First thing I'm instructed is have all other apps closed & double check none are running while playing timelines...
So even if you had the space on your device to vidcap gameplay, how will that happen with only timelines allowed to be running?
I’ve run into this issue a couple of times on my iPhone X. The first time, I couldn’t close the window and accidentally bought the chronitons while trying to swipe up to close the app.
Luckily, Disruptor Beam’s support has been awesome and refunded me the dilithium, but I just encountered the issue again, so I wanted to post it here so that they have visual evidence of it.