lennycutler

Same problem reported In The installation bug section..it also is ocurring to me

Black Shark 2 Key Error I am asked to supply the serial number....the key is already shown in the field, I hit bind...but it does not enable BS 2 to show up as one of my modules. I had previously rec'd the key listed to reflect my upgrade of BS 1 to BS 2. Happens each time I load the game.

Today my Hotas Warthog Joystick is no longer working. It is a relative new joystick and I think the problem is some new software conflict. I re-installed the driver, which was done successfully per the Thrustmaster installer, and I am using the latest installation package. When I troubleshoot this via windows 7 device settings, I get the message "Thrustmaster HD Filter 01 doesn't have a driver" I have tried several times to re-install the drivers with the same result. I even copied my old drivers back in to the Thrustmaster directory from a backup, with no improvement. Everything was fine a few days ago. I shut my machine down for a couple of days...started it up today and now I am unable to use the joystick. Anyone have any suggestions? Appreciate any help.

Things Re sharper With sharpening set to max I can easily read the warning messages on the f14 fuselage...so for me this setting works with no drop in fps.

Does it Make a Difference I have enabled it but I have no clue if it really changes anything. Perhaps ED will comment soon as to its effect and optimal setting if it does work with DCS.

Confirm with Warthog Controllers, Max engine never goes above 40%....and control indicator shows after burner position fulling engage on throttle axis....AB flame appears on F2 view. This should be easy to confirm by the developers by now.

Has anyone else experienced this

I have the Hotas Warthog...and I set up the Bomb Pickle button on the HW stick as button 2, as usual...for bomb releases. My results was that the bombs rarely dropped. Then I discovered that the space button on the keyboard which fires the guns also dropped the bombs....I had the fire guns of course mapped to my HW trigger...and pressing the trigger dropped the bombs. I could not find this as a reported bug....but at least for me it is. What can I do to fix this?...so that the HW button 2 drops the bombs , not the space key or the HW trigger.

Just tested with the Hotfix mentioned above, and now it works correctly...no CTD. So it was a Nvidia issue after all.

I employed the MK-20 today in missions with the FA-18C and the F-14B. In every case as the bomb was about to explode - release its bomb-lets...DCS crashed. I have sent the crash reports in thru the crash report utility. I don't see anything posted about this problem...and this is happening prior to and after today's patch. I did upgrade my NVIDIA drivers to the latest drivers the other day....but I don't see how that would produce this problem.

In the current beta version the realistic option actually works easier for me, I am using the Hotas Warthog, assigning a TDC down to a button on the stick, and the movement of the cross hair to a hat button on my Hotas Warthog throttle. However, I agree that today's patch is not the same version as what Wags used in his recent video.

How to Kill a Ship AGM-65E My FAC was supposed to lase armor on a pier in the Persian Gulf Map. I had a sub right off the pier. As I launched my Mavs the sub moved out a bit from the pier. Seems like the laser which was aiming at the armor was now hitting the sub. I sank the sub with 4 Mavs. Although I am pleased with the outcome, I could not get the FAC to lase the sub even when it was indicated as the target group. Am I wrong that DCS is currently not able to have a AI FAC actually lase a ship object? Video is here:

Thanks for confirming the issue....I agree, hopefully it will be addressed in the near future, but yes, the mouse works except for having to take my hand off the stick to get to it...since I use my right hand for both mouse and stick.

When I assign the dispense switch to my throttle, the assignment works, however, when I actually try to use it, the dispense button moves up and once I release pressure on the assigned throttle button the dispense key moves back to its off position. If however, I use the mouse to select the dispense button, the button stays in the on position, and I can then dispense a flare or chaff. So something which is beyond my knowledge, prevents the key assignment to the throttle button from being persistent. Suspect a minor change to a lua file can fix this, but I don't know how to do it. But thankfully, the mouse click works. Master Arm is on when I try this.

MeToo Same here dcs.log-20180530-132213.zip

I have 1.5 ssaa, no msaa, but I turned on FXAA...this gives me the best result.

For me running with Nvidia 1070, I got best results with SSAA=1.5 and MSAA=OFF. Crisper image and no loss in FPS.

In the latest Beta version issued on 5/23/2018 when I set up my Mavericks for a run on 4 tanks, once I fire the first Mav, the MFD shifts back to the stores screen....I then have to recage the mav, make the IMRV active adjust fov and pickle....prior to the latest version and in 2.5.1....once I engage with the first mav the screen stays in the correct Mav uncaged view, I just adjust fov if needed and pickle. I see no one else commenting on this change....which does appear to me to be unintended and perhaps a bug. Can others confirm this behavior? I tried this with AGM65-G and AGM 65-D...not yet tried the other Mavs.

Thanks, I set it up now with an E3, plus made sure my Comms 1 Frequency matched for all aircraft...Now the AI Wingman does engage.

I am try to get my wingman, in a Harrier to attack a few KA-50s ...the command engage bandits or ground targets does not seem to get a reaction from my wingman. Is there a trick to getting AI Wingman to engage a Helicopter?

Yes, somehow they were in the old Mods folder.

After installing the current release version today, i was asked upon startup of DCS Ver. 2.5 for my Serial Numbers for the DCS SU-27 and SU-33. I skipped past these screens and all seemed normal. I checked my Module Manager and found entries specifically for the DCS SU-27 and one for DCS SU-33....when I only really own Flaiming Cliffs. I tried this a few times with the same starting message that I needed to enter serial numbers...and the system said I could have authorization for 2 days etc. I got rid of this annoyance by simply deleting the entries for the DCS SU-27 and the DCS SU-33 from the module manager screen. I then tested the system with missions for both planes and as I suspected no problems were encountered. This did not happen in the 2.5 Beta. I hope ED ensures that those of us who own flaming cliffs do not have to be bothered with this issue in the future.

On another note: at least it seems like the Auto Pilot, and Altitude Hold is working.

I have also reported in the Alpha 2 section that the Samuel Chase will cause a crash involving WeaponsBase.dll when firing at objects with its main guns...does not happen when it fires at aircraft. This does not occur when the LST fires on objects.

Thanks all...sometimes it is good to know it is not just happening to me....PS...Yes..this issue applies to the Beta only from my experience.