manne

Correct :) That's why I said "I run games like ArmA 2 also high with good fps", I never claimed to run it maxed out. Texture, postprocess, shadows etc. all high and viewdistance of 5000. Runs fluent in any community/coop mission (not campaign missions which I don't play). In the Armory I am able to set the view to 10000 but this is because there's no AI etc. @DCS: I thought I read somewhere you could change a setting so it sort of makes use of more cores, but I'm not sure if I remember correctly? I'll try to turn some settings down though, to see what kind of effects they have. I don't mind how high my fps is, as long as it is fluent, which it currently isn't. Most of the time I don't see any difference if it's at least 25 ~ 30 fps. So I'm not far away from that. I'll try some tweaking tonight :)

Any way I can see that? I can't remember if I installed it... The startup screen says 1.0 but it doesn't show any third number. True. ArmA 2 has a max visible range of 10 kilometers on an island with 245 square kilometers filled with cities, villages, forests, mountains, bullet drop, gravity etc. It's considered one of the heaviest games both for GPU and CPU. But I agree, comparisons are difficult especially with different engines, different coding etc. I'll stop my ArmA promotion now and focus on getting DCS to run smooth for now :music_whistling:

I understand that lowering some graphics settings should help my FPS :) What I don't understand is why it is not able to run all on high with a pretty high end system like that. I run games like ArmA 2 also high with good fps, which is also an open world persitant game with big viewdistances, lots of ai and cpu calculations etc. Yeah, I tried those and it gives me the 17 ~ 20 fps. I'll try some different settings later today. It's set to fullscreen :thumbup:

I always noticed that BS didn't run that fluid on my pc, but today I finally checked my FPS. It turns out I get between 17 and 20 fps on in example the Shooting range mission with everything maxed out. My setup is as follows: AMD 955BE x4 3.2Ghz Ati HD4890 1GB graphics 4GB DDR3 RAM Windows 7 64-bit 1440x900 resolution Is it normal to run with such low fps with a system like that?

I tried to re-create the problem today but haven't been able to yet. Maybe it was a controller issue after all. From now on I also unplug any other controller in my PC, just in case.

I'm having some problems with setting targets with the shkval. Sometimes it works perfectly, sometimes it won't lock the targets and sometimes the system gets a life on it's own and skipping all over the place while I'm unable to influence where the camera is pointed. Laser > ON Cannon > MOV Mov ground target > ON Master Arm > YES Weapons > Outer side (Y) shkval uncaged > YES Using RALT + ,./; I change the targeting position. With ENTER I set a target (tank). It seems that "randomly" the RALT + ,./; don't work. Sometimes the shkval starts spinning over the area and I'm unable to stop it. I have the same problem with using the cannon. Did parabellum's tutorial mission a few times, first time it wouldn't lock on the tanks, second time it all worked perfectly, third time it wouldn't lock again and I couldn't control the shkval anymore etc. I hope someone can help me :cry:

Ah thanks :) I can't seem to lock on any of the 3 tanks in the tutorial of Parabellum though. It does lock on any moving car driving around the area but I can't seem to set the tanks as target. As far as I can see I did everything the tutorial says.

Where can I find this tutorial? I can't seem to find any user named par_bellum, par or bellum.

Bug description: After changing from an outside helicopter camera view back to the cockpit camera view the sound FX still produce the sounds as if viewing the Ka-50 from an outside view (softer sound) and the mouse cannot be used for freelook and zoom (scrollwheel) anymore. This is fixed by pressing 'esc' (going into the menu) and 'esc' again (getting back into the game). After this the sound kicks back in and the mouse is available for freelook and zoom again. Steps to reproduce / Conditions of occurence While flying change the camerview to an outside view (like F2 or F3) and back to the cockpitview (F1). It occurs always. PC Configuration 1. AMD Phenom II x4 955BE stock 3.2Ghz 2. MSI 790GX-G65 3. 2x2GB Kingston 1333mhz DDR3 4. Sapphire Radeon HD4890 1GB driver version 8.612.0.0 5. Audigy Xfi XtremeGamer PCI soundcard 6. Logitech Extreme 3D PRO 8. Windows 7 64-bit 6.1, build 7100 9. DirectX 11 (says dxdiag?) Attachments none

I found the problem: I set the APU engine selecter to the left engine, it needs to be set to the APU (left, not left down corner). Thanks for the help, I must have re-watched it 6 times and still didn't see that I did not exactly what he said...

Hello all, I'm new to Black Shark, I've been reading for a while and bought the game yesterday. Today I bought a stick so the fun can begin! I've been toying around a bit and now I'm learning the startup procedure. I've been watching the startup video and trying to replicate those actions in the game. But for some reason something doesn't happen when it should (according to the video). First I turn on AC and DC power, both fuelpumps, fuelgage, APU Fuel shutoff valve, collision beacon, standby attitude indicator power and APU power. Then I select the left engine with the APU engine selecter switch (setting it to the left). Then I hit the start switch and only one light comes up in the APU gauge which is APU VLV OPEN. Nothing happens after that while in the video the other lights get lit up too. I've tried the whole procedure several times but I keep getting stuck there. I also tried by first requesting clearance to start the engines from the tower, makes no difference. I really don't know what I'm forgetting or simply unable to see in the video? EDIT: oh shoot, nevermind! I shouldn't have set the APU engine selecter to the left engine, it needs to be set to the APU (left, not left down corner). Doh! It seems this issue is resolved already