Legolasindar

Seeing that is a great idea (thanks PhoenixBvo), does ED have tried to implement this idea in the BS? I think we should not be discarded, because it is a great solution. And if you can not be implemented in the BS, at least if in the coming releases. Sorry for my english.

The best beta tester, is that we throw more videos :music_whistling::megalol:

Choppers can attack small targets, see videos of apaches firing gun to enemy soldiers. Can provide close support for friend soldiers, stay and hold near of this soldiers, evade enemy radar using terrain. Airplanes cant hold, cant evade radars, cant shoot small targets. Airplanes need airports for operating, choppers can takeoff/landing from anywhere. Both aircraft as helicopters, are magnificent machines of war, but each has its role, and develop a kind of mission better than another.

198x or 199x with ace of the pacific and others, X29 Retailator, Red Baron, rusian sim forgotten name, F117 (same others friends cant start engine of F117 of this sim xD)...

Hotas Cougar is a good option. It's metal, is nearly identical to the real F16, is very complex, with a programming language that lets us hundreds and hundreds of combinations. Of course there are some negative, as in all joysticks, but is a wonderful option, that you will not regret. I have since I put it up for sale, with preorder of special edition of the 111 Squadron and except for a couple of problems I'm very happy with.

This article analize this posibility. http://www.guru3d.com/article/physx-by-nvidia-review/5 Have various pages.

It's simple, we need that are in different PCI-E. Anyway I do not have a 9800GX2, so I can not guarantee. The best thing is to try it yourself.

Correct me if I am wrong, but the 9800GX2 is a single card with two processors. For what you can not do it. We need two cards (not two in one).

Yes, I forgot that point, sorry :P. Fortunately the new motherboards usually carry more than one.

Yes say software, but in oficial web of nvidia say hardware. I test with 8800 GTX and work. For download. http://www.nvidia.com/content/forcewithin/us/download.asp Only need first option, others is optional. Note: If you have installed a previous version of the drivers ageia PhysX, it is advisable to remove the old, before installing new ones. The programme Nvidia PhysX propierties tell you that we have no Nvidia PhysX processor installed, which is true, but in Settings, you will come three options, one GeForce PhysX, which must be checked, and that is that you have enabled the acceleration physics. Also commenting that as many have already found, you can have two GeForce cards, one dedicated to the graphic and another dedicated to the physical part. We can put our GeForce most powerful to accelerate graphics. And the other GeForce less powerful and less expensive to accelerate physics. And we do not need to be in SLI. A big hit by Nvidia, for those who prefer to spend a little more money to get an exclusive card for physics may do so. Also in the future when we buy a new card, the old may be left for physics.

But this is PhysX drivers, no nvidia geforce drivers (with support PhysX) and not official.

NVIDIA uncorking PhysX support for GeForce cards on August 12th NVIDIA uncorking PhysX support for GeForce cards on August 12th http://www.engadget.com/2008/08/07/nvidia-uncorking-physx-support-for-geforce-cards-on-august-12th

I no read this notice ATI ability Havok for run in GPU. In this point, yes is hardware acceleration. But CPU is a part of hardware yes, but it does not consider hardware acceleration. Since when calculations are made by the main CPU there is no acceleration, and therefore is considered software. This is semantics.

¿No have GPU, no have PPU, and have installed PhysX drivers? You cant play games with physics accelerations. Only you can is force CPU to use process PhysX, but its not accelerated and you is forced processes.

Havok is not accelerated with GPU. Havok processes is run in CPU, PhysX processes is run in GPU (or old PPU of Ageia). Conclusion, Havok is not hardware accelerated, its very simple. You can play in game with video cards (not all games), but no accelerate graphics, CPU calculate graphics. Uou install GPU (graphic acceleration card) and can play with advanced graphics.

PhysX is hardware acceleration, same the GeForce or ATI graphics acceleration are. Acceleration software = CPU computer perform the calculations. Acceleration hardware = The alternative CPU (in this case the GPU) performs calculations. Same the graphics acceleration. Conclusion, PhysX is hardware acceleration.

I find this surfing in internet. Development line 1 T10 – the project designation, also name for early four prototypes Su-27S – serial configuration for russian air force, air attacks, ground attacks only with unguided munition Su-27P – serial configuration for russian air force, only for air attacks (because international agreements it can use only air-to-air weapons) Su-27U – trainer without radar (not realized) Su-27UB – combat trainer for Su-27S/P fighters Su-27RV – six machines for acrobatic group Russkije Vitjazi Su-27SK – export version of Su-27S for China (J-11A) Su-27SMK – modernized Su-27SK Su-27UBK – export version of Su-27UB Su-27PK – export version of Su-27P (no customers) Su-27PMK – modernised Su-27PK (no customers) Su-27SM – modernised Su-27S, unrealised and designation was later used again Su-27PM – modernised Su-27P for russian air force (not realized) Su-27UBM – proposed early modernization of Su-27UB, unrealized and designation was later used again Su-27BM1 – Belarus upgrade of Su-27S/P Su-27UBM1 – Belarus upgrade of Su-27UB Su-30 (Su-27PU) – two seat air defence fighter Su-30D (Dozapravka Su-27PUD) – two serial Su-30, bought for Anatolij Kvotchur acrobatic team (second was later rebuilt as Su-30MK) Su-30RV – special version for acrobatic team Russkije Vitjazi (not realized) Su-30K (kommercheskij – commercial) export version of Su-30, all bought by India Su-30KI – single seat version for Indonesia. In fact Su-27SMK with air refueling system from Su-30 Su-30M – multirole fighter/bomber unsuccesfully offered to russian air force (designation used later again) Su-30MK – export version of Su-30MK Su-30MKI (Modernizirovannyj Kommercheskij dla India) – Su-30MK version for India Su-30MKK (Modernizirovannyj Kommercheskij dla Kitaja) – Su-30MK version for China without TVC and cannards Su-30MKM – Su-30MK for Malaysia Su-30MK2V – Su-30MK for Vietnam Su-30MKB – proposed designation Su-30MK for Brasilia (yet not realized) Su-30MKL – proposed designation Su-30MK for Lybia (yet not realized) Su-30MKT – proposed designation Su-30MK for Thailand (yet not realized) Su-27SKM (Su-27SKU) – single seat version of Su-30MK (no customer) Su-30M – second accepted proposal of modernisation of Su-30 used by russian air force (not related to original Su-30M modernisation) Su-27UBM – modernisation of russian Su-27UB nearly to Su-30M standard Su-27SM (Su-27KN) – modernisation of russian Su-27P/S nearly to Su-27SKM standard Su-30BM (Su-30KNM, SU-27UBML) – radical modernisation of Su-30M and Su-27UBM in 2010 timeframe Su-27BM – radical modernisation of Su-27SM in 2010 timeframe Development line 2 Su-27KI (K stands for Korabelnyj – navy and not Kommercheskij – commercial) – first navy proposal (not realized) Su-27KTM – preproduction T10-20 with collapsible wing and uncollapsible cannards – first step to Su-33 Su-27PGO – one of the first navy serial machines with movable cannards Su-33 (Su-27K, T-10K) – serial navy fighter Su-33M (Su-27KM) – proposed modernization of Su-33 (yet not realized) Su-33MK (Su-33KM) – export version of Su-33M (no customers) Su-27KU (T10KM-2) – original two seat navy proposal, development stopped due to lack of fundings Su-27KRC – proposed navy reconnaissance version derived from Su-27KU (not realized) Su-27KRT – targeting version derived from Su-27KU (not realized) Su-27KTZ – air refueling version derived from Su-27KU (not realized) Su-27KPP – electronic warfare version derived from Su-27KU (not realized) Su-28 – mini AWACS version with antenna on the top (designation later used for acrobatic version of Su-25) Su-33UB (Su-27KUB) – two seat navy fighter/bomber/trainer, only one prototype built, now under tests Su-30K2 – two seat long endurance fighter (in fact hybrid of Su-35 and Su-33UB, now under development) Development line 3 Su-35 (Su-27M) – second generation of Su-27 with cannards, new targeting system etc. Su-37MR – proposed Su-35 derivate for SAE (not realized) Su-37 (Su-27MP, Su-27M2) – eleventh prototype of Su-35 modified with TVC engines, new radar etc. It was destroyed in 2002 Su-37KK – proposed export version for China (not realized) Su-35UB – two seat version, rival of Su-30MKI Su-35RV – six machines, modified for acrobatic team Russkije Vitjazi Su-35BM – planned modernisation of Su-35 in 2010 timeframe Su-35UBM – planned modernisation of Su-35UB in 2010 timeframe Development line 4 Su-27IB (Su-27KU, Su-27UK) – first prototype of two seat fighter/bomber with seats one next to other and with cannards Su-32FN – promotional version for antisubmarine and antiship operations Su-32MF (Su-34) – promotional version for surface attacks Su-32 (the official NATO name is Fullback, not Platypus) – serial production version for russian air force based on Su-34 Su-34P (Su-27IBP, Su-27PP) – electronic warfare version, derived from Su-34 Su-34R (Su-27IBR, Su-27R) – reconnaissance version, derived from Su-34 Experimental versions T10-15 – hybrid consists of front part from T10S and rear from T10 T10-20 (T10R, T10KTM) – record breaker modification (built but not used) P-42 (T10-15) – record breaker modification, made 27 FAI records Su-27LL/PS (Su-27LL/UV, Su-27UB-PS) – 2D nozzle platform Su-27LL/KS (Su-27KSI) – 3D nozzle platform Su-27LMK (Su-27ACE) – test platform with new avionics and joystick at the right panel Su-27LL/OS – Su-27UB used for guided missiles tests Su-27P (not related to serial Su-27P) – experimental aircraft for avionics test without radar and IRST

PhysX is hardware, not software. Only need to use this technology is drivers. For use my Hotas Cougar (is hardware) need drivers (software part). For use PhysX need drivers, and this drivers use CUDA technology, similar to language used by ATI. For use Havok no need specially drivers, no need include support for this technology in drivers, all graphics can run Havok.

Not correct. Havok is software. Any graphic can be operated Havok. PhysX is hardware, but Nvidia already reported that both ATI graphics cards such as Nvidia, may use such technology. Both.

Amazing agility and amazing ability of the pilot. :thumbup:

This is my tactic :smartass::pilotfly:

Nice video :) But have especial petition. In future videos, please use others videowebs, non youtube. Others web http://www.vimeo.com http://wuapi.com http://www.veoh.com http://divxvine.com This webs have excelent quality, and same options youtube. Fast, easy and good for upload video. Quality of youtube is very very veeeeeery bad. And thanks again for this great video.

WoW, very very nice:cheer3nc: Great work. You can upload in 1440x900 for use to a wallpaper?:smilewink:

I think films while flying. As far as flying with this view that we see in the video. What we must be very difficult on a soft landing in autorotación with a view outside.

CRV-7 of Kusch post are photographs taken with the slow shutter of the camera, do not serve as a benchmark real.