Silversmith

Same here 2.5.6 will not load with Voiceattack & Vaicom Pro. Only way out is to REPAIR DCS and allow it to delete \Sounds\Speech\common.lua and \Sounds\Speech\speech.lua. Seems ED have Encrypted all the SOUND files and amended the folder structure, which means Voiceattack/ vaicom is incompatible with 2.5.6

DCS 2.5.6 fails to load with VoiceAttack and Vaicom pro running, I assume this is also related to the SOUND encryption issue. Only way to restart DCS is to REPAIR then allow repair to deletd files Sounds\Speech\common.lua and Sounds\Speech\speech.lua

Updated to 2.5.6, DCS hung on Load with bar at 10%. Did a REPAIR and it loads fine . BUT if I load VOICEATTACK running VAICOM Pro profile DCS reverts to not loading, getting stuck with bar on 10%. Again only way to sort it is to REPAIR again, then run without Voiceattack running. The R EPAIR says it finds 2 files (which I assume Voiceattack is creating or modifying), these have to be deleted to get DCS to load Sounds/Speech/common.lua Sounds/Speech/speech.lua the log says (I'm running in VR with Oculus Rift) 2020-02-15 00:27:45.216 INFO VISUALIZER: LAUNCH IN VR : OculusRift : Oculus Rift CV1 2020-02-15 00:27:45.226 INFO GRAPHICSVISTA: renderer: 'dx11backend.dll' 2020-02-15 00:27:45.501 INFO DX11BACKEND: DX11Renderer initialization (w:880 h:1050 fullscrn:0 vsync:0 adapter:0 monitor:0 shaderErrors:1) 2020-02-15 00:27:45.674 INFO DX11BACKEND: Driver Concurrent Creates - 1 2020-02-15 00:27:45.674 INFO DX11BACKEND: Driver Command Lists - 0 2020-02-15 00:27:45.701 INFO DX11BACKEND: NVIDIA API init OK 2020-02-15 00:27:45.701 INFO DX11BACKEND: NVIDIA Display Driver Version 44219.r440_00 2020-02-15 00:27:45.701 INFO DX11BACKEND: GPU count:1 2020-02-15 00:27:45.781 INFO DX11BACKEND: commonPool: 68-128, cbPool: 4-14, samplerPool: 5-16 2020-02-15 00:27:45.793 INFO DX11BACKEND: DX11ShaderBinaries::loadCache Bazar/shaders/fxo/fxo.zip 2020-02-15 00:27:47.475 INFO DX11BACKEND: DX11ShaderBinaries::loadCache done. Loaded 1007/1007. 2020-02-15 00:27:47.487 INFO DX11BACKEND: DX11ShaderBinaries::loadCache E:\Users\andre_000\Saved Games\DCS.openbeta\fxo 2020-02-15 00:27:47.575 INFO DX11BACKEND: DX11ShaderBinaries::loadCache done. Loaded 85/85. 2020-02-15 00:27:47.684 INFO VISUALIZER: SceneManager initialization 2020-02-15 00:27:48.185 INFO VISUALIZER: cascade shadows init (preset:'default' quality:4 layers:4 size:4096) 2020-02-15 00:27:48.256 INFO SOUND: Opening audio device "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{04304962-f7f5-4f03-8368-2fc48f7a1b0f}#{e6327cad-dcec-4949-ae8a-991e976a79d2}" 2020-02-15 00:27:48.256 ERROR SOUND: Failed to open device "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{04304962-f7f5-4f03-8368-2fc48f7a1b0f}#{e6327cad-dcec-4949-ae8a-991e976a79d2}": 0x80070057 2020-02-15 00:27:48.256 INFO SOUND: Opening default audio device. 2020-02-15 00:27:48.259 INFO SOUND: Using 2 channels at 48000 Hz 2020-02-15 00:27:48.259 INFO SOUND: Channel layout: Headphones/Stereo 2020-02-15 00:27:48.289 INFO SOUND: Opening audio device "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{04304962-f7f5-4f03-8368-2fc48f7a1b0f}#{e6327cad-dcec-4949-ae8a-991e976a79d2}" 2020-02-15 00:27:48.289 ERROR SOUND: Failed to open device "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{04304962-f7f5-4f03-8368-2fc48f7a1b0f}#{e6327cad-dcec-4949-ae8a-991e976a79d2}": 0x80070057 2020-02-15 00:27:48.289 INFO SOUND: Opening default audio device. 2020-02-15 00:27:48.292 INFO SOUND: Using 2 channels at 48000 Hz 2020-02-15 00:27:48.292 INFO SOUND: Channel layout: Headphones/Stereo 2020-02-15 00:27:48.365 INFO DCS: gDescription: "NVIDIA GeForce GTX 1080 Ti" gVendorId: 4318 gDeviceId: 6918 gMemory: 11127 MB 2020-02-15 00:27:48.386 ERROR EDOBJECTS: Destruction shape not found AVIASHTAB_CRASH 2020-02-15 00:27:48.392 ERROR EDOBJECTS: Object HB_F14_EXT_PHX_ALU with id=312 already declared in table MissileTable 2020-02-15 00:27:50.485 INFO DX11BACKEND: DX11ShaderBinaries::loadCache ./Mods/aircraft/F14/fxo 2020-02-15 00:27:50.490 INFO DX11BACKEND: DX11ShaderBinaries::loadCache done. Loaded 0/0. 2020-02-15 00:27:50.652 INFO EDCORE: (dDispatcher)enterToState_:1 2020-02-15 00:27:52.199 ALERT Dispatcher: Error starting Game GUI: [string "./Scripts/UI/gameMessages.lua"]:30: module 'lentaMessages' not found: no field package.preload['lentaMessages'] no file './dxgui/bind/lentaMessages.lua' no file './dxgui/loader/lentaMessages.lua' no file './dxgui/skins/skinME/lentaMessages.lua' no file './dxgui/skins/common/lentaMessages.lua' no file './MissionEditor/lentaMessages.lua' no file './MissionEditor/modules/lentaMessages.lua' no file './Scripts/lentaMessages.lua' no file './LuaSocket/lentaMessages.lua' no file './Scripts/UI/lentaMessages.lua' no file './Scripts/UI/Multiplayer/lentaMessages.lua' no file './Scripts/DemoScenes/lentaMessages.lua' no file './MAC_Gui/lentaMessages.lua' no file './dxgui/skins/skinME/lentaMessages.lua' no file './dxgui/skins/common/lentaMessages.lua' no file './Scripts/lentaMessages.lua' no file './Scripts/Common/lentaMessages.lua' no file './Scripts/UI/lentaMessages.lua' no file './Scripts/UI/F10View/lentaMessages.lua' no file './dxgui/bind/lentaMessages.lua' no file './dxgui/loader/lentaMessages.lua' no file './dxgui/skins/skinME/lentaMessages.lua' no file './dxgui/skins/common/lentaMessages.lua' no file './MissionEditor/modules/lentaMessages.lua' no file './Mods/tech/CombinedArms/UI/lentaMessages.lua' no file './Scripts/lentaMessages.lua' no file './Scripts/Common/lentaMessages.lua' no file './Scripts/UI/lentaMessages.lua' no file './Scripts/UI/F10View/lentaMessages.lua' no file './dxgui/bind/lentaMessages.lua' no file './dxgui/loader/lentaMessages.lua' no file './dxgui/skins/skinME/lentaMessages.lua' no file './dxgui/skins/common/lentaMessages.lua' no file './MissionEditor/modules/lentaMessages.lua' no file './Mods/tech/CombinedArms/UI/lentaMessages.lua' no file './Scripts/lentaMessages.lua' no file './Scripts/Common/lentaMessages.lua' no file './Scripts/UI/lentaMessages.lua' no file './Scripts/UI/F10View/lentaMessages.lua' no file './dxgui/bind/lentaMessages.lua' no file './dxgui/loader/lentaMessages.lua' no file './dxgui/skins/skinME/lentaMessages.lua' no file './dxgui/skins/common/lentaMessages.lua' no file './MissionEditor/modules/lentaMessages.lua' no file './Mods/tech/CombinedArms/UI/lentaMessages.lua' no file './Scripts/lentaMessages.lua' no file './Scripts/Common/lentaMessages.lua' no file './Scripts/UI/lentaMessages.lua' no file './Scripts/UI/F10View/lentaMessages.lua' no file './dxgui/bind/lentaMessages.lua' no file './dxgui/loader/lentaMessages.lua' no file './dxgui/skins/skinME/lentaMessages.lua' no file './dxgui/skins/common/lentaMessages.lua' no file './MissionEditor/modules/lentaMessages.lua' no file './Mods/tech/CombinedArms/UI/lentaMessages.lua' no file './Scripts/lentaMessages.lua' no file './Scripts/Common/lentaMessages.lua' no file './Scripts/UI/lentaMessages.lua' no file './Scripts/UI/F10View/lentaMessages.lua' no file './dxgui/bind/lentaMessages.lua' no file './dxgui/loader/lentaMessages.lua' no file './dxgui/skins/skinME/lentaMessages.lua' no file './dxgui/skins/common/lentaMessages.lua' no file './MissionEditor/modules/lentaMessages.lua' no file './Mods/tech/CombinedArms/UI/lentaMessages.lua' no file './Scripts/lentaMessages.lua' no file './Scripts/Common/lentaMessages.lua' no file './Scripts/UI/lentaMessages.lua' no file './Scripts/UI/F10View/lentaMessages.lua' no file './dxgui/bind/lentaMessages.lua' no file './dxgui/loader/lentaMessages.lua' no file './dxgui/skins/skinME/lentaMessages.lua' no file './dxgui/skins/common/lentaMessages.lua' no file './MissionEditor/modules/lentaMessages.lua' no file './Mods/tech/CombinedArms/UI/lentaMessages.lua'lentaMessages no file '.\lua-lentaMessages.dll' no file '.\lentaMessages.dll' no file 'E:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\lua-lentaMessages.dll' no file 'E:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\lentaMessages.dll' 2020-02-15 00:27:52.199 INFO EDCORE: (dDispatcher)enterToState_:2

https://www.digitalcombatsimulator.c...a/2.5.6.43453/

Its like any other muscle memory, takes time to learn to use the Keyboard without seeing it. I also use a Razer Naga Trinity mouse, which gives me MANY soft mapped buttons on the mouse (configurable by game). https://www.pcworld.com/article/3302041/razer-naga-trinity-review.html I map the 12x Function keys to the side keypad, and the spacebar to the Mouse 3 (scroll wheel press button. Zoom in/out to the scroll wheel. Much easier to muscle memory than the keyboard (the cat is usually sat on the keyboard anyway).

Hi Mr Hollywood, might you be able to offer advice on this problem I have. When I use Vaicom Pro it keeps 'recognising' words that are not in the Vaicom editor list. If I go into keyword training from the editor screen, then open the dictionary (e.g. Edit or add a word option) I see hundreds of words/phrases that are not Vaicom kwywords. However the Vaicom manual says the dictionary when entering Training mode should be loaded with only the list of Vaicom keywords. Do I have to do something special to 'switch' Windows speech recognition to use specifically the Vaicom Pro dictionary? Or have I totally misunderstood? Probably the latter, but any advice appreciated.

Old dogs??? Nummut nibblets. I'm 64 !!

Paypal for DCS modules via the DCS store working fine for me.

Puzzled... A10A is in the game and flyable. Its one of the FC3 modules purchasable either as part of the FC3 bundle, or as standalone in the DCS store

Working fine for me. Need to fly pretty accurately to the Waypoint for it to register you've overflown it and auto switch to the next WP.

Repeated the same mission on the STABLE version and it works correctly. So seems to be an issue related to the latest Open Beta release?

Thats interesting.. just tried one of my old missions which has always worked fine.... Now it DOES NOT LOAD THE WEAPONS CONFIG wht first time I do a LOAD ALL from the DTS LOAD page. (Open Beta latest release). However if I REPEAT the DTS Load (have to reconfig the MFD buttons to give access to the LOAD MFD page again) the 2nd time I LOAD ALL it works correctly.

If its a cold start remember you have , as part of the startup' to LOAD the mission details using the LOAD MFD page (Use the load ALL mfd button on the LOAD mfd page.. that will load everything including weapons config and Flight plan from the mission file ). You also have to do this is you land and rearm/refuel during a mission. If the LOAD MFD page is not assigned to a menu button you can reconfigure the buttons to show it. It works for me every time. I see you imply that you did indeed use the LOAD page, if so I'm puzzled why it isn't working.

If the antenna elevation increase/decrease are bound to KEYS rather than an axis since the latest update one short press slews the radar a huge amount making it virtually impossible to use.

Practice really is the answer, and not thinking too much. I couldn't get this right for WEEKS of trying. The one day it suddenly just 'happened' and now I land without any issues every time without thinking about it. Little consolation at the moment I know , but you WILL get there eventually. Constantly moving throttle IS the key. Initially just constantly mess about with it on approach to see the effect. Eventually your muscle memory will take over for you .

I use the in game bindings, not a profile for my Warthog HOTAS. Try looking at the Grim Reapers tutorial on Key bindings. I used to have all sorts of problems with bindings changing after updates/release of new modules. And I certainly could NOT copy my binding files between the OB version and the release version, simply did not work. BUT when I adopted the GR approach of 1) Set Bindings as desired for the module you want to fly 2) For each 'device' Keyboard , Joystick, Throttle , Rudder and Mouse (if you bind mouse buttons, I don't) save each device's profile to a distinct named file ( click on a binding in the relevant column, then use save profile). e.g. For A10C I save files A10CKBD.diff.lua , A10CJST.diff.lua , A10CTHR.diff.lua into my Users/username/Saved Games/DCS folder). I do this for every module I have so I end up with lots of xxxx.diff.lua files BUT ITS WORTH IT. Since then I have had NO ISSUES whatsoever with key bindings changing, AND I can copy the files between DCS and DCS Open Beta and they work. The sim keeps track of which files to load when you fly each module. OH be careful if making changes whilst in a mission .. it by defaults saves in the Users/username/Saved Games/DCS/Missions folder, it seems to work more reliably to save in the higher level folder Users/username/Saved Games/DCS (or DCS.Openbeta if using the open beta installation)

I suspect this is a matter of personal preference appropriate to the style of missile avoidance manoeuvre you fly. Pgm 1 2 x chaff, 0 Flares , Repeat 3 Interval 2sec Pgm 5 0 x chaff, 4 x Flares Repeat 2 Interval 2 secs works for me. I guess a mixed chaff and flare pgm might be useful if you don't know what is inbound, but you should always KNOW when locked by a Radar guided missile. Maybe a mixed program if engaged by a Flanker firing a double RADAR & IR pair, but I've never bothered. Of course neither Chaff or Flares help with an Optically guided missile, flying good avoidance manoeuvre is the key (applies to all missile types).

Not convinced of that. The 'same' missile fired from a different plane can behave very differently. For the Aim 120/Hornet pairing of course it may not actually be the missile in this case, possibly its the radar that is the problem. I would point out one very obvious 'same missile different performamce' effect (that takes radar out of the mix). Fire an Aim 9m sidewinder without a radar lock from a hornet at a SU25 target and it will probably take at least 2 hits to kill. Fire the same missile from a F14B and 1 hit totally evaporates the same target. Even more obvious when the target is a larger aircraft such as a fencer when the Aim 9m from the F14 still kills with one hit every time.

Using distinct PP1 and PP2 does indeed work BUT you have to watch out for the somewhat bizarre release sequence when you pickle. The sequence is not one from each station for 6 stores 8,2,7,3, then the 2nd store for 8 and 2. I forget the exact sequence but its something odd like 8,2,7,2,8,3 . So you can't just pickle 4 times, then switch to PP2 , you have to keep an eye on which station is dropping next and use a manual STEP to ensure all the 4 PP1 stores have dropped before switching to PP2 for the 2nd store on 8 and 2. May work better with 8 stores loaded?

Setting ELEV to the burst height did what you'd expect. The weapon appears to add the ELEV to the Burst height, so the burst was way too high. That makes perfect sense. I also tried setting Elev correctly to the target elevation then tried various burst height settings. At 900 ft Zero hits on a Shilka At 500 ft 1 hit on the Shilka , but not destroyed. At 400 ft 3 hits on the Shilka, but not destroyed At 300 ft 4 hits on the Shilka , but not destroyed.

This is interesting. You must be doing something different (i'd love to know what). I get the same results as others in this thread, JSOW A is almost totally ineffective. I did see a video of someone using the DCS JSOW A and I noticed he didn't set the HEIGHT on the TERM settings at all, so that would be defaulting to 1500ft (?) but instead he set the Elevation (which should be the target elevation) to his desired burst height of 900 ft. He destroyed a complete SA10 installation with one weapon. I will give that a try. Doesn't make any sense, but you never know ! By the way .. what are you setting EFUZE to, Instant or Vtt?

ah, just seen Kasius's post , and Wags confirmation. Looks like the procedure is different now that it was previously for JDAMs. I'll try again

That's what I did. But dropping the first JSOW blanked the PP target data for all the others. I had set up different PPs for each station, and did try to switch PP between drops as usual. BUt the PPs were blanked after the first drop. Stepping through stations and / or PPs had no effect , all blanked after first weapon dropped.

I get the identical thing if I try multiple JSOW As. Set up multiple PP targets. Good alignment First drops fine. All the rest of the PP targets are instantly blanked. Haven't tried a JDAM since the latest update, but pre-update JDAMS worked fine with multiple PP targets. Happens without switching to AA mode then back, just dropping the first JSOW blanks the PP targets for the rest. Worth a bug report, I'd do it but as I fly VR track files simply don't work, so I cant provide the evidence. (I wish they could fix the VR track file problem too!)

You are of course correct , no such animal as a type 49 !!:music_whistling: