No, it doesn't cause problems, because FSX calls DX9 runtimes and you need to have DX9 installed, which is the DX version FSX uses. For DX10 many things changed from DX9 and in many cases you still need DX9 runtimes to run DX9 software, so there is just partly backwards compatibility with DX10 and 11 to DX9. DX11 versions are however able to run DX10 software, if you are using DX10 preview in FSX.
Beware of Windows 8.1 Preview
- Thread starter dhazelgrove
- Start date
dhazelgrove
Charter Member
Ah, yes - but you should be aware that the preview is removing things as well as adding. Supposedly 'incompatible' items are disappearing with every update received. I had half a dozen 'updates' this morning.
I've already lost Bitdefender and something else I haven't identified as yet (gaps in my desktop icons), so who knows what else is being changed/removed?
It's certainly true that we're not warned or otherwise notified.
I've forgotten how to identify the DX variant I have. Perhaps someone can remind me?
Just remembered: "dxdiag". It's showing a DirectX version of "11", but it's beyond that. 11.1, perhaps?
Dave
dhazelgrove
Charter Member
Update
Some news on this issue:
We're told that the issue has been fixed in "released Build 9471" of the Preview.
I asked when the build would be made available, as I've only got Build 9431. The response was that the word 'leaked' should be used for the word 'released'.
This suggests that the issue may well have been looked at, but the date that this possible fix is made available has yet to be decided, so don't hold your breath.
I've told them - bluntly - that I'm taking this as notice that the issue has been addressed in a possible future update.
We'll tell them when/if it's actually fixed.
Dave (Annoyed in the UK)
Some news on this issue:
We're told that the issue has been fixed in "released Build 9471" of the Preview.
I asked when the build would be made available, as I've only got Build 9431. The response was that the word 'leaked' should be used for the word 'released'.
This suggests that the issue may well have been looked at, but the date that this possible fix is made available has yet to be decided, so don't hold your breath.
I've told them - bluntly - that I'm taking this as notice that the issue has been addressed in a possible future update.
We'll tell them when/if it's actually fixed.
Dave (Annoyed in the UK)