|
Technical threads All discussions about technical issues |
|
Thread Tools | Display Modes |
#1
|
||||
|
||||
DX9 Support for Battle over Moscow
Please Please Please Tell "US" the community that you are dropping DX9 for the Sequel.
|
#2
|
|||
|
|||
Drop it and I'll drop you!
|
#3
|
||||
|
||||
Assuming the sequel will be like CoD, where CoD makes use of the DX11 API there really is no need to drop DX9.. Because the DX11 API supports DX9, 10 and 11 feature levels and all the sub variants of each. For example, if you want to make use of DX9 feature levels in CoD simply edit your conf.ini file and chage it from DX10 to DX9.. Also, something not many people realise is CoD does currently support DX11! Problem is it is beta and not recomended! At the time of CoD relase DX11 feature levels still had some 'issues' (read buggie) so 1C limited the feature levels to DX10. But if you want to try the DX11 feature levels you can edit your conf.ini file and try them out. That is the beauty/benifit of programing the game using the DX11 API, the ability to switch to other feature levels
__________________
Theres a reason for instrumenting a plane for test..
That being a pilots's 'perception' of what is going on can be very different from what is 'actually' going on. |
#4
|
|||
|
|||
Quote:
|
#5
|
|||
|
|||
Quote:
|
#6
|
||||
|
||||
Again.. DX11 feature levels are NOT recommended! I tried them.. My fps seems a little better, but I lost all the grass rendering at the airfield. I ultimately switched back to DX10 in that overall it just seemed to look better.. But that is a personal call
Keep in mind most vid cards today support DX9 feature levels, some support DX10, and a few support DX11. So it should go without saying, to use DX11 you video card has to support DX11 If you want to try different feature levels (DX9, DX10, DX11) here are the settings you can use Code:
D3D11_0 D3D10_0 D3D10_1 D3D9_1 D3D9_2 D3D9_3 C:\Users\<YOUR USER NAME HERE>\Documents\1C SoftClub\il-2 sturmovik cliffs of dover Search for the section called '[window]' within that section you should see the following Code:
[window] Render=D3D10_0 So.. Say you want to 'try' DX 11.0 feature levels edit that line to read as follows Code:
[window] Render=D3D11_0 Code:
[window] Render=D3D10_1 Code:
[window] Render=D3D9_1 Code:
[window] Render=D3D9_2 Code:
[window] Render=D3D9_3 Enjoy and let us know if you get better or worse results! PS one thing you will probally want to do is del all the files and folders in your 'cache' dir each time you change the feature levels
__________________
Theres a reason for instrumenting a plane for test..
That being a pilots's 'perception' of what is going on can be very different from what is 'actually' going on. Last edited by ACE-OF-ACES; 12-24-2011 at 07:11 PM. |
#7
|
||||
|
||||
Quote:
Because one of the new features of the DX11 API is the ability to select different feature levels (DX9, 10, 11) on the fly. The good news is they did NOT do that and you can switch to use different feature levels. May sound silly to limit a DX10 capable video card to DX9 feature levels, but when it comes to 'visuals' it is so 'user' specific that some may like the look better, or, in some strange hardware configs find the game runs smoother at those lover levels.. Which I find hard to belive myself, but I have seen some folks make stranger claims than that!
__________________
Theres a reason for instrumenting a plane for test..
That being a pilots's 'perception' of what is going on can be very different from what is 'actually' going on. |
#8
|
|||
|
|||
Quote:
Also all GPUs today sold on the market have dx9, In fact I cant find a dx9 only gpu in shops anymore, the lowest end cards you find now in the west for nvidia are bottom barrel 8k-9k range, now they are shipping out bottom end 400s so really nearly all new gpus from now on purchased will be dx11. In any case I blew the horn on this whole compatibility issue in early 2010, go back a few hundred posts and have a look, nearly every prediction was correct |
#9
|
||||
|
||||
Quote:
Well don't take my word for it.. Spend 5min an do a little research and you will see that I am right! There are plenty of Microsoft Links on the subject.. But I know how the uninformed love to bash anything Bill Gates so instead allow me to post something from AMD on the subject, i.e. Quote:
If not set your conf.ini to DX11, or 10.1, or 10.0, or 9.3, or 9.2, or 9.1 and see for yourself!
__________________
Theres a reason for instrumenting a plane for test..
That being a pilots's 'perception' of what is going on can be very different from what is 'actually' going on. Last edited by ACE-OF-ACES; 12-25-2011 at 09:11 PM. |
#10
|
|||
|
|||
Quote:
You quoted me as saying (which I did): "you are wrong on a number of your points, DX11 has no API for dx9 features and such more then any other engine" You replied with this: "If they did that it would defeat the purpose of upgrading to the DX11 API.. Because one of the new features of the DX11 API is the ability to select different feature levels (DX9, 10, 11) on the fly." First off I hate having to educate people so I will make this brief: In the above statement you said that one the DX11 api features was to select different DX levels. ZOMG, you do realize that just means that the API is backwards compatable? For example I could use a DX9 lighting system while also using dx11 tesselation. So its nothing new, its existed for nearly every DX upgrade (they normally build on each other) and the whole point of switching to dx11 is to use the new dx10/11 lighting features among other things. These are completely new for dx11/10 and are "new dx11 features" and they are NOT back compatible. However like said a older dx9 system can be used (of course, not news to anyone but you it seems) instead of the new code etc. Your statement basically was like: "upgrade to a new car, hover car, it can even use wheels if you want!" The reply is then wtf is the point of upgrading? (and the only reply would be say, a more powerful engine but the main selling point no longer is useful). http://forum.1cpublishing.eu/showthr...795#post233795 |
|
|