Jump to content

ChadCloman

Members
  • Posts

    94
  • Joined

Reputation

15 Good

Personal Information

  • Location
    Colorado
  1. More information regarding Hoth and this quicktravel bug. The first image, hoth1.png, shows Whiterock Wastes completely explored in the area map, but with a large (and incorrect) unexplored area displayed in the world map. Only one of the three Whiterock Wastes quicktravel points is visible on the world map. The second image, hoth2.png, shows the entire map of Hoth explored except for one small area in Clabburn Tundra. The (incorrect) unexplored area in Whiterock Wastes is still displayed in the world map. Two of the three Whiterock Wastes quicktravel points are now visible on the world map. Not sure when the second one appeared. The third image, hoth3.png, shows the world map after all of Hoth has been explored. The (incorrect) unexplored area in Whiterock Wastes is no longer displayed, and we can finally see all three quicktravel points for the area.
  2. I originally reported this bug on Voss. What it appears to be, after investigating the similar issues on Hoth, is that if there is a non-explored area on the World map that is close to a quick travel point, especially a quick travel point inside a building, then that will cause the quick travel point to not appear on the World map. The area map works fine and correctly displays the quick travel points For Voss, the non-explored area is the temple in Voss-ka, and the quick travel point is inside the cantina. Once I explored the temple area, the quick travel point showed on the World map. It’s not necessary to explore the entire area (as I originally reported); rather, it’s just an unexplored temple area that’s causing the quick travel point to not appear on the World map. In the case of Hoth, there is an old bug in the world map that marks part of the Republic intro area as undiscovered, even though it’s been fully explored. I remember dealing with this a very long time ago when I first did Hoth, driving myself crazy trying to find the unexplored area in a map that had been fully explored. I believe it may have been this way since launch. When combined with the bug added by this latest update, this means that two of the three quick travel points in that area are not visible on the world map and you have to use the area map instead. The false “unexplored” area only disappears once you have explored the entire world of Hoth, and then you can see the missing quick travel points on the World map
  3. I originally reported this bug on Voss. What it appears to be, after investigating the similar issues on Hoth, is that if there is a non-explored area on the World map that is close to a quick travel point, especially a quick travel point inside a building, then that will cause the quick travel point to not appear on the World map. The area map works fine and correctly displays the quick travel points For Voss, the non-explored area is the temple in Voss-ka, and the quick travel point is inside the cantina. Once I explored the temple area, the quick travel point showed on the World map. In the case of Hoth, there is a bug in the world map that marks part of the Republic intro area as undiscovered, even though it’s been fully explored. I remember dealing with this a very long time ago and believe it may have been this way since launch. When combined with the bug added by this latest update, this means that two of the three quick travel points in that area are not visible on the world map and you have to use the area map instead. The false “unexplored” area only disappears once you have explored the entire world of Hoth, and then you can see the missing quick travel points on the World map
  4. It's still a bug. The QT point was unlocked and the map area it existed in had been explored. I simply provided a workaround. I've noticed this in other areas across the galaxy as well, although I forget which ones.
  5. I found the problem causing this bug. Once I fully explored Voss-Ka, the qt icon appeared.
  6. I have additional information. Please note: this bug is inconsistent in that it changes between characters. Not sure what the criteria is, but here's another screen shot from a different character, showing the qt point correctly displayed in the world map. The first player, with the bug, was power-leveled and hasn't made it to Voss in the story. Both were imperial characters, both lightning Sorc.
  7. [EDIT: This happens when the area map isn't completely explored. See my posts, below.] The quick travel icon for the Voss Cantina doesn't appear on the world map, but it does show in the Voss-Ka area map. See attached screen prints.
  8. This has happened to me twice in the last few days. Can't kick a disconnected player. Everything looks fine, but nothing happens. Everyone tried to initiate the vote kick.
  9. [Resurrecting old thread because I had this problem and the solution here didn't work.] I have an update to this. There was absolutely nothing clickable, not even the non-blue part directly above the blue part at the bottom. I dismissed Kaliyo, exited the instance, teleported to fleet, returned to Zakuul, quick-traveled to Breaktown, summoned Kaliyo, re-entered the instance, and voila! the non-blue part directly above the very bottom was now clickable.
  10. [I know this is an older thread, but I was searching for the answer and this is what I had to use] As of July 2023 the Dual Monitor Tools utility doesn't work for SWTOR in Windows 11 build 22H2 using Fullscreen (Windowed) mode. It works okay outside of SWTOR, but the mouse moves freely between monitors when SWTOR is the primary window. Fortunately the Cursor Lock program works correctly with SWTOR, despite being a 10-year old program.
  11. [Necro because I'm seeing this issue and have additional input and this is the only discussion I found about it.] I was blown away when I first encountered the higher (100% gray) crit rate, and then seriously disappointed when it would vanish. Here are some things that haven't already been mentioned: Most times, but not always, I have the 100% gray crit rate immediately after logging in with a character in a stronghold. I haven't tested it for logging in outside a stronghold. If I switch areas, I return to the normal crit rate and stay there. The only way I've found to restore the high crit rate is to log out and back in. This doesn't always work. When I want the higher crit rate, I log in to the character, verify the correct rate is in effect, and do all my crafting without changing areas or logging out. This is the only reliable method I've found. Starting the crafts and logging out until they're complete can be a bit hit-or-miss. In addition: If the crit rate displayed in the crafting window reads 79% or higher, I get a guaranteed 100% gray crit rate. The Professional Training buff doesn't affect the displayed crit rate, but if missing it will drop the "79%" gray crit rate slightly below 100%. When the displayed crit rate is 77% or lower (for lack of guild perks or because it dropped from a higher value) I get the normal crit rate. The higher crit rate seems to affect non-gray crafts, but not nearly as much as for the gray crafts. The effect diminishes significantly for orange crafts. Obviously this is a bug, but I still find it weird that a 2% drop in the displayed crit rate translates into a 25% to 35% drop in the effective gray crit rate.
  12. Allow people to instantly remove the cooldown on guild/flagship summons by paying credits. Make it something non-trivial, like 1 million credits, and it will become a credit sink to help reduce inflation. I know that a lot of people would gladly use it, even for that much.
  13. [Necro because: I found this when Googling the topic, and it no longer works.] This settings file appears to only store the comments on your friends list, not the actual friends. If you have a comment for someone that's not a friend, it doesn't add that character as a friend. I added a friend from a different file and saved it. Logged in. The added character didn't appear. I deleted the file outright and logged in. Still had all my friends, but no comments. The friends list is obviously stored somewhere else, possibly even on the game server.
  14. From the patch notes: Can anyone give me the specific numbers on this? I'd like to know for planning purposes with my weekly raid group.
  15. #facepalm Another update courtesy of BioWare "we don't test our fixes" Austin. #really? Do you guys have any QA staff left on this game? #LetsCutQASinceTheyDontMatter
×
×
  • Create New...