Star Wars: Squadrons

Star Wars: Squadrons Dev Tracker




26 Nov

Comment

Originally posted by BlackBricklyBear

Thank you very much for your attention to this matter. Developer attention like this is why we are rooting for Motive!

Check my other reply in this thread. This was actually part of our recent change to how controllers are detected.

Comment

I believe this is due to our latest change that untethered controllers, namely Xbox controllers, from HOTAS devices. So, when you start up the game, the first button you press should be on the input you want to use. This is so you don't run into trouble if the Xbox controller falls asleep while you play.

Comment

Originally posted by BlackBricklyBear

It should still work. We need to get /u/EA_Charlemagne on the job here to find out why so many people are experiencing HOTAS problems when they worked just fine before.

We're tracking this issue and I think we have some tweaks coming in December to resolve it. Let me see if there's a current workaround.

Comment

Originally posted by Billkwando

Chatted with the team and they advise the following: You should use the Joystick Tweak to block all the inputs on the original Hori device since you’ve already remapped it to vJoy.

Additionally, we have some tweaks coming in TU4 next month that may help.

Comment

Originally posted by elppaenip

I kinda like it

I understood that reference.

Comment

Originally posted by Billkwando

/u/EA_Charlemagne If I move the stick slightly it reacts, but if I move it to the extremes it stops, unless I hold down Button 3 or 5. Yaw is similar. I can yaw right, but I can only yaw left if I hold down either those two buttons.

Edit: It's also taking inputs from both the flight stick and controller tabs. I had to unmap all the controller functions, because when I would hit boost, it would also route power to shields, because the game was picking up the button press as a thumbpad direction, because that's what it said it was under Controller.

I guess no more 19 kill matches for me, for the foreseeable future. Everything worked perfectly when I went to bed last night.

Interesting. Can you file a bug report on EA Answers HQ about this and then send me the link? The bug report template will ask you to fill in a lot of useful information for us.


25 Nov

Comment

Originally posted by skerpz

In the patch notes, it states that the Guided Burst Cannon has been nerfed from 35% of the Unguided damage to 28%. In game, it appears that what has actually happened is that the Unguided Burst Cannon has been buffed, and Guided damage has stayed the same, so, while Guided damage has gone down as a percentage of Unguided damage, the actual nominal damage of Guided has not changed, and Unguided has been buffed. Has anyone tested this? Was this intended? u/EA_Charlemagne ?

So, funny story. There was a bug (that we fixed) that made the stats displayed for those components bugged. The current stats are accurate and you should feel the difference when playing.

Comment

Originally posted by geevmo

u/EA_Charlemagne Where is the forward rendering option for VR users located? I can't find it.

It's built into the system now, so it's works automatically. Nothing you need to do!

Comment

Forward rendering is automatically used when your VR quality settings are set to Low. (It’s not a standalone option)

Comment

Originally posted by pharmacist10

Great, thanks for communicating so much with the community. It's really helping erase the "EA bad" memes :)

Praise Geraldo.

Comment

Originally posted by KillionJones

Thank you very much for the response!

Fixed!

Comment

Originally posted by KillionJones

Been able to connect to exactly 1 match since the update. Have had 3 seperate searches time out at 10 minutes of searching, with Error 1066 popping up, even after I reset my router n such. Any insight as to why? /u/EA_Charlemagne

This is an issue on our end, not yours. Stay tuned to EA Star Wars or EA Help on Twitter. We'll confirm shortly when it's been resolved.

Comment

Originally posted by InkCollection

Fair enough, but the DL was like 30 seconds and I was getting matches no problem prior to it. But yeah, I suppose people went to work in that time span.

Nah, it's something we're just finishing resolving now. Should be good soon!

Comment

Originally posted by ClarkFable

Nerfing the A wing with lower shields and not giving it access to most of the new equipment. As an Awing pilot, I begrudgingly applaud these changes. Something needed to be done.

This response did not go in the direction I expected.

The following bug fixes, changes, and additions come in Update 3.0. Bolded are some highlights we think the community will be most interested in. For full details on the new content added and what’s coming next, check out the Pilot Briefing on our Holiday Supply Drops.

General

  • Added Fostar Haven as a map to Dogfight and Fleet Battles (Solo/Co-Op vs AI and PvP)
  • Added next gen improvements
    • The game now supports up to 120FPS and up to 4K on Xbox Series X|S
      • Added an option for players on the Xbox Series X|S to priorit...
Read more External link →
Comment

Yes, if you’re referring to the black screen when you exit the hangar mid-mission, the issue is known and a fix is coming.


24 Nov

Comment

I distinctly remember on Battlefront II when we increased the level cap across the board to 1000 and said, "It'll take hours upon hours to max out levels now and it's nearly impossible to max them all," or something to that effect.

Not long (enough) later, I got a message from a player showing me a maxed out character. Some of you have a drive like no other.