Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Broken in patch 1.7.1

First BioWare Post First BioWare Post

Eldrenath's Avatar


Eldrenath
03.07.2013 , 12:24 PM | #11
Quote: Originally Posted by AmberGreen View Post
We've been investigating the reports in this thread about partial searches not working. Can you please let us know if this is still happening for you after patch 1.7.2? If so, can you please confirm your examples and tell us what server you're on? Thanks bunches for your help while look into it.

Amber, the fact that you are responding and interacting as regards these issues speaks volumes. The little bugs are annoying, but the fact that someone official from BW is addressing the concerns and responding to player queries is very, very much appreciated.

BobaScott's Avatar


BobaScott
03.07.2013 , 02:00 PM | #12
Quote: Originally Posted by AmberGreen View Post
We've been investigating the reports in this thread about partial searches not working. Can you please let us know if this is still happening for you after patch 1.7.2? If so, can you please confirm your examples and tell us what server you're on? Thanks bunches for your help while look into it.

On shadowlands - search "nerve". You will get two earpieces (as of now).

Now search "nerve-". You get 2 pages of Nerve-Damaging Chemical.

Glower's Avatar


Glower
03.07.2013 , 03:17 PM | #13
Quote: Originally Posted by BobaScott View Post
On shadowlands - search "nerve". You will get two earpieces (as of now).

Now search "nerve-". You get 2 pages of Nerve-Damaging Chemical.
This condition also is not constant... Everything is too random.
SWTOR goes F2P: http://i.imgur.com/1962X.jpg
A: "They’d love to do that at some point, but technically very challenging and unlikely to happen in the near future." (c)
PvP FAQ, A: "We have no plans at this time" (c)

BobaScott's Avatar


BobaScott
03.07.2013 , 04:07 PM | #14
Quote: Originally Posted by Glower View Post
This condition also is not constant... Everything is too random.
Really? I must have run each search 15 times each, while also mixing in other random ones to see if I could mix it up. I got the same results each time I searched no matter what. The "-" seem to consistently trip it up.

Glower's Avatar


Glower
03.07.2013 , 05:28 PM | #15
Quote: Originally Posted by BobaScott View Post
Really? I must have run each search 15 times each, while also mixing in other random ones to see if I could mix it up. I got the same results each time I searched no matter what. The "-" seem to consistently trip it up.
Umm... i mean this may change in next few hours or days, not seconds!
SWTOR goes F2P: http://i.imgur.com/1962X.jpg
A: "They’d love to do that at some point, but technically very challenging and unlikely to happen in the near future." (c)
PvP FAQ, A: "We have no plans at this time" (c)

Lusche's Avatar


Lusche
03.08.2013 , 07:59 AM | #16
Searching for "skip tracer" only leads to "Title: The Skip Tracer", while searching for "skip tracer`" leads to "Skip Tracer`s Cartel Pack" and searching "skip trace" leads to both.

Seems like a problem occurs if a special character (like ` or -) is the next character in the item name after the part you search for.

BobaScott's Avatar


BobaScott
03.08.2013 , 08:49 AM | #17
Quote: Originally Posted by Glower View Post
Umm... i mean this may change in next few hours or days, not seconds!
Lol, ok. I was just testing it he way I test my own SQL searches. You run some normal, best case searches, add in some crazy, see if you can break it.

AmberGreen's Avatar


AmberGreen
03.08.2013 , 01:46 PM | #18 This is the last staff post in this thread.  
Thanks for the examples and continued feedback. We appreciate it and are keeping an eye on this thread and this issue.
Amber Green | Live Services Specialist
Follow us on Twitter @SWTOR | Like us on Facebook
[Contact Us] [Rules of Conduct] [F.A.Q.] [Dev Tracker]

Magnusheart's Avatar


Magnusheart
03.08.2013 , 01:56 PM | #19
quite a few more bugs amber.

Revan's set has long been broken.

image of revans chest plate in 1.6.0
http://oi48.tinypic.com/dovzi9.jpg
image of revans chest plate in 1.6.1
http://oi50.tinypic.com/2rekxhu.jpg

same bodytype and classs in the pictures, you can see how light grey the set became changed and its ugly. especially in bright lit areas.

set also has two hoods. which is not the case for revan as seen in all convorsation segments of the foundry.
http://oi50.tinypic.com/14b84gk.jpg
and in the foundry 1.6.1 same as the time this ss above was taken
http://oi48.tinypic.com/1z2n51j.jpg

Pathfinder's AND the Investigator's Robe also suffer from a 2 hood conundrum. while the devistator's also from the CC pack has a wrong icon claiming it has the hood up, now down. not a big issue, but I was set back a few CC coins discovering this the hard way.

Revan's robe leg peice when graphically fixed in 1.6.2 to be the right design, is the wrong color.
http://oi47.tinypic.com/sqmmx3.jpg
When they should be as seen in the previous picture.

and lastly, you guys never did add a "Classic" Version of the Chest and Robes. where it would of been the maelstrom version of revan's chest plate and the old version of the robes you had us use in 1.6.0


The gray helix sabers loose their gree graphic if used with a weapon dissapearing from hand like attack, i.e. saber throw, dispatch, etc. the blade then becomes a shorter normal blade like all the others.

the removed cartel relics Revans Cowl, Bastila's Sash, And the gauntlet of Tulak Hord I hope get returned.

in the 2.0 PTS you finally fix kalig's countenance to work with hoods again after a YEAR. I truly hope this wont be the case with this.

Doriru's Avatar


Doriru
03.08.2013 , 09:05 PM | #20
Just to clarify this: http://www.swtor.com/community/showthread.php?t=607614

In short, you now can't hear a companions casual talks (i.e. when you come to a new planet) when you are running or not facing him. I've actually thought it was a problem on my side, but it seems like it's not just me (people responded in the thread above that they have had similar problems). Started after 1.7.1 obviously.