Sh4rk

This bug is really a game breaker, it screws over any attempts at having a mission that includes Tactical Command slots for players that have Combined Arms.

Issue 1: When I fire a Vikhr, the laser range resets to 0.1 km and I get a X on the Shkval (meaning "too close") even though the target is many km away. If I touch anything before the missile hits, or try to lock again, the Shkval slews away from the target and the Vikhr shot misses. Issue 2: Similar to issue 1 but without even firing, the Shkval loses track and starts slewing in a random direction. The range reading is cut by half, more or less. Quickly pressing the lock button will lock it to the ground, but 2 or 3 seconds later it will lose track and slew away again. In all cases, the Shkval is inside slewing angle at all times, there are no buildings, trees or wires in front of the target, the line of sight is clear. This is making it VERY frustrating to try to engage any ground units, using anything but rockets and fixed cannon, specially if they're moving or shooting back. :cry:

Not so many bugs, but the ones that are there are really annoying. The wandering slew is still happening as of the latest patch, also the laser lock distance resetting to 0.1 km.

Hey ED, please, PLEASE don't make it in a way the aircraft will share the same slots. Sure slots are a limited commodity in MP servers, but this would WRECK the MP server owner's ability to restrict the usage of FC-level aircraft in order to achieve game balance. If someone can join a slot for say a F/A-18C whether they have the full fidelity module or the FC version, we're gonna run even deeper into the same balancing issues we have now with F-15s and the lack of redfor clicky modules. So, don't do that. Do keep the different versions in different slots. I for myself could even buy FC4 like I did buy FC3, if they were different aircraft. But if I buy FC4, why would I buy the full fidelity versions later, unless I really, really want the FF aircraft? And as all I play DCS in is multiplayer... If multiplayer is less fun because it gets less attention from ED, and is made even worse because of balancing issues, I'm not gonna play DCS or buy any more modules, FC3 level or not. Off topic, but SC's business model of selling ships based off hype, not keeping their promises regarding "never selling these same ships again" etc etc. isn't any different of where ED is going now, apparently ("no more FC3 level aircraft").

For example? Being vague doesn't help bring attention to these issues, whatever they are. Do you have a link to a topic reporting your issues or similar?

It doesn't have many problems, but in the current openbeta patch 2.5.1, the lighting is completely broken. I'm just hoping they fix it before pushing to release, the sooner the better.

Now in 2.5.1, Deferred Shading forcefully on killed DCS for me. I'm not able to play with it on. I have a pair of GTX 770s. The performance drop with DS on, and the jagged edges because I have to turn MSAA off are too much. It was fine in 1.5, and very much playable in 2.5.0 with DS off. No crashes or any major problems related to memory etc. I have 32 GB RAM, SSD. But 20 fps full of jaggies when trying to fly a helo low among buildings and trees and wavy power lines and speedgrowing trees is just awful. I'm not even buying the Gulf or F18 anymore, because I think I won't be able to play them in my current rig. Which I unfortunately don't have plans on upgrading anytime too soon, given the current price on gfx cards. So yeah I'm kissing DCS goodbye for a while. Until everything is fixed at least. Can't even just go back to 2.5.0 or 1.5 and keep playing alone in my corner, as all I play DCS in is multiplayer. Meanwhile, I'll just go play other games, like ArmA 3 or Star Citizen... that run much better visuals and fps on the same hardware.

DS on makes the Ka50 cockpit look awful in general. No updates to the Ka50 cockpit since 2.5 is out. Nothing on today's patch. I'm not surprised. Not only the lights for the AP are inverted, but the targeting buttons are mostly impossible to tell if they are on or off. A workaround might be editing the cockpit textures or downloading an alternative cockpit skin, like Ricardo's. I'm about to just open the textures and paint the buttons red or something else.

The Ka-50 cockpit reflections are bugged and this has to be fixed. The sooner, the better. I don't expect ED to do anything else other than fixing the textures (maybe not even improving/changing them). I wouldn't pay for them to improve the textures or model, the ones already in game are enough (as long as they're fixed to work with the new engine). The Ka50 also has a couple unfinished features, stuff like IFF, sling loading, etc - the non functional cockpit switches. And some stuff the Kas have IRL, but not in DCS. While I'd like those to be made into functional features, and it being updated would probably help renew interest in the heli and boost sales, I'd still not want to pay for just a "revamped Ka50". Or for add-ons like the Garmin GPS, for that matter. I would however pay for a Black Shark 3 if it was the Ka-52. ;) ;) Crossing fingers that the Ka50's textures be fixed soon. In the meantime, I just edited the textures to make the autopilot buttons a bit more visible, that and the K-401 targeting buttons not lighting are the most annoying.