-
Posts
121 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by =SCoRPioN=
-
Password reset not working at DCS site
=SCoRPioN= replied to sSnakeyes's topic in Forum and Site Issues
I have sent multiple emails from my registered address to support@eagle.ru, webmaster@eagle.ru with no reply. -
The patch did not optimize for multicores, it just set it to all cores by default for XP. Win7 and Vista use it properly.. XP does a horrible job at spreading the threads over the cores. Set to CPU0 on XP, it will be used more efficiently. You might even get higher FPS and quicker response.
-
Disable SLI and Intel HT, if u have it. Also, on Win XP, set BS to just CPU0.
-
Too generic. I specifically put what to do to avoid stuttering. As well as using MSCONFIG and getting rid of the useless services. My system running on XP has only 21 processes after McAfee and ZoneAlarm is loaded. Without those, it's down to 16. Stuttering is mainly caused by the onboard sound chip. Get a separate sound card! Just as important as gfx card.
-
I never has stuttering, of any kind, it's all just smooth. I'm using an older SB Audigy card with a gameport that I use MS Sidewinder Precision Pro joystick on. Even got it to work on Win7 :) If you have a separate Sound Card, make sure you DISABLE the onboard Sound Chip from BIOS, otherwise it's sending the sound to both of them, and that doesnt help. Also, if you have over 2GB of RAM, Disable the Windows Page Swap File in XP. Unless you have programs like Photoshop that require it. No Page File = faster loads, using HDD less. Definitely Defragment on regular basis. DO NOT use the Windows Defrag, and use Diskeeper Lite or something like that.
-
Disabling Physx doesnt seem to have an effect on fps, but then again, my system is fast. Disabling the 3D stereoscopic function will definitely help however. But I just use older driver that dont have that: 181.71 on Win7, 182.08 on XP.
-
Yeah, Windows 7 rocks!
-
Has little to do with defrag, and a lot to do with the Sound Chip and its Driver. If you do not have a separate PCI Sound Card installed, or if you installed it and did not disable the onboard chip, you will get stutter when there's a lot of sounds qued up, like when firing a cannon. A separate Sound Card is just as important as a Graphics Card, believe me. No matter how good your onboard sound chip is, it will never process the sound as fast as a separate card. So, there's your problem. Try installing another sound driver or go buy a sound card and disable the onboard one in BIOS. You can pick up a used card like an older SB Audigy on craigslist or somewhere else, and the problem will go away.
-
Use the 181.71 beta driver for Win7. Faster than 190.38 Set 16x AF and High Quality textures in Nvidia Control Panel also. (mine is vertical sync on as well) http://www.nvidia.com/object/win7_x86_181.71_beta.html http://www.nvidia.com/object/win7_x86_181.71_beta.html "Blurry" is a subjective opinion. It may seem blurry depending on resolution, monitor and how much zoom you have. Please provide the screenshots like the ones attached.
-
If you dont see the kill, install 182.x or 185.x and you will see the gain instead. Maybe it only does it on some cards, like top notch ones, like GTX. Yours is just an older card, and your system is probably limited by it. http://forums.eagle.ru/showthread.php?t=44336&page=6
-
Someone needs to make a side by side comparison of fps and quality of the same mission on price comparable ATI vs Nvidia cards. All I know is that DCS is super fun to fly with vertical sync on, 16x AF, 8x AA and 30fps minimum. When I turn on the Shkval, it does it instantaneously and seamlessly. My fps is always 60, and never goes below 30, even on panzertards any more, it's crazy. Nvidia: "The Way it's Meant to be Played!" Windows 7 rocks!
-
Yeah, the review is pointless. It's specifically comparing the newest crappy 190.x driver. It's not a fair review. With 182.x and 185.x, Nvidia runs as it should. They just screwed up once with 190.x, and the review is picking on that. Once in a lifetime Nvidia released a crappy driver set. ATI has always had problems with drivers, and there are tons of reviews, like on Tomshardware, that show that. However, it's good to have two companies, and have a choice of this many graphics cards. Games that use PhysX engine look like crap on ATI: Crysis Warhead. It's not all about framerate. Quality, stability, overclockability, and heat dissipation are factors as well. ATI runs hot, even hotter on desktop than in 3D, coz of the fan speed bug. The default coolers also run very loud, was fixed by setting the driver to run the fan at very low speed when in 2D = 80'C on desktop. If yours doesnt, that probably means you have modded drivers or the fan is not ATI, but Saphire or some other brand = more expensive. Nvidia is also better in OpenGL games. If ATI was so great, why did they go bankrupt?? Thanks to AMD for saving its a$$. Matter of opinion. Go ahead and stick with your ATI. Nice fancy red boxes with red cards, running red hot lol
-
Do NOT use 190.x drivers! They kill the fps in every game! Use 182.x or 185.x Problem solved.
-
GET NVIDIA! Read about ATI crap here: http://forums.eagle.ru/showthread.php?p=731499#post731499
-
BS 1.01A hosting port issue NOT resolved!!!!!
=SCoRPioN= replied to graywo1fg's topic in Bugs and Problems
The problem is YOUR ROUTER and NOT the GAME! Leave ED alone, they've done a great job. FIX your ROUTER or connect DIRECTLY! -
Only engage autohover after u have stabilized the chopper yourself and definitely have Heading Hold activated. If you dont meet to conditions prior to engaging it, it will start blinking the autopilot buttons and not engage properly. Dont do it right after takeoff, because the gyroscope needs to spin up first. Dont do it when you have navigation position fix warning by Ekran. I'm sure there are other conditions that you didnt meet, but these are the main ones.
-
Trust me, with 190.x you will have issues, if not yet. You're right, the newer GTX 275 is not supported by that driver. Use 185.81 instead. Just search nvidia.com for it. It is a beta, but I bet it gives better fps than 190.x
-
They do not purposefully program them in, that's what I meant. A lot of graphics/sound bugs are system specific, and it's not possible to test the patch on all possible system hardware. That's why we have forums so people can let the developers know if such bugs exist. I do not see any gfx bugs in DCS. On both computers, with Nvidia cards, no bugs. There's a sound bug when running DCS on Win7 with SB Audigy Advanced HD SB0160 but that's because of inaccurate 3D sound (EAX) implementation in the DRIVER that Creative has provided. The APU and blades are very loud at the start. If your game is unstable with Intel CPUs - Disable HT.
-
No DCSmax. The affinity is automatically set to all cores since the patch. In XP, I do alt tab and manually set it to just CPU0. Win7 181.71 drivers: x86 (32-bit): http://www.nvidia.com/object/win7_x86_181.71_beta.html x64 (64-bit): http://www.nvidia.com/object/win7_x64_181.71_beta.html REMOVE the newer Nvidia drivers as well as PhysX and 3D stuff by uninstalling them from Control Panel: Programs & Features in 7. Then Reboot. And only then install the new (older) driver.
-
As with the new trim function, the new cockpit mouse function should have an option to be turned off. I use the LAlt+C all the time, and now I have to switch it more often. The bug with clickable mouse+mouse look that was appearing out of nowhere randomly it seemed, was fixed by adding it as the 3rd setting. The problem with having both functions in one is that when using the mouse wheel to zoom in/out, you almost certainly going to adjust something else as the cursor is moving across the screen, like HUD brightness.
-
The developers do not program the bugs into the game. They do their best to develop and patch the game so it would be playable. And since this is a very advanced simulator game, bugs are expected. The only sure way to sort them out is by posting them on the forums together with your system specs and every other little piece of information you can provide to better describe the issue. Simply by demanding another "service pack 2" or to fix a problem that is most likely specific to your system is not going to resolve the issue.
-
Vacuum the insides of your computer. Do not use a dusk blower, use a vacuum with a tube. Also, dust conducts electricity. Do not let the fans spin as you vacuum, because they will generate electricity and can fry your board. Disconnect them if you gona let them spin.
-
Vista sound issue solution for IDT High Definition Audio
=SCoRPioN= replied to REL's topic in Bugs and Problems
Had the same issue on Win7 with an older SB Audigy Advanced HD model SB0160 with gameport. I got the gameport to work in 7 :) The APU made a loud noise when starting and also did the blades, the air waves extremely loud and annoying, like whistling when starting. Opening the cockpit door and closing helps, but if come back from external view or any other view into F1, the sound of the APU and/or engines becomes extremely annoying, but only up until take off. Had to manually force an older Vista driver into Win7. Had to disable 3D effect and EAX. -
You accidentally used the mouse wheel to zoom in/out while in the clickable mouse/mouse look mode on one of the contrast/brightness knobs behind the stick. Otherwise, gfx driver issue. In computers, nothing happens for no reason, everything that happens has a reason and can be fixed.
-
Whatever problems everyone is having is your specific system related and not the patch. The 1.0.1a patch boosted my FPS by a noticeable amount. Do not run 190.x drivers, not even in Win7. The best driver for Win7 I found is the Beta 181.71 I tested on both WinXP and Win7 (dual boot:), and even though 7 gives more fps overall (2x the min fps, never goes under 30, even with shkval), the fps in XP got a nice boost since the patch as well. With Win7+190.x it went as low as 9fps! 181.71 fixed it.