Bugs: More things that keep me from embracing prime
I do not want to join the ranks of those blaming prime, BUT here is a collection of bugs/shortcomings that make it hard for me not switch back to redacted. Other agents confirmed these observations. Remark: I‘m using prime 2.30.2 mostly on Android, but sometimes also on iOS.
- If you have an open app of prime, close the cell phone, travel some distance and open prime again, the scanner sometimes just does not react. It is in zombie land: You can do gestures, but the server will not respond. It *even does not show nearby missions*. Restarting the app does not work. Cleaning the app from memory and restarting sometimes works. Restarting the phone and then the app usually works. I think the app waits for a signal from the sevre that is transmitted only every 10-15 minutes, because I think, waiting that long mostly works.
- If I fill a portal with 2xlv5, 4xlv4 and 2xlv3 and go to the next portal, the default resonator is again lv5. GOOD! If I fill the portal just with 1xlv7 or with 1xlv7, 1xlv6, at the next portal I get l6 as the default resonator. Annoying! I cannot just walk through 50 white portals and give them one lv7 resonator each, I have to reselect the lv7 reso every time.
- If I **** lv8 XMP and they are empty, the scanner chooses the lowest US next. ANNOYING! I think this only happens when lv7 XMP are also empty at that time.
- The colors in the scanner are just **** in plain daylight. I am 53, my eyesight is just ok. Answering red questions on black background for mission passwords is a PAIN. Do the developers of NIA sometimes play in daylight or do they leave the company only at night to try out the skin??
- I have a lot of keys. I open a caps to pack them. I select one key - so far, so good. Then I use the button on the left to fill all the (up to 100) keys into the caps. The numbers showing how many keys are packed (Total: 7 selected: 0) have NOTHING to do with the real numbers that you expect as an explanation for the selection. This is so simple - why is nobody fixing that. It is a bug from the very first version onwards.
- It is interesting to know how many MODS you have left. In REDACTED you just look at the mods count. in prime???
- For many purposes one wants to know the MU size of the fields you build. This was shown in the COMM in Redacted, you can see it on the COMM in the intel map - but not on the COMM in prime. Why??
- When the prime scanner app runs for 1 hour or so, portals start not to respond when you glyph them. You initiate gylphing, you hack in the commands (fast, more keys) - and then ... NOTHING HAPPENS. You just wait for the glyphs. Sometimes they come after 20 seconds, sometimes you have to restart the scanner to glyph again.
- When you play missions with "protals in order", the map shows the portals and the numbers, but does not link them with a line. Why? This is so useful to quickly understand the sequence of the portals. Instead you have to read the (tiny) font to decipher the numbers. AGAIN: This worked in REDACTED, it seems to be the same map subroutine, but apparently there is no distinction between "any order" and "in order".
Bottom line: I am ready to switch to prime. I play prime 70% of the time. But all this is annoying. It is the more annoying because all of this WORKS in REDACTED.
Comments, anyone?
Regards, Nasgorian
5
Comments
we can only hope most of those bugs will get fixed by the end of this month.
Yes, I sure hope those issues will be fixed before we are forced to switch to new app!
Item 1 for me is a deal breaker. Urgently needs fixing. Other items are annoying, but that one is critical. I should be able to play other games or read emails and not get speedlocked when I reopen the app. It should function like the original client did.
Also, I recently noticed that mission with hidden waypoints show all the waypoints in the list with Prime but they don't show on the map. Again, in the original client these were not visible at all.