Prophet

I think I have seen tests that show even x4 PCIe doesn't show much difference. I'm getting great FPS with a 970 on a 4820K. Considering the whole memory thing though the 970 is not a great choice for SLI.

Well I finally upgraded. Got the 4820K overclocked to 4.8GHz with ease. Changed the 970 BIOS and got it clocked to something. I remember struggling before with FPS. It wasn't unplayable, but it was far from smooth. Usually around 30-45 FPS. I never considered upgrading much because LOMAC 2.0 and on has never really performed all that great. It was considered CPU intensive and there has not been much improvement in single core performance. Man was I wrong. 100 FPS on all high settings. Now I got to fix my Cougar and see what is going on in the servers.

They can't do an A2G radar until ED implements it. The best educated guess is that ED is going to implement A2G radar when they release their F18. When that happens what is the point of the Coretex F18?

Different clients sharing the same map. Imagine flying DCS within the ARMA3 map.

Hey glad I could help!

I am not a wiz with Foxy. By default S3 is the modifier using the /I and /O. I believe you can change that with a command to S4 using USE S4 AS SHIFTBTN. What you wrote seems like it should work though. The /H might be confusing it. Try moving the /H to the TMM instead of the TMJ. I know I had to do that with almost everything in the A10C to get the held button commands to work. We didn't have any of those before the A10C. I attached the profile I used for the A10C. I have KA50 commands in the TMM because at one time I intended to make a complete DCS TMM. DCS_A10C.zip

I have 2 GTX285, and my GTX970 should be here tomorrow. I'm guessing I should be seeing a decent difference. Also upgrading from an i7-920 to the 5820K.

Resolution has been the problem with all the VR setups forever. If Rift doesn't address this, I am not sure what its bringing that all the others don't. Or why its taking so long to develop. The specs show 960x1080 per eye, or I would assume 1920x1080 effective. I am surprised thats not good enough.

2 times that is it? :D

Been having this problem for a while. Pretty much gave up on the stupid thing, but this Mig-21 interested me, since Cobra was so gracious to donate the key I won. But I just couldn't get by this Error 2 when opening the CCP. Couldn't read/write from the device, if I could manage to get the Firmware updater open without error, it wouldn't recognize the trigger pull to erase it. Obviously either a permanent defect, or bad firmware. Its a Cougar, lets go with firmware. This problem is much to the same as what Cali had with 2. http://forums.eagle.ru/showthread.php?t=61124&highlight=Cougar What caught my eye this time was what hollywood villian said. "If anybody else is still having this problem I think I might have figured out the solution. The key for everything to work is having the firmware in the controller already flashed BEFORE you plug it into windows7 x64. I myself had to use another PC with windows XP 32bit just to flash it, and btw, at first it didn't work in XP 32bit AT ALL either, but it did allow me run the HOTAS cougar update, and then it magically seemed to come alive. After that i just plugged it into the win7 machine and it seems so far to be working perfectly." I created and booted from BartPE. I installed the drivers. Ran the Firmware updater no problem, and here I am back in Win 8 working like a charm. If you got problems, it appears that sometimes only a 32bit system will do. P.S. I tried XP mode and other virtualizations and it wouldn't read/write either. Also keep this in mind. "Up-date I have solved my problem! It was very easy and maybe a little bit stupid of me but, all new motherboards come with the new USB 3.0 plug's and that was the problem! The Cougar isn't USB 3.0 compatible!"

Hasn't this always been an issue since LOMAC? I recall the F15C never being able to cruise as high or as fast as it should have.

When I read that, it seems that the ED team is saying it could take some huge code changes. I don't think the common Chinese person understands the difficulty their language presents in situations like this. I imagine it would take more effort than getting EDGE released.

Yeah. Used to get real good at pit-bulling on the dots. The sun is bright. It would be cool to see a brighter reflection.

I got motion sickness with TrackIR, at first. Your brain has to re-learn what its perceiving. It expects to feel motion when it sees motion. Its uncomfortable, but you will get over it.

2x GTX285 SLI.

I had said years ago that ArmA and DCS, throw in steel beasts and some really good Ship sim... One can dream.

I was downloading around 1.5Mbps.

Thanks cichlidfan for the drawing and chance to win! Thank you Beczl for offering the gift I won! I am really looking forward to the release! Merry Christmas everyone!

DCS Mig-21BIS

Is your Track IR plugged into its own USB port on the Motherboard, or on a hub with the MFDs?

My USB hubs power suspend was already disabled. I enabled them, rebooted. No work. Disabled them, rebooted, no work.

Anyone got them working? Mine just flash, and the driver keeps trying to install. I have rebooted with driver signing disabled, no good. It also appears it may have killed one of them too, the lights don't come on no more.

They do pick up the Shilka, just very close range. Usually once you are very close to firing range. I have used it though and sometimes managed to get a Vihkir or the laser guided rocket on them.

The instructions and LUA file for DCS:A10C, versus DCS World, work and have no coordinate issues. http://www.ivibe.com/index.php?page=DCS_A10CSupport The files need to be extracted into the user/saved games/dcs/script folder instead of the dcs/config/export folder.

Sock puppet.