I don't have a file called "client_settings_ini" or "settings.ini" in my AppData SWTOR folder.

But where's the part about the dozens of posts on the forums of players unable to login since 7.4.1? The post you made earlier (i.e. "Check that your antivirus didn't suddenly start hating SWTOR; delete [folder most of you already tried deleting]; or make sure your PC didn't downgrade itself when 7.4.1 dropped") didn't help - many of us can't actually play, making what you're fixing essentially irrelevant.

I also have this issue Once I launch the game (not steam version, direct) I get stuck on the loading screen

Thanks for the info, but I have some further concerns. Why did you remove the Very Low Shaders setting? It was a lifeline for those using lower-end machines, and in busy environments. Personally, I really don't care to spend several minutes loading into every location I travel to (fleet, planets, flashpoints etc), and I'm effectively locked of operations entirely since they push my frame"rate" to the low single digits. Besides, some players actually prefer the way things look that way, since the lighting for higher settings makes everything look like plastic (same reflectivity etc. regardless of an object being a creature, metallic, wooden etc.). Moreover, Balameb (above me) has a good point. The game seems still to be poorly optimized, even after all the technical improvements added since launch. I often have to wait several seconds for things like dialog boxes (character menu, crafting menu, legacy window, GSF hangar etc.) to load, or for things like detailed character stats (accuracy rating, armor rating etc.) to appear in the character menu, despite my machine meeting the requirements listed above. It's frustrating and needlessly time-consuming - not to mention new-player-unfriendly. Finally, I wanted to ask about the whole 64-bit thing. Since my machine is 64-bit, SWTOR was placed into "Program Files (x86)" when I first installed it, so should it now be in "Program Files"? Would that do anything?

I also lament the removal of this setting. Why does BW like removing things for no reason? They've done it with many items, quests, schematics etc., but an in-game setting has got to be a new one. Even if we set aside low-end machines and poor eyesight (some of the reasons that others in this thread dislike this change), what if I want to save computing power in a high-intensity environment, such as an Operation? Unfortunately, I don't anticipate that this will be fixed before July, and what a slog it'll be until then...

I've also been getting disconnects, so often that I regularly get DC'd before character login completes, or if I do log in, it only lasts a few minutes. This is regardless of server or planet.

Over a year and it still hasn't been fixed. This is quite frankly disgusting. Reminds me of how long it took for the "bugged post-Arkis mobs on TFE" glitch to get fixed: years and years and years... Btw, do you guys remember when they claimed that they fixed the Face Merchants mob respawn times? I do. Yeah, nice "fix" BW.

To be clear, the Force Charge/Leap bug mentioned in the original post is present regardless of whether or not Warmonger is being used. Moreover, what about the other leap abilities (i.e. for Vang/PT, scoun/op, and shad/sin)? Many times I'll activate the ability but not actually be taken to the target for another 1 to 20+ seconds (cooldown and relevant ability procs will still occur). Sometimes I won't actually leap to the target until after it has already been killed.

Nice that you're finally fixing the Possessed Hunter respawn timer, but what about The Face Merchants (Coruscant [you tried fixing this in 5.5 but it didn't work]), Mutations (Taris - Republic), Down the Hole (Tatooine - Republic [Rhigoth only])?

What if you did the Odessen conversation but they're not listed in the companions window? Non-JK btw

Did Onslaught on my Saboteur Warrior. Did the Odessen conversation. Did not receive them as companions. (Not on the comps list.) Entered the Force Enclave. Was attacked by K&S. Couldn't see/target them, therefore couldn't kill them; had to rely on having Theron with me at the time to kill them. Have submitted ticket. No response received so far. What gives, Bioware? Why are your patches invariably incomplete?

How did you guys kill Vowrawn? I was concerned about getting mail from Shaar even though she died in my playthrough.

On Mek-Sha I , but later I . I had already completed the Onslaught story by the time I noticed so I'm worried about whether it's still rectifiable.

No need to rush, we won't unsubscribe if you take 2 minutes too long to get this thread up

By the way, here's a workaround for the "companions won't attack enemies/heal allies not already in range/LoS" thing: Just tell them to use a specific ability (e.g. target self and use companion's burst heal, target enemy and use companion's stun). That will make them close the gap. Also, for anyone wondering why Shae's DPS is so good, look at the first bullet point in the wall of text I posted above.

Doorways are weird like that. It's linked to the fact that that doorway can be locked or unlocked (i.e. depending on whether you do the bonus) - most doorways are fine. Note that AoEs centred on one side also won't hit enemies on the other. While we wait for this to be fixed, a workaround would be to dismiss the companion, cross the doorway, then resummon (though I acknowledge that that's not always possible).

While we're on the subject: Companion AoE abilities are bugged; they deal the full damage per tick. This means that Shae is the strongest companion by far, since her AoE has 6 ticks, compared to 2 for most other companions, and 1 for the rest. That said, most AoEs feel like they do about the right amount of damage, so to fix this, I'd suggest buffing companion AoE DPS abilities by 100%-150% (or alternatively, just halve the cooldown), but then, actually make sure that that's the total damage dealt. Why are Tech-using companions' stuns 5 seconds long but Force-using companions' stuns are 4 seconds long? All companion stuns should be 4 seconds long. Why are some melee companions' executes cast but others are instant? I understand having the ranged executes be cast, but why melee? All melee executes should be instant. Why do healers act as though they're trying to attack before healing? It's especially bad with melee companions. If I'm trying to LoS a mob, and I take my companion off passive, instead of healing me they'll run up to the enemies as if they're going to attack them, then start healing. This makes no sense. Healers should pretty much ignore enemies outright, except for the situation described below. Could you please improve companions' AI so that they immediately leave enemy AoEs? I know that such programming wouldn't be new (at least not entirely) because there are enemy NPCs that leave player AoEs - one example is the mob in the Republic Taris Heroic "Fall of the Locust" encountered immediately after releasing and speaking to the prisoners. Soloing certain Master Mode Fallen Empire chapters is also virtually impossible (looking at you, GenoHaradan) because you have to fight your companion's stupidity in addition to the actual boss. Speaking of AI, I'd like to request the following modes, in addition to the current "attack the target" and "ignore enemies" modes: Follow the player, but still use abilities (except leaps, and abilities that can't be used while moving) (On that note, the channelled healing ability and ranged execute should be usable while moving) Move to, and remain at, the targeted location (or at least the player's exact current location, i.e. not 1m away like usual). Abilities should still be used unless they would require movement from the designated location. [*] Why does HK-51 not have an AoE ability, or an ability that Sunders the target? Because of this, HK-51 has gone from being the strongest to the weakest DPS companion. (Note that I have tested his DPS while my character applied Sundered to the target, and in that case his DPS was equal to the others'.) I'd say have his channelled ability do AoE damage centred on the primary target and Sunder the primary target. I think that's all that would be required. [*] Why is Shae's AoE marker so much smaller than the actual ability? Please fix this. [*] Please give each companion back 1 unique ability that can be used regardless of role. Many of us miss those abilities and, though I admit that balancing them so that each companion's overall effectiveness is equal won't be easy, it doesn't seem like it'd be impossible either - certainly not harder than balancing 24 disciplines in both PvP and PvE scenarios. Please consider the points above. Cheers!

More lore-building articles would definitely be appreciated! May I just say, if it's not already finalised (I don't know how it is on PTS), can you not lock the Dantooine dailies behind story content? Or otherwise, at least make a future daily area that isn't? So far, the unlocked ones are The Black Hole Section X CZ-198 Rishi (kind of, but they're really spread out) and the locked ones are Makeb Oricon Yavin Ziost Iokath Ossus Granted, most of these are understandable because they're part of the main plot, but I'd like to do a variety of daily planets without locking myself out of story, or playing through it on the hundredth toon for another 20+ hours. You could make it a small, quick one (like CZ-198) on Manaan, about grabbing a bunch of kolto, which is a plausible scenario regardless of the character's progress in the story. It would also give you an excuse to open up that dead end on the Manaan map AND make it a place to go other than to do 1 story mission (seriously, Quesh is more of a planet than Manaan is).

That would be amazing, but while we're on that subject, how come we can buy extra copies of decorations for our guild, but not for ourselves? To clarify, if a guilded character selects a decoration they own in the Decoration Window, there's an option to purchase a copy of it for that character's Guild Stronghold/Flagship for credits. However, there's no option to do the same for that character's personal Stronghold. Any chance that could be changed? I'd greatly appreciate it (as would many other people, I'd imagine). Cheers! P.S. If you do decide to create a Dantooine SH, could you please ensure - and I mean this with the utmost respect - that the hooks are aligned properly? Manaan is a nightmare

What this person said. Maybe make it a daily area (expanding the map beyond that one door in the existing map that is closed and has a sign explaining why, near the Manaan Flashpoint vendor), with the theme being that you need to procure kolto for the faction you sided with. Also, make the dailies really quick to do. We already have enough large daily areas (Yavin, Iokath, Ossus); we need another CZ-198.

Jaesa, Khem Val, Nadia, and Doc can now be acquired from the Companion Locator Terminal. But what about everyone else? When any of my characters use the CLT, I enter the cutscene but no text comes up so I can't retrieve any of my companions. Yes, I have already submitted a bug report about it (and a few months ago at that, I think).

A few questions: Can you add the Masterwork vendors to the fleet and make the masterwork crystals legacybound? What if we want to gear up toons for whom we don't have time to play through all the story content or are unwilling to skip it just to get to Ossus? We could always gear up without having to play through story content before; why should this change now? Will this fix the first Imperial Ossus story mission not granting after the introductory cutscene, thereby preventing advancing the mission? A few of my guildmates have been getting that bug and it's frustrating not being able to get reputation, crystals etc. right now.

How will you combat match throwers? What about people who deliberately get into combat and /stuck instantly over and over?

Wait what? What was going on there?

Thought I could run it with 4GB RAM. I was wrong. I'll get more RAM installed ASAP, but is there anything else I can do to make the game go easy on my machine in the meantime? Yes, I am running with all graphics settings at their lowest.