We are constantly working to make your experience with Viperpits.org the best it can be!!
Hello,RWR does not currently work on DCS-BIOS or DCStoF4. DCS does not provide data for RWR or eHSI. They have gone to the single export of these 2 screens. I'll have to test to see if DCS-BIOS is in conflict but in my last tests all worked. Try placing the line for DCStoF4 before DCS-BIOS. This week I won't have time. Can anyone help?
For your YAME setup, what version are you using? I have both the "New(?)" v1.2.1, and also a 2.0.0.44 version. With BMS the only version i could get to work at all was the 2.0.0.44 version, the v1.2.1 i couldnt even get to look for BMS/launch the CPD window (the direct data input option was greyed out, with the only option being "get data from server"). Its likely something I've messed up, i could not completely follow your steps as YAME64 auto-launches BMS or it wont open the CPD for some reason.
My startup sequence was; 1. Start DCStoF42. Start YAME64 and (auto)launch BMS + CPD through YAME client.3. Minimise BMS and Start DCS, load into mission. At this point the DCStoF4 window would begin printing, but CPD would still be inactive.
Also, does DCStoF4 convert values both ways? I have a DED & arduinos programmed to DCS-BIOS, would i have to reporgramme to BMS and then use DCStoF4 to interpose the values? How do you do it with your panels?
I'm happy someone else wants to have a hybrid DCS/BMS CPD Thank you for the tips! I tried them but I couldnt get it to work on with me. DCStF4 seems to work correctly and prints out all the data it is interposing. However, YAME64/The CPD just sits blank with the text "Waiting for BMS" and doesnt work.For your YAME setup, what version are you using? I have both the "New(?)" v1.2.1, and also a 2.0.0.44 version. With BMS the only version i could get to work at all was the 2.0.0.44 version, the v1.2.1 i couldnt even get to look for BMS/launch the CPD window (the direct data input option was greyed out, with the only option being "get data from server"). Its likely something I've messed up, i could not completely follow your steps as YAME64 auto-launches BMS or it wont open the CPD for some reason.My startup sequence was; 1. Start DCStoF42. Start YAME64 and (auto)launch BMS + CPD through YAME client.3. Minimise BMS and Start DCS, load into mission. At this point the DCStoF4 window would begin printing, but CPD would still be inactive. Do you have your YAME set to pull data direct from BMS or set to a local server at 127.0.0.1? If the server, what port do you use?Also, does DCStoF4 convert values both ways? I have a DED & arduinos programmed to DCS-BIOS, would i have to reporgramme to BMS and then use DCStoF4 to interpose the values? How do you do it with your panels?Thank you for all your help, I greatly appreciate it
(My apologies i havent worked out how to use the quote feature yet).I found the same with YAME, its a nightmare to setup, but I have got the CPD and the ATD working perfectly with BMS just for testing. Have been flying around in BMS for the last couple of days with it on my workstation and its been working great (I had to use version 2.0.0.44, version 1.2.1 did not work at all). I have my LCD turning up soon for my CPD so will test it out properly then.As for DCS, still have had no luck with getting it to work with DCS/DCStoF4, however I will try what questerymj mentioned and get rid of all the other exports and just put in the DCStoF4 and see if that fixes it (thank you for suggesting that ). I also have Tacview and DCS-BIOS so it might be an issue caused by one of them as suggested...Overall, pretty happy with the CPD/ATD in BMS. Thank you both for your help! I will update as to whether I got DCS working
I've just tried it with version V0.10.0 and no problems.The DCS-BIOS WEB page displays the DCS F-16 instrument values in real time. And DCStoF4 too.The .lua export file looks like this: -- Data export script for DCS, version 1.2.-- Copyright (C) 2006-2014, Eagle Dynamics.-- See http://www.lua.org for Lua script system info -- We recommend to use the LuaSocket addon (http://www.tecgraf.puc-rio.br/luasocket) -- to use standard network protocols in Lua scripts.-- LuaSocket 2.0 files (*.dll and *.lua) are supplied in the Scripts/LuaSocket folder-- and in the installation folder of the DCS. -- Expand the functionality of following functions for your external application needs.-- Look into Saved Games\DCS\Logs\dcs.log for this script errors, please.--dofile(lfs.writedir()..[[scripts\WitchcraftExport.lua]])-- DCStoF4local xflight=require('lfs');dofile(xflight.writedir()..[[Scripts\DCS-XFLIGHT\Util-Dial.lua]])-- WinWinglocal wwtlfs=require('lfs');dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua')-- TacViewlocal Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua')-- Helios--dofile(lfs.writedir()..[[Scripts\Helios\HeliosExport16.lua]])--dofile(lfs.writedir() .. [[Scripts\DCS-BIOS\BIOS.lua]])--[[DCS-BIOS Automatic Setup]]BIOS = {}; BIOS.LuaScriptDir = [[C:\Program Files\DCS-BIOS\dcs-lua\]]; BIOS.PluginDir = [[C:\Users\Sharknoir\AppData\Roaming/DCS-BIOS/Plugins\]]; if lfs.attributes(BIOS.LuaScriptDir..[[BIOS.lua]]) ~= nil then dofile(BIOS.LuaScriptDir..[[BIOS.lua]]) end