fjacobsen

I rather hope it´s A-10C, KA-50, M2000C and AJS-37 day... If so, then I´m starting to look towards F/A-18 day.

Too much is broken in 2.5.1 and not only in the open beta version, since most of the bugs with the KA-50 and A-10C and 3rd party modules also exist in the release version. 2.5 is in my view not ready to replace 1.5.8, which now has become unsupported. Old modules has seen alot of bugs introduced, like datalink for both the KA-50 and A-10C. Cockpits in various modules cannot be used, like inop button lights in the KA-50. Functions that worked in other modules, like the RB-15F in the AJS-37 Viggen also has become inop. If these issues only where present in the open beta, then there is an excuse, but most of these exist in the release version. Seems to mee that too much focus right now is put on getting the F/A-18 and Strait of Hormus into DCS 2.5

I´m just afraid that they will start on the next new module and still leave the old modules full of bugs. Maybe fix some easy bugs. Sorry to say, but the last few years it seems there is much more focus on stuff that will bring payment, than stuff all ready paid for. I know it sounds negative, but honestly most early acces modules goes into a kind of sleep mode a couple of month after early access release. Regarding this threads headline, I have yet to hear feedback on whats going to happen with this from the developers or moderators.

Does this also count the RB-15F inability to set Bx6-9 via radar ?

I rather think they should have waited with Defered shading until all modules where ready. Right now most of the more complex modules are more or less porked with 2.5.1OB, so I´m not very fnd of buying earley acces to the F/A-18 when fixes for the older modues comes so slow. Until now I have been a happy supporter of DCS, having bought all modules as soon as they where released for early acces, but I think it has taken overhand with alpha, beta and EA in DCS. What I want is too see those modules I allready have come to a finished state as proof for ED and their 3rd party developers that they actually can deliver the promised products.

Not fully unfair... What we often see with DCS (not only Heatblur) is that once they start on a new project, the old ones are getteng much less attention an takes painstakingly long time to get finished and "hangs" in their beta state almost forever. It´s fully understandable that dev's not needed on a project moves on to the next project. But it´s not fair if developers, who still have work on a module that has been released for early acces and still isn´t at release state, doesn´t finish thier job on those modules for which they allready got payment. Thats actually what frustrates me the most with DCS - too much focus on new modules, rather than finishing older ones.

Also reported in the A-10C forum... Data link does still not work in 2.5.1 I have setup a mission with 1x A-10C and a JTAC including datalink. JTAC tells "DATA SEND", but no indications at all in my A-10C Mission: A-10C_Caucasus.miz Actually the same with the KA-50 - cannot send or recieve Data link targets to AI wingmen. FinnJ

How about the RB-15F Bx6-9 points ? Right now they cannot be set with the radar.

Nope... Neither data link in the A-10C or the KA-50 works :mad:

Could You please tell how to make it work ? Sending data to my wingman simply makes the SEND/MEM blink and my wingman doesn't send targets when asked to recce. I was able to use Data link with 1.5.

Any news on this ? Still doesn´t work with 2.5.1 updated 2018-05-11

If they doesn't release a hotfix for this, then I wonder when to issue hotfixes.

Just installed todays update (2018-05-11). Polychop SA342 Viviane sight still black. KA-50 - still inop or reversed lights.

Yeah... Incredible that they did not include a fix. I wonder at what level comms between 3rd party developers and ED are :mad:

Note that with deffered shading, the AP lights are inverted (Lit when Off and unlit when On) and the button lights on the Auto turn to target, Ground moving target, etc. does not lit, but still works. Frustrating that a module that once worked more or less flawless, now has become so bugged.

Deffered shading also causes the KA-50 AP lights to be inversed, as well as making lights on the "Auto turn to target" and "Ground moving target" Inop ( and probably a bunch of other button lights too).

As Title says... The AP lights are inverted and the Auto turn to Target, Ground moving target etc.. lights are INOP. Setting the AP lights opposite as expected (Those turned on are indicated dark, and those Off indicated as lit) makes the AP work. Pressing the Auto turn to taret does work when pressed, but lights on the button does not lit. Common.... Why all those one step forward and two step back. Don´t wreck stuff that has worked and please re-assure that modules that has been working, still are working after each update... Where are the beta testers, cause Early acces customers has time and time again been told that they are not beta testers !! I really start to plan installing good old Blackshark 2 and A-10C standalone, just to get something that worked out of the box.

Since I trashed all my "old" 2.5.0 missions and re-build new ones in 2.5.1 I have yet to experience a crash. It actually runs smooth, apart from when new objects are loaded (Comming into range, or undamaged models are replaced with damaged ones). But it´s still frustrating to see all other bugs introduced with 2.5.1, like the black Vivian sight on the SA-342, RB-15F missile setting in the Viggen, wronf and INOP lights in the KA-50... etc.

I got the same problem with the RB-15F. I cannot set the Bx6-9 waypoints. Setting Bx8 first, will let the circle and crosshair disappear after hitting TV set and trying to afterwards set Bx7 and Bx9 gives me EL on the waypoint readout until hitting T0. I had no problems using the RB-15F in DCS 1.5.8 and 2.5.0, so these issues must have been introduced with 2.5.1.

As I reported in another thread, it seems that "old" 2.5.0 missions causes the crashes for me. I have tried to load the old 2.5.0 missions in the mission builder and then re-save them, but they still causes crashes. New build 2.5.1 missions has not yet caused any crashes. Actually 2.5.1 runs rather smooth and with much better FPS than 2.5.0. FinnJ

I have found that all my crashes happened with old 2.5.0 missions. New build missions in 2.5.1 has not crashed DCS for me yet, even after prolonged flights. FinnJ

Could the crashes relate to using pre 2.5.1 missions ? Normally after updating to a new version, I will load the mission I want to fly in the Mission builder and then make a small change and then save it. The missions that crashed for me since 2.5.1 are those I have re-saved. As a test I have build a couple of missions from scratch, similar to those that crashes and now haven´t seen a crash even after flying for a long time. I have tested on the Caucasus and Nevada maps. FinnJ

Sure - I definitly haven´t any critics for Your support.

Strange - since so many has reported this issue with DCS 2.5.1 --> https://forums.eagle.ru/showthread.php?t=205782 I see this too, but has no issues with any other game on my system. I´m using latest Nvidia driver for my GTX 960.

I guess it's more DCS causing the videocard to crash than it' the videocard that causes DCS to crash. No other game on my system acts that way.