Groove_C

Mi24_P RoF should go in ascending order (300-2000-2600) and not in descending (like on Vodnik BPPU, BMP-2/3, BTR-90 and Ka-52 (300-600)). Su34 pilot is missing zoom in/out if in "manual fire". Only working if no "manual fire" selected. BTR90 gunner is missing laser rangefinder (unlike T-90). GAZ_Vodnik_HMG gunner is missing zoom in/out (unlike old-timers BRDM-2 or BMP-2 with same scope). GAZ_Vodnik_HMG gunner is missing laser rangefinder (unlike T-90). GAZ_Vodnik_HMG gunner/driver are missing night vision. https://dev.withsix.com/issues/68103 The BPPU turret is equipped with sights 1PZ-9(day) and TPN-3 or TPN-3-42 "Kristall" (night). Source: http://en.wikipedia.org/wiki/BTR-80 BMP3 gunner is missing laser rangefinder (unlike T-90). BMP3 gunner is missing zeroing up to 3000 m for 2A70 (unlike T-90 with 2A46M). BMP3 is missing radio commands to "Get In" as "Gunner Left" or "Gunner Right", only having "Gunner" option (hopefully not engine limitation :D). https://dev.withsix.com/issues/2079

Roger that. Thank you anyway :)

A bug that's ruining the whole gameplay/ game experience: http://dev.withsix.com/issues/13586 In MP, all controls are lost after respawn if killed while naming a marker placed on the map. Even "Escape" and "Alt+F4" are not working. Only option left is to "end task" in "processes" once "Ctrl+Alt+Delete". A bug that's deadly on battlefield. One cannot check gear ("G") while prone if equipped with pistol, while it's working flawlessly with a rifle. If you press "G" to check gear while prone equipped with pistol, you will be forced to stand up against your will. http://dev.withsix.com/issues/24719

Just amazing news! Keep it up man!

M230 cannon on AH64D, AH64D_Sidewinders, AH64D_EP1 and BAF_Apache_AH1_D has wrong movement limits. Real limits are: vertically: -60° and 11° horisontally: -100° and 100° https://dev.withsix.com/issues/67715 Source: http://www.kitsune.addr.com/Rifts/Rifts-Earth-Vehicles/Golden_Age/GAW_AH-64_Apache.htm In CCP cannon movement limits for Ka-52 were corrected, but despite my report they've omitted to do the same for AH-64D. http://dev.withsix.com/issues/16815

If you would have followed this thread closely, you would have noticed, that goliath86 is fixing config related issues as well. One should be grateful to people like him for bringing the game that some of us still love this much to a whole new level by putting this much enthusiastic efforts in it.

RPK_74 automatic rifle's 75Rnd_545x39_RPK magazine should be replaced by a 45Rnd_545x39_RPK orange magazine instead of a drum. Because drums of 75 rounds are RPK 7.62x39 specific only. https://dev.withsix.com/issues/70371 pic of actual RPK-74 AGS-30 and Mk-19 rate of fire is only 150 rpm, but should be 400 rpm. http://dev.withsix.com/issues/27347 Source: http://en.wikipedia.org/wiki/AGS-30 Mi24_P GSh302K is missing middle (2000 rpm) rate of fire mode. 300 rpm to low (to weak) and 2600 rpm quickly out of ammo. Source: http://en.wikipedia.org/wiki/Gryazev-Shipunov_GSh-30-2

After yesterday's update Su-34 pilot has gained control over the cannon, but has lost control over FFARs :rolleyes:

Understood :) Than let's at least add zeroing function to these helicopters: YakB (Mi-24) practical range is 1500 m. GSh23L (Mi-24) practical range is 1500 m. Source: http://fas.org/man/dod-101/sys/ac/row/mi-24.htm 2A42 (Ka-52) practical range is: 1500 m for light armor targets 3000 m for flying targets 4000 m for soft-skinned targets. Source: http://en.wikipedia.org/wiki/30_mm_automatic_cannon_2A42 So let's say 2000 m (+500 m) compared to YakB and GSh23L. + correct practical range from 1200 m to 1500 m for: M197 (AH-1Z Cobra) practical range is 1500 m M230 (AH-64D Apache) practical range is 1500 m

Maybe enough time before today's beta release to add zeroing + rangefinders to these helicopters: ??? :rolleyes:

Good to know

In 1.63.125548 BETA (CorePatch) and in 1.63 stable + @ANZINS Flashlights are still not working on: M4A1_HWS_GL M4A1_HWS_GL_camo M4A1_HWS_GL_SD_Camo IR laser pointing 90° to the right straight out of the magazine on: M4A1_RCO_GL. Iron sights not working on: AK_107_GL_pso AK_107_pso In 1.63.125548 BETA (CorePatch) Iron sights/ look over scope not working on: SVD SVD_CAMO SVD_des_EP1 KSVK M4SPR M249_M145_EP1 M240_Scoped_EP1 M24 M24_Des_EP1 M107 BUT! In 1.63 stable + @ANZINS they work properly.

If you're talking about this bug that was introduced in patch 1.57, than it has already bean fixed in CorePatch v1.0.0.18 (07/01/2015) :)

These helicopters: are missing zeroing and rangefinders (unlike AH-1Z Cobra and AH-64D Apache). https://dev.withsix.com/issues/67638 https://dev.withsix.com/issues/67640 In real life Mi-24D has electro-optical rangefinder. In real life Mi-24V has laser rangefinder. In real life Ka-52 has laser rangefinder.

goliath86, thank you very much for all your efforts - great work! Wanted to repport 3 errors introduced in v1.0.0.17 concerning Mi-24P. 1. GSh302K cannon should carry "250Rnd_30mm_GSh302" as on Su-25 instead of "750Rnd_30mm_GSh302" currently. https://dev.withsix.com/issues/71143 Here's the proof: Ми-24П (изделие 243) — Ми-24 Ñ Ð¿ÑƒÑˆÐºÐ¾Ð¹ ГШ-30К, размещённой на правом борту в неподвижной уÑтановке ÐПУ-30, боекомплект — 250 ÑнарÑдов. Source: https://ru.wikipedia.org/wiki/Ми-24 2. The pilot somehow has lost he's ability to fire 40 unguided missiles, as they've simply became unavailable. 3. The pilot has received 2 FAB-250 + 4 Ataka-V additionally to those available from gunner (manual fire mode), which makes the gunship to carry twice the amount of ammo actually physically available in reality. ---------- Post added at 02:31 AM ---------- Previous post was at 01:34 AM ---------- + 1 error concerning Su-34. In Su-34 for an unknown reason the Gsh cannon is controlled by the gunner and not by the pilot, which is more than strange since Su-34 has also a fixed Gsh cannon as Mi-24P and therefor aiming has to be done by maneuvering the aircraft which involves the pilot and justifies more than enough his ability to control the fixed Gsh cannon. https://dev.withsix.com/issues/67741

@forteh i5-750 can't do more than 3.8 - 4.0 GHz before hitting voltage limit. MAX voltage for i5-750 is 1.4 V with LLC disabled or 1.35 V with LLC enabled (LLC - Load Line Calibration - adds another 0.050 V to the voltage shown).

@ forteh And don't wonder why 4 sticks for a total of 8/16 GB are more expensive than 2 sticks for a total of 8/16 GB. Because if you have your 8/16 GB spread on only 2 slots, your bandwith is 128 bit only. But if you have your 8/16 GB spread on 4 slots, your bandwith is 256 bit. As each slot is 64 bit.

@ forteh Yes, you are. But you shouldn't put together different sticks' brends, models, speeds, timings, voltage, volume. All sticks must come from the same manufacturer, same model and each stick must be of the same volume, run at the same speed with same timings and voltage. Otherwise it can make your sistem unstable or make you lose performance. When you overclock your 1333 MHz sticks, you must upper their timings and voltage accordingly. But you can't dou this in your case. Otherwise you will also upper timings and voltage for your 1600 MHz sticks. Let's imagine you wanna buy 8 GB RAM. In this case you should buy a single kit of 4 sticks 2 GB each. In worst case if you already bought a single kit of 2 sticks (2 GB each) and wanna add some more RAM, you can later buy exactly the same kit to add another 4 GB (2 sticks of 2 GB each) to reach 8 GB in total. There can even be problems if you have added more RAM to your already existing RAM with same speed, timings and voltage, but form another manufacturer and model. Like you have 2x 2 GB 1600 MHz 8-8-8-24 1.65 V (Corsair) and you addd 2x 2 GB 1600 MHz 8-8-8-24 1.65 V (Kingston)

@ forteh What is your RAM speed? 1333 MHz or 1600 MHz? If you have 1600 MHz RAM sticks, you can simply set your BCLK to 200 MHz, Multi (Ratio) to 20 for CPU and 8 for RAM. This will result in 4.0 GHz for CPU and 1600 MHz for RAM. You don't need a "K" model for this. If you have 1333 MHz RAM sticks, you can simply set your BCLK to 190 MHz, Multi (Ratio) to 21 for CPU and 7 for RAM. This will result in 3.990 MHz for CPU and 1330 MHz for RAM. You don't need a "K" model for this. Don't forget to disable Turbo Boost, CPU and PCI-E Spreed Specrum, EIST (Speed Step), C1E and C-States. Don't forget to enable LLC (Loadline Calibration adds 0.050 V to voltage you set) Don't go above MAX 1.4 V! Or 1.35 + LLC enabled

@ forteh Here is the difference in average and minimum FPS in A2 RFT patch 1.62 GTX 580 (512 CUDA cores + 384 bit) 2x 2 GB DDR3 1333 Kingston LoVo (CL7-7-7-20-1T @ 1,25 Volt) Win 7 X64 SP1 http://i.imgur.com/iOcMRQ2.jpg (221 kB) http://i.imgur.com/MtvBOt7.jpg (206 kB) Look for i7-870, i5-760 and i3-540. As you can see the average FPS difference is evident, but the min FPS difference is not as high as the average is. An i5-760 with @ turbo boost on 4 cores clockes from it's default 2.8 GHz to 3.0 GHz (3.2 GHz 2 cores and 3.33 GHz 1 core) brings you 6 minimum FPS more than an i3-540 @ 3.0 GHz @ Hyper-Threading An i5-760 with @ turbo boost on 4 cores clockes from it's default 2.8 GHz to 3.0 GHz (3.2 GHz 2 cores and 3.33 GHz 1 core) brings you 12 average FPS more than an i3-540 @ 3.0 GHz @ Hyper-Threading

@ forteh If you're low on budget and want to keep you current mainboard, go for an i5-760 (8 MB cache) @ 4.0 GHz as an i7-870 won't bring you more FPS at all. I had the i5-760 @ 4.0 GHz (1.3475 V) for 3.5 years. Changed to an i7-4790K (4.6 GHz) an guess what - I still have FPS deeps below 20 FPS at times in multiplayer despite the fact that average FPS is "way" higher. Try to get atleast a GTX 760 or a GTX 660 Ti, but not the GTX 660.

Downclocked my 16 GB (4X4) from 2133 MHz 9-11-10-27 to 1600 MHz 8-8-8-24 and did 3 runs @ Altis benchmark. Lost 5 FPS (average). Don't think the minimal FPS was affected. Gained 1 FPS (average) going to 2400 MHz 10-11-11-30 @ 1.65 V. So going from 1600 MHz 8-8-8-24 to 2400 MHz 10-11-11-30 will give you 4-5 FPS more (average). Minimal FPS won't change much I think (if at all). Have managed to get 50 FPS @ Altis after 3 runs (51, 50, 50) @ Ultra @ 1680x1050 @ Win 8.1 x64 @ SSD Intel X-25M SATA II 275 MB/s read & 80 MB/s write. Have compared FPS at different RAM speeds on Altis Scores: 45 FPS @ 1600 MHz 8-8-8-24 2T 46 FPS @ 1866 MHz 9-9-9-27 2T 49 FPS @ 2133 MHz 9-11-10-27 2T 50 FPS @ 2400 MHz 10-11-11-30 2T Downclocked from 2400 MHz @ 1.65 to 2133 MHz @ 1.5 V. I don't see the need to stress my RAM because of 1 addition FPS and that's average - not minimal. Faster RAM brings you more FPS only at lower resolutions and lower graphic settings. The higher the resolution and graphic settings the less faster RAM makes the difference.

@killerwhale Your i7-930 despite being clocked to 4.0 GHz is still 10+ FPS behind i5-4690K @ 4.5 GHz. DDR3 2400 MHz can give you up to 5 FPS more on Altis compared to DDR3 1600 MHz. Your GTX 580 with only 512 CUDA cores and it's 1.5 GB vRAM is far from being the one which would give you comfortable FPS. Better get a GTX 970 or a GTX 780 if low on budget. And don't forget that since patch 1.14 ArmA III is able to use over 2 GB vRAM. (20.04.2014) Patch 1.14 SPOTREP #00021 ENGINE •VRAM management changed (optimization) On my res 1680x1050 with everything on Ultra in MP my GTX Titan is always @ 2800-3000 MB vRAM of it's 6000 MB.

I will than use only -enableHT :) Becasue I didn't know they've implemented autodetection. Thought there was certain number of cores set by default as for ArmA II. Thx anyway :)

Greenfist have a look here: patch 1.07.71143 Improved: -cpuCount=4 is now default on computers with more than four logical CPUs. If you want to use more CPUs, use -cpuCount=N to override this.