CaptJackG

It seems that the terrain elevations in multiplayer are askew now. Looking at the F10 map in multiplayer now you get some bad elevation readings while in single player they are normal.

First understand the FCS. With the flaps AUTO the FCS flies a 1G aircraft. You do not trim the ac when flaps are in AUTO, just point the nose where you want to go and the FCS will take care of the pitch trim. All that changes when you go to 1/2 or FULL flaps. The FCS now flies AOA. Specifically it sets the AOA to 4.0. You can get airborne and slow to 230, LDG down and maintain 230. You'll see the E-bracket appear when the LDG is down. Your E-bracket represents your AOA indexer just on the left side of your HUD. When your VV (Velocity Vector) touched the bottom of the E-bracket you'll see the donut and bottom chevron, as you approach the middle of the E-b you'll get the donut, and if you continue towards the top of the E-b you'll see the donut and top chevron. Now back to our flight (stable at 230 LDG down), you'll notice your AOA number displayed on the left side of your HUD, start to slow while holding altitude until your VV is in the center of the E-b. You'll see your HUD AOA numbers disappear from your HUD when your VV touches the E-b. If you have your FCS page on a DDI you can see your actual AOA number and the bottom of the FCS page on the left and right at the bottom showing the actual readout from the 2 AOA sensors. Stabilize your VV in the middle of the E-b, you can see the AOA on the bottom of the FCS page showing 8.1 AOA. Your ac FCS is still flying a !G environment. Your 8.1 is the optimum AOA for trapping, best app speed and hook attitude. Now we will select flaps !/2. Don't trim the ac!!!!!!!!! Your FCS is now flying AOA, not the 1G. We now want to use the throttles to control our altitude. Get your ac stable, on altitude without retrimming. When you get stable you will see your AOA sitting at 4.0. Doesn't matter whether you go to 1/2 or FULL flap the initial FCS setting is 4.0. You'll find yourself constantly making small power adjustment to hold your altitude. You can now start to slow your ac by reducing power and bumping your trim up until you have the VV in the middle of the E-b. Stabilize the VV in the middle of the E-b. Again when your VV touches the E-b you'll lose your AOA readout on your HUD. You can look at the FCS page on the bottom and see 8.1 when the VV wing touched the middle of the E-b. You can now practice flying the proper AOA using the throttles to control your altitude and app path, let the FCS control your AOA. Hope this helps and answers some of your questions. This is all part of the training we do in VCVW 11. "Homer" DCAG VCVW 11

I had the binding problem and I found a fix. All I did was delete my joystick file from Users/my name/saved games/desopenbeta/config/input/f-14b/joystick. Then copied and dropped my f 18 joystick file into the f 14. Then went in and set up all the controls with no problem at all.

I do a lot of training for our wing and I've noticed since the latest update that the VVI on the HUD is now less that half of what it use to show. Doing a stall the VVI now shows 4200' decent when it used to show 9500' when fully stalled. The standby VVI is pegged a 6000 down.

set QNH altimeter and see what that reads. Should show field elevation. QNH is used in the US and your approach chart altitudes are base on QNH.

When I set the QNH altimeter it reads about 150 below field elevation at Nellis.

I think I may have fixed the problem by turning off Net Guard in McAfee's Firewall settings.

I'm having the same problem with McAfee

Corsair makes an excellent mouse.

After yesterdays patch my is back to normal.

Follow up, I use McAfee Firewall and if I turned that off I could have people connect. It has not been a problem with 156 or 21.

Same problem here in 1.5.7 since the update, Can connect in world & open alpha. I've made sure that the firewall and AV both have exclusions for DCS Open beta.

Thanks...will do

It was stopping on the f86_protect.exe file and I could not delete or copy over with the new file. But I ran the update later that evening and it worked with no problem at all.

McAfee

I just ran the update again and it worked this time with no errors.

I get the error message at the end when I try to update. --- Log file: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\autoupdate_log.txt === Log opened UTC 2017-07-05 21:08:28 INFO : DCS_Updater/2.6.21.16 (Windows NT 10.0.15063; Win64; en-US) INFO : cmdline: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" --apply update C:\Users\Jack\AppData\Local\Temp\DCS.openbeta\update_info.json 1.5.7.7473.311 STATUS: Initializing... INFO : basedir: C:\Program Files\Eagle Dynamics\DCS World OpenBeta INFO : dcs_variant.txt: openbeta INFO : DCS/1.5.6.5199.291 (x86_64; EN; WORLD,A-10A,FC3,MIG-15BIS,A-10C,UH-1H,MI-8MTV2,P-51D,FW-190D9,F-86F,CA,BF-109K4,MIG-21BIS,SU27-ULTIMATE_campaign,RAZBAM_M-2000C,P51D-HIGHSTAKES_campaign,F-5E,F86-MIG15-RELIC_campaign,SPITFIRE-MKIX,AJS37) INFO : branch: openbeta INFO : Got reply from http://www.digitalcombatsimulator.com STATUS: Verifying cached version info... STATUS: Verifying installed files... INFO : 0 files are changed or missing. STATUS: Preparing download... STATUS: Asking Yes/No: Found 267 files with 938683763 bytes left from an unfinished download, which are not needed for the curent operation. Do you want to DELETE them ? STATUS: Got YES when asked: Found 267 files with 938683763 bytes left from an unfinished download, which are not needed for the curent oINFO : RMDIR C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\.torrents ERROR: Can't cleanup C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\.torrents: Can't remove directory C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\.torrents: (145) The directory is not empty. STATUS: Downloading update... INFO : Using HTTP/2 INFO : MKDIR C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/aircraft/MIG-21bis/Cockpit/HUD/ INFO : MKDIR C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/aircraft/MIG-21bis/Cockpit/HUD/Indicator/ STATUS: Removing obsolete files... INFO : Removed 0 files. INFO : Kept 39106 files. STATUS: Installing new files... INFO : INSTALL Mods/aircraft/F-86/bin/f86_protect.exe STATUS: Shutting the torrents down... INFO : Kill timer set to 30 seconds... INFO : Torrents have been shutdown in time. INFO : Kill timer reset. ERROR: Can't move C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/aircraft/F-86/bin/f86_protect.exe to C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods/aircraft/F-86/bin/f86_protect.exe: (183) Cannot create a file when that file already exists. === Log closed.

These 2 are both US servers. !==RAF662.org WWII Server==! <-SteelBalls-> WW 2 (Server USA)

Why can an AI trailing thick black smoke (that completely obscures the plane) keep flying and fighting/attacking as if nothing is wrong. Apparently no mechanical problems of any kind, oil leak, coolent loss, fuel leaks have no affect on the AI aircraft. At times you just want to give up on DCS when other sims have a much better AI damage model. This comes after chasing an AI 109 in a Spit that I had damaged and it stayed in the combat area continuing to attack ground targets while being completely obscured by his smoke when I could get close enough for a shot. Please fix this.

Thanks Dolphin887 for your earlier reply to my question. Everything went exactly as you said.

I have a question. I have 3 installs of DCS. I patched in March, not being aware of the Mig 21 problems, and found I could not start the World or Beta game due to the Mig 21. I deleted the Leatherneck out of the registry and reactivated the Mig in both games with no other problems in either game and the Mig working normally. Is there anything I should do before patching tomorrow?

Please fix the AI damage model, it is a joke.

Make sure your not running filtered air to the carb.

I had the same problem and then saw on another thread that if you start the game, go into the Viggen and adjust controls. Set your axis and/or any commands and save the profile. Once I did this I can now go into control settings and modify as desired without the crash.

Warthog does with no problems at all.