Are you GPU or CPU limited now? The performance gains will depend on that . If you are running at those settings and are GPU limited, which I would expect as I have a similar card, then you are likely to see much in FPS gains. Maybe less stuttering, but time will tell.
Server load as all the console gamers come on to try it out… thats what I see as being the #1 issue 
4 Likes
I have two cheap MB’s as old as that with TPM 2.0 it’s been around since at least 2014. Have you checked your security settings in Bios? It is also possible that it goes by a different name, eg. TXE etc.
1 Like
Not much in the way of stutters even so like I said I am pretty happy as it stands right now. My expectations are based on decades of flight siming so I know just how good this is as it relates to past sims.
That’s also why I think the xbox launch is going to be a bit dicey for MS. There will be a flood of new “gamers” who will be of the mind set that 60 FPS is minimum for gaming and the photogrammetry among other graphics oddities are seen as bugs.
Maybe MS should force them to use FSX for a few days before they can use FS2020 and then they will understand for sure 
2 Likes
Don’t say that … lately I squeezed 300fps out of FSX (just for a laugh)
Most of the console crowd are very much used to 30 FPS 
2 Likes
That’s good to hear. I have never owned a console and listen to too much Linus tech tips. He says 60 FPS for gaming minimum but he probably doesn’t know his flight yoke from his egg yoke
1 Like
For buyers, DX-12 is the same as Ultimate. If it is not, they won’t call it “DX-12”.? save the buzzword ?
But there will be no road block. They can release a basic, common version using DX-12_1, that runs perfectly on XBox, all PC GPU’s and all flavours of Windows 10 including Sun Valley.
And I think it will still be the same code. There are no Ultimate features yet… The DX-12 Ultimate is only supported on 1080+ boards. So why initialize it on PC’s when it is not used ? Introducing raytracing and mesh shading would also need work on scenery and much more… to get ray tracing up to speed in a flight simulator will be witchcraft. Don’t expect it before 2023.
See also above answer to CaptLucky. There will be common source code, preferably a common executable. They must do that because of the server connections and cost of maintenance. They key: there are two DX-12 versions. The light version DX-12_1 does not require high end graphics (on entry they test DX-11 caps!) but it won’t be able to do some Ultimate stuff. So on XBox they will be able to initialize it, on PC they do DX-12_1. As long as Ultimate features are not used, MSFS need not initialize Ultimate.
And with XBox still not supporting VR, that’s probably ok?
30 fps is perfectly fine for VR. I know, I’ve used it for 10 years now…
It’s really not. You may be sending 30fps but something in the chain (like reprojection) must be adding frames to at least get to 60. 60 is about the bare minimum. 90 is much better, and 120 fps just rocks. Everything feels much more solid at higher frame rates.
If you really are running at 30, you might see what you can do to get more frames. 30 is just too low for good VR. I suspect you are at at least 60 though.
Look at a wing leading edge as you taxi. If you see it jumping forward and back against the tarmac, you are in reprojection.
1 Like
There’s no way it’ll be a common executable. As I said, the core code is surely based in the same code base, but surely not all the code is shared. Is there any reason to think the Xbox version will use any DX12 Ultimate features? Just because DX12U is supported on the new Xbox doesn’t mean MSFS will any time soon. If they did use those features, there would be a miss match between the DX11 PC version and the Xbox version in terms of features and probably look. Even after the PC version goes DX12, it won’t require DX12U because large portions of the video cards now used and are supported will never do DX12U.
Agreed, DX12 Ultimate will have no relevance to MSFS, at least on the PC, for a long time. Too much hardware on the MSFS compatibility list that will never support those features. But since any card that supports raytracing in silicon will support DX12U, it’s possible MSFS will, or at least will be able to, support DX12U when it supports raytracing. Not holding my breath. DX12 versions before Ultimate do support ray tracing, just Ultimate does so more efficiently.
1 Like
I don’t know if a binary copy of the executable would be possible, or even appropriate, but the graphics part has no issue… if you assume both platforms will make use of the DX-12_1 entry level.
We agree for a large part, you repeated my submit in other words. Difference is… I think MSFS DX-11 will end on 27/7. For both platforms, they will release the entry level DX-12_1, allowing for a (very large, near 100%) common code base… and the nice thing is: a lot of PC-users can keep using their system, because DX-12_1 requires only DX-11 capabilities… all current customers have these capabilities.
Before DX-12U, it was very difficult to shade complex scenery with raytracing, let alone animate it. It runs on high end 30xx boards, thanks to NVidia technology. And AMD has done development, especially for XBox. But it is definitely not fast enough yet, to show any relevant MSFS scenery. Another issue is, the scenery itself needs to be sorted in the eye direction and rendered multiple times when more than one light is active, when raytracing is used. To do that fast enough is very diffucult.
I understand DX12 Ultimate does give better performance, but ray tracing worked fine on my RTX 2070 for 6 months or something like that before DX12 Ultimate was released. But, it’s a reasonable expectation that when raytracing is added to MSFS, it will use DX12 Ultimate.
My previous old MB from 2012 Asus P8Z77-V was already TPM ready. I just checked with my new MB MSI MPG Z490 Gaming Edge Wifi as the Windows tools said previously I cannot run Win11. I found the bios setting, turned it ON and voila!
I’m Win 11 friendly 
My guess is your old MB supports TPM 1.2, not 2.0 as required by Win 11. I believe TPM 2.0 started appearing in hardware in late 2014 (TPM 2.0 was released in Oct 2014). TPM 1.2 was around as far back as 2009.
Microsoft has opened a gigantic can of confusion and anger with this draconian move.
ASUS and MSI have released lists of MBs that will support Win 11. Anything after 2014/2015 should be good to go. But my older PC and it’s 2012 era motherboard (Asus ROG Rampage Gene IV) will have to stay Win 10 and that has a end of updates date in 2025. It’s still a useful computer for most tasks. MSFS, wasn’t the best on that, but I did get by for quite a while on that old CPU/motherboard. I’d keep using that old PC another 10 years if I could, if just to keep my fancy new 3D machine uncluttered of anything that doesn’t need to be on it for MSFS and 3D content creation.
Friendly reminder, we are talking about 5+ year old motherboards that will age out on Windows10 in 2025, not getting 11 is nothing to boohoo.
FYI:
I had to update Bios for it to work despite having a rather new X570 pro carbon motherboard.