well, you can add a keyboard, mouse and cheap joystick and you have the same
All 3pd aircraft needs to be coded seperately for xbox so devs need to build two sets of code, one for pc and the other for xbox. In this case, I think the code is just too complex to make it for both versions.
Also curious about this.
What are they doing that prevents sombody from using a plane on Xbox?
I wasn’t aware MSFS would allow planes to be available only for one platform, I thought the whole Xbox idea was to have two different platforms to share the planes, scenery etc.
Now if add-on developers start to make “only for PC” planes the Xbox market would probably not be so interesting.
no its not. you get true 4k not checkerboard, you get +30fps to start with!
If you are adding a keyboard, mouse and cheap joystick to your Xbox to run MSFS you are probably totally fine with the default A320. I might be wrong about this.
On Xbox it’s 4k 30 fps or 1080 30fps depending of your model, not bad at all
Yeah, but why do you want the Fenix one and not stick with the default one. you want something complex, detailed, etc. Why would it be different for some console player
no one wants that. But its not always possible. I think he is right XBOX is not the same target as PC.
We might be surprised to see how many ‘simmers’ might just get the xbox too to sim in their, say living room on a 4k 65 inch tv. Considering the current chip shortage these days and the fact that the xbox price and specs are pretty good, it is quite an attractive proposition to have one as a backup unit.
Just my 2 cents.
Similarly to the Majestic Q400, they are running a lot of the aircraft systems, totally independent from the actual sim. Therefore because of the difference in architecture, the independent stuff won’t be compatible.
I think there’s a stigma among simmers to consoles, because we tend to think because of their history ‘Xbox’ and ‘PS5’ and for gamers and kids. When in fact both devices are literally the same as a PC hardware wise, (they have a cpu and gpu chip, ram ssd etc). The only difference is the operating system, windows. MSFS allows us to bridge the OS gap by allowing someone to use console devices for simming now.
Don’t take this for 100% but I believe the dev (Aamir) said the systems involved are too complicated to work on Xbox.
Well, there’s a hard guarantee that it won’t be happening on Xbox simply because the plane itself is “external” and that’s plain not possible on Xbox with it’s limitations and security model.
AFAIK they’ve even cut SimConnect out of it, so there’s not much to discuss.
Converting an “external” plane to a normal Xbox friendly one might be possible but definitely not with current WASM performance and limitations, it’s barely possible to do anything meaningful in there let alone run a complicated plane.
This is why they should stop with the pc security model and aloow .DLLs on PC.
You know I’ve always wondered about this, lots of failures and operable cbs are all fine and good as a selling point but seriously…who even uses these?
I’d expect a very small percentage of buyers actually set up failures and ever need to touch the cbs.
For most of us they might as well be static elements.
Good god… I cannot wait for this. I just flew the FBW 320 to see the latest stuff and it just suffered from flight plan nonsense on approach. I used a SimBrief plan file on the WorldMap screen and so when it loaded, it didn’t have an approach assigned, which is fine by me. But boy… When I actually began the approach, all of a sudden, all the lines on the flight plan changed. It was still following waypoints in the FMC, but they weren’t on the “green line” on the MFD. It was following some strange USR waypoints that showed up out of nowhere. When I selected the approach I was assigned by ATC, I was immediately greeted by some nonsense USR waypoints and just general insanity. I managed to land it safely, but the thought of an aircraft that doesn’t use the default MSFS flight planner or navigation is music to my ears. I actually thought if this flight goes well, I just MAY delete the FSLabs Airbuses for P3D. Fat chance of that happening until I have something that doesn’t fly weird plans that get drafted by a drunk DePaul student.
To be fair, the custom flight plan manager for the FBW 320 is coming very soon which should end those issues, using the WT code, which is flawless.
Yeah, I hope so. I am using the Development version right now and the sooner we have that working, the better…
If it can work the way the CJ-4 and CRJ does when I can just enter my own plan from cold and dark, that will be EVEN BETTER. Better yet, since WT is now working for Asobo, I can’t wait for them to fix this insanity in the core sim. It’s such a bummer. I felt like I wasn’t in control of what’s happening and I don’t like it. 
Same here, looking forward to both the Fenix and FBW stuff. I feel your pain, and still have nightmares with anything related to navigation in the sim, except the CJ4 
Or the pmdg dc6, switch to the radios only option and fly via radio nav beacons then at you destination fly a vor / ndb approach.
I usually plan my flight in littlenavmap and don’t even touch the msfs flight plan system.