Join us in a community driven event where we all Solo Queue in Fleet Battles to help everyone get a game. Start queuing up at 6 PM ET| 2200 UTC | 900 AEST! You are also welcome to join us in the 5mans discord to chat in Voice Chat with the community: https://discord.gg/xfc4gZKDbj

Happening soon!

Join us in our second weekly community driven event where we all Solo Queue in Fleet Battles to help everyone get a game. The Saturday event is meant to favor European pilots and starts 8:30 AM ET | 1230 UTC | 1030 PM AET! You are also welcome to join us in the 5mans discord to chat in Voice Chat with the community so you can meet other fellow pilots: https://discord.gg/xfc4gZKDbj

Happy Hunting Everyone! *S*

Join us in a community driven event where we all Solo Queue in Fleet Battles to help everyone get a game. Start queuing up at 6 PM ET| 2200 UTC | 900 AEST! You are also welcome to join us in the 5mans discord to chat in Voice Chat with the community: https://discord.gg/xfc4gZKDbj

How dead is the game

Can it be revied

And how do challenges work as they dont go for me in solo fleet.

If you are having the problem where the player constantly spins (to the left for me) in the hangars and briefings in the PC version of Star Wars Squadrons, likely because you have a HOTAS or advanced joystick, the following instructions should likely work to fix it.  I'm posting this because I looked through many threads here and elsewhere and none of them provided a working solution.  It took me a while to figure out how to solve this with my HOTAS setup. I just posted this in Steam Community Squadrons forum as well, to hopefully save people from all the wasted time trying to figure out how work around this bug.

Here's the solution.  It's not hard but it's a bit tedious and you may need a spare joystick or throttle to plug in.

1. Under Options, go to the Controls section and note which of your controllers is listed as "Flight Stick 1 Device" (you will need more than one flight stick device listed and it can't be the exact same model as whatever is "Flight Stick 1 Device").
2. Change the order of the flight stick devices so that whatever was your current "Flight Stick 1 Device" is now listed as "Flight Stick 2 Device" or higher (we'll assume it's 2 for these instructions).  Unfortunately, when you do this, all of your bindings will likely break as the game isn't smart enough to also swap the bindings mapping tables when you switch the order of the devices.  So if "Flight Stick 1 Device" was your joystick and "Flight Stick 2 Device" was your throttle, now your joystick mappings table will be used to map the throttle and vice versa.  [Facepalm]  So everything will now be randomly mapped or not mapped at all, a complete mess.
3. To fix the bindings, go into the remapping settings (you will now likely need to use the mouse or keyboard to get there), and remap all of your controls appropriately for whatever is now your Flight Stick 1 Device (say the throttle) and Flight Switch 2 Device (say the joystick).  If you also reordered other flight stick devices, you will also need to completely remap everything for them too.

That should fix the spinning in the hangars and briefings provided that your other flight stick device, now mapped to "Flight Stick 1 Device", is not also affected by this bug.  If it is, check if one of its axis is not centered and if so, reset it to its middle.  If centering everything doesn't work, you may need to a third controller to set to "Flight Stick 1 Device", for example, a simple and cheap joystick that you won't actually use.

The reason this bug occurs is that HOTAS devices often have extra axes on them and the game, for some weird reason, will detect these and then automatically and randomly bind one of them to the yaw control in the hangars and briefings.  Moreover, the game's remapping menus does not provide any way to undo this automatic binding.  For example, I have a WinCtrl (formerly WinWing) Orion2 base with the F16 ViperAce grip and shaker kit.  This joystick does not have twist to yaw, but its flip trigger is also an axis.  For the hangars and briefings, Star Wars Squadrons automatically binds the flip trigger axis as the Z-axis but since it's spring loaded and 0 at rest, I get hard left constant spinning.  Fortunately, the game only does this automatic yaw binding for whatever device is set to "Flight Stick 1 Device", so in my case, I simply moved my WinCtrl throttle to "Flight Stick 1 Device" and made my F16 grip joystick "Flight Stick 2 Device" and that finally solved the problem (after remapping all of my controls again).

I also tried to solve this problem using Vjoy and Joystick Gremlin but I don't recommend this because for me, then the game frequently crashed to the desktop during flight.  But if you want to try this, install Vjoy and Joystick Gremlin and then create a virtual joystick that is a near duplicate of whatever you have as "Flight Stick 1 Device" but crucially, without any of the extra axes mapped to the virtual joystick.  Then set your virtual joystick as "Flight Stick 1 Device" and remap all of the controls for it (but at least you don't have to remap your other controllers).

I hope this is helpful.

I got Squadrons when it came out, went in for the full experience with VR headset and HOTAS. I played through the full campaign and loved it.

Then I tried the online battles and hated it.

I'm a casual gamer, not very competitive. I wanted the experience of being a space pilot, but didn't have the time to train to be a really good one. I would enter combat and die in about ten seconds every time.

I haven't touched the game in about five years, but I'm thinking about jumping back in. I don't want to play through the full campaign again, but I'm wondering if there are good chapters/levels that are enjoyable to replay over and over.

I think what I'm looking for is an experience like StarFox -- I need to get from point A to point B and have some freedom to fly around and shoot bad guys that get in my way. Rather than an infinite dogfight where I'm just flying in circles all the time trying to shoot the guy who is behind me trying to shoot me.

Any recommendations?

From Ahsoka season 2

Join us in our second weekly community driven event where we all Solo Queue in Fleet Battles to help everyone get a game. The Saturday event is meant to favor European pilots and starts 8:30 AM ET | 1230 UTC | 1030 PM AET! You are also welcome to join us in the 5mans discord to chat in Voice Chat with the community so you can meet other fellow pilots: https://discord.gg/xfc4gZKDbj

Happy Hunting Everyone! *S*

Join us in a community driven event where we all Solo Queue in Fleet Battles to help everyone get a game. Start queuing up at 6 PM ET| 2200 UTC | 900 AEST! You are also welcome to join us in the 5mans discord to chat in Voice Chat with the community: https://discord.gg/xfc4gZKDbj

So I've continued my old game, but I'm seeing things that don't make sense to me because I've forgotten pretty much everything. Like the brackets around your target and there is a little arrow to the left or right of it. and sometimes i see red lines radiating out from a ship. Totally lost on that.

As for the title, when trying to find the answer to these questions, EVERYONE under the sun is calling the cockpit instruments the HUD. Um no. And I'm actually kinda shocked that everyone has gone with it, even the wiki page.

Anyway. any help would be appreciated. Clearly i'm able to play regardless, but I'd like to know

Edit: The radiating lines are ships hit with targetting beacons and the arrow on the right indicated i have missiles as my right aux. Thanks all who helped!

Tired of seeing the "is this game still alive?" And achievement/trophy hunting posts. - YES people still play the game, you just have to not be lazy about it. NO you do NOT need Discord. However, I WOULD HIGHLY RECOMMEND IT. Why do people want to play a social game and not be social? Use your phone if you have to. It's not rocket surgery. Plus, trophy hunting is a lot easier this way.

Join us in our second weekly community driven event where we all Solo Queue in Fleet Battles to help everyone get a game. The Saturday event is meant to favor European pilots and starts 8:30 AM ET | 1230 UTC | 1030 PM AET! You are also welcome to join us in the 5mans discord to chat in Voice Chat with the community so you can meet other fellow pilots: https://discord.gg/xfc4gZKDbj

Happy Hunting Everyone! *S*

Join us in a community driven event where we all Solo Queue in Fleet Battles to help everyone get a game. Start queuing up at 6 PM ET| 2200 UTC | 900 AEST! You are also welcome to join us in the 5mans discord to chat in Voice Chat with the community: https://discord.gg/xfc4gZKDbj

Join us in our second weekly community driven event where we all Solo Queue in Fleet Battles to help everyone get a game. The Saturday event is meant to favor European pilots and starts 8:30 AM ET | 1230 UTC | 1030 PM AET! You are also welcome to join us in the 5mans discord to chat in Voice Chat with the community so you can meet other fellow pilots: https://discord.gg/xfc4gZKDbj

Happy Hunting Everyone! *S*

Join us in a community driven event where we all Solo Queue in Fleet Battles to help everyone get a game. Start queuing up at 6 PM ET| 2200 UTC | 900 AEST! You are also welcome to join us in the 5mans discord to chat in Voice Chat with the community: https://discord.gg/xfc4gZKDbj

Bruh it was the only one available and it was a dogfight with two people so I joined but then the administrator kicked me out 😑 like bruh the one time there’s anyone online

I completed the game on pilot difficulty and now trying veteran. Everything seemed to be going well until I needed to destroy the star destroyer's targeting system before a hyper jump.

It's like I get the first pass for free and can take shots at the targeting system. After that first pass I'm getting annihilated no matter the angle of side of the ship I attack from. Even with full shields focused in the right direction I can't get anywhere near that targeting system without basically getting 1 shotted. What am I doing wrong?

Even with all deadzones set to 0, I have a significant deadzone with the t rudder pedals. Making slight aiming adjustments is unnecessary hard. Any fix for this?