Hi. I developed a little prototype several months ago with flyable ships. They were not star wars ships, but models created by my own team for an unrelated indie project.
However, creating an entire game is way more work than focusing on remaking the flight engine of an existing game. We made some bad (at the moment) decisions, like using the Unity physics engine to model a more realistical space combat than the one in X-Wing.

The problem is that more realistic doesn't equal more fun, and also figuring doing something as simple as a homing concussion missile, or two ships docking while one is still moving, as seen in X-Wing, it's way more complex with a realistic physics engine where you need to account for linear and angular momentum and continuously correct the thrust applied in all directions. A headache.

That project is now on hold for other reasons (art assets responsible chickened out). So instead, for this one, I am moving to a simplified physics approach, just like the X-Wing series use and needs.

If you feel curious about what we had back then, this is one of the later builds of the flight engine. There is no story or anything. Just a few flightgroups, fighting in a team deathmatch.
The controls, during the development, were a mix of X-Wing's and Quake, so that someone could test the game by using their hands as they play a FPS.
W: Speed up throttle by 33%.
A: Rotate counterclockwise.
S: Slow down throttle by 33%.
D: Rotate clockwise.
ENTER: Attempt to match speed with target. It tries to keep it matched, unlike in XW series.
T: Select next target.
Y: Select previous target.
You move the ship with the mouse like in X-Wing and TIE Fighter DOS versions.

The game has several navigation aids that will not be used in this remake. You will identify them easily.
You will also identify some placeholder sounds taken from XvT.

In any case, I'm writing the flight engine for this XW project from scratch. It can already read the .XWI mission files so that I can test the engine with real life missions from the X-Wing installation folder or its CD. It has basic definitions for the different craft types, and programs all ships with their objectives, orders and other data.

It is not that I have been just planning. However I am approaching the development of the flight engine from a different direction than what I did with Ships On Fire. Instead of having something flyable as soon as possible, I am going for writing the code that takes care of simulating the mission and the AI of the different flight groups.

The reasons are two:
- Flying a ship requires the cockpit art and instrument panel definition work done. I don't want to program something to later scrap it with another thing, so I will program the player craft last.
- X-Wing missions are more than deathmatches. They have many events and triggers that rely on everyone following their choreography to the letter. I need to have the AI fly around in the same way as it does in X-Wing, otherwise the missions' balance will be broken.

So what I am doing currently is a mission flight engine where the player can only look around with a free camera and see how the different flightgroups carry out their designated orders.
It's basically the same as what you could see if you pressed Shift+M in XvT. You would go to the Map screen and your ship would be taken over by the AI. And you could see the battle going on without you.

I am using the XWAU models as placeholders. I repeat, they are placeholders until we find something else (or we get their permission to use them).
These are some screenshots: