Jump to content

Recommended Posts

Posted

I recently had an issue in which VAICOM would work for the first mission I flew after starting DCS.  On the second mission, the configuration tool would show "None Detected" insteald of the F-18C.  This was very repeatable, so I started turning on/off everything else I run (Simshaker, Razer, DCRealistic, etc.).  I finally figured out how to reproduce the bug and how to work around it.  When a mission starts, DCRealistic autostarts.  If I don't close DCRealistic after ending a mission, it doesn't autostart on the next mission.  If I close DCRealistic after each mission, it will autostart on the next mission and VAICOM works fine.   I just have to remember to close DCR after every mission I fly.

I'm just putting this out there in case there is somebody else having the same issue.  I think I have the latest versions of VAICOM and DCRealistic.

  • Like 1

Windows 11, GPU: RTX-4090, Ram: 32gb, CPU: 12700k, Headset: Varjo Aero

Posted



I recently had an issue in which VAICOM would work for the first mission I flew after starting DCS.  On the second mission, the configuration tool would show "None Detected" insteald of the F-18C.  This was very repeatable, so I started turning on/off everything else I run (Simshaker, Razer, DCRealistic, etc.).  I finally figured out how to reproduce the bug and how to work around it.  When a mission starts, DCRealistic autostarts.  If I don't close DCRealistic after ending a mission, it doesn't autostart on the next mission.  If I close DCRealistic after each mission, it will autostart on the next mission and VAICOM works fine.   I just have to remember to close DCR after every mission I fly.
I'm just putting this out there in case there is somebody else having the same issue.  I think I have the latest versions of VAICOM and DCRealistic.


Oh! That's interesting, nice catch! Could you try to swap the order of VAICOM SC Realistic in the export.lua, just to see if that changes things?
Cheers and thanks!

Sent from my SM-A536B using Tapatalk

Posted

I am having the exact same issue with SimHaptic. If I close SimHaptic after every mission, everything works normal. If I do not, SimHaptic works fine, but Vaicom does not recognize the aircraft or commands properly.

I looked everywhere for the solution, but this one above is the only thing that works for me. Thanks for the tip

CaptStevieJ

ASUS ROG STRIX X670E-E, AMD 7800X3D, RTX 4090, 64Gb@6000, Pimax Crystal, Thrustmaster Warthog HOTAS/Throttle, MFG Crosswind Rudder, 2TB NVME boot drive, 2TB NVME DCS dedicated drive, Windows 11

Posted

Upon further investigation, it appears the Auto Start feature of SimHaptics is the culprit. If I turn that off in Settings for SimHaptics and start the SimHaptic plugin manually, everything works as normal. All aircraft are recognized and all Vaicom functions are working.

 

CaptStevieJ

ASUS ROG STRIX X670E-E, AMD 7800X3D, RTX 4090, 64Gb@6000, Pimax Crystal, Thrustmaster Warthog HOTAS/Throttle, MFG Crosswind Rudder, 2TB NVME boot drive, 2TB NVME DCS dedicated drive, Windows 11

Posted

Are Simhaptics and DCRealistic made by the same (rkApps)?  I use Simshaker instead of SimHaptics, but I do use DCR.  I will try turning off auto-start for DCRealistic and do a manual start.  

Windows 11, GPU: RTX-4090, Ram: 32gb, CPU: 12700k, Headset: Varjo Aero

Posted
Are Simhaptics and DCRealistic made by the same (rkApps)?  I use Simshaker instead of SimHaptics, but I do use DCR.  I will try turning off auto-start for DCRealistic and do a manual start.  
Yes they are.
Did you try to change the order?

Sent from my SM-A536B using Tapatalk


Posted

I did some additional testing with the autostart being set either on or off for DCR.   If autostart is OFF, VAICOM works for multiple missions without any issues.  It works regardless if DCR is not running or running by a manual start.  If autostart is ON, autostart has to be executed while starting a mission or VAICOM will not work.  I looked in the export.lua file in my Saved Games directory, and the code below shows how the file changes when selecting autostart ON/OFF in DCR.   For now I will just do manual starts and avoid this issue.

 

Autostart ON

local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[Scripts\VAICOMPRO\VAICOMPRO.export.lua]])
--[[RKAPPS_REFERENCE]]dofile("C:\\Users\\drmar\\OneDrive\\Desktop\\DCRealistic/Plugins\\rkApps_Export.lua")
--[[DCREALISTIC_AUTOSTART]]os.execute('start "" "C:\\Users\\drmar\\OneDrive\\Desktop\\DCRealistic\\DCRealistic.exe"')

Autostart OFF

local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[Scripts\VAICOMPRO\VAICOMPRO.export.lua]])
--[[RKAPPS_REFERENCE]]dofile("C:\\Users\\drmar\\OneDrive\\Desktop\\DCRealistic/Plugins\\rkApps_Export.lua")


 

 

 

Windows 11, GPU: RTX-4090, Ram: 32gb, CPU: 12700k, Headset: Varjo Aero

Posted (edited)

@MAXsenna, I am not too familiar with export.lua.  What order would I switch?
 

 

 

Edited by MAThrasher

Windows 11, GPU: RTX-4090, Ram: 32gb, CPU: 12700k, Headset: Varjo Aero

Posted

@MAThrasher Hi! Take a look at the screenshots. You might not have ".openbeta" in your path. Download Notepad++ end open the export.lua in it. Switch the order of VAICOM and DCRealistic just by switching the text lines. I have commented out what I currently don't use with -- as you can see.

 

image.png

 

image.png

 

 

 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...