So if we are talking of going from dx9 > dx11, the 3 options are what tuttle says : a) porting, b) optimised patching, c) start from scratch (with regards to dx code)
Well, after a certain amount of reading it would seem that options a) and b) are non starters, unless you want a bodge job that does not give you the results you are looking for, and also a lot more problems on top. dx10 and dx11 are not just improved versions of dx9, the way they are operating internally has some fundamental differences and to gain those benefits available you need to do things differently yourself which involves quite a lot of work changing code.
So, if you go to dx11 via option c (scratch built dx code), ISI is saying that will break all 3rd party content, is that right? If that is right then that is almost the end of the discussion. But it would also lead to the question why? Who is going to be taking the hit exactly, the modders or the developers of the game engine, or both?
If it is going to hit the modders then I assume when IRacing upgrade to dx11, as they are, then IR will also have to upgrade all of the content also to go with it? Or can it stay the same in fact and only* affect the game engine? If not and IR can use the same content then why cannot RF2? I do not know answers to these questions. Are the content of our rfcmp's intrinsically linked to dx9? I do not know.
* I say 'only', it is not a small undertaking! But it's a huge difference between doing massive work on engine AND writing off all 3rd party RF2 content, which will basically kill the game probably.
Sure dx11 would be nice to have however the main reason I see to do such a huge amount of work on engine is to solve the problems that have plagued the dx9 engine for so long, by which I mean the SLI issue. ISI reckons there is no issue, but I reckon there almost certainly is. If it would take a huge amount of work to fix that on dx9 maybe it is then more appealing to take on dx11 and kill 2 birds with one stone. If that would even do it, even that is unknown. And that's just the thing. DirectX is very complicated, you probably need to know a lot about it to know what is and is not possible, and I don't and prob most of us here don't. There are many small details that are hugely important that we cannot determine ourselves, thus it is almost pointless to be discussing these things endlessly in the dark.
Owing to my frank and open discussions with fanboys here I am often awarded by ISI a kind of special elevated 'greyed out' status on this forum, which I believe is ISI's way of telling me what I am saying is so obviously true that it is not even necessary for me to expand any further on that undeniable and comprehensive truth which has already been stated. And I must say I do appreciate and enjoy my special greyed out status very much, but sadly all good things must come to an end.
What I get tired of, is every time my special status expires I come here and see the same old tired issues still churning on and on. The same issues as 6 months ago, 1 year ago, 2 3 or 4 years ago, and it will be the same in 6 months and 1 year time and 2 years time also. It's a waste of all of our energies typing anything here it seems.
And ISI do not help, because ISI are about as forthcoming with information on future plans as the Illuminati themselves. It does not really happen. Perhaps they do not even exist!
I think ISI should seriously consider making a 'roadmap' available, so we can see what is and is not in the pipeline and what the priorities are. Is it the drive train model? Is it a newer dx? I am not talking about cast iron guarantees with deadlines, that's stupid, just a loose plan with no solid commitments that gives us an idea of what to expect over next 12 months. And it will reduce all the moaning and perennial speculation on forum too which must be a good thing.
Getting back to the dx I expect the following 2 things need to be true if a migration is to occur :
1) To get RF2 working natively with dx11, using dx11 properly, not these cheap ass quick ways of porting to dx11, which is probably a big mistake.
2) To keep all the 3rd party content working throughout, cause it will be fatal not to do so.
So for a very start, that involves huge amount of work for ISI to rework gfx engine big time for native dx11 support, so my final question is the same as where I started, IF, even IF ISI did do that, is it technically possible for the existing 3rd party content to still work or not? That is crucial thing.
I wish ISI would be more forthcoming with information and also consider making a 'roadmap' as suggested.