Jump to content

hornblower793

ED Closed Beta Testers Team
  • Posts

    1628
  • Joined

  • Last visited

Everything posted by hornblower793

  1. If this is with VCP also running have you tried the REL HOT option in VCP? Sent from my SM-T835 using Tapatalk
  2. I don't think so, as the wheel is just a visual way to get the Vaicom options so Hollywood will need to change both Sent from my SM-T835 using Tapatalk
  3. You either need to keep the pause or add the phrase you want to use as an alias Sent from my SM-T835 using Tapatalk
  4. Or just double-click any single row in the column saying AI Communications Sent from my SM-T835 using Tapatalk
  5. It normally means something has got slightly corrupted. If shutting everything down and restarting doesn't work try: 1. Close DCS and VA, copy Export.lua in your saved games > scripts folder and then delete export.lua. Restart to see if it works. Copy back any other lines in your saved export.lua (put them back in the same order). If still not fixed then 2. Use the set custom path option in Vaicom config. Point this to your main DCS folder, tick fix reg, set the sliders the right way and then restart VA - go back into config and uncheck set custom path. If neither work, post your Vaicom log file here (with Vaicom debug turned on) and we will have a look. Sent from my SM-T835 using Tapatalk
  6. If you have installed the 64-bit version of VoiceAttack (VA) and have used the Vaicom installer you will need to add an additional step. 64-bit is a recent development for VA and the Vaicom installer still assumes VA is installed in the Program Files (x86) folder as a 32-bit program. You will therefore need to copy the files from Voiceattack\apps\vaicompro in the x86 folder to Program Files\Voiceattack\apps\vaicompro Sent from my SM-T835 using Tapatalk
  7. If it is not showing the module that normally means it is looking in the wrong place for DCS. Please could start VoiceAttack, open Vaicom config, turn on Debug on the Config tab, restart VA and then post the Vaicom logfile here (this will be found in the <voiceattack install dir>\apps\VAICOMPRO\logs folder. Please could you also post a screenshot of the Vaicom Config and MP tabs Like Max I am just a user, but between us and others on the forum we can normally sort issues
  8. The information above is not quite correct - you do not need the 'Auto browse' feature for it to work. Auto browse allows you to switch tabs without just by saying the name of the tab, but also means that if you are elsewhere in the Kneeboard (e.g. on an airfield layout) it will switch back to the Vaicom tabs whenever a message comes in. Without auto browse on you have to say <tab>.....page (e.g. Texaco....page, air traffic....page) to bring the relevant tab up. You can use callsigns for the relevant tab - REF works with Chief as a page name (REF = Refueling)
  9. Dave, It sounds like the configuration isn't right and the other issues are following on from that. Just checking that you have set up Voiceattack and Vaicom following the instructions in the Vaicom manual, and that you have correctly pointed Vaicom to your DCS install (standalone / steam and OB / stable) in the Vaicom config. Please could you post a screenshot of the (voice disabled) message. Are you on Discord? If so, I am happy to jump on a voice call at the weekend to work through this.
  10. Is it CTD or does VA just close leaving you in DCS with no voice commands? If the second one then try using the Vaicom app to start VA - if VA then closes during flight this will automatically restart it Sent from my SM-T835 using Tapatalk
  11. Yes to slider - it means that they are totally off when the pedals are not pressed and fully on when you have pushed them down Sent from my SM-T835 using Tapatalk
  12. Like@Maxsenna says, we have all been there.... Sent from my SM-T835 using Tapatalk
  13. You have the keyboard disabled in VA (the middle icon on the right hand side of the screen) click on it to remove the red circle Sent from my SM-T835 using Tapatalk
  14. It is a long standing issue with DCS replays - the don't actually record the flight but control inputs and therefore take on a life of their own
  15. Interesting - if you are OK with it, it might be worth posting the piggy-backed profile here and we could then see if we can replicate or spot an issue
  16. Do you know what you were doing at the time?
  17. Will try my Yak at some point Sent from my SM-T835 using Tapatalk
  18. The install path will be because you have the 64-bit version of VoiceAttack and not the 32-bit one (64-bit is new)
  19. The options.lua is in your saved games > DCS (or DCS.openbeta) > Config folder. Just rename it and you should be OK (you will need to redo your DCS options)
  20. Should do Sent from my SM-T835 using Tapatalk
  21. I took some of the OC off my CPU - I am GPU limited anyway and it removed some very rare crash issues The 222559 log show you getting the DXGI_ERROR_DEVICE_REMOVED issue, which I think is related to OC or undervolting - if you search the forums for it there have been several threads recently - these might give you more information 2021-07-01 22:25:58.483 ERROR DX11BACKEND: DX device removed. Reason: 0x887A0006 2021-07-01 22:25:58.508 WARNING LOG: 3 duplicate message(s) skipped. 2021-07-01 22:25:58.508 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-07-01 22:25:58.508 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-07-01 22:25:58.508 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-07-01 22:25:58.508 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-07-01 22:25:58.513 ERROR DX11BACKEND: DX device removed. Reason: 0x887A0006 2021-07-01 22:25:58.624 WARNING LOG: 17 duplicate message(s) skipped. 2021-07-01 22:25:58.624 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-07-01 22:25:58.624 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-07-01 22:25:58.624 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-07-01 22:25:58.624 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-07-01 22:25:58.624 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-07-01 22:25:58.624 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-07-01 22:25:58.624 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-07-01 22:25:58.624 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-07-01 22:25:58.629 ERROR DX11BACKEND: DX device removed. Reason: 0x887A0006 2021-07-01 22:25:58.724 WARNING LOG: 15 duplicate message(s) skipped. 2021-07-01 22:25:58.724 ERROR DX11BACKEND: failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-07-01 22:25:58.729 INFO EDCORE: try to write dump information 2021-07-01 22:25:58.733 INFO EDCORE: # -------------- 20210701-222559 -------------- 2021-07-01 22:25:58.734 INFO EDCORE: DCS/2.7.2.8165 (x86_64; Windows NT 10.0.19041) 2021-07-01 22:25:58.737 INFO EDCORE: C:\Program Files\Eagle Dynamics\DCS World\bin\dxgi.dll
  22. I am running Bitdefender quite happily so I think it must be configuration
  23. Try Crystal Palace for AOCS, Tanker / Texaco / Shell etc for AAR and Chief for REF
  24. Do you have DiCE installed?
  25. You shouldn't do - they are stored in the Saved Games > Config folder - I periodically take a copy of this so that I can restore it in the case of any issues
×
×
  • Create New...