Star Wars: The Old Republic Dev Tracker

5 minutes ago, Nee-Elder said:

i saw a few other players mentioning  the same thing  in Fleet genchat , about missing Legacy bank slots and "empty"  Collections tab, etc.

( i was too paranoid to look at my own character's stuff  , so i just logged offline immediately  hoping server database had already saved )

@JackieKo ,  i'll obviously double-check my own character when i log back in later but quick question:  Could all these recent  STAR FORGE downtimes be related to the migration to 64-bit ?  And if not,  any chance you or ...

Players should be able to log back into Star Forge now. 

Just now, Gilrenna said:

I was playing when the message came up in chat. Just before that, my character was downgraded, too, and I lost all the inventory slots I had bought like 5 years ago. lol

When you log back in, can you please confirm that your account goes back to normal? 

Just now, Amorianallund said:

It's been down for over half an hour, and you say "were taking it down in 10 minutes" ??

The sheer incompetence.....

Players not being able to log in is different than the server being down. Some players were still on the server hence the messaging of taking down the server. 

Hi again, 

We will be taking down Star Forge in about 10 minutes. It'll be a quick bounce so players will be able to log in almost immediately after. 

Hi everyone, 

We're aware of the issue and investigating. I'll post the forum banners with an update when I get info from the team. 

Thanks! 

Hi there, 

PTS is not currently open. We brought down the server on Friday. Feel free to follow 7.2.1 updates from this thread. Thanks! 

On 2/11/2023 at 8:54 AM, SilentMagician said:

Note that your other thread specifically directed people to come here to give feedback. So if you're going around deleting feedback that you directed to come here, you need to be clear in your original instructions.

That's fair. I updated the language in the general thread. I'm also repeating for the fourth time here in this thread that PTS feedback be left here and general discussion be kept to the general thread. I am leaving your comment here because you made a fair point in communication flow. 

Adding a note here for players who need a boost to level 80 on the PTS. There is a level boost terminal on Odessen if you need it. Once you land on Odessen, turn around, and the terminal should be close by! 

11 hours ago, Cindron said:

I am confused.  Will you only get the mount if you participate while the devs are on at 1:30 ct Thursday?  Or as long as you hit a warzone before they shut down on Friday?

 

The criteria is: 

• Log onto PTS
• Complete a Warzone

Playing a match with the team is not required at all. We're just hopping into the queues to see how everything is working live, and to also encourage pops for everyone participating.

Hi everyone, 

We're setting up another play test with the devs for tomorrow, February 16th at 1:30pm CT to further test the Alderaan PvP Map. Please note the following: 

• This phase of PTS will be closing on Friday, February 17th at 5:00pm CT
• As a heads up, the Opal Vulptilla mount can only be earned during this phase of PTS, so you will no longer have the opportunity to earn the reward after the Friday deadline. 

See you all during tomorrow's play test!

On 2/10/2023 at 10:53 PM, Stalha said:

I had the same issue, but I was able to fix it by turning compatibility mode off for both executables as suggested by a few other posts in the Testing 64 bit thread. Go to the SWTOR directory (for me that was Windows (C:)/Program Files (x86)/Electronic Arts/BioWare/Star Wars - The Old Republic), right click on launcher.exe, select Properties, go to the Compatibility tab, and make sure the compatibility mode box is unchecked. Do the same check for the PTS launcher, which is at Star Wars - The Old Republic/publictest/retailclient/swtor.exe. Once my two launchers had the same compatibility settings, the PTS showed up in my server select screen.

Hi there, 

Glad that this is working for you. We had a follow question to this workaround. Was there ever a point in the past where you manually updated compatibility mode? Possibly for other workaroun...